From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] libgcrypt: version bump 1.11.2 -> 1.12.4
Date: Tue, 17 Nov 2026 07:14:40 +0100 [thread overview]
Message-ID: <20261117061440.3091620-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261106215320.1719664-1-s.pueschel@pengutronix.de>
Thanks, applied as b632dd00cb8cdeba7aae97e36f411762b9b6d4fc.
Michael
[sent from post-receive hook]
On Tue, 17 Nov 2026 07:14:40 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> The LICENSE files only replaced the FSF postal address with the webite
> and Ty Coon with Moe Ghoul.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20261106215320.1719664-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libgcrypt.make b/rules/libgcrypt.make
> index cca90315021a..d6a702c1c4e4 100644
> --- a/rules/libgcrypt.make
> +++ b/rules/libgcrypt.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBGCRYPT) += libgcrypt
> #
> # Paths and names
> #
> -LIBGCRYPT_VERSION := 1.11.2
> -LIBGCRYPT_SHA256 := 6ba59dd192270e8c1d22ddb41a07d95dcdbc1f0fb02d03c4b54b235814330aac
> +LIBGCRYPT_VERSION := 1.12.4
> +LIBGCRYPT_SHA256 := d77f68f48879510e79a2f65977ccc68981781ea0923e5bdffac2a193ea3d660e
> LIBGCRYPT := libgcrypt-$(LIBGCRYPT_VERSION)
> LIBGCRYPT_SUFFIX := tar.bz2
> LIBGCRYPT_URL := https://www.gnupg.org/ftp/gcrypt/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX)
> @@ -24,8 +24,8 @@ LIBGCRYPT_SOURCE := $(SRCDIR)/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX)
> LIBGCRYPT_DIR := $(BUILDDIR)/$(LIBGCRYPT)
> LIBGCRYPT_LICENSE := GPL-2.0-only AND LGPL-2.0-only
> LIBGCRYPT_LICENSE_FILES := \
> - file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> - file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c
> + file://COPYING;md5=570a9b3749dd0463a1778803b12a6dce \
> + file://COPYING.LIB;md5=4bf661c1e3793e55c8d1051bc5e0ae21
>
> # ----------------------------------------------------------------------------
> # Prepare
prev parent reply other threads:[~2026-11-17 6:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 21:52 [ptxdist] [PATCH 1/3] " Sven Püschel
2026-11-06 21:52 ` [ptxdist] [PATCH 2/3] libksba: version bump 1.6.7 -> 1.8.1 Sven Püschel
2026-11-17 6:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2026-11-06 21:52 ` [ptxdist] [PATCH 3/3] gnupg: version bump 2.4.8 -> 2.5.24 Sven Püschel
2026-11-17 6:14 ` [ptxdist] [APPLIED] " Michael Olbrich
2026-11-17 6:14 ` 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=20261117061440.3091620-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