From: Adrian Bunk <bunk@stusta.de>
To: openembedded-core@lists.openembedded.org
Subject: [warrior][PATCH 2/3] gnupg: upgrade 2.2.15 -> 2.2.16
Date: Sun, 15 Mar 2020 20:13:07 +0200 [thread overview]
Message-ID: <20200315181308.12792-2-bunk@stusta.de> (raw)
In-Reply-To: <20200315181308.12792-1-bunk@stusta.de>
From: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
(From OE-Core rev: 825be9d66ae9f503f1dd2dce0fac530554057613)
Signed-off-by: Zang Ruochen <zangrc.fnst@cn.fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
---
.../gnupg/{gnupg_2.2.15.bb => gnupg_2.2.16.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/gnupg/{gnupg_2.2.15.bb => gnupg_2.2.16.bb} (93%)
diff --git a/meta/recipes-support/gnupg/gnupg_2.2.15.bb b/meta/recipes-support/gnupg/gnupg_2.2.16.bb
similarity index 93%
rename from meta/recipes-support/gnupg/gnupg_2.2.15.bb
rename to meta/recipes-support/gnupg/gnupg_2.2.16.bb
index 06a257333d..cb7c6c5c62 100644
--- a/meta/recipes-support/gnupg/gnupg_2.2.15.bb
+++ b/meta/recipes-support/gnupg/gnupg_2.2.16.bb
@@ -20,8 +20,8 @@ SRC_URI_append_class-native = " file://0001-configure.ac-use-a-custom-value-for-
file://relocate.patch"
-SRC_URI[md5sum] = "3ab87e377aa0af2f463649515bf66508"
-SRC_URI[sha256sum] = "cb8ce298d7b36558ffc48aec961b14c830ff1783eef7a623411188b5e0f5d454"
+SRC_URI[md5sum] = "d90e186df1c06845880ea58a318f070b"
+SRC_URI[sha256sum] = "6cbe8d454bf5dc204621eed3016d721b66298fa95363395bb8eeceb1d2fd14cb"
EXTRA_OECONF = "--disable-ldap \
--disable-ccid-driver \
--
2.17.1
next prev parent reply other threads:[~2020-03-15 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 18:13 [warrior][PATCH 1/3] gnupg: update to 2.2.15 Adrian Bunk
2020-03-15 18:13 ` Adrian Bunk [this message]
2020-03-15 18:13 ` [warrior][PATCH 3/3] gnupg: upgrade 2.2.16 -> 2.2.17 Adrian Bunk
2020-03-15 18:56 ` akuster808
2020-03-15 19:07 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200315181308.12792-2-bunk@stusta.de \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.