From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libgcrypt: Version bump. 1.10.3 -> 1.11.0
Date: Mon, 5 Aug 2024 08:49:23 +0200 [thread overview]
Message-ID: <20240805064923.889444-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240715175939.3868346-1-christian.melki@t2data.com>
Thanks, applied as a6cd460e8b7b87efa7b0b4d29d7a05351d95376e.
Michael
[sent from post-receive hook]
On Mon, 05 Aug 2024 08:49:23 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Bunch of changes.
> https://github.com/gpg/libgcrypt/blob/libgcrypt-1.11.0/NEWS
>
> * Remove obsoleted options.
>
> * Changed license file hashes. Licenses had updates to reflect
> original file changes. This results in various changes.
> Whitespace, address, dates etc. But doesn't change any conditions.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20240715175939.3868346-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libgcrypt.make b/rules/libgcrypt.make
> index c1101d7a43ae..2d615ece40f9 100644
> --- a/rules/libgcrypt.make
> +++ b/rules/libgcrypt.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_LIBGCRYPT) += libgcrypt
> #
> # Paths and names
> #
> -LIBGCRYPT_VERSION := 1.10.3
> -LIBGCRYPT_MD5 := a8cada0b343e10dbee51c9e92d856a94
> +LIBGCRYPT_VERSION := 1.11.0
> +LIBGCRYPT_MD5 := 321c4975cfd6a496f0530b65a673f9a4
> 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=94d55d512a9ba36caa9b7df079bae19f \
> - file://COPYING.LIB;md5=bbb461211a33b134d42ed5ee802b37ff
> + file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
> + file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c
>
> # ----------------------------------------------------------------------------
> # Prepare
> @@ -55,9 +55,7 @@ LIBGCRYPT_CONF_OPT := \
> --enable-endian-check \
> --enable-random=linux \
> --enable-dev-random \
> - --disable-random-daemon \
> --$(call ptx/endis,LIBGCRYPT_ASM)-asm \
> - --disable-m-guard \
> --disable-large-data-tests \
> --disable-force-soft-hwfeatures \
> --disable-hmac-binary-check \
prev parent reply other threads:[~2024-08-05 6:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 17:59 [ptxdist] [PATCH] " Christian Melki
2024-08-05 6:49 ` 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=20240805064923.889444-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.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