lsof: correct LICENSE
PATCH 1/6 lsof: correct LICENSE
From: Ross Burton <[email protected]>
The lsof LICENSE is superficially BSD-like, but it isn't BSD. Now that we have the full SPDX license set in oe-core, use Spencer-94.
(From OE-Core rev: 5c1d61d1d4dfacb643a366285c0392e6a31087ed)
--- meta/recipes-extended/lsof/lsof_4.91.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-extended/lsof/lsof_4.91.bb +1 -1
@@ -3,7 +3,7 @@ DESCRIPTION = "Lsof is a Unix-specific diagnostic tool. \ Its name stands for LiSt Open Files, and it does just that." HOMEPAGE = "http://people.freebsd.org/~abe/" SECTION = "devel" -LICENSE = "BSD" +LICENSE = "Spencer-94" LIC_FILES_CHKSUM = "file://00README;beginline=645;endline=679;md5=964df275d26429ba3b39dbb9f205172a" # Upstream lsof releases are hosted on an ftp server which times out download
Signature · 1 line
2.17.1
PATCH 2/6 tzdata: Remove BSD License specifier
From: Joshua Watt <[email protected]>
The code in question is licensed under the BSD-3-Clause license, so including the generic "BSD" license is unnecessary.
(From OE-Core rev: c39fc075ce3fd5b53c2a2fccb43500ee0a12f39d)
--- meta/recipes-extended/timezone/timezone.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-extended/timezone/timezone.inc +1 -1
@@ -3,7 +3,7 @@ DESCRIPTION = "The Time Zone Database contains code and data that represent \ the history of local time for many representative locations around the globe." HOMEPAGE = "http://www.iana.org/time-zones" SECTION = "base" -LICENSE = "PD & BSD & BSD-3-Clause" +LICENSE = "PD & BSD-3-Clause" LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba" PV = "2021e"
Signature · 1 line
2.17.1
PATCH 3/6 e2fsprogs: Use specific BSD license variant
In reply to Nisha ParrakatFrom: Joshua Watt <[email protected]>
Make the license more accurate by specifying the specific variant of BSD license instead of the generic one. This helps with SPDX license attribution as "BSD" is not a valid SPDX license.
(From OE-Core rev: 966fb77981e4fed0ab7998439940b1e05dd0ee43)
--- meta/recipes-devtools/e2fsprogs/e2fsprogs.inc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
meta/recipes-devtools/e2fsprogs/e2fsprogs.inc +6 -6
@@ -3,12 +3,12 @@ DESCRIPTION = "The Ext2 Filesystem Utilities (e2fsprogs) contain all of the stan fixing, configuring , and debugging ext2 filesystems." HOMEPAGE = "http://e2fsprogs.sourceforge.net/" -LICENSE = "GPLv2 & LGPLv2 & BSD & MIT" -LICENSE_e2fsprogs-dumpe2fs = "GPLv2" -LICENSE_e2fsprogs-e2fsck = "GPLv2" -LICENSE_e2fsprogs-mke2fs = "GPLv2" -LICENSE_e2fsprogs-tune2fs = "GPLv2" -LICENSE_e2fsprogs-badblocks = "GPLv2" +LICENSE = "GPLv2 & LGPLv2 & BSD-3-Clause & MIT" +LICENSE:e2fsprogs-dumpe2fs = "GPLv2" +LICENSE:e2fsprogs-e2fsck = "GPLv2" +LICENSE:e2fsprogs-mke2fs = "GPLv2" +LICENSE:e2fsprogs-tune2fs = "GPLv2" +LICENSE:e2fsprogs-badblocks = "GPLv2" LIC_FILES_CHKSUM = "file://NOTICE;md5=d50be0580c0b0a7fbc7a4830bbe6c12b \ file://lib/ext2fs/ext2fs.h;beginline=1;endline=9;md5=596a8dedcb4e731c6b21c7a46fba6bef \ file://lib/e2p/e2p.h;beginline=1;endline=7;md5=8a74ade8f9d65095d70ef2d4bf48e36a \
Signature · 1 line
2.17.1
PATCH 4/6 glib-2.0: Use specific BSD license variant
In reply to Nisha ParrakatFrom: Joshua Watt <[email protected]>
Make the license more accurate by specifying the specific variant of BSD license instead of the generic one. This helps with SPDX license attribution as "BSD" is not a valid SPDX license.
(From OE-Core rev: 91cd1ef01a3f3883c04bac67af2672ec60e20fb8)
--- meta/recipes-core/glib-2.0/glib.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-core/glib-2.0/glib.inc +1 -1
@@ -4,7 +4,7 @@ HOMEPAGE = "https://developer.gnome.org/glib/" # pcre is under BSD; # docs/reference/COPYING is with a 'public domain'-like license! -LICENSE = "LGPLv2.1+ & BSD & PD" +LICENSE = "LGPLv2.1+ & BSD-3-Clause & PD" LIC_FILES_CHKSUM = "file://COPYING;md5=4fbd65380cdd255951079008b364516c \ file://glib/glib.h;beginline=4;endline=17;md5=b88abb7f3ad09607e71cb9d530155906 \ file://gmodule/COPYING;md5=4fbd65380cdd255951079008b364516c \
Signature · 1 line
2.17.1
PATCH 5/6 shadow: Use specific BSD license variant
In reply to Nisha ParrakatFrom: Joshua Watt <[email protected]>
Make the license more accurate by specifying the specific variant of BSD license instead of the generic one. This helps with SPDX license attribution as "BSD" is not a valid SPDX license.
(From OE-Core rev: 65e3b23e1b266653fd30c90222e953f7e37fba0c)
--- meta/recipes-extended/shadow/shadow.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-extended/shadow/shadow.inc +1 -1
@@ -3,7 +3,7 @@ HOMEPAGE = "http://github.com/shadow-maint/shadow" DESCRIPTION = "${SUMMARY}" BUGTRACKER = "http://github.com/shadow-maint/shadow/issues" SECTION = "base/utils" -LICENSE = "BSD | Artistic-1.0" +LICENSE = "BSD-3-Clause | Artistic-1.0" LIC_FILES_CHKSUM = "file://COPYING;md5=ed80ff1c2b40843cf5768e5229cf16e5 \ file://src/passwd.c;beginline=2;endline=30;md5=5720ff729a6ff39ecc9f64555d75f4af"
Signature · 1 line
2.17.1
PATCH 6/6 shadow-sysroot: sync license with shadow
In reply to Nisha ParrakatFrom: Ross Burton <[email protected]>
This recipe is just a single data file from shadow, but as we can't easily tell what license that specific file is under just copy the full license statement.
(From OE-Core rev: f0e2f3b1f855ea6e184bd1d8d796279fedcbfa33)
--- meta/recipes-extended/shadow/shadow-sysroot_4.6.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-extended/shadow/shadow-sysroot_4.6.bb +1 -1
@@ -2,7 +2,7 @@ SUMMARY = "Shadow utils requirements for useradd.bbclass" HOMEPAGE = "http://github.com/shadow-maint/shadow" BUGTRACKER = "http://github.com/shadow-maint/shadow/issues" SECTION = "base utils" -LICENSE = "BSD | Artistic-1.0" +LICENSE = "BSD-3-Clause | Artistic-1.0" LIC_FILES_CHKSUM = "file://login.defs_shadow-sysroot;md5=25e2f2de4dfc8f966ac5cdfce45cd7d5" DEPENDS = "base-passwd"
Signature · 1 line
2.17.1
Quoted 5 lines · Nisha Parrakat
From: Ross Burton <[email protected]>
The lsof LICENSE is superficially BSD-like, but it isn't BSD. Now that we have the full SPDX license set in oe-core, use Spencer-94.
Results in following warning:
WARNING: build-appliance-image-15.0.0-r0 do_rootfs: The license listed Spencer-94 was not in the licenses collected for recipe lsof
Steve
Quoted 35 lines
(From OE-Core rev:
5c1d61d1d4dfacb643a366285c0392e6a31087ed)Signed-off-by Ross Burton <[email protected]>Signed-off-by Richard Purdie <[email protected]>Signed-off-by Nisha Parrakat <[email protected]>--- meta/recipes-extended/lsof/lsof_4.91.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)meta/recipes-extended/lsof/lsof_4.91.bb +1
-2@@ -3,7 +3,7 @@ DESCRIPTION = "Lsof is a Unix-specific diagnostic tool. \ Its name stands for LiSt Open Files, and it does just that." HOMEPAGE = "http://people.freebsd.org/~abe/" SECTION = "devel" -LICENSE = "BSD" +LICENSE = "Spencer-94" LIC_FILES_CHKSUM = "file://00README;beginline=645;endline=679;md5=964df275d26429ba3b39dbb9f205172a" # Upstream lsof releases are hosted on an ftp server which times out download --2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#160883): https://lists.openembedded.org/g/openembedded-core/message/160883
Mute This Topic: https://lists.openembedded.org/mt/88651664/3620601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
On 29/01/2022, 15:21, "Steve Sakoman" <[email protected]> wrote:
On Mon, Jan 24, 2022 at 7:16 AM Nisha Parrakat <[email protected]> wrote:
>
> From: Ross Burton <[email protected]>
>
> The lsof LICENSE is superficially BSD-like, but it isn't BSD. Now that > we have the full SPDX license set in oe-core, use Spencer-94.
Results in following warning:
WARNING: build-appliance-image-15.0.0-r0 do_rootfs: The license listed Spencer-94 was not in the licenses collected for recipe lsof
If you're going to backport these license fixes, then you'll really need oe-core e2f9092c37395f4e3ee9d0777e28c83cce6007ee too which adds the new license files.
Ross
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
ack. I will submit a new patch set.
Quoted 2 lines · Nisha Parrakat
ack. I will submit a new patch set.
You can see the ones I've already pulled in here, so no need to resubmit those:
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/dunfell-nut
Steve
Quoted 8 lines
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161136): https://lists.openembedded.org/g/openembedded-core/message/161136
Mute This Topic: https://lists.openembedded.org/mt/88651664/3617601
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-