From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>
Cc: Julien Olivain <ju.o@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 4/4] package/libgpgme: bump to version 1.20.0
Date: Sun, 18 Jun 2023 13:19:21 +0200 [thread overview]
Message-ID: <87ilblj9vq.fsf@48ers.dk> (raw)
In-Reply-To: <20230608185255.3505647-4-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Thu, 8 Jun 2023 20:52:55 +0200")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> Added upstream sha1 & sha256 hashes.
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Committed to 2023.02.x, thanks.
> ---
> package/libgpgme/libgpgme.hash | 7 +++----
> package/libgpgme/libgpgme.mk | 2 +-
> 2 files changed, 4 insertions(+), 5 deletions(-)
> diff --git a/package/libgpgme/libgpgme.hash b/package/libgpgme/libgpgme.hash
> index 7d02b9e139..a71cec1e38 100644
> --- a/package/libgpgme/libgpgme.hash
> +++ b/package/libgpgme/libgpgme.hash
> @@ -1,6 +1,5 @@
> -# Locally calculated after checking pgp signature
> -# https://gnupg.org/ftp/gcrypt/gpgme/gpgme-1.17.1.tar.bz2.sig
> -# using key 6DAA6E64A76D2840571B4902528897B826403ADA
> -sha256 711eabf5dd661b9b04be9edc9ace2a7bc031f6bd9d37a768d02d0efdef108f5f gpgme-1.17.1.tar.bz2
> +# From https://www.gnupg.org/download/integrity_check.html
> +sha1 369deeec95f1bb77fafc0b6c8fa65995ba82fd1e gpgme-1.20.0.tar.bz2
> +sha256 25a5785a5da356689001440926b94e967d02e13c49eb7743e35ef0cf22e42750 gpgme-1.20.0.tar.bz2
> # Locally calculated
> sha256 ca0061fc1381a3ab242310e4b3f56389f28e3d460eb2fd822ed7a21c6f030532 COPYING.LESSER
> diff --git a/package/libgpgme/libgpgme.mk b/package/libgpgme/libgpgme.mk
> index 2120ee8e3c..21a0b30d3b 100644
> --- a/package/libgpgme/libgpgme.mk
> +++ b/package/libgpgme/libgpgme.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
> -LIBGPGME_VERSION = 1.17.1
> +LIBGPGME_VERSION = 1.20.0
> LIBGPGME_SITE = https://gnupg.org/ftp/gcrypt/gpgme
> LIBGPGME_SOURCE = gpgme-$(LIBGPGME_VERSION).tar.bz2
> LIBGPGME_LICENSE = LGPL-2.1+
> --
> 2.39.2
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-18 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 18:52 [Buildroot] [PATCH 1/4] package/gnupg2: bump version to 2.4.2 Bernd Kuhls
2023-06-08 18:52 ` [Buildroot] [PATCH 2/4] package/libgcrypt: bump to version 1.10.2 Bernd Kuhls
2023-06-18 11:19 ` Peter Korsgaard
2023-07-06 8:43 ` Peter Korsgaard
2023-06-08 18:52 ` [Buildroot] [PATCH 3/4] package/libgpg-error: bump version to 1.47 Bernd Kuhls
2023-06-18 11:19 ` Peter Korsgaard
2023-07-06 8:44 ` Peter Korsgaard
2023-06-08 18:52 ` [Buildroot] [PATCH 4/4] package/libgpgme: bump to version 1.20.0 Bernd Kuhls
2023-06-18 11:19 ` Peter Korsgaard [this message]
2023-06-18 11:20 ` Peter Korsgaard
2023-06-18 11:19 ` [Buildroot] [PATCH 1/4] package/gnupg2: bump version to 2.4.2 Peter Korsgaard
2023-07-06 8:43 ` Peter Korsgaard
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=87ilblj9vq.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
/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