Patch review
cover Patch review
Please review this set of changes for scarthgap and have comments back by end of day Thursday, July 11
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/7115
The following changes since commit 1cab8d06ce5df7a8d00cff8531965a84d90d265a:
curl: locale-base-en-us isn't glibc-specific (2024-07-03 07:09:47 -0700)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/scarthgap-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/scarthgap-nut
Changqing Li (2):
apt-native: don't let dpkg overwrite files by default
apt: runtime error: filename too long (tmpdir length)
Hitendra Prajapati (1):
ghostscript: upgrade 10.02.1 -> 10.03.1
Peter Marko (2):
flac: fix buildpaths warnings
cargo: remove True option to getVar calls
Xiangyu Chen (1):
qemu: Upgrade 8.2.1 -> 8.2.2
aszh07 (1):
xz: Update LICENSE variable for xz packages
meta/classes-recipe/cargo_common.bbclass | 4 +-
meta/classes-recipe/ptest-cargo.bbclass | 18 ++--
...he-filename-can-t-be-longer-than-255.patch | 40 ++++++++
meta/recipes-devtools/apt/apt_2.6.1.bb | 3 +-
...u-native_8.2.1.bb => qemu-native_8.2.2.bb} | 0
...e_8.2.1.bb => qemu-system-native_8.2.2.bb} | 0
meta/recipes-devtools/qemu/qemu.inc | 3 +-
.../qemu/qemu/CVE-2023-6683.patch | 91 -----------------
.../qemu/{qemu_8.2.1.bb => qemu_8.2.2.bb} | 0
.../ghostscript/CVE-2024-29510.patch | 84 ----------------
.../ghostscript/CVE-2024-33869-0001.patch | 39 --------
.../ghostscript/CVE-2024-33869-0002.patch | 52 ----------
.../ghostscript/CVE-2024-33870.patch | 99 -------------------
.../ghostscript/CVE-2024-33871.patch | 43 --------
.../avoid-host-contamination.patch | 11 +--
...dd-option-to-explicitly-disable-neon.patch | 99 -------------------
...ript_10.02.1.bb => ghostscript_10.03.1.bb} | 8 +-
meta/recipes-extended/xz/xz_5.4.6.bb | 6 +-
meta/recipes-multimedia/flac/flac_1.4.3.bb | 7 ++
19 files changed, 69 insertions(+), 538 deletions(-)
create mode 100644 meta/recipes-devtools/apt/apt/0001-strutl.cc-the-filename-can-t-be-longer-than-255.patch
rename meta/recipes-devtools/qemu/{qemu-native_8.2.1.bb => qemu-native_8.2.2.bb} (100%)
rename meta/recipes-devtools/qemu/{qemu-system-native_8.2.1.bb => qemu-system-native_8.2.2.bb} (100%)
delete mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-6683.patch
rename meta/recipes-devtools/qemu/{qemu_8.2.1.bb => qemu_8.2.2.bb} (100%)
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-29510.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33869-0001.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33869-0002.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33870.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33871.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/configure.ac-add-option-to-explicitly-disable-neon.patch
rename meta/recipes-extended/ghostscript/{ghostscript_10.02.1.bb => ghostscript_10.03.1.bb} (88%)Signature · 1 line
2.34.1
PATCH 1/7 ghostscript: upgrade 10.02.1 -> 10.03.1
From: Hitendra Prajapati <[email protected]>
avoid-host-contamination.patch refreshed for 10.03.1
Below patches are no longer needed as it's included in this upgrade.
1. CVE-2024-29510.patch
2. CVE-2024-33869-0001.patch
3. CVE-2024-33869-0002.patch
4. CVE-2024-33870.patch
5. CVE-2024-33871.patch
6. configure.ac-add-option-to-explicitly-disable-neon.patch
other patch release to address security bugs:
CVE-2024-29506
CVE-2024-29507
CVE-2024-29508
CVE-2024-29509
CVE-2024-29511
(From OE-Core rev: 9a424fbcdc0c792ff3b99bf0e8a5e380582f53bc)
---
.../ghostscript/CVE-2024-29510.patch | 84 ----------------
.../ghostscript/CVE-2024-33869-0001.patch | 39 --------
.../ghostscript/CVE-2024-33869-0002.patch | 52 ----------
.../ghostscript/CVE-2024-33870.patch | 99 -------------------
.../ghostscript/CVE-2024-33871.patch | 43 --------
.../avoid-host-contamination.patch | 11 +--
...dd-option-to-explicitly-disable-neon.patch | 99 -------------------
...ript_10.02.1.bb => ghostscript_10.03.1.bb} | 8 +-
8 files changed, 5 insertions(+), 430 deletions(-)
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-29510.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33869-0001.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33869-0002.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33870.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33871.patch
delete mode 100644 meta/recipes-extended/ghostscript/ghostscript/configure.ac-add-option-to-explicitly-disable-neon.patch
rename meta/recipes-extended/ghostscript/{ghostscript_10.02.1.bb => ghostscript_10.03.1.bb} (88%)meta/recipes-extended/ghostscript/ghostscript/CVE-2024-29510.patch deleted +0 -84
@@ -1,84 +0,0 @@ -From 3b1735085ecef20b29e8db3416ab36de93e86d1f Mon Sep 17 00:00:00 2001 -From: Ken Sharp <[email protected]> -Date: Thu, 21 Mar 2024 09:01:15 +0000 -Subject: [PATCH 5/5] Uniprint device - prevent string configuration changes - when SAFER - -Bug #707662 - -We cannot sanitise the string arguments used by the Uniprint device -because they can potentially include anything. - -This commit ensures that these strings are locked and cannot be -changed by PostScript once SAFER is activated. Full configuration from -the command line is still possible (see the *.upp files in lib). - -This addresses CVE-2024-29510 - -CVE: CVE-2024-29510 - -Upstream-Status: Backport [https://cgit.ghostscript.com/cgi-bin/cgit.cgi/ghostpdl.git/commit/?id=3b1735085ecef20b29e] - -Signed-off-by: Archana Polampalli <[email protected]> ---- - devices/gdevupd.c | 31 +++++++++++++++++++++++++++++++ - 1 file changed, 31 insertions(+) - -diff --git a/devices/gdevupd.c b/devices/gdevupd.c -index 740dae0..a50571a 100644 ---- a/devices/gdevupd.c -+++ b/devices/gdevupd.c -@@ -1887,6 +1887,16 @@ out on this copies. - if(!upd_strings[i]) continue; - UPD_PARAM_READ(param_read_string,upd_strings[i],value,udev->memory); - if(0 == code) { -+ if (gs_is_path_control_active(udev->memory)) { -+ if (strings[i].size != value.size) -+ error = gs_error_invalidaccess; -+ else { -+ if (strings[i].data && memcmp(strings[i].data, value.data, strings[i].size) != 0) -+ error = gs_error_invalidaccess; -+ } -+ if (error < 0) -+ goto exit; -+ } - if(0 <= error) error |= UPD_PUT_STRINGS; - UPD_MM_DEL_PARAM(udev->memory, strings[i]); - if(!value.size) { -@@ -1904,6 +1914,26 @@ out on this copies. - if(!upd_string_a[i]) continue; - UPD_PARAM_READ(param_read_string_array,upd_string_a[i],value,udev->memory); - if(0 == code) { -+ if (gs_is_path_control_active(udev->memory)) { -+ if (string_a[i].size != value.size) -+ error = gs_error_invalidaccess; -+ else { -+ int loop; -+ for (loop = 0;loop < string_a[i].size;loop++) { -+ gs_param_string *tmp1 = (gs_param_string *)&(string_a[i].data[loop]); -+ gs_param_string *tmp2 = (gs_param_string *)&value.data[loop]; -+ -+ if (tmp1->size != tmp2->size) -+ error = gs_error_invalidaccess; -+ else { -+ if (tmp1->data && memcmp(tmp1->data, tmp2->data, tmp1->size) != 0) -+ error = gs_error_invalidaccess; -+ } -+ } -+ } -+ if (error < 0) -+ goto exit; -+ } - if(0 <= error) error |= UPD_PUT_STRING_A; - UPD_MM_DEL_APARAM(udev->memory, string_a[i]); - if(!value.size) { -@@ -2098,6 +2128,7 @@ transferred into the device-structure. In the case of "uniprint", this may - if(0 > code) error = code; - } - -+exit: - if(0 < error) { /* Actually something loaded without error */ - - if(!(upd = udev->upd)) { --- -2.40.0
meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33869-0001.patch deleted +0 -39
@@ -1,39 +0,0 @@ -From 5ae2e320d69a7d0973011796bd388cd5befa1a43 Mon Sep 17 00:00:00 2001 -From: Ken Sharp <[email protected]> -Date: Tue, 26 Mar 2024 12:02:57 +0000 -Subject: [PATCH 2/5] Bug #707691 - -Part 1; when stripping a potential Current Working Dirctory specifier -from a path, make certain it really is a CWD, and not simply large -ebough to be a CWD. - -Reasons are in the bug thread, this is not (IMO) serious. - -This is part of the fix for CVE-2024-33869 - -CVE: CVE-2024-33869 - -Upstream-Status: Backport [https://cgit.ghostscript.com/cgi-bin/cgit.cgi/ghostpdl.git/commit/?id=5ae2e320d69a7d0973] - -Signed-off-by: Archana Polampalli <[email protected]> ---- - base/gpmisc.c | 4 ++-- - 1 file changed, 2 insertions(+), 2 deletions(-) - -diff --git a/base/gpmisc.c b/base/gpmisc.c -index c4a69b0..1d4d5d8 100644 ---- a/base/gpmisc.c -+++ b/base/gpmisc.c -@@ -1164,8 +1164,8 @@ gp_validate_path_len(const gs_memory_t *mem, - - continue; - } -- else if (code < 0 && cdirstrl > 0 && prefix_len == 0 && buffer == bufferfull) { -- buffer = bufferfull + cdirstrl + dirsepstrl; -+ else if (code < 0 && cdirstrl > 0 && prefix_len == 0 && buffer == bufferfull -+ && memcmp(buffer, cdirstr, cdirstrl) && !memcmp(buffer + cdirstrl, dirsepstr, dirsepstrl)) { - continue; - } - break; --- -2.40.0
meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33869-0002.patch deleted +0 -52
52 lines not on this page · raw message
meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33870.patch deleted +0 -99
99 lines not on this page · raw message
meta/recipes-extended/ghostscript/ghostscript/CVE-2024-33871.patch deleted +0 -43
43 lines not on this page · raw message
meta/recipes-extended/ghostscript/ghostscript/avoid-host-contamination.patch +4 -7
@@ -1,7 +1,7 @@ -From 0ccbaa134093bf6afc79f2d20d061bca5a8754ed Mon Sep 17 00:00:00 2001 +From b36713c8f1ba0e5755b78845a433354a63663b1a Mon Sep 17 00:00:00 2001 From: Kai Kang <[email protected]> Date: Thu, 29 Mar 2018 16:02:05 +0800 -Subject: [PATCH 04/10] avoid host contamination +Subject: [PATCH] avoid host contamination Remove hardcode path refer to host to avoid host contamination.
@@ -15,10 +15,10 @@ Signed-off-by: Hongxu Jia <[email protected]> 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devices/devs.mak b/devices/devs.mak -index 846aa50..9570182 100644 +index 186f704..88ab8c9 100644 --- a/devices/devs.mak +++ b/devices/devs.mak -@@ -393,7 +393,7 @@ $(DEVOBJ)gdevxalt.$(OBJ) : $(DEVSRC)gdevxalt.c $(GDEVX) $(math__h) $(memory__h)\ +@@ -397,7 +397,7 @@ $(DEVOBJ)gdevxalt.$(OBJ) : $(DEVSRC)gdevxalt.c $(GDEVX) $(math__h) $(memory__h)\ ### NON PORTABLE, ONLY UNIX WITH GCC SUPPORT $(DEVOBJ)X11.so : $(x11alt_) $(x11_) $(DEVS_MAK) $(MAKEDIRS)
@@ -27,6 +27,3 @@ index 846aa50..9570182 100644 ###### --------------- Memory-buffered printer devices --------------- ###### --- -1.8.3.1 -
meta/recipes-extended/ghostscript/ghostscript/configure.ac-add-option-to-explicitly-disable-neon.patch deleted +0 -99
99 lines not on this page · raw message
meta/recipes-extended/ghostscript/ghostscript_10.03.1.bb renamed from meta/recipes-extended/ghostscript/ghostscript_10.02.1.bb +1 -7
@@ -25,15 +25,9 @@ def gs_verdir(v): SRC_URI = "https://github.com/ArtifexSoftware/ghostpdl-downloads/releases/download/gs${@gs_verdir("${PV}")}/${BPN}-${PV}.tar.gz \ file://ghostscript-9.16-Werror-return-type.patch \ file://avoid-host-contamination.patch \ - file://configure.ac-add-option-to-explicitly-disable-neon.patch \ - file://CVE-2024-33870.patch \ - file://CVE-2024-33869-0001.patch \ - file://CVE-2024-33869-0002.patch \ - file://CVE-2024-33871.patch \ - file://CVE-2024-29510.patch \ " -SRC_URI[sha256sum] = "e429e4f5b01615a4f0f93a4128e8a1a4d932dff983b1774174c79c0630717ad9" +SRC_URI[sha256sum] = "31cd01682ad23a801cc3bbc222a55f07c4ea3e068bdfb447792d54db21a2e8ad" PACKAGECONFIG ??= "" PACKAGECONFIG[gtk] = "--enable-gtk,--disable-gtk,gtk+3"
Signature · 1 line
2.34.1
PATCH 2/7 qemu: Upgrade 8.2.1 -> 8.2.2
In reply to Steve SakomanFrom: Xiangyu Chen <[email protected]>
This was a bugfix release, this version fixed several important fixes according to upstream.
Dropped CVE-2023-6683.patch since already contained the fix.
---
...u-native_8.2.1.bb => qemu-native_8.2.2.bb} | 0
...e_8.2.1.bb => qemu-system-native_8.2.2.bb} | 0
meta/recipes-devtools/qemu/qemu.inc | 3 +-
.../qemu/qemu/CVE-2023-6683.patch | 91 -------------------
.../qemu/{qemu_8.2.1.bb => qemu_8.2.2.bb} | 0
5 files changed, 1 insertion(+), 93 deletions(-)
rename meta/recipes-devtools/qemu/{qemu-native_8.2.1.bb => qemu-native_8.2.2.bb} (100%)
rename meta/recipes-devtools/qemu/{qemu-system-native_8.2.1.bb => qemu-system-native_8.2.2.bb} (100%)
delete mode 100644 meta/recipes-devtools/qemu/qemu/CVE-2023-6683.patch
rename meta/recipes-devtools/qemu/{qemu_8.2.1.bb => qemu_8.2.2.bb} (100%)meta/recipes-devtools/qemu/qemu-native_8.2.2.bb renamed from meta/recipes-devtools/qemu/qemu-native_8.2.1.bb +0 -0
meta/recipes-devtools/qemu/qemu-system-native_8.2.2.bb renamed from meta/recipes-devtools/qemu/qemu-system-native_8.2.1.bb +0 -0
meta/recipes-devtools/qemu/qemu.inc +1 -2
@@ -39,7 +39,6 @@ SRC_URI = "https://download.qemu.org/${BPN}-${PV}.tar.xz \ file://0003-linux-user-Add-strace-for-shmat.patch \ file://0004-linux-user-Rewrite-target_shmat.patch \ file://0005-tests-tcg-Check-that-shmat-does-not-break-proc-self-.patch \ - file://CVE-2023-6683.patch \ file://qemu-guest-agent.init \ file://qemu-guest-agent.udev \ file://CVE-2024-3446-01.patch \
@@ -63,7 +62,7 @@ SRC_URI:append:class-native = " \ file://0012-linux-user-workaround-for-missing-MAP_SHARED_VALIDAT.patch \ " -SRC_URI[sha256sum] = "8562751158175f9d187c5f22b57555abe3c870f0325c8ced12c34c6d987729be" +SRC_URI[sha256sum] = "847346c1b82c1a54b2c38f6edbd85549edeb17430b7d4d3da12620e2962bc4f3" CVE_STATUS[CVE-2007-0998] = "not-applicable-config: The VNC server can expose host files uder some circumstances. We don't enable it by default."
meta/recipes-devtools/qemu/qemu/CVE-2023-6683.patch deleted +0 -91
91 lines not on this page · raw message
meta/recipes-devtools/qemu/qemu_8.2.2.bb renamed from meta/recipes-devtools/qemu/qemu_8.2.1.bb +0 -0
Signature · 1 line
2.34.1
PATCH 3/7 apt-native: don't let dpkg overwrite files by default
In reply to Steve SakomanFrom: Changqing Li <[email protected]>
With --force-overwrite (implied by --force-all), dpkg will not abort when a package overwrites files from different packages. As this can also lead to "The following package disappeared from your system as all files have been overwritten by other packages: <package>" and subsequently broken dependencies, this makes the simple case of conflicting files hard to debug.
Instead of finding all possibly required force options, only disable overwrite for now.
Take back from https://git.openembedded.org/openembedded-core/commit/?id=4292387ef6c4e80428bad6a07c844a288b27d9a1
--- meta/recipes-devtools/apt/apt_2.6.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-devtools/apt/apt_2.6.1.bb +1 -1
@@ -111,7 +111,7 @@ Acquire AllowInsecureRepositories "true"; }; -DPkg::Options {"--root=#ROOTFS#";"--admindir=#ROOTFS#/var/lib/dpkg";"--force-all";"--no-debsig"}; +DPkg::Options {"--root=#ROOTFS#";"--admindir=#ROOTFS#/var/lib/dpkg";"--force-all";"--no-force-overwrite";"--no-debsig"}; DPkg::Path ""; EOF }
Signature · 1 line
2.34.1
PATCH 4/7 apt: runtime error: filename too long (tmpdir length)
In reply to Steve SakomanFrom: Changqing Li <[email protected]>
when the tmpdir dir is longer than 220, there is no files saved in tmp/sysroots/x86_64-linux/var/lib/apt/lists/ after run apt-get update, this is because apt-get uses the path as the file name, but the file name can't be longer than 255 according to /usr/include/linux/limits.h.
[YOCTO #2688]
Take back from https://git.openembedded.org/openembedded-core/commit/?id=9a0c0393871eda4bbcecfdd4b595f0c1b8e42edf
--- ...he-filename-can-t-be-longer-than-255.patch | 40 +++++++++++++++++++ meta/recipes-devtools/apt/apt_2.6.1.bb | 1 + 2 files changed, 41 insertions(+) create mode 100644 meta/recipes-devtools/apt/apt/0001-strutl.cc-the-filename-can-t-be-longer-than-255.patch
meta/recipes-devtools/apt/apt/0001-strutl.cc-the-filename-can-t-be-longer-than-255.patch new file +40 -0
@@ -0,0 +1,40 @@ +From 918295aa1320718d342116f76c98d2289d377800 Mon Sep 17 00:00:00 2001 +From: Changqing Li <[email protected]> +Date: Tue, 18 Jun 2024 10:32:55 +0800 +Subject: [PATCH] strutl.cc: the filename can't be longer than 255 + +The URItoFileName translates the path into the filename, but the +filename can't be longer than 255 according to +/usr/include/linux/limits.h. + +Truncate it when it is longer than 240 (leave some spaces for +".Packages" and "._Release" suffix) + +Upstream-Status: Submitted [https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073591] +Signed-off-by: Robert Yang <[email protected]> +Signed-off-by: Changqing Li <[email protected]> +--- + apt-pkg/contrib/strutl.cc | 7 ++++++- + 1 file changed, 6 insertions(+), 1 deletion(-) + +diff --git a/apt-pkg/contrib/strutl.cc b/apt-pkg/contrib/strutl.cc +index 67100f1..5076b35 100644 +--- a/apt-pkg/contrib/strutl.cc ++++ b/apt-pkg/contrib/strutl.cc +@@ -565,7 +565,12 @@ string URItoFileName(const string &URI) + // "\x00-\x20{}|\\\\^\\[\\]<>\"\x7F-\xFF"; + string NewURI = QuoteString(U,"\\|{}[]<>\"^~_=!@#$%^&*"); + replace(NewURI.begin(),NewURI.end(),'/','_'); +- return NewURI; ++ ++ // Truncate from the head when it is longer than 240 ++ if(NewURI.length() > 240) ++ return NewURI.substr(NewURI.length() - 240, NewURI.length() - 1); ++ else ++ return NewURI; + } + /*}}}*/ + // Base64Encode - Base64 Encoding routine for short strings /*{{{*/ +-- +2.25.1 +
meta/recipes-devtools/apt/apt_2.6.1.bb +1 -0
@@ -14,6 +14,7 @@ SRC_URI = "${DEBIAN_MIRROR}/main/a/apt/${BPN}_${PV}.tar.xz \ file://0001-Hide-fstatat64-and-prlimit64-defines-on-musl.patch \ file://0001-aptwebserver.cc-Include-array.patch \ file://0001-Remove-using-std-binary_function.patch \ + file://0001-strutl.cc-the-filename-can-t-be-longer-than-255.patch \ " SRC_URI:append:class-native = " \
Signature · 1 line
2.34.1
PATCH 5/7 flac: fix buildpaths warnings
In reply to Steve SakomanFrom: Peter Marko <[email protected]>
Generated documentation (html) contain absolute paths cources using buildpaths warnings.
Replace them with relative links.
The file with root path to sources is in my build /usr/share/doc/flac/api/dir_c122f5d6544f32779f55e8358fb78605.html which does not looks as stable name, so replace it in all files.
--- meta/recipes-multimedia/flac/flac_1.4.3.bb | 7 +++++++ 1 file changed, 7 insertions(+)
meta/recipes-multimedia/flac/flac_1.4.3.bb +7 -0
@@ -34,3 +34,10 @@ PACKAGES += "libflac libflac++" FILES:${PN} = "${bindir}/*" FILES:libflac = "${libdir}/libFLAC.so.*" FILES:libflac++ = "${libdir}/libFLAC++.so.*" + +do_install:append() { + # make the links in documentation relative to avoid buildpaths reproducibility problem + sed -i "s#${S}/include#${includedir}#g" ${D}${docdir}/flac/FLAC.tag ${D}${docdir}/flac/api/*.html + # there is also one root path without trailing slash + sed -i "s#${S}#/#g" ${D}${docdir}/flac/api/*.html +}
Signature · 1 line
2.34.1
PATCH 6/7 cargo: remove True option to getVar calls
In reply to Steve SakomanFrom: Peter Marko <[email protected]>
Layer cleanup similar to
https://git.openembedded.org/openembedded-core/commit/?id=26c74fd10614582e177437608908eb43688ab510
--- meta/classes-recipe/cargo_common.bbclass | 4 ++-- meta/classes-recipe/ptest-cargo.bbclass | 18 +++++++++--------- 2 files changed, 11 insertions(+), 11 deletions(-)
meta/classes-recipe/cargo_common.bbclass +2 -2
@@ -41,7 +41,7 @@ CARGO_SRC_DIR ??= "" CARGO_MANIFEST_PATH ??= "${S}/${CARGO_SRC_DIR}/Cargo.toml" # Path to Cargo.lock -CARGO_LOCK_PATH ??= "${@ os.path.join(os.path.dirname(d.getVar('CARGO_MANIFEST_PATH', True)), 'Cargo.lock')}" +CARGO_LOCK_PATH ??= "${@ os.path.join(os.path.dirname(d.getVar('CARGO_MANIFEST_PATH')), 'Cargo.lock')}" CARGO_RUST_TARGET_CCLD ??= "${RUST_TARGET_CCLD}" cargo_common_do_configure () {
@@ -171,7 +171,7 @@ python cargo_common_do_patch_paths() { # here is better than letting cargo tell (in case the file is missing) # "Cargo.lock should be modified but --frozen was given" - lockfile = d.getVar("CARGO_LOCK_PATH", True) + lockfile = d.getVar("CARGO_LOCK_PATH") if not os.path.exists(lockfile): bb.fatal(f"{lockfile} file doesn't exist")
meta/classes-recipe/ptest-cargo.bbclass +9 -9
@@ -12,10 +12,10 @@ python do_compile_ptest_cargo() { import subprocess import json - cargo = bb.utils.which(d.getVar("PATH"), d.getVar("CARGO", True)) - cargo_build_flags = d.getVar("CARGO_BUILD_FLAGS", True) - rust_flags = d.getVar("RUSTFLAGS", True) - manifest_path = d.getVar("CARGO_MANIFEST_PATH", True) + cargo = bb.utils.which(d.getVar("PATH"), d.getVar("CARGO")) + cargo_build_flags = d.getVar("CARGO_BUILD_FLAGS") + rust_flags = d.getVar("RUSTFLAGS") + manifest_path = d.getVar("CARGO_MANIFEST_PATH") project_manifest_path = os.path.normpath(manifest_path) manifest_dir = os.path.dirname(manifest_path)
@@ -66,7 +66,7 @@ python do_compile_ptest_cargo() { if not test_bins: bb.fatal("Unable to find any test binaries") - cargo_test_binaries_file = d.getVar('CARGO_TEST_BINARIES_FILES', True) + cargo_test_binaries_file = d.getVar('CARGO_TEST_BINARIES_FILES') bb.note(f"Found {len(test_bins)} tests, write their paths into {cargo_test_binaries_file}") with open(cargo_test_binaries_file, "w") as f: for test_bin in test_bins:
@@ -77,10 +77,10 @@ python do_compile_ptest_cargo() { python do_install_ptest_cargo() { import shutil - dest_dir = d.getVar("D", True) - pn = d.getVar("PN", True) - ptest_path = d.getVar("PTEST_PATH", True) - cargo_test_binaries_file = d.getVar('CARGO_TEST_BINARIES_FILES', True) + dest_dir = d.getVar("D") + pn = d.getVar("PN") + ptest_path = d.getVar("PTEST_PATH") + cargo_test_binaries_file = d.getVar('CARGO_TEST_BINARIES_FILES') rust_test_args = d.getVar('RUST_TEST_ARGS') or "" ptest_dir = os.path.join(dest_dir, ptest_path.lstrip('/'))
Signature · 1 line
2.34.1
PATCH 7/7 xz: Update LICENSE variable for xz packages
In reply to Steve SakomanFrom: aszh07 <[email protected]>
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.4.6/COPYING
https://github.com/tukaani-project/xz/blob/v5.4.6/PACKAGERS
--- meta/recipes-extended/xz/xz_5.4.6.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-extended/xz/xz_5.4.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.34.1