From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Subject: [PATCH 3/4] gnupg: upgrade from 2.1.18 to 2.1.20
Date: Mon, 8 May 2017 22:47:25 +0800 [thread overview]
Message-ID: <1494254846-9382-4-git-send-email-sgw@linux.intel.com> (raw)
In-Reply-To: <1494254846-9382-1-git-send-email-sgw@linux.intel.com>
From: Choong YinThong <yin.thong.choong@intel.com>
Signed-off-by: Choong YinThong <yin.thong.choong@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
meta/recipes-support/gnupg/{gnupg_2.1.18.bb => gnupg_2.1.20.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/gnupg/{gnupg_2.1.18.bb => gnupg_2.1.20.bb} (90%)
diff --git a/meta/recipes-support/gnupg/gnupg_2.1.18.bb b/meta/recipes-support/gnupg/gnupg_2.1.20.bb
similarity index 90%
rename from meta/recipes-support/gnupg/gnupg_2.1.18.bb
rename to meta/recipes-support/gnupg/gnupg_2.1.20.bb
index a0611aa..bbda283 100644
--- a/meta/recipes-support/gnupg/gnupg_2.1.18.bb
+++ b/meta/recipes-support/gnupg/gnupg_2.1.20.bb
@@ -16,8 +16,8 @@ SRC_URI = "${GNUPG_MIRROR}/${BPN}/${BPN}-${PV}.tar.bz2 \
file://autogen.sh-fix-find-version-for-beta-checking.patch \
"
-SRC_URI[md5sum] = "c67f908b0b35c7ebc62144f362757e1e"
-SRC_URI[sha256sum] = "d04c6fab7e5562ce4b915b22020e34d4c1a256847690cf149842264fc7cef994"
+SRC_URI[md5sum] = "f6bc7e0b82893dfafe09109d86ff6e9b"
+SRC_URI[sha256sum] = "24cf9a69369be64a9f6f8cc11a1be33ab7780ad77a6a1b93719438f49f69960d"
EXTRA_OECONF = "--disable-ldap \
--disable-ccid-driver \
--
2.7.4
next prev parent reply other threads:[~2017-05-08 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 14:47 [PATCH 0/4] Packages updates Saul Wold
2017-05-08 14:47 ` [PATCH 1/4] man-pages: upgrade from 4.09 to 4.10 Saul Wold
2017-05-08 14:47 ` [PATCH 2/4] nspr: upgrade recipe to version 4.14 Saul Wold
2017-05-08 14:47 ` Saul Wold [this message]
2017-05-08 14:47 ` [PATCH 4/4] mc: Upgrade from 4.8.18 to 4.8.19 Saul Wold
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=1494254846-9382-4-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox