From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: bruno.thomsen@gmail.com
Subject: [ptxdist] [PATCH 3/5] libgcrypt: version bump 1.10.1 -> 1.10.3
Date: Thu, 21 Dec 2023 16:14:28 +0100 [thread overview]
Message-ID: <20231221151430.6104-3-bruno.thomsen@gmail.com> (raw)
In-Reply-To: <20231221151430.6104-1-bruno.thomsen@gmail.com>
New option --with-libtool-modification control how local modification of
libtool for Windows are handled.
Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
rules/libgcrypt.make | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rules/libgcrypt.make b/rules/libgcrypt.make
index 1e415fd2c451..c1101d7a43ae 100644
--- a/rules/libgcrypt.make
+++ b/rules/libgcrypt.make
@@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBGCRYPT) += libgcrypt
#
# Paths and names
#
-LIBGCRYPT_VERSION := 1.10.1
-LIBGCRYPT_MD5 := 8fadbe1fddafa341dce5ef3869f70e25
+LIBGCRYPT_VERSION := 1.10.3
+LIBGCRYPT_MD5 := a8cada0b343e10dbee51c9e92d856a94
LIBGCRYPT := libgcrypt-$(LIBGCRYPT_VERSION)
LIBGCRYPT_SUFFIX := tar.bz2
LIBGCRYPT_URL := https://www.gnupg.org/ftp/gcrypt/libgcrypt/$(LIBGCRYPT).$(LIBGCRYPT_SUFFIX)
--
2.43.0
next prev parent reply other threads:[~2023-12-21 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 15:14 [ptxdist] [PATCH 1/5] gnupg: version bump 2.3.7 -> 2.4.3 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 ` Bruno Thomsen [this message]
2024-01-10 16:57 ` [ptxdist] [APPLIED] libgcrypt: version bump 1.10.1 -> 1.10.3 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 ` [ptxdist] [APPLIED] gnupg: version bump 2.3.7 -> 2.4.3 Michael Olbrich
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=20231221151430.6104-3-bruno.thomsen@gmail.com \
--to=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