From: Bruno Thomsen <bruno.thomsen@gmail.com>
To: ptxdist@pengutronix.de
Cc: bruno.thomsen@gmail.com
Subject: [ptxdist] [PATCH] cryptsetup: update license info
Date: Wed, 8 Nov 2023 23:30:52 +0100 [thread overview]
Message-ID: <20231108223052.69231-1-bruno.thomsen@gmail.com> (raw)
Add hash of license files and include "AND LGPL-2.0-or-later".
License was clarified back in v1.5.1 release note:
* Cryptsetup and libcryptsetup is now released under GPLv2+
(GPL version 2 or any later).
Some internal code handling files (loopaes, verity, tcrypt
and crypto backend wrapper) are LGPLv2+.
Previously code was GPL version 2 only.
Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.com>
---
rules/cryptsetup.make | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/rules/cryptsetup.make b/rules/cryptsetup.make
index aacf7e138259..6e14cab8a67d 100644
--- a/rules/cryptsetup.make
+++ b/rules/cryptsetup.make
@@ -14,14 +14,17 @@ PACKAGES-$(PTXCONF_CRYPTSETUP) += cryptsetup
#
# Paths and names
#
-CRYPTSETUP_VERSION := 2.6.0
-CRYPTSETUP_MD5 := 8b67da403a2515dc75d40c42e8196e4e
-CRYPTSETUP := cryptsetup-$(CRYPTSETUP_VERSION)
-CRYPTSETUP_SUFFIX := tar.xz
-CRYPTSETUP_URL := https://www.kernel.org/pub/linux/utils/cryptsetup/v$(basename $(CRYPTSETUP_VERSION))/$(CRYPTSETUP).$(CRYPTSETUP_SUFFIX)
-CRYPTSETUP_SOURCE := $(SRCDIR)/$(CRYPTSETUP).$(CRYPTSETUP_SUFFIX)
-CRYPTSETUP_DIR := $(BUILDDIR)/$(CRYPTSETUP)
-CRYPTSETUP_LICENSE := GPL-2.0-or-later
+CRYPTSETUP_VERSION := 2.6.0
+CRYPTSETUP_MD5 := 8b67da403a2515dc75d40c42e8196e4e
+CRYPTSETUP := cryptsetup-$(CRYPTSETUP_VERSION)
+CRYPTSETUP_SUFFIX := tar.xz
+CRYPTSETUP_URL := https://www.kernel.org/pub/linux/utils/cryptsetup/v$(basename $(CRYPTSETUP_VERSION))/$(CRYPTSETUP).$(CRYPTSETUP_SUFFIX)
+CRYPTSETUP_SOURCE := $(SRCDIR)/$(CRYPTSETUP).$(CRYPTSETUP_SUFFIX)
+CRYPTSETUP_DIR := $(BUILDDIR)/$(CRYPTSETUP)
+CRYPTSETUP_LICENSE := GPL-2.0-or-later AND LGPL-2.0-or-later
+CRYPTSETUP_LICENSE_FILES := \
+ file://COPYING;md5=32107dd283b1dfeb66c9b3e6be312326 \
+ file://COPYING.LGPL;md5=1960515788100ce5f9c98ea78a65dc52
# ----------------------------------------------------------------------------
# Prepare
base-commit: cae7daaa8850c4d952427fac5bcf4d8ffc553226
--
2.41.0
next reply other threads:[~2023-11-08 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 22:30 Bruno Thomsen [this message]
2023-11-17 7:20 ` [ptxdist] [APPLIED] " 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=20231108223052.69231-1-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