From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] gnupg: use the stable 2.4 version line
Date: Fri, 17 Oct 2025 10:20:56 +0200 [thread overview]
Message-ID: <20251017082056.3112689-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20251013092343.1237782-1-s.pueschel@pengutronix.de>
Thanks, applied as dc556e8dd9ad698f8923972b5b827cc852a89d2f.
Michael
[sent from post-receive hook]
On Fri, 17 Oct 2025 10:20:56 +0200, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> The 2.4.x releases of GnuPG represent stable releases, whereas the 2.5.x
> releases are marked as devel. While they are also fully supported and
> ready for production use, stay at the latest stable version for PTXDist.
>
> Fixes: fa1e4439f3a6 ("gnupg: version bump 2.4.5 -> 2.5.3")
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20251013092343.1237782-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/gnupg.make b/rules/gnupg.make
> index 68e7103569f2..a962c79d825d 100644
> --- a/rules/gnupg.make
> +++ b/rules/gnupg.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_GNUPG) += gnupg
> #
> # Paths and names
> #
> -GNUPG_VERSION := 2.5.3
> -GNUPG_MD5 := 0f6c849e3c7ad7cefd35b54647044348
> +GNUPG_VERSION := 2.4.8
> +GNUPG_MD5 := a165b60aeaac0bb4d251117a45199c5f
> GNUPG := gnupg-$(GNUPG_VERSION)
> GNUPG_SUFFIX := tar.bz2
> GNUPG_URL := https://www.gnupg.org/ftp/gcrypt/gnupg/$(GNUPG).$(GNUPG_SUFFIX)
> @@ -50,6 +50,7 @@ GNUPG_CONF_OPT := $(CROSS_AUTOCONF_USR) \
> --disable-doc \
> --$(call ptx/endis, PTXCONF_GNUPG_GPGTAR)-gpgtar \
> --disable-wks-tools \
> + --disable-gpg-is-gpg2 \
> --$(call ptx/endis, PTXCONF_GLOBAL_SELINUX)-selinux-support \
> --disable-large-secmem \
> --enable-trust-models \
prev parent reply other threads:[~2025-10-17 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 9:23 [ptxdist] [PATCH] " Sven Püschel
2025-10-17 8:20 ` 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=20251017082056.3112689-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@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