From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] gnupg: version bump 2.3.7 -> 2.4.3
Date: Wed, 10 Jan 2024 17:57:27 +0100 [thread overview]
Message-ID: <20240110165727.4191048-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231221151430.6104-1-bruno.thomsen@gmail.com>
Thanks, applied as 2b2e25425335ffbbca51b136ea2b12038e3faeb0.
Michael
[sent from post-receive hook]
On Wed, 10 Jan 2024 17:57:27 +0100, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> [Announce] GnuPG 2.3.8 released
> https://lists.gnupg.org/pipermail/gnupg-announce/2022q4/000476.html
> [Announce] GnuPG 2.4.0 released (silver anniversary)
> https://lists.gnupg.org/pipermail/gnupg-announce/2022q4/000477.html
> [Announce] GnuPG 2.4.1 released
> https://lists.gnupg.org/pipermail/gnupg-announce/2023q2/000478.html
> [Announce] GnuPG 2.4.2 released
> https://lists.gnupg.org/pipermail/gnupg-announce/2023q2/000479.html
> [Announce] GnuPG 2.4.3 released
> https://lists.gnupg.org/pipermail/gnupg-announce/2023q3/000480.html
>
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20231221151430.6104-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/gnupg.make b/rules/gnupg.make
> index c5ec8e844d18..1a90f472f9bf 100644
> --- a/rules/gnupg.make
> +++ b/rules/gnupg.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_GNUPG) += gnupg
> #
> # Paths and names
> #
> -GNUPG_VERSION := 2.3.7
> -GNUPG_MD5 := 1c6a6722b9cececcf10ca4e24106e34b
> +GNUPG_VERSION := 2.4.3
> +GNUPG_MD5 := e21ab42c629af80f19f813eeb61aa939
> GNUPG := gnupg-$(GNUPG_VERSION)
> GNUPG_SUFFIX := tar.bz2
> GNUPG_URL := \
prev parent reply other threads:[~2024-01-10 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:14 [ptxdist] [PATCH 1/5] " Bruno Thomsen
2023-12-21 15:14 ` [ptxdist] [PATCH 2/5] libgpg-error: version bump 1.45 -> 1.47 Bruno Thomsen
2024-01-10 16:57 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-12-21 15:14 ` [ptxdist] [PATCH 3/5] libgcrypt: version bump 1.10.1 -> 1.10.3 Bruno Thomsen
2024-01-10 16:57 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-12-21 15:14 ` [ptxdist] [PATCH 4/5] libksba: version bump 1.6.0 -> 1.6.5 Bruno Thomsen
2024-01-10 16:57 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-12-21 15:14 ` [ptxdist] [PATCH 5/5] libassuan: version bump 2.5.5 -> 2.5.6 Bruno Thomsen
2024-01-10 16:57 ` [ptxdist] [APPLIED] " Michael Olbrich
2024-01-10 16:57 ` Michael Olbrich [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=20240110165727.4191048-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=bruno.thomsen@gmail.com \
--cc=ptxdist@pengutronix.de \
/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