Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gpgme: updated to 1.3.2
Date: Mon, 25 Jun 2012 09:04:52 -0700	[thread overview]
Message-ID: <4FE88C24.9090302@linux.intel.com> (raw)
In-Reply-To: <1340368073-7078-1-git-send-email-valentin.popa@intel.com>

On 06/22/2012 05:27 AM, Valentin Popa wrote:
> Licence update: the same licence and new copyright years added
>
> Signed-off-by: Valentin Popa<valentin.popa@intel.com>
> ---
>   .../disable_gpgconf_check.patch                    |    0
>   .../gpgme/{gpgme_1.3.1.bb =>  gpgme_1.3.2.bb}       |    8 ++++----
>   2 files changed, 4 insertions(+), 4 deletions(-)
>   rename meta/recipes-support/gpgme/{gpgme-1.3.1 =>  gpgme-1.3.2}/disable_gpgconf_check.patch (100%)
>   rename meta/recipes-support/gpgme/{gpgme_1.3.1.bb =>  gpgme_1.3.2.bb} (83%)
>
> diff --git a/meta/recipes-support/gpgme/gpgme-1.3.1/disable_gpgconf_check.patch b/meta/recipes-support/gpgme/gpgme-1.3.2/disable_gpgconf_check.patch
> similarity index 100%
> rename from meta/recipes-support/gpgme/gpgme-1.3.1/disable_gpgconf_check.patch
> rename to meta/recipes-support/gpgme/gpgme-1.3.2/disable_gpgconf_check.patch
> diff --git a/meta/recipes-support/gpgme/gpgme_1.3.1.bb b/meta/recipes-support/gpgme/gpgme_1.3.2.bb
> similarity index 83%
> rename from meta/recipes-support/gpgme/gpgme_1.3.1.bb
> rename to meta/recipes-support/gpgme/gpgme_1.3.2.bb
> index 949a24c..b3c1d46 100644
> --- a/meta/recipes-support/gpgme/gpgme_1.3.1.bb
> +++ b/meta/recipes-support/gpgme/gpgme_1.3.2.bb
> @@ -5,19 +5,19 @@ BUGTRACKER = "https://bugs.g10code.com/gnupg/index"
>   LICENSE = "GPLv2+&  LGPLv2.1+"
>   LIC_FILES_CHKSUM = "file://COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>                       file://COPYING.LESSER;md5=bbb461211a33b134d42ed5ee802b37ff \
> -                    file://src/gpgme.h.in;endline=23;md5=942b47052c0674c6a3b9b9e6127628a4 \
> +                    file://src/gpgme.h.in;endline=23;md5=00846fee29ec2a6f5c808bfe7fc24e65 \
>                       file://src/engine.h;endline=22;md5=e96acfaab1cff82dd8fbefddd2f5c436"
>
>   SRC_URI = "ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-${PV}.tar.bz2 \
>              file://disable_gpgconf_check.patch"
>
> -SRC_URI[md5sum] = "90afa8436ce2b2683c001c824bd22601"
> -SRC_URI[sha256sum] = "15ef27a875ae0d79d7446fd931deda11438e724ffbeac74449ed19cba23df4d4"
> +SRC_URI[md5sum] = "326fe97077141713f0930aa87949a287"
> +SRC_URI[sha256sum] = "cfd235663f1d1adc97abb38dd5e6d093bb7e155580f171f9ba0158feab69f875"
>   DEPENDS = "libgpg-error libassuan ${PTH}"
>   PTH_libc-uclibc = "npth"
>   PTH = "pth"
>
> -PR = "r3"
> +PR = "r0"
>
>   EXTRA_OECONF = "--with-pth=${STAGING_DIR_HOST} --without-pth-test \
>                   --with-gpg=${bindir}/gpg --without-gpgsm"

Merged into OE-Core

Thanks
	Sau!



  reply	other threads:[~2012-06-25 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 12:27 [PATCH] gpgme: updated to 1.3.2 Valentin Popa
2012-06-25 16:04 ` Saul Wold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-20  7:56 Valentin Popa
2012-06-21 11:57 ` Richard Purdie

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=4FE88C24.9090302@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox