From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 2/2] python3-pycryptodomex: fix license identifier
Date: Wed, 7 Jul 2021 16:38:20 +0200 [thread overview]
Message-ID: <20210707143820.GH4015839@pengutronix.de> (raw)
In-Reply-To: <20210707135306.30900-2-rhi@pengutronix.de>
On Wed, Jul 07, 2021 at 03:53:06PM +0200, Roland Hieber wrote:
> LICENSE.rst includes an Unlicense and a BSD-2-Clause, and refers to
> additional licenses for the OCB code, which contains a restriction for
> "military purposes", and is not compatible with the Open Source
> Definition.
>
> Fixes: b8958ad388ba104527e2 (2021-07-02, "python3-pycryptodomex: new package")
> Cc: Lars Pedersen <lapeddk@gmail.com>
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> ---
> rules/python3-pycryptodomex.make | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/rules/python3-pycryptodomex.make b/rules/python3-pycryptodomex.make
> index 59dadfbd0d29..9409bb414e88 100644
> --- a/rules/python3-pycryptodomex.make
> +++ b/rules/python3-pycryptodomex.make
> @@ -21,9 +21,12 @@ PYTHON3_PYCRYPTODOMEX_SUFFIX := tar.gz
> PYTHON3_PYCRYPTODOMEX_URL := $(call ptx/mirror-pypi, pycryptodomex, $(PYTHON3_PYCRYPTODOMEX).$(PYTHON3_PYCRYPTODOMEX_SUFFIX))
> PYTHON3_PYCRYPTODOMEX_SOURCE := $(SRCDIR)/$(PYTHON3_PYCRYPTODOMEX).$(PYTHON3_PYCRYPTODOMEX_SUFFIX)
> PYTHON3_PYCRYPTODOMEX_DIR := $(BUILDDIR)/$(PYTHON3_PYCRYPTODOMEX)
> -PYTHON3_PYCRYPTODOMEX_LICENSE := BSD-2
> +PYTHON3_PYCRYPTODOMEX_LICENSE := Unlicense AND BSD-2-Clause and proprietary
I think this should be 'custom' not 'proprietary'. If 'proprietary' then we
assume that the code is closed source. That's not the case here.
Michael
> PYTHON3_PYCRYPTODOMEX_LICENSE_FILES := \
> - file://LICENSE.rst;md5=accfa6aeaceb3ba96676edf18e78302c
> + file://LICENSE.rst;md5=accfa6aeaceb3ba96676edf18e78302c \
> + file://Doc/ocb/license1.pdf;md5=e33fa8dcf4d10e5c0d9a9e9291714d3d \
> + file://Doc/ocb/license2.pdf;md5=68cfc4690fbbaa0d89d3ea3abcc60b0f \
> + file://Doc/ocb/license3.pdf;md5=2124679d48d559681738985e040ae388
>
> # ----------------------------------------------------------------------------
> # Prepare
> --
> 2.30.2
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
> To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next prev parent reply other threads:[~2021-07-07 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:53 [ptxdist] [PATCH 1/2] ptxd_make_world_license: handle PDFs in _LICENSE_FILES Roland Hieber
2021-07-07 13:53 ` [ptxdist] [PATCH 2/2] python3-pycryptodomex: fix license identifier Roland Hieber
2021-07-07 14:38 ` Michael Olbrich [this message]
2021-07-08 18:46 ` [ptxdist] [PATCH] fixup! ptxd_make_world_license: handle PDFs in _LICENSE_FILES Roland Hieber
2021-07-08 18:49 ` Roland Hieber
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=20210707143820.GH4015839@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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