From: "Khem Raj" <raj.khem@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>,
openembedded-core@lists.openembedded.org
Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Alexandre BELLONI <alexandre.belloni@bootlin.com>
Subject: Re: [OE-core] [PATCH] recipes-core/busybox: fixup licensing information
Date: Tue, 27 Oct 2020 13:25:59 -0700 [thread overview]
Message-ID: <ee39bffd-e43b-69a6-98e2-b3f4963e346f@gmail.com> (raw)
In-Reply-To: <20201027164831.3297010-1-yann.morin.1998@free.fr>
On 10/27/20 9:48 AM, Yann E. MORIN wrote:
> Commit 7d32417b4d (busybox: Correct the name of the bzip2 license)
> changes the licesne from 'bzip2' to 'bzip2-1.0.6' on the rationale
> that the 'bzip2 license was renamed from "bzip2" to "bzip2-1.0.6"
> [...] to match the official SPDX identifier.'
>
> Though the above is true for the bzip2 and pbzip2 packages, the bzip2
> code bundled in busybox is a copy from the bzip2 1.0.4 version, not the
> 1.0.6 version.
>
> As such, using bzip2-1.0.6 is wrong.
>
> Unfortunately, there is no official SPDX license identifier for this
> bzip2 1.0.4 version, so we just mimick the existing ones (bzip2-1.0.5
> and bzip2-1.0.6) by using bzip2-1.0.4.
>
> Also, there is a license file attached to that, so we add it to the
> list.
>
we also need a text file for this license in meta/files/common-licenses
perhaps a symlink to bzip2-1.0.6 might be ok.
> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
> Cc: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> Cc: Alexandre BELLONI <alexandre.belloni@bootlin.com>
>
> ---
> Respin, as I was not yet subscribed to the list...
> Sorry for any duplicates...
> ---
> meta/recipes-core/busybox/busybox.inc | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
> index 45aaa2b41c..e0522be729 100644
> --- a/meta/recipes-core/busybox/busybox.inc
> +++ b/meta/recipes-core/busybox/busybox.inc
> @@ -5,10 +5,11 @@ BUGTRACKER = "https://bugs.busybox.net/"
>
> DEPENDS += "kern-tools-native virtual/crypt"
>
> -# bzip2 applet in busybox is based on lightly-modified bzip2 source
> +# bzip2 applet in busybox is based on lightly-modified bzip2-1.0.4 source
> # the GPL is version 2 only
> -LICENSE = "GPLv2 & bzip2-1.0.6"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=de10de48642ab74318e893a61105afbb"
> +LICENSE = "GPLv2 & bzip2-1.0.4"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=de10de48642ab74318e893a61105afbb \
> + file://archival/libarchive/bz/LICENSE;md5=28e3301eae987e8cfe19988e98383dae"
>
> SECTION = "base"
>
>
>
>
>
>
next prev parent reply other threads:[~2020-10-27 20:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:48 [PATCH] recipes-core/busybox: fixup licensing information Yann E. MORIN
2020-10-27 20:25 ` Khem Raj [this message]
2020-10-27 20:50 ` [OE-core] " Yann E. MORIN
2020-10-29 8:40 ` Peter Kjellerstedt
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=ee39bffd-e43b-69a6-98e2-b3f4963e346f@gmail.com \
--to=raj.khem@gmail.com \
--cc=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=yann.morin.1998@free.fr \
/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