From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gnupg: Update to upstream version 2.0.19
Date: Fri, 18 May 2012 08:45:02 +0300 [thread overview]
Message-ID: <4FB5E1DE.7080309@linux.intel.com> (raw)
In-Reply-To: <1337176070-16359-1-git-send-email-laurentiu.palcu@intel.com>
On 05/16/2012 04:47 PM, Laurentiu Palcu wrote:
> Signed-off-by: Laurentiu Palcu<laurentiu.palcu@intel.com>
> ---
> .../gnupg/{gnupg_2.0.18.bb => gnupg_2.0.19.bb} | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
> rename meta/recipes-support/gnupg/{gnupg_2.0.18.bb => gnupg_2.0.19.bb} (81%)
>
> diff --git a/meta/recipes-support/gnupg/gnupg_2.0.18.bb b/meta/recipes-support/gnupg/gnupg_2.0.19.bb
> similarity index 81%
> rename from meta/recipes-support/gnupg/gnupg_2.0.18.bb
> rename to meta/recipes-support/gnupg/gnupg_2.0.19.bb
> index 3085494..1d19fe3 100644
> --- a/meta/recipes-support/gnupg/gnupg_2.0.18.bb
> +++ b/meta/recipes-support/gnupg/gnupg_2.0.19.bb
> @@ -5,14 +5,14 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949 \
> file://COPYING.LIB;md5=6a6a8e020838b23406c81b19c1d46df6"
>
> DEPENDS = "pth libassuan libksba zlib bzip2 readline libgcrypt"
> -PR = "r1"
> +PR = "r0"
>
> inherit autotools gettext
>
> SRC_URI = "ftp://ftp.gnupg.org/gcrypt/${BPN}/${BPN}-${PV}.tar.bz2"
>
> -SRC_URI[md5sum] = "2f37e0722666a0fedbe4d9f9227ac4d7"
> -SRC_URI[sha256sum] = "48aedd762ca443fb952a9e859efe3c66706d7c2c9c77c32dbdbac4fe962dae5b"
> +SRC_URI[md5sum] = "6a8589381ca1b0c1a921e9955f42b016"
> +SRC_URI[sha256sum] = "efa23a8a925adb51c7d3b708c25b6d000300f5ce37de9bdec6453be7b419c622"
>
> EXTRA_OECONF = "--disable-ldap \
> --with-zlib=${STAGING_LIBDIR}/.. \
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-05-18 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 13:47 [PATCH] gnupg: Update to upstream version 2.0.19 Laurentiu Palcu
2012-05-18 5:45 ` Saul Wold [this message]
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=4FB5E1DE.7080309@linux.intel.com \
--to=sgw@linux.intel.com \
--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.