From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Peter Seiderer <ps.report@gmx.net>
Cc: Julien Olivain <ju.o@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v1] package/gnupg2: bump version to 2.4.1
Date: Sat, 6 May 2023 18:09:28 +0200 [thread overview]
Message-ID: <20230506160928.GL252090@scaer> (raw)
In-Reply-To: <20230503185832.14339-1-ps.report@gmx.net>
Peter, All,
On 2023-05-03 20:58 +0200, Peter Seiderer spake thusly:
> For details see [1].
>
> [1] https://lists.gnupg.org/pipermail/gnupg-announce/2023q2/000478.html
>
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> package/gnupg2/gnupg2.hash | 8 ++++----
> package/gnupg2/gnupg2.mk | 2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/package/gnupg2/gnupg2.hash b/package/gnupg2/gnupg2.hash
> index c642862fe2..baee824104 100644
> --- a/package/gnupg2/gnupg2.hash
> +++ b/package/gnupg2/gnupg2.hash
> @@ -1,7 +1,7 @@
> -# From https://lists.gnupg.org/pipermail/gnupg-announce/2022q4/000477.html
> -sha1 63dde155a8df0d5e1987efa5fc17438beca83ac1 gnupg-2.4.0.tar.bz2
> +# From https://lists.gnupg.org/pipermail/gnupg-announce/2023q2/000478.html
> +sha1 d7d021101361a5e1166a6c0cc1731276e7134547 gnupg-2.4.1.tar.bz2
> # Calculated based on the hash above and signature
> -# https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.4.0.tar.bz2.sig
> +# https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.4.1.tar.bz2.sig
> # using key 6DAA6E64A76D2840571B4902528897B826403ADA
> -sha256 1d79158dd01d992431dd2e3facb89fdac97127f89784ea2cb610c600fb0c1483 gnupg-2.4.0.tar.bz2
> +sha256 76b71e5aeb443bfd910ce9cbc8281b617c8341687afb67bae455877972b59de8 gnupg-2.4.1.tar.bz2
> sha256 bc2d6664f6276fa0a72d57633b3ae68dc7dcb677b71018bf08c8e93e509f1357 COPYING
> diff --git a/package/gnupg2/gnupg2.mk b/package/gnupg2/gnupg2.mk
> index 73de185ba7..f7c7ae847c 100644
> --- a/package/gnupg2/gnupg2.mk
> +++ b/package/gnupg2/gnupg2.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -GNUPG2_VERSION = 2.4.0
> +GNUPG2_VERSION = 2.4.1
> GNUPG2_SOURCE = gnupg-$(GNUPG2_VERSION).tar.bz2
> GNUPG2_SITE = https://gnupg.org/ftp/gcrypt/gnupg
> GNUPG2_LICENSE = GPL-3.0+
> --
> 2.40.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-05-06 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 18:58 [Buildroot] [PATCH v1] package/gnupg2: bump version to 2.4.1 Peter Seiderer
2023-05-06 16:09 ` Yann E. MORIN [this message]
2023-05-30 19:51 ` 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=20230506160928.GL252090@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=ps.report@gmx.net \
/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.