xz: Update LICENSE variable for xz packages
PATCH 1/1 xz: Update LICENSE variable for xz packages
Update LICENSE defined for xz packages to match the license information provided in the xz COPYING file.
The License information from PACKAGERS file of xz mentions packages with lzma files are in public domain.They ask to use GPLv2+, if only it's not possible to mention "PD and GPLv2+".
Include PD license with GPLv2 to packages with lzma content:
xz-dev package contains lzma header
xz-doc package contains lzma man pages
xz packages contains lzma binaries
Links: https://github.com/tukaani-project/xz/blob/v5.2.6/COPYING
https://github.com/tukaani-project/xz/blob/v5.4.1/PACKAGERS
--- meta/recipes-extended/xz/xz_5.2.6.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-extended/xz/xz_5.2.6.bb +3 -3
@@ -9,10 +9,10 @@ SECTION = "base" # libgnu, which appears to be used for DOS builds. So we're left with # GPL-2.0-or-later and PD. LICENSE = "GPL-2.0-or-later & GPL-3.0-with-autoconf-exception & LGPL-2.1-or-later & PD" -LICENSE:${PN} = "GPL-2.0-or-later" -LICENSE:${PN}-dev = "GPL-2.0-or-later" +LICENSE:${PN} = "PD & GPL-2.0-or-later" +LICENSE:${PN}-dev = "PD & GPL-2.0-or-later" LICENSE:${PN}-staticdev = "GPL-2.0-or-later" -LICENSE:${PN}-doc = "GPL-2.0-or-later" +LICENSE:${PN}-doc = "PD & GPL-2.0-or-later" LICENSE:${PN}-dbg = "GPL-2.0-or-later" LICENSE:${PN}-locale = "GPL-2.0-or-later" LICENSE:liblzma = "PD"
Signature · 1 line
2.25.1
Quoted 41 lines · On Mon, 6 May 2024, 13:09 nikhil via lists.openembedded.org, <nikhilar2410=…
Update LICENSE defined for xz packages to match the license information provided in the xz COPYING file.
The License information from PACKAGERS file of xz mentions packages with lzma files are in public domain.They ask to use GPLv2+, if only it's not possible to mention "PD and GPLv2+".
Include PD license with GPLv2 to packages with lzma content:
xz-dev package contains lzma header
xz-doc package contains lzma man pages
xz packages contains lzma binariesLinks: https://github.com/tukaani-project/xz/blob/v5.2.6/COPYING
https://github.com/tukaani-project/xz/blob/v5.4.1/PACKAGERSSigned-off-by Bhabu Bindu <[email protected]>--- meta/recipes-extended/xz/xz_5.2.6.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)meta/recipes-extended/xz/xz_5.2.6.bb +0
-0@@ -9,10 +9,10 @@ SECTION = "base" # libgnu, which appears to be used for DOS builds. So we're left with # GPL-2.0-or-later and PD. LICENSE = "GPL-2.0-or-later & GPL-3.0-with-autoconf-exception &LGPL-2.1-or-later & PD"
meta/recipes-extended/xz/xz_5.2.6.bb +3
-4-LICENSE:${PN} = "GPL-2.0-or-later" -LICENSE:${PN}-dev = "GPL-2.0-or-later" +LICENSE:${PN} = "PD & GPL-2.0-or-later" +LICENSE:${PN}-dev = "PD & GPL-2.0-or-later" LICENSE:${PN}-staticdev = "GPL-2.0-or-later" -LICENSE:${PN}-doc = "GPL-2.0-or-later" +LICENSE:${PN}-doc = "PD & GPL-2.0-or-later" LICENSE:${PN}-dbg = "GPL-2.0-or-later" LICENSE:${PN}-locale = "GPL-2.0-or-later" LICENSE:liblzma = "PD" --
Quoted 2 lines
2.25.1
I'm not a copyright lawyer, but from what I understand public domain is not a licence. For a discussion see
https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
The next version of xz will be 0BSD so the statement will change too.
Regards,
Marta
Quoted 1 line
PD is not a license for legal compliance purposes, but it's a valid identifier in a recipe's LICENSE field. We have plenty of those already.
Also, shouldn't this be addressed in master first?
Alex
Quoted 63 lines · Marta Rybczynska via lists.openembedded.org
Quoted 40 lines · On Mon, 6 May 2024, 13:09 nikhil via lists.openembedded.org…
Update LICENSE defined for xz packages to match the license information provided in the xz COPYING file.
The License information from PACKAGERS file of xz mentions packages with lzma files are in public domain.They ask to use GPLv2+, if only it's not possible to mention "PD and GPLv2+".
Include PD license with GPLv2 to packages with lzma content:
xz-dev package contains lzma header
xz-doc package contains lzma man pages
xz packages contains lzma binariesLinks: https://github.com/tukaani-project/xz/blob/v5.2.6/COPYING
https://github.com/tukaani-project/xz/blob/v5.4.1/PACKAGERSSigned-off-by Bhabu Bindu <[email protected]>--- meta/recipes-extended/xz/xz_5.2.6.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)meta/recipes-extended/xz/xz_5.2.6.bb +3
-4@@ -9,10 +9,10 @@ SECTION = "base" # libgnu, which appears to be used for DOS builds. So we're left with # GPL-2.0-or-later and PD. LICENSE = "GPL-2.0-or-later & GPL-3.0-with-autoconf-exception & LGPL-2.1-or-later & PD" -LICENSE:${PN} = "GPL-2.0-or-later" -LICENSE:${PN}-dev = "GPL-2.0-or-later" +LICENSE:${PN} = "PD & GPL-2.0-or-later" +LICENSE:${PN}-dev = "PD & GPL-2.0-or-later" LICENSE:${PN}-staticdev = "GPL-2.0-or-later" -LICENSE:${PN}-doc = "GPL-2.0-or-later" +LICENSE:${PN}-doc = "PD & GPL-2.0-or-later" LICENSE:${PN}-dbg = "GPL-2.0-or-later" LICENSE:${PN}-locale = "GPL-2.0-or-later" LICENSE:liblzma = "PD" --Quoted 1 line
2.25.1
I'm not a copyright lawyer, but from what I understand public domain is not a licence. For a discussion see https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
The next version of xz will be 0BSD so the statement will change too.
Regards,
Marta-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199047): https://lists.openembedded.org/g/openembedded-core/message/199047
Mute This Topic: https://lists.openembedded.org/mt/105937026/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Quoted 40 lines · Marta Rybczynska via lists.openembedded.org
Quoted 36 lines · On Mon, 6 May 2024, 13:09 nikhil via lists.openembedded.org…
Update LICENSE defined for xz packages to match the license information provided in the xz COPYING file.
The License information from PACKAGERS file of xz mentions packages with lzma files are in public domain.They ask to use GPLv2+, if only it's not possible to mention "PD and GPLv2+".
Include PD license with GPLv2 to packages with lzma content:
xz-dev package contains lzma header
xz-doc package contains lzma man pages
xz packages contains lzma binariesLinks: https://github.com/tukaani-project/xz/blob/v5.2.6/COPYING
https://github.com/tukaani-project/xz/blob/v5.4.1/PACKAGERSSigned-off-by Bhabu Bindu <[email protected]>--- meta/recipes-extended/xz/xz_5.2.6.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)meta/recipes-extended/xz/xz_5.2.6.bb +3
-3@@ -9,10 +9,10 @@ SECTION = "base" # libgnu, which appears to be used for DOS builds. So we're left with # GPL-2.0-or-later and PD. LICENSE = "GPL-2.0-or-later & GPL-3.0-with-autoconf-exception & LGPL-2.1-or-later & PD" -LICENSE:${PN} = "GPL-2.0-or-later" -LICENSE:${PN}-dev = "GPL-2.0-or-later" +LICENSE:${PN} = "PD & GPL-2.0-or-later" +LICENSE:${PN}-dev = "PD & GPL-2.0-or-later" LICENSE:${PN}-staticdev = "GPL-2.0-or-later" -LICENSE:${PN}-doc = "GPL-2.0-or-later" +LICENSE:${PN}-doc = "PD & GPL-2.0-or-later"
Quoted 9 lines
Quoted 5 lines
meta/recipes-extended/xz/xz_5.2.6.bb +0
-1LICENSE:${PN}-dbg = "GPL-2.0-or-later" LICENSE:${PN}-locale = "GPL-2.0-or-later" LICENSE:liblzma = "PD" --2.25.1
I'm not a copyright lawyer, but from what I understand public domain is not a licence. For a discussion see https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files
rather each PD is a license of its own is what I understand.
Quoted 14 lines
The next version of xz will be 0BSD so the statement will change too.
Regards,
Marta-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199047): https://lists.openembedded.org/g/openembedded-core/message/199047
Mute This Topic: https://lists.openembedded.org/mt/105937026/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Hello,
Change is addressed and upstreamed to master and scarthgap as well, as suggested by Alexander Kanavin<https://lists.openembedded.org/g/openembedded-core/topic/105937026#>.
[https://lists.openembedded.org/g/openembedded-core/coverphoto]<https://lists.openembedded.org/g/openembedded-core/message/201152>
[master][scarthgap][PATCH] xz: Update LICENSE variable for xz packages<https://lists.openembedded.org/g/openembedded-core/message/201152> /
lists.openembedded.org
Best Regards,
Bindu B
________________________________
From: Khem Raj <[email protected]>
Sent: 07 May 2024 21:53
To: [email protected] <[email protected]>
Cc: [email protected] <[email protected]>; OE-core <[email protected]>; Bhabu Bindu <[email protected]>; Nikhil R <[email protected]>; Bhabu Bindu <[email protected]>
Subject: Re: [OE-core][kirkstone][PATCH] xz: Update LICENSE variable for xz packages
Caution: This email originated from outside of the KPIT. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Quoted 40 lines · Marta Rybczynska via lists.openembedded.org
Quoted 36 lines · On Mon, 6 May 2024, 13:09 nikhil via lists.openembedded.org…
Update LICENSE defined for xz packages to match the license information provided in the xz COPYING file.
The License information from PACKAGERS file of xz mentions packages with lzma files are in public domain.They ask to use GPLv2+, if only it's not possible to mention "PD and GPLv2+".
Include PD license with GPLv2 to packages with lzma content:
xz-dev package contains lzma header
xz-doc package contains lzma man pages
xz packages contains lzma binariesLinks: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftukaani-project%2Fxz%2Fblob%2Fv5.2.6%2FCOPYING&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C01a3b5884c804aee6e3a08dc6eb210b5%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638506958271791055%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=C0A5fTtas5I9fkl3fjp%2BzTwngQ%2Fg3fy5iofajIO0wa4%3D&reserved=0<https://github.com/tukaani-project/xz/blob/v5.2.6/COPYING>
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftukaani-project%2Fxz%2Fblob%2Fv5.4.1%2FPACKAGERS&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C01a3b5884c804aee6e3a08dc6eb210b5%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638506958271799257%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=eIoutADbpn0BNjCYjMWeaEzrQ1yR2tuMGS1WCmV6AuY%3D&reserved=0<https://github.com/tukaani-project/xz/blob/v5.4.1/PACKAGERS>Signed-off-by Bhabu Bindu <[email protected]>--- meta/recipes-extended/xz/xz_5.2.6.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)meta/recipes-extended/xz/xz_5.2.6.bb +3
-3@@ -9,10 +9,10 @@ SECTION = "base" # libgnu, which appears to be used for DOS builds. So we're left with # GPL-2.0-or-later and PD. LICENSE = "GPL-2.0-or-later & GPL-3.0-with-autoconf-exception & LGPL-2.1-or-later & PD" -LICENSE:${PN} = "GPL-2.0-or-later" -LICENSE:${PN}-dev = "GPL-2.0-or-later" +LICENSE:${PN} = "PD & GPL-2.0-or-later" +LICENSE:${PN}-dev = "PD & GPL-2.0-or-later" LICENSE:${PN}-staticdev = "GPL-2.0-or-later" -LICENSE:${PN}-doc = "GPL-2.0-or-later" +LICENSE:${PN}-doc = "PD & GPL-2.0-or-later"
Quoted 9 lines
Quoted 5 lines
meta/recipes-extended/xz/xz_5.2.6.bb +0
-1LICENSE:${PN}-dbg = "GPL-2.0-or-later" LICENSE:${PN}-locale = "GPL-2.0-or-later" LICENSE:liblzma = "PD" --2.25.1
I'm not a copyright lawyer, but from what I understand public domain is not a licence. For a discussion see https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.spdx.org%2Fview%2FLegal_Team%2FDecisions%2FDealing_with_Public_Domain_within_SPDX_Files&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C01a3b5884c804aee6e3a08dc6eb210b5%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638506958271801872%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=gpmcahLD%2B1%2B5qo82XLYUgZZ39tOMVnHvMmmZY04U2go%3D&reserved=0<https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_Files>
rather each PD is a license of its own is what I understand.
Quoted 6 lines
The next version of xz will be 0BSD so the statement will change too.
Regards,
Marta
Quoted 8 lines
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#199047): https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openembedded.org%2Fg%2Fopenembedded-core%2Fmessage%2F199047&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C01a3b5884c804aee6e3a08dc6eb210b5%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638506958271804456%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=zEZSamS5RU4HUm9J%2Fhn0Yx7KVRsex6ywQE7V%2BWQzuus%3D&reserved=0<https://lists.openembedded.org/g/openembedded-core/message/199047>
Mute This Topic: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openembedded.org%2Fmt%2F105937026%2F1997914&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C01a3b5884c804aee6e3a08dc6eb210b5%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638506958271806963%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=kczbJlRfa8%2B0RhGK%2BIGV5BwpIJYbOep%2FMA3B8MTc8jw%3D&reserved=0<https://lists.openembedded.org/mt/105937026/1997914>
Group Owner: [email protected]
Unsubscribe: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openembedded.org%2Fg%2Fopenembedded-core%2Funsub&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C01a3b5884c804aee6e3a08dc6eb210b5%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638506958271809429%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=gFpc362jFWcnzrf445x7OYJgfaLhsQXZkOtZnwrnRDM%3D&reserved=0<https://lists.openembedded.org/g/openembedded-core/unsub> [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.
Quoted 6 lines · Marta Rybczynska via lists.openembedded.org
I'm not a copyright lawyer, but from what I understand public domain is not a licence. For a discussion
see https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Public_Domain_within_SPDX_FilesThe next version of xz will be 0BSD so the statement will change too.
I did check into this a bit. We do have a "placeholder" license file in our common-licenses directory so PD is accepted in our license fields but there is no SPDX PD license identifier for the reasons linked to above, each wording is different. PD means different things in different locations too.
Switching to 0BSD probably makes things easier!
For now, mentioning PD in the LICENSE field would match other recipes.
Cheers,
Richard
Hello ,
The LICENSE variable for xz package is updated, and this change is already part of scarthgap and master branch.
May I know when this change will be part of kirkstone.
https://lists.openembedded.org/g/openembedded-core/message/199040
Best Regards,
Bindu B
________________________________
From: Richard Purdie <[email protected]>
Sent: 27 June 2024 04:06
To: [email protected] <[email protected]>; [email protected] <[email protected]>
Cc: OE-core <[email protected]>; Bhabu Bindu <[email protected]>; Nikhil R <[email protected]>; Bhabu Bindu <[email protected]>
Subject: Re: [OE-core][kirkstone][PATCH] xz: Update LICENSE variable for xz packages
Caution: This email originated from outside of the KPIT. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Quoted 6 lines · Marta Rybczynska via lists.openembedded.org
I'm not a copyright lawyer, but from what I understand public domain
is not a licence. For a discussion
see https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.spdx.org%2Fview%2FLegal_Team%2FDecisions%2FDealing_with_Publ&data=05%7C02%7Cbhabu.bindu%40kpit.com%7C2ea7b1fb245347fc31ec08dc96306b75%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C638550382007188689%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=71LsYBUvsIlOxDGTkkZKVRvHkWrn0mxAx6Vu9wzZqPs%3D&reserved=0<https://wiki.spdx.org/view/Legal_Team/Decisions/Dealing_with_Publ>ic_Domain_within_SPDX_FilesThe next version of xz will be 0BSD so the statement will change too.
I did check into this a bit. We do have a "placeholder" license file in our common-licenses directory so PD is accepted in our license fields but there is no SPDX PD license identifier for the reasons linked to above, each wording is different. PD means different things in different locations too.
Switching to 0BSD probably makes things easier!
For now, mentioning PD in the LICENSE field would match other recipes.
Cheers,
Richard
This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.