From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>
Subject: Re: [ptxdist] [APPLIED] gnutls: add license file and hash
Date: Fri, 24 Nov 2023 08:28:13 +0100 [thread overview]
Message-ID: <20231124072813.1904218-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20231114114807.23620-1-bruno.thomsen@gmail.com>
Thanks, applied as fed5d01d34cf669c2c4c63062f4f13de8ed289c9.
Michael
[sent from post-receive hook]
On Fri, 24 Nov 2023 08:28:13 +0100, Bruno Thomsen <bruno.thomsen@gmail.com> wrote:
> Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
> Message-Id: <20231114114807.23620-1-bruno.thomsen@gmail.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/gnutls.make b/rules/gnutls.make
> index 5420fd4c2cc9..d49fbd1b17d6 100644
> --- a/rules/gnutls.make
> +++ b/rules/gnutls.make
> @@ -14,14 +14,16 @@ PACKAGES-$(PTXCONF_GNUTLS) += gnutls
> #
> # Paths and names
> #
> -GNUTLS_VERSION := 3.7.7
> -GNUTLS_MD5 := 39e5c71af7f444bdf175094a787843a2
> -GNUTLS := gnutls-$(GNUTLS_VERSION)
> -GNUTLS_SUFFIX := tar.xz
> -GNUTLS_URL := https://www.gnupg.org/ftp/gcrypt/gnutls/v3.7/$(GNUTLS).$(GNUTLS_SUFFIX)
> -GNUTLS_SOURCE := $(SRCDIR)/$(GNUTLS).$(GNUTLS_SUFFIX)
> -GNUTLS_DIR := $(BUILDDIR)/$(GNUTLS)
> -GNUTLS_LICENSE := LGPL-3.0-or-later
> +GNUTLS_VERSION := 3.7.7
> +GNUTLS_MD5 := 39e5c71af7f444bdf175094a787843a2
> +GNUTLS := gnutls-$(GNUTLS_VERSION)
> +GNUTLS_SUFFIX := tar.xz
> +GNUTLS_URL := https://www.gnupg.org/ftp/gcrypt/gnutls/v3.7/$(GNUTLS).$(GNUTLS_SUFFIX)
> +GNUTLS_SOURCE := $(SRCDIR)/$(GNUTLS).$(GNUTLS_SUFFIX)
> +GNUTLS_DIR := $(BUILDDIR)/$(GNUTLS)
> +GNUTLS_LICENSE := LGPL-3.0-or-later
> +GNUTLS_LICENSE_FILES := \
> + file://LICENSE;md5=71391c8e0c1cfe68077e7fce3b586283
>
> # ----------------------------------------------------------------------------
> # Prepare
next prev parent reply other threads:[~2023-11-24 7:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 11:48 [ptxdist] [PATCH 1/6] " Bruno Thomsen
2023-11-14 11:48 ` [ptxdist] [PATCH 2/6] grep: add license information Bruno Thomsen
2023-11-24 7:28 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 3/6] htop: add license file and hash Bruno Thomsen
2023-11-24 7:28 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 4/6] iptables: " Bruno Thomsen
2023-11-24 7:28 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 5/6] libfastjson: " Bruno Thomsen
2023-11-24 7:28 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-14 11:48 ` [ptxdist] [PATCH 6/6] json-glib: " Bruno Thomsen
2023-11-24 7:28 ` [ptxdist] [APPLIED] " Michael Olbrich
2023-11-24 7:28 ` Michael Olbrich [this message]
2023-11-24 11:31 ` [ptxdist] [PATCH 1/6] gnutls: " Roland Hieber
2023-11-27 19:55 ` Bruno Thomsen
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=20231124072813.1904218-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