Skip to contentSkip to conversation

Patch review

PATCH New Steve Sakoman 1 participant 19 messages Nov 27, 2024

lore
Share & tools
lore
#0 lore raw

cover Patch review

Please review this set of changes for styhead and have comments back by end of day Thursday, November 28

Passed a-full on autobuilder:

https://valkyrie.yoctoproject.org/#/builders/29/builds/532

The following changes since commit 045d50e63bcaf13056ce749c616eecc4d4516958:

e2fsprogs: removed 'sed -u' option (2024-11-22 05:46:04 -0800)

are available in the Git repository at:

https://git.openembedded.org/openembedded-core-contrib stable/styhead-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/styhead-nut

Aleksandar Nikolic (1):
scripts/install-buildtools: Update to 5.1

Alexander Kanavin (3):
selftest/sstatetests: run CDN mirror check only once
package_rpm: use zstd's default compression level
package_rpm: restrict rpm to 4 threads

Bruce Ashfield (3):
linux-yocto/6.10: genericarm64.cfg: enable CONFIG_DMA_CMA linux-yocto/6.10: cfg: gpio: allow to re-enable the deprecated GPIO
sysfs interface
linux-yocto/6.10: bsp/genericarm64: disable ARM64_SME

Chen Qi (1):
shadow: use update-alternatives to handle groups.1

Jinfeng Wang (1):
tzdata/tzcode-native: upgrade 2024a -> 2024b

Kai Kang (1):
kexec-tools: update COMPATIBLE_HOST because of makedumpfile

Markus Volk (1):
gcc: add a backport patch to fix an issue with tzdata 2024b

Martin Jansa (1):
ffmpeg: fix packaging examples

Peter Marko (2):
cve-check: do not skip cve status description after :
cve-check: fix malformed cve status description with : characters

Richard Purdie (1):
openssl: Fix SDK environment script to avoid unbound variable

Vijay Anusuri (1):
xwayland: upgrade 24.1.3 -> 24.1.4

Wang Mingyu (1):
xwayland: upgrade 24.1.2 -> 24.1.3

Yi Zhao (1):
systemd: fix broken links for sysvinit-compatible commands

 meta/classes-global/package_rpm.bbclass       |   3 +-
 meta/lib/oe/cve_check.py                      |   4 +-
 meta/lib/oeqa/selftest/cases/sstatetests.py   |   2 -
 .../openssl/files/environment.d-openssl.sh    |   2 +-
 .../packagegroup-core-tools-testapps.bb       |   1 +
 meta/recipes-core/systemd/systemd_256.5.bb    |   6 +-
 meta/recipes-devtools/gcc/gcc-14.2.inc        |   1 +
 ...4fffe3fc82a710bea66ad651720d71c938b8.patch | 549 ++++++++++++++++++
 meta/recipes-extended/shadow/shadow.inc       |   3 +-
 meta/recipes-extended/timezone/timezone.inc   |   6 +-
 ...{xwayland_24.1.2.bb => xwayland_24.1.4.bb} |   2 +-
 .../kexec/kexec-tools_2.0.29.bb               |   3 +
 .../linux/linux-yocto-rt_6.10.bb              |   2 +-
 .../linux/linux-yocto-tiny_6.10.bb            |   2 +-
 meta/recipes-kernel/linux/linux-yocto_6.10.bb |   2 +-
 .../recipes-multimedia/ffmpeg/ffmpeg_7.0.2.bb |   2 +-
 scripts/install-buildtools                    |   4 +-
 17 files changed, 575 insertions(+), 19 deletions(-)
 create mode 100644 meta/recipes-devtools/gcc/gcc/gcc.git-ab884fffe3fc82a710bea66ad651720d71c938b8.patch
 rename meta/recipes-graphics/xwayland/{xwayland_24.1.2.bb => xwayland_24.1.4.bb} (96%)
Signature · 1 line
2.34.1
#1 lore raw

PATCH 1/18 cve-check: do not skip cve status description after :

From: Peter Marko <[email protected]>

Correct maxsplit parameter from 5 to 4 to not drop text if description contains ":".

Example:

Quoted 1 line
Quoted 1 line
Quoted 1 line

"detail: cpe:vendor:product:description:cont".split(':', 5)

['detail', ' cpe', 'vendor', 'product', 'description', 'xxx']

Quoted 1 line
Quoted 1 line
Quoted 1 line

"detail: cpe:vendor:product:description:cont".split(':', 4)

['detail', ' cpe', 'vendor', 'product', 'description:xxx']

(cherry picked from commit 3c4d8ca41ac0b429af92bf0ea84f1dfd0cda9e1f)
---
 meta/lib/oe/cve_check.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/lib/oe/cve_check.py +1 -1
index 487f30dc25..268adfb528 100644
@@ -239,7 +239,7 @@ def decode_cve_status(d, cve):
     if not status:
         return {}
 
-    status_split = status.split(':', 5)
+    status_split = status.split(':', 4)
     status_out = {}
     status_out["detail"] = status_split[0]
     product = "*"
Signature · 1 line
2.34.1
#2 lore raw

PATCH 2/18 cve-check: fix malformed cve status description with : characters

In reply to Steve Sakoman

From: Peter Marko <[email protected]>

When CPE is not provided and character ":" is in cve status description, current code takes only last part of split function.
This works only if there is no ":" in description, otherwise it drops the other split parts.

Do a new split of the original string to take the whole description unchanged. This fixes following entries from world build of poky+meta-oe+meta-python:

tiff-4.6.0-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2015-7313
CVE_STATUS:  fixed-version: Tested with check from https://security-tracker.debian.org/tracker/CVE-2015-7313 and already 4.3.0 doesn't have the issue
description: //security-tracker.debian.org/tracker/CVE-2015-7313 and already 4.3.0 doesn't have the issue
corrected:   Tested with check from https://security-tracker.debian.org/tracker/CVE-2015-7313 and already 4.3.0 doesn't have the issue
gnupg-2.5.0-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2022-3219
CVE_STATUS:  upstream-wontfix: Upstream doesn't seem to be keen on merging the proposed commit - https://dev.gnupg.org/T5993
description: //dev.gnupg.org/T5993
corrected:   Upstream doesn't seem to be keen on merging the proposed commit - https://dev.gnupg.org/T5993
libyaml-0.2.5-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2024-35325
CVE_STATUS:  upstream-wontfix: Upstream thinks this is a misuse (or wrong use) of the libyaml API - https://github.com/yaml/libyaml/issues/303
description: //github.com/yaml/libyaml/issues/303
corrected:   Upstream thinks this is a misuse (or wrong use) of the libyaml API - https://github.com/yaml/libyaml/issues/303
libyaml-0.2.5-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2024-35326
CVE_STATUS:  upstream-wontfix: Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302
description: //github.com/yaml/libyaml/issues/302
corrected:   Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302
libyaml-0.2.5-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2024-35328
CVE_STATUS:  upstream-wontfix: Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302
description: //github.com/yaml/libyaml/issues/302
corrected:   Upstream thinks there is no working code that is exploitable - https://github.com/yaml/libyaml/issues/302
cpio-2.15-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2023-7216
CVE_STATUS:  disputed: intended behaviour, see https://lists.gnu.org/archive/html/bug-cpio/2024-03/msg00000.html
description: //lists.gnu.org/archive/html/bug-cpio/2024-03/msg00000.html
corrected:   intended behaviour, see https://lists.gnu.org/archive/html/bug-cpio/2024-03/msg00000.html
openssh-9.9p1-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2023-51767
CVE_STATUS:  upstream-wontfix: It was demonstrated on modified sshd and does not exist in upstream openssh https://bugzilla.mindrot.org/show_bug.cgi?id=3656#c1.
description: //bugzilla.mindrot.org/show_bug.cgi?id=3656#c1.
corrected:   It was demonstrated on modified sshd and does not exist in upstream openssh https://bugzilla.mindrot.org/show_bug.cgi?id=3656#c1.
cups-2.4.10-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2021-25317
CVE_STATUS:  not-applicable-config: This concerns /var/log/cups having lp ownership, our /var/log/cups is root:root, so this doesn't apply.
description: root, so this doesn't apply.
corrected:   This concerns /var/log/cups having lp ownership, our /var/log/cups is root:root, so this doesn't apply.
unzip-1_6.0-r0 do_cve_check: CVE_STATUS with 3 parts for CVE-2008-0888
CVE_STATUS:  fixed-version: Patch from https://bugzilla.redhat.com/attachment.cgi?id=293893&action=diff applied to 6.0 source
description: //bugzilla.redhat.com/attachment.cgi?id=293893&action=diff applied to 6.0 source
corrected:   Patch from https://bugzilla.redhat.com/attachment.cgi?id=293893&action=diff applied to 6.0 source
syslog-ng-4.7.0-r0 do_cve_check: CVE_STATUS with 6 parts for CVE-2022-38725
CVE_STATUS:  cpe-incorrect: cve-check wrongly matches cpe:2.3:a:oneidentity:syslog-ng:*:*:*:*:premium:*:*:* < 7.0.32
description: syslog-ng:*:*:*:*:premium:*:*:* < 7.0.32
corrected:   cve-check wrongly matches cpe:2.3:a:oneidentity:syslog-ng:*:*:*:*:premium:*:*:* < 7.0.32
(cherry picked from commit cc33dd9176726cb4b2d2f142ed1bc655da8e0a9f)
---
 meta/lib/oe/cve_check.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/lib/oe/cve_check.py +1 -1
index 268adfb528..647a94f5af 100644
@@ -257,7 +257,7 @@ def decode_cve_status(d, cve):
     else:
         # Other case: no CPE, the syntax is then:
         # detail: description
-        description = status_split[len(status_split)-1].strip() if (len(status_split) > 1) else ""
+        description = status.split(':', 1)[1].strip() if (len(status_split) > 1) else ""
 
     status_out["vendor"] = vendor
     status_out["product"] = product
Signature · 1 line
2.34.1
#3 lore raw

PATCH 3/18 tzdata/tzcode-native: upgrade 2024a -> 2024b

In reply to Steve Sakoman

From: Jinfeng Wang <[email protected]>

(cherry picked from commit b84b29b1827624270cc1698feda2ee87d55c01e4)
---
 meta/recipes-extended/timezone/timezone.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
meta/recipes-extended/timezone/timezone.inc +3 -3
index 4734adcc08..adf095280f 100644
@@ -6,7 +6,7 @@ SECTION = "base"
 LICENSE = "PD & BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=c679c9d6b02bc2757b3eaf8f53c43fba"
 
-PV = "2024a"
+PV = "2024b"
 
 SRC_URI =" http://www.iana.org/time-zones/repository/releases/tzcode${PV}.tar.gz;name=tzcode;subdir=tz \
            http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata;subdir=tz \
@@ -16,5 +16,5 @@ S = "${WORKDIR}/tz"
 
 UPSTREAM_CHECK_URI = "http://www.iana.org/time-zones"
 
-SRC_URI[tzcode.sha256sum] = "80072894adff5a458f1d143e16e4ca1d8b2a122c9c5399da482cb68cba6a1ff8"
-SRC_URI[tzdata.sha256sum] = "0d0434459acbd2059a7a8da1f3304a84a86591f6ed69c6248fffa502b6edffe3"
+SRC_URI[tzcode.sha256sum] = "5e438fc449624906af16a18ff4573739f0cda9862e5ec28d3bcb19cbaed0f672"
+SRC_URI[tzdata.sha256sum] = "70e754db126a8d0db3d16d6b4cb5f7ec1e04d5f261255e4558a67fe92d39e550"
Signature · 1 line
2.34.1
#4 lore raw

PATCH 4/18 xwayland: upgrade 24.1.2 -> 24.1.3

In reply to Steve Sakoman

From: Wang Mingyu <[email protected]>

(cherry picked from commit b42744482d5b883c04e81b4be56ef19bc27caa3f)
---
 .../xwayland/{xwayland_24.1.2.bb => xwayland_24.1.3.bb}         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/xwayland/{xwayland_24.1.2.bb => xwayland_24.1.3.bb} (96%)
meta/recipes-graphics/xwayland/xwayland_24.1.3.bb renamed from meta/recipes-graphics/xwayland/xwayland_24.1.2.bb +1 -1
similarity index 96%
rename from meta/recipes-graphics/xwayland/xwayland_24.1.2.bb
rename to meta/recipes-graphics/xwayland/xwayland_24.1.3.bb
index a3ece64348..7e817a7241 100644
@@ -10,7 +10,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=5df87950af51ac2c5822094553ea1880"
 
 SRC_URI = "https://www.x.org/archive/individual/xserver/xwayland-${PV}.tar.xz"
-SRC_URI[sha256sum] = "141eb76e7e422a3661c08782c70be40931084755042c04506e0d97dd463ef7d2"
+SRC_URI[sha256sum] = "dcdb57a66cc9b124c8f936760592628ac4e744a7d7b3179aa86189ad7ea4cb10"
 
 UPSTREAM_CHECK_REGEX = "xwayland-(?P<pver>\d+(\.(?!90\d)\d+)+)\.tar"
 
Signature · 1 line
2.34.1
#5 lore raw

PATCH 5/18 xwayland: upgrade 24.1.3 -> 24.1.4

In reply to Steve Sakoman

From: Vijay Anusuri <[email protected]>

Includes security fix CVE-2024-9632

Ref: https://lists.x.org/archives/xorg/2024-October/061766.html

(cherry picked from commit 3fdc716d1260b4a92a46cfd2059ce044447f9172)
---
 .../xwayland/{xwayland_24.1.3.bb => xwayland_24.1.4.bb}         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-graphics/xwayland/{xwayland_24.1.3.bb => xwayland_24.1.4.bb} (96%)
meta/recipes-graphics/xwayland/xwayland_24.1.4.bb renamed from meta/recipes-graphics/xwayland/xwayland_24.1.3.bb +1 -1
similarity index 96%
rename from meta/recipes-graphics/xwayland/xwayland_24.1.3.bb
rename to meta/recipes-graphics/xwayland/xwayland_24.1.4.bb
index 7e817a7241..6f8589ba5a 100644
@@ -10,7 +10,7 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=5df87950af51ac2c5822094553ea1880"
 
 SRC_URI = "https://www.x.org/archive/individual/xserver/xwayland-${PV}.tar.xz"
-SRC_URI[sha256sum] = "dcdb57a66cc9b124c8f936760592628ac4e744a7d7b3179aa86189ad7ea4cb10"
+SRC_URI[sha256sum] = "d96a78dbab819f55750173444444995b5031ebdcc15b77afebbd8dbc02af34f4"
 
 UPSTREAM_CHECK_REGEX = "xwayland-(?P<pver>\d+(\.(?!90\d)\d+)+)\.tar"
 
Signature · 1 line
2.34.1
#6 lore raw

PATCH 6/18 linux-yocto/6.10: genericarm64.cfg: enable CONFIG_DMA_CMA

In reply to Steve Sakoman

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

1/1 [
Author: Mikko Rapeli
Email: [email protected]
Subject: genericarm64.cfg: enable CONFIG_DMA_CMA
Date: Thu, 24 Oct 2024 08:49:29 +0300

It's needed for graphics on AMD KV260.

]

(cherry picked from commit 7d1572bce914ff67c3e08f95dfd8504b00b9a8e0)
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.10.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb +1 -1
index a1096f6a04..8f87a096ad 100644
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "3e91e02b6041d6720a5cf2f64323bb9b73f20765"
-SRCREV_meta ?= "83eed9befe28696b06fc5cc7bb31d81b27a7f325"
+SRCREV_meta ?= "0e4596272608c13c9e25bbefd6f27f213bac077d"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.10;destsuffix=${KMETA};protocol=https"
meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb +1 -1
index 50a461149d..abfee6953d 100644
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
-SRCREV_meta ?= "83eed9befe28696b06fc5cc7bb31d81b27a7f325"
+SRCREV_meta ?= "0e4596272608c13c9e25bbefd6f27f213bac077d"
 
 PV = "${LINUX_VERSION}+git"
 
meta/recipes-kernel/linux/linux-yocto_6.10.bb +1 -1
index 81898a4328..9b2334afd0 100644
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
 SRCREV_machine:qemux86-64 ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
 SRCREV_machine:qemumips64 ?= "61cac1396fe9250a4b7a5cc6ae3deb9dda4290c3"
 SRCREV_machine ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
-SRCREV_meta ?= "83eed9befe28696b06fc5cc7bb31d81b27a7f325"
+SRCREV_meta ?= "0e4596272608c13c9e25bbefd6f27f213bac077d"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
Signature · 1 line
2.34.1
#7 lore raw

PATCH 7/18 linux-yocto/6.10: cfg: gpio: allow to re-enable the deprecated GPIO sysfs interface

In reply to Steve Sakoman

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

1/1 [
Author: Bartosz Golaszewski
Email: [email protected]
Subject: gpio: allow to re-enable the deprecated GPIO sysfs interface
Date: Mon, 11 Nov 2024 14:08:23 +0100

The GPIO sysfs interface is disabled in standard linux config and in general users should use the character device instead but there are still programs out there that depend on it so for the time being add a kernel feature allowing to enable it.

]

(cherry picked from commit ae19861bfc336d869a7a84b13ab3e7b318e1b560)
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.10.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb +1 -1
index 8f87a096ad..fa78313a9e 100644
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "3e91e02b6041d6720a5cf2f64323bb9b73f20765"
-SRCREV_meta ?= "0e4596272608c13c9e25bbefd6f27f213bac077d"
+SRCREV_meta ?= "3a72fcf6df4fd9edc8c5933393be76cea6cb4a42"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.10;destsuffix=${KMETA};protocol=https"
meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb +1 -1
index abfee6953d..d21fd63d38 100644
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
-SRCREV_meta ?= "0e4596272608c13c9e25bbefd6f27f213bac077d"
+SRCREV_meta ?= "3a72fcf6df4fd9edc8c5933393be76cea6cb4a42"
 
 PV = "${LINUX_VERSION}+git"
 
meta/recipes-kernel/linux/linux-yocto_6.10.bb +1 -1
index 9b2334afd0..45d7bfd619 100644
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
 SRCREV_machine:qemux86-64 ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
 SRCREV_machine:qemumips64 ?= "61cac1396fe9250a4b7a5cc6ae3deb9dda4290c3"
 SRCREV_machine ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
-SRCREV_meta ?= "0e4596272608c13c9e25bbefd6f27f213bac077d"
+SRCREV_meta ?= "3a72fcf6df4fd9edc8c5933393be76cea6cb4a42"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
Signature · 1 line
2.34.1
#8 lore raw

PATCH 8/18 linux-yocto/6.10: bsp/genericarm64: disable ARM64_SME

In reply to Steve Sakoman

From: Bruce Ashfield <[email protected]>

Integrating the following commit(s) to linux-yocto/.:

1/1 [
Author: Ross Burton
Email: [email protected]
Subject: bsp/genericarm64: disable ARM64_SME
Date: Thu, 21 Nov 2024 15:53:35 +0000

From upstream:

arm64: Kconfig: Make SME depend on BROKEN for now

commit 81235ae0c846e1fb46a2c6fe9283fe2b2b24f7dc upstream.

Although support for SME was merged in v5.19, we've since uncovered a number of issues with the implementation, including issues which might corrupt the FPSIMD/SVE/SME state of arbitrary tasks. While there are patches to address some of these issues, ongoing review has highlighted additional functional problems, and more time is necessary to analyse and fix these.

For now, mark SME as BROKEN in the hope that we can fix things properly in the near future. As SME is an OPTIONAL part of ARMv9.2+, and there is very little extant hardware, this should not adversely affect the vast majority of users.

]

(cherry picked from commit 022f9814cb9d6d420e9d89a746f4c67b452c498f)
---
 meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb   | 2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb | 2 +-
 meta/recipes-kernel/linux/linux-yocto_6.10.bb      | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)
meta/recipes-kernel/linux/linux-yocto-rt_6.10.bb +1 -1
index fa78313a9e..7c0425bb27 100644
@@ -15,7 +15,7 @@ python () {
 }
 
 SRCREV_machine ?= "3e91e02b6041d6720a5cf2f64323bb9b73f20765"
-SRCREV_meta ?= "3a72fcf6df4fd9edc8c5933393be76cea6cb4a42"
+SRCREV_meta ?= "af06ad75b8da89e99d2cc0090ce2a7877ef51391"
 
 SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine;protocol=https \
            git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-6.10;destsuffix=${KMETA};protocol=https"
meta/recipes-kernel/linux/linux-yocto-tiny_6.10.bb +1 -1
index d21fd63d38..891dcb596a 100644
@@ -18,7 +18,7 @@ KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
-SRCREV_meta ?= "3a72fcf6df4fd9edc8c5933393be76cea6cb4a42"
+SRCREV_meta ?= "af06ad75b8da89e99d2cc0090ce2a7877ef51391"
 
 PV = "${LINUX_VERSION}+git"
 
meta/recipes-kernel/linux/linux-yocto_6.10.bb +1 -1
index 45d7bfd619..3718077ea9 100644
@@ -29,7 +29,7 @@ SRCREV_machine:qemux86 ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
 SRCREV_machine:qemux86-64 ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
 SRCREV_machine:qemumips64 ?= "61cac1396fe9250a4b7a5cc6ae3deb9dda4290c3"
 SRCREV_machine ?= "bbe3d1be4e9c03765cb4f93155eabfc0724d3bee"
-SRCREV_meta ?= "3a72fcf6df4fd9edc8c5933393be76cea6cb4a42"
+SRCREV_meta ?= "af06ad75b8da89e99d2cc0090ce2a7877ef51391"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and you'll
 # get the <version>/base branch, which is pure upstream -stable, and the same
Signature · 1 line
2.34.1
#9 lore raw

PATCH 9/18 scripts/install-buildtools: Update to 5.1

In reply to Steve Sakoman

From: Aleksandar Nikolic <[email protected]>

Update to the 5.1 release of the 5.1 series for buildtools.

---
 scripts/install-buildtools | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
scripts/install-buildtools +2 -2
index 92a4c9dfb1..6387287ade 100755
@@ -57,8 +57,8 @@ logger = scriptutils.logger_create(PROGNAME, stream=sys.stdout)
 
 DEFAULT_INSTALL_DIR = os.path.join(os.path.split(scripts_path)[0],'buildtools')
 DEFAULT_BASE_URL = 'https://downloads.yoctoproject.org/releases/yocto'
-DEFAULT_RELEASE = 'yocto-5.0.3'
-DEFAULT_INSTALLER_VERSION = '5.0.3'
+DEFAULT_RELEASE = 'yocto-5.1'
+DEFAULT_INSTALLER_VERSION = '5.1'
 DEFAULT_BUILDDATE = '202110XX'
 
 # Python version sanity check
Signature · 1 line
2.34.1
#10 lore raw

PATCH 10/18 systemd: fix broken links for sysvinit-compatible commands

In reply to Steve Sakoman

From: Yi Zhao <[email protected]>

Since commit[1], PACKAGECONFIG[sysvinit] is not enabled by default when sysvinit is not in DISTRO_FEATURES, which causes the following sysvinit-compatible commands/services to not be built and installed:

runlevel
telinit
rc-local.service
systemd-initctl
systemd-initctl.service
systemd-rc-local-generator
systemd-sysv-generator
systemd-update-utmp-runlevel.service

Therefore, links to these commands/services should only be created when PACKAGECONFIG[sysvinit] is enabled.

[1] https://git.openembedded.org/openembedded-core/commit/?id=3668235fd60a9027608f37251c4b453ed21b3687

(cherry picked from commit a20b698f1acdee972cf1ff570b09a2e2c36bef1a)
---
 meta/recipes-core/systemd/systemd_256.5.bb | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)
meta/recipes-core/systemd/systemd_256.5.bb +4 -2
index 68f15ab065..af810c0fcd 100644
@@ -339,7 +339,7 @@ do_install() {
 	install -d ${D}${systemd_system_unitdir}/rescue.target.wants
 
 	# Create symlinks for systemd-update-utmp-runlevel.service
-	if ${@bb.utils.contains('PACKAGECONFIG', 'utmp', 'true', 'false', d)}; then
+	if ${@bb.utils.contains('PACKAGECONFIG', 'utmp', 'true', 'false', d)} && ${@bb.utils.contains('PACKAGECONFIG', 'sysvinit', 'true', 'false', d)}; then
 		ln -sf ../systemd-update-utmp-runlevel.service ${D}${systemd_system_unitdir}/graphical.target.wants/systemd-update-utmp-runlevel.service
 		ln -sf ../systemd-update-utmp-runlevel.service ${D}${systemd_system_unitdir}/multi-user.target.wants/systemd-update-utmp-runlevel.service
 		ln -sf ../systemd-update-utmp-runlevel.service ${D}${systemd_system_unitdir}/poweroff.target.wants/systemd-update-utmp-runlevel.service
@@ -841,7 +841,9 @@ python do_warn_musl() {
 }
 addtask warn_musl before do_configure
 
-ALTERNATIVE:${PN} = "halt reboot shutdown poweroff runlevel ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'resolv-conf', '', d)}"
+ALTERNATIVE:${PN} = "halt reboot shutdown poweroff \
+                     ${@bb.utils.contains('PACKAGECONFIG', 'sysvinit', 'runlevel', '', d)} \
+                     ${@bb.utils.contains('PACKAGECONFIG', 'resolved', 'resolv-conf', '', d)}"
 
 ALTERNATIVE_TARGET[resolv-conf] = "${sysconfdir}/resolv-conf.systemd"
 ALTERNATIVE_LINK_NAME[resolv-conf] = "${sysconfdir}/resolv.conf"
Signature · 1 line
2.34.1
#11 lore raw

PATCH 11/18 ffmpeg: fix packaging examples

In reply to Steve Sakoman

From: Martin Jansa <[email protected]>

* I've noticed that ffmpeg package isn't created in my builds, due to --disable-programs in EXTRA_OECONF added by our .bbappend, but was surprised that lib32-ffmpeg is created.

* lib32-ffmpeg was created only because it contained the examples which are installed in /usr/share/ffmpeg even when PN is lib32-ffmpeg as we pass --datadir=${datadir}/ffmpeg in EXTRA_OECONF here

* --disable-programs controls ${bindir}/ffprobe ${bindir}/ffmpeg and ${datadir}/ffmpeg/ffprobe.xsd ${datadir}/ffmpeg/libvpx-*.ffpreset

(cherry picked from commit d7bf828b6431a254201675e41047f53da47912f5)
---
 meta/recipes-multimedia/ffmpeg/ffmpeg_7.0.2.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-multimedia/ffmpeg/ffmpeg_7.0.2.bb +1 -1
index bb6b71735c..db0aa60826 100644
@@ -182,6 +182,6 @@ FILES:libavutil = "${libdir}/libavutil${SOLIBS}"
 FILES:libpostproc = "${libdir}/libpostproc${SOLIBS}"
 FILES:libswresample = "${libdir}/libswresample${SOLIBS}"
 FILES:libswscale = "${libdir}/libswscale${SOLIBS}"
-FILES:${PN}-examples = "${datadir}/${PN}/examples"
+FILES:${PN}-examples = "${datadir}/${BPN}/examples"
 
 CVE_PRODUCT = "ffmpeg libswresample libavcodec"
Signature · 1 line
2.34.1
#12 lore raw

PATCH 12/18 shadow: use update-alternatives to handle groups.1

In reply to Steve Sakoman

From: Chen Qi <[email protected]>

This patch fixes the following error at do_rootfs:

update-alternatives: Error: not linking /PATH/TO/rootfs/usr/share /man/man1/groups.1 to /usr/share/man/man1/groups.1.coreutils since /PATH/TO/rootfs/usr/share/man/man1/groups.1 exists and is not a link

The problem can be reproduced by adding the following lines to local.conf and then building an image:

EXTRA_IMAGE_FEATURES:append = " doc-pkgs"
IMAGE_INSTALL:append = " shadow coreutils"

groups.1 is handled by update-alternatives in coreutils recipe, so do it in shadow recipe too.

(cherry picked from commit 78c8eb60097df2e16c699464c39ff9142fc1ae69)
---
 meta/recipes-extended/shadow/shadow.inc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
meta/recipes-extended/shadow/shadow.inc +2 -1
index b5e77b9874..171d6e27c3 100644
@@ -200,9 +200,10 @@ ALTERNATIVE_LINK_NAME[vipw] = "${base_sbindir}/vipw"
 ALTERNATIVE_LINK_NAME[vigr] = "${base_sbindir}/vigr"
 ALTERNATIVE_LINK_NAME[nologin] = "${base_sbindir}/nologin"
 
-ALTERNATIVE:${PN}-doc = "chfn.1 chsh.1"
+ALTERNATIVE:${PN}-doc = "chfn.1 chsh.1 groups.1"
 ALTERNATIVE_LINK_NAME[chfn.1] = "${mandir}/man1/chfn.1"
 ALTERNATIVE_LINK_NAME[chsh.1] = "${mandir}/man1/chsh.1"
+ALTERNATIVE_LINK_NAME[groups.1] = "${mandir}/man1/groups.1"
 
 ALTERNATIVE:${PN}-base = "newgrp groups login su"
 ALTERNATIVE_LINK_NAME[login] = "${base_bindir}/login"
Signature · 1 line
2.34.1
#13 lore raw

PATCH 13/18 openssl: Fix SDK environment script to avoid unbound variable

In reply to Steve Sakoman

From: Richard Purdie <[email protected]>

Avoid errors like:

buildtools/sysroots/x86_64-pokysdk-linux/environment-setup.d/openssl.sh: line 6: BB_ENV_PASSTHROUGH_ADDITIONS: unbound variable

by setting an explicit empty default value.

(cherry picked from commit 5a2a4910a22668f25679a47deaa9e2ed28665efa)
---
 .../recipes-connectivity/openssl/files/environment.d-openssl.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-connectivity/openssl/files/environment.d-openssl.sh +1 -1
index f90088aab7..aadf1edcb6 100644
@@ -3,4 +3,4 @@ export SSL_CERT_DIR="$OECORE_NATIVE_SYSROOT/usr/lib/ssl/certs"
 export SSL_CERT_FILE="$OECORE_NATIVE_SYSROOT/usr/lib/ssl/certs/ca-certificates.crt"
 export OPENSSL_MODULES="$OECORE_NATIVE_SYSROOT/usr/lib/ossl-modules/"
 export OPENSSL_ENGINES="$OECORE_NATIVE_SYSROOT/usr/lib/engines-3"
-export BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS SSL_CERT_DIR SSL_CERT_FILE OPENSSL_CONF OPENSSL_MODULES OPENSSL_ENGINES"
+export BB_ENV_PASSTHROUGH_ADDITIONS="${BB_ENV_PASSTHROUGH_ADDITIONS:-} SSL_CERT_DIR SSL_CERT_FILE OPENSSL_CONF OPENSSL_MODULES OPENSSL_ENGINES"
Signature · 1 line
2.34.1
#14 lore raw

PATCH 14/18 selftest/sstatetests: run CDN mirror check only once

In reply to Steve Sakoman

From: Alexander Kanavin <[email protected]>

The first no-fail check was an attempt to work around the old CDN's instability (and it didn't really help); it should not be necessary with the new CDN, and only delays a-full completion.

(cherry picked from commit 7f75c42b7fcf60a9ca58d3ded9047df675d76dc2)
---
 meta/lib/oeqa/selftest/cases/sstatetests.py | 2 --
 1 file changed, 2 deletions(-)
meta/lib/oeqa/selftest/cases/sstatetests.py +0 -2
index faaf7f6b0c..fa0172dd6d 100644
@@ -978,12 +978,10 @@ MACHINE = "{}"
 
     def test_cdn_mirror_qemux86_64(self):
         exceptions = []
-        self.run_test("qemux86-64", "core-image-minimal core-image-full-cmdline core-image-sato-sdk", exceptions, ignore_errors = True)
         self.run_test("qemux86-64", "core-image-minimal core-image-full-cmdline core-image-sato-sdk", exceptions)
 
     def test_cdn_mirror_qemuarm64(self):
         exceptions = []
-        self.run_test("qemuarm64", "core-image-minimal core-image-full-cmdline core-image-sato-sdk", exceptions, ignore_errors = True)
         self.run_test("qemuarm64", "core-image-minimal core-image-full-cmdline core-image-sato-sdk", exceptions)
 
     def test_local_cache_qemux86_64(self):
Signature · 1 line
2.34.1
#15 lore raw

PATCH 15/18 kexec-tools: update COMPATIBLE_HOST because of makedumpfile

In reply to Steve Sakoman

From: Kai Kang <[email protected]>

makedumpfile is not compatible with mipsarcho32 and riscv32, so set for kexec-tools accordingly.

And update packagegroup-core-tools-testapps too.

(cherry picked from commit 9107d9c09c7dab385c6034778cefadca3613be9c)
---
 .../packagegroups/packagegroup-core-tools-testapps.bb          | 1 +
 meta/recipes-kernel/kexec/kexec-tools_2.0.29.bb                | 3 +++
 2 files changed, 4 insertions(+)
meta/recipes-core/packagegroups/packagegroup-core-tools-testapps.bb +1 -0
index 34af40a43f..180660adab 100644
@@ -13,6 +13,7 @@ inherit packagegroup
 KEXECTOOLS ?= "kexec"
 KEXECTOOLS:e5500-64b ?= ""
 KEXECTOOLS:microblaze ?= ""
+KEXECTOOLS:mipsarcho32 ?= ""
 KEXECTOOLS:nios2 ?= ""
 KEXECTOOLS:riscv64 ?= ""
 KEXECTOOLS:riscv32 ?= ""
meta/recipes-kernel/kexec/kexec-tools_2.0.29.bb +3 -0
index 2c2901f19e..4edd6b2c65 100644
@@ -81,5 +81,8 @@ SYSTEMD_SERVICE:kdump = "kdump.service"
 SECURITY_PIE_CFLAGS:remove = "-fPIE -pie"
 
 COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|aarch64.*|powerpc.*|mips.*)-(linux|freebsd.*)'
+# makedumpfile would not compile on mips/rv32
+COMPATIBLE_HOST:mipsarcho32 = "null"
+COMPATIBLE_HOST:riscv32 = "null"
 
 INSANE_SKIP:${PN} = "arch"
Signature · 1 line
2.34.1
#16 lore raw

PATCH 16/18 gcc: add a backport patch to fix an issue with tzdata 2024b

In reply to Steve Sakoman

From: Markus Volk <[email protected]>

There is an issue in the std::chrono::tzdb parser that causes problems since the tzdata-2024b release started using %z in the main format.

As a real world problem I encounter an issue with the waybar clock module, which ignores the timezone setting and only shows system time.

(cherry picked from commit 39018429f05511053ab12e23e7f4487ea25ee529)
---
 meta/recipes-devtools/gcc/gcc-14.2.inc        |   1 +
 ...4fffe3fc82a710bea66ad651720d71c938b8.patch | 549 ++++++++++++++++++
 2 files changed, 550 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc/gcc.git-ab884fffe3fc82a710bea66ad651720d71c938b8.patch
meta/recipes-devtools/gcc/gcc-14.2.inc +1 -0
index f05484cfc0..9cfb246294 100644
@@ -68,6 +68,7 @@ SRC_URI = "${BASEURI} \
            file://0023-Fix-install-path-of-linux64.h.patch \
            file://0024-Avoid-hardcoded-build-paths-into-ppc-libgcc.patch \
            file://0025-gcc-testsuite-tweaks-for-mips-OE.patch \
+           file://gcc.git-ab884fffe3fc82a710bea66ad651720d71c938b8.patch \
 "
 
 S = "${TMPDIR}/work-shared/gcc-${PV}-${PR}/${SOURCEDIR}"
meta/recipes-devtools/gcc/gcc/gcc.git-ab884fffe3fc82a710bea66ad651720d71c938b8.patch new file +549 -0

549 lines not on this page · raw message

Signature · 1 line
2.34.1
#17 lore raw

PATCH 17/18 package_rpm: use zstd's default compression level

In reply to Steve Sakoman

From: Alexander Kanavin <[email protected]>

zstd uses 3 by default, while 19 is the highest and slowest. It's not clear why 19 was picked to begin with, possibly I copy-pasted it from rpm's examples without thinking:
https://git.yoctoproject.org/poky/commit/?h=master-next&id=4a4d5f78a6962dda5f63e9891825c80a8a87bf66

This brings significant speedups in rpm's compression step:
for example compressing webkitgtk takes 11s instead of 36s.

The rpm size increases from 175648k to 234860k. I think it's a worthy default tradeoff.

---
 meta/classes-global/package_rpm.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/classes-global/package_rpm.bbclass +1 -1
index ddc4bf3a6a..b2b7fafa17 100644
@@ -10,7 +10,7 @@ IMAGE_PKGTYPE ?= "rpm"
 
 RPM = "rpm"
 RPMBUILD = "rpmbuild"
-RPMBUILD_COMPMODE ?= "${@'w19T%d.zstdio' % int(d.getVar('ZSTD_THREADS'))}"
+RPMBUILD_COMPMODE ?= "${@'w3T%d.zstdio' % int(d.getVar('ZSTD_THREADS'))}"
 
 PKGWRITEDIRRPM = "${WORKDIR}/deploy-rpms"
 
Signature · 1 line
2.34.1
#18 lore raw

PATCH 18/18 package_rpm: restrict rpm to 4 threads

In reply to Steve Sakoman

From: Alexander Kanavin <[email protected]>

TL;DR version:

with this, and the previous compression level changes
I am seeing drastic speedups in package_write_rpm completion times:

webkitgtk goes from 78 seconds to 37 seconds glibc-locale goes from 399 seconds to 58 seconds (!)

The long version:

rpm uses multithreading for two purposes:

- spawning compressors (which are nowadays themselves multi-threaded, so the feature is not as useful as it once was)
- parallel file classification

While the former behaves well on massively parallel CPUs (it was written and verified here :), the latter was then added by upstream and only benchmarked on their very old, slow laptop, apparently:
https://github.com/rpm-software-management/rpm/commit/41f0e214f2266f02d6185ba11f797716de8125d4

On anything more capable it starts showing pathologic behavior, presumably from spawning massive amount of very short-lived threads, and then having to synchronize them. For example classifying glibc-locale takes
5m20s with 256 threads (default on my machine!)
1m49s with 64 threads
59s with 16 threads
48s with 8 threads

Even a more typical recipe like webkitgtk is affected:
47s with 256 threads
32s with 64 threads
27s with 16 or 8 threads

I have found that the optimal amount is actually four: this also means that only four compressors are running at a time, but as they're themselves using threads, and typical recipes are dominated by just two or three large packages, this does not affect overall completion time.

---
 meta/classes-global/package_rpm.bbclass | 1 +
 1 file changed, 1 insertion(+)
meta/classes-global/package_rpm.bbclass +1 -0
index b2b7fafa17..021c53593f 100644
@@ -696,6 +696,7 @@ python do_package_rpm () {
     cmd = cmd + " --define '_use_internal_dependency_generator 0'"
     cmd = cmd + " --define '_binaries_in_noarch_packages_terminate_build 0'"
     cmd = cmd + " --define '_build_id_links none'"
+    cmd = cmd + " --define '_smp_ncpus_max 4'"
     cmd = cmd + " --define '_source_payload %s'" % rpmbuild_compmode
     cmd = cmd + " --define '_binary_payload %s'" % rpmbuild_compmode
     cmd = cmd + " --define 'clamp_mtime_to_source_date_epoch 1'"
Signature · 1 line
2.34.1