[OE-core] [AUH] stress-ng: upgrading to 0.17.05 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.17.05* has
Succeeded.
Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.17.04-0.17.05.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 335f1157f467d76b979bd2db09073845f0dc1d46 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:53:47 +
Subject: [PATCH] stress-ng: upgrade 0.17.04 -> 0.17.05
---
.../stress-ng/{stress-ng_0.17.04.bb => stress-ng_0.17.05.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/stress-ng/{stress-ng_0.17.04.bb =>
stress-ng_0.17.05.bb} (94%)
diff --git a/meta/recipes-extended/stress-ng/stress-ng_0.17.04.bb
b/meta/recipes-extended/stress-ng/stress-ng_0.17.05.bb
similarity index 94%
rename from meta/recipes-extended/stress-ng/stress-ng_0.17.04.bb
rename to meta/recipes-extended/stress-ng/stress-ng_0.17.05.bb
index fde51f67ac..d4a427f89d 100644
--- a/meta/recipes-extended/stress-ng/stress-ng_0.17.04.bb
+++ b/meta/recipes-extended/stress-ng/stress-ng_0.17.05.bb
@@ -7,7 +7,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
SRC_URI =
"git://github.com/ColinIanKing/stress-ng.git;protocol=https;branch=master \
"
-SRCREV = "2f22ad595f067aa940cfe4f64107e10872c2f7b5"
+SRCREV = "4e68895f4fe68863b360ab4a6a57e2dfcff85d60"
S = "${WORKDIR}/git"
DEPENDS = "coreutils-native libbsd"
--
2.42.0
packages/core2-64-poky-linux/stress-ng: PV changed from "0.17.04" to "0.17.05"
packages/core2-64-poky-linux/stress-ng: PKGV changed from 0.17.04 [default] to
0.17.05 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-bash-completion: PV changed
from "0.17.04" to "0.17.05"
packages/core2-64-poky-linux/stress-ng/stress-ng-bash-completion: PKGV changed
from 0.17.04 [default] to 0.17.05 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-dbg: PV changed from "0.17.04"
to "0.17.05"
packages/core2-64-poky-linux/stress-ng/stress-ng-dbg: PKGV changed from 0.17.04
[default] to 0.17.05 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-dbg: PKGSIZE changed from
18575424 to 18752968 (+1%)
packages/core2-64-poky-linux/stress-ng/stress-ng-dev: PV changed from "0.17.04"
to "0.17.05"
packages/core2-64-poky-linux/stress-ng/stress-ng-dev: PKGV changed from 0.17.04
[default] to 0.17.05 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-doc: PV changed from "0.17.04"
to "0.17.05"
packages/core2-64-poky-linux/stress-ng/stress-ng-doc: PKGV changed from 0.17.04
[default] to 0.17.05 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-doc: PKGSIZE changed from
81049 to 83159 (+3%)
packages/core2-64-poky-linux/stress-ng/stress-ng-locale: PV changed from
"0.17.04" to "0.17.05"
packages/core2-64-poky-linux/stress-ng/stress-ng-locale: PKGV changed from
0.17.04 [default] to 0.17.05 [default]
packages/core2-64-poky-linux/stress-ng/stress-ng-src: PV changed from "0.17.04"
to "0.17.05"
packages/core2-64-poky-linux/stress-ng/stress-ng-src: FILELIST: removed
"/usr/src/debug/stress-ng/0.17.04/stress-ioprio.c
/usr/src/debug/stress-ng/0.17.04/stress-sigpending.c
/usr/src/debug/stress-ng/0.17.04/stress-led.c
/usr/src/debug/stress-ng/0.17.04/core-mincore.c
/usr/src/debug/stress-ng/0.17.04/stress-peterson.c
/usr/src/debug/stress-ng/0.17.04/core-mincore.h
/usr/src/debug/stress-ng/0.17.04/stress-rlimit.c
/usr/src/debug/stress-ng/0.17.04/stress-regs.c
/usr/src/debug/stress-ng/0.17.04/stress-fcntl.c
/usr/src/debug/stress-ng/0.17.04/stress-tlb-shootdown.c
/usr/src/debug/stress-ng/0.17.04/stress-judy.c
/usr/src/debug/stress-ng/0.17.04/stress-remap.c
/usr/src/debug/stress-ng/0.17.04/core-asm-x86.h
/usr/src/debug/stress-ng/0.17.04/stress-fifo.c
/usr/src/debug/stress-ng/0.17.04/stress-procfs.c
/usr/src/debug/stress-ng/0.17.04/stress-fiemap.c
/usr/src/debug/stress-ng/0.17.04/stress-msg.c
/usr/src/debug/stress-ng/0.17.04/stress-schedmix.c
/usr/src/debug/stress-ng/0.17.04/stress-skipl
ist.c /usr/src/debug/stress-ng/0.17.04/stress-exit-group.c
/usr/src/debug/stress-ng/0.17.04/stress-fpunch.c
/usr/src/debug/stress-ng/0.17.04/core-nt-store.h
/usr/src/debug/stress-ng/0.17.04/stress-ring-pipe.c
/usr/src/debug/stress-ng/0.17.04/stress-tee.c
[OE-core] [AUH] python3-hypothesis: upgrading to 6.98.5 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.98.5* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.97.3-6.98.5.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From c77ad97675788d190f03916efb61337b3f65de70 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:04:38 +
Subject: [PATCH] python3-hypothesis: upgrade 6.97.3 -> 6.98.5
---
...ython3-hypothesis_6.97.3.bb => python3-hypothesis_6.98.5.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-hypothesis_6.97.3.bb =>
python3-hypothesis_6.98.5.bb} (91%)
diff --git a/meta/recipes-devtools/python/python3-hypothesis_6.97.3.bb
b/meta/recipes-devtools/python/python3-hypothesis_6.98.5.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-hypothesis_6.97.3.bb
rename to meta/recipes-devtools/python/python3-hypothesis_6.98.5.bb
index c93727f36c..13b1387c05 100644
--- a/meta/recipes-devtools/python/python3-hypothesis_6.97.3.bb
+++ b/meta/recipes-devtools/python/python3-hypothesis_6.98.5.bb
@@ -13,7 +13,7 @@ SRC_URI += " \
file://test_rle.py \
"
-SRC_URI[sha256sum] =
"00216ddadaee17ba73451e262f973970a97d34fd75ec34ef57510147264c34d1"
+SRC_URI[sha256sum] =
"cfe4c2320580f97dd0d11cd3ee954a347764aec42aa0c95b7a0285c2b02447ab"
RDEPENDS:${PN} += " \
python3-attrs \
--
2.42.0
packages/core2-64-poky-linux/python3-hypothesis: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-6.97.3.tar.gz;downloadfilename=hypothesis-6.97.3.tar.gz
file://run-ptest file://test_binary_search.py file://test_rle.py" to
"https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-6.98.5.tar.gz;downloadfilename=hypothesis-6.98.5.tar.gz
file://run-ptest file://test_binary_search.py file://test_rle.py"
packages/core2-64-poky-linux/python3-hypothesis: PV changed from "6.97.3" to
"6.98.5"
packages/core2-64-poky-linux/python3-hypothesis: PKGV changed from 6.97.3
[default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PV
changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-dev: PV
changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-dev: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-doc: PV
changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-doc: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-locale: PV
changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-locale: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-ptest: PV
changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-ptest: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-src: PV
changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-src: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-staticdev:
PV changed from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis-staticdev:
PKGV changed from 6.97.3 [default] to 6.98.5 [default]
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis: PV changed
from "6.97.3" to "6.98.5"
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis: PKGSIZE
changed from 2875008 to 2935411 (+2%)
packages/core2-64-poky-linux/python3-hypothesis/python3-hypothesis: PKGV
changed from 6.97.3 [default] to 6.98.5 [default]
Changes to packages/core2-64-poky-linux/python3-hypothesis (sysroot):
[OE-core] [AUH] python3-urllib3: upgrading to 2.2.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-urllib3* to *2.2.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-urllib3-upgrade-2.1.0-2.2.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 03bb0b8fd3ebe4556e324f4aa5300a11db5dfc61 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:37:56 +
Subject: [PATCH] python3-urllib3: upgrade 2.1.0 -> 2.2.0
---
.../{python3-urllib3_2.1.0.bb => python3-urllib3_2.2.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-urllib3_2.1.0.bb =>
python3-urllib3_2.2.0.bb} (87%)
diff --git a/meta/recipes-devtools/python/python3-urllib3_2.1.0.bb
b/meta/recipes-devtools/python/python3-urllib3_2.2.0.bb
similarity index 87%
rename from meta/recipes-devtools/python/python3-urllib3_2.1.0.bb
rename to meta/recipes-devtools/python/python3-urllib3_2.2.0.bb
index b5b37e2924..294ad8026f 100644
--- a/meta/recipes-devtools/python/python3-urllib3_2.1.0.bb
+++ b/meta/recipes-devtools/python/python3-urllib3_2.2.0.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/shazow/urllib3;
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=52d273a3054ced561275d4d15260ecda"
-SRC_URI[sha256sum] =
"df7aa8afb0148fa78488e7899b2c59b5f4ffcfa82e6c54ccb9dd37c1d7b52d54"
+SRC_URI[sha256sum] =
"051d961ad0c62a94e50ecf1af379c3aba230c66c710493493560c0c223c49f20"
inherit pypi python_hatchling
--
2.42.0
packages/core2-64-poky-linux/python3-urllib3: PKGV changed from 2.1.0 [default]
to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3: PV changed from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/u/urllib3/urllib3-2.1.0.tar.gz;downloadfilename=urllib3-2.1.0.tar.gz;
to
"https://files.pythonhosted.org/packages/source/u/urllib3/urllib3-2.2.0.tar.gz;downloadfilename=urllib3-2.2.0.tar.gz;
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-dbg: PKGV changed
from 2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-dbg: PV changed
from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-dev: PKGV changed
from 2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-dev: PV changed
from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-doc: PKGV changed
from 2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-doc: PV changed
from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-locale: PKGV
changed from 2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-locale: PV changed
from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-src: PKGV changed
from 2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-src: PV changed
from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-staticdev: PKGV
changed from 2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3-staticdev: PV
changed from "2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3: PKGV changed from
2.1.0 [default] to 2.2.0 [default]
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3: PV changed from
"2.1.0" to "2.2.0"
packages/core2-64-poky-linux/python3-urllib3/python3-urllib3: FILELIST:
directory renamed /usr/lib/python3.12/site-packages/urllib3-2.1.0.dist-info ->
/usr/lib/python3.12/site-packages/urllib3-2.2.0.dist-info, directory renamed
/usr/lib/python3.12/site-packages/urllib3-2.1.0.dist-info/licenses ->
/usr/lib/python3.12/site-packages/urllib3-2.2.0.dist-info/licenses, added
"/usr/lib/python3.12/site-packages/urllib3/contrib/emscripten/__pycache__/fetch.cpython-312.pyc
/usr/lib/python3.12/site-packages/urllib3/contrib/emscripten/__pycache__/__init__.cpython-312.pyc
/usr/lib/python3.12/site-packages/urllib3/contrib/emscripten/__pycache__/connection.cpython-312.pyc
[OE-core] [AUH] gstreamer1.0-libav: upgrading to 1.22.10 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-libav* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-libav-upgrade-1.22.9-1.22.10.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 7da9baccebbdcaf00196c8a9dac24e4f43e3e466 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 14:47:16 +
Subject: [PATCH] gstreamer1.0-libav: upgrade 1.22.9 -> 1.22.10
---
...treamer1.0-libav_1.22.9.bb => gstreamer1.0-libav_1.22.10.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-libav_1.22.9.bb =>
gstreamer1.0-libav_1.22.10.bb} (91%)
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.9.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.10.bb
similarity index 91%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.9.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.10.bb
index 10536acc87..818dbf4e5e 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.9.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.10.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=69333daa044cb77e486cc36129f7a770 \
"
SRC_URI =
"https://gstreamer.freedesktop.org/src/gst-libav/gst-libav-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"192f7d27d21c1e7c72c339a2647a9b0c247fedc62ea5029115f8c3e22ebb87d8"
+SRC_URI[sha256sum] =
"d6dda7aa38a44173278de675ccd92acff0abf473f7bc02e7d1cdd4ce0f3b7642"
S = "${WORKDIR}/gst-libav-${PV}"
--
2.42.0
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-dbg: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-dbg: PKGSIZE
changed from 856816 to 856848 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-dbg: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-dev: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-dev: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-doc: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-doc: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-locale: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-locale: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-src: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-src: PKGSIZE
changed from 500246 to 500358 (+0%)
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-src: PV
changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-staticdev:
PKGV changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav-staticdev:
PV changed from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav: PKGV
changed from 1.22.9 [default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav/gstreamer1.0-libav: PV changed
from "1.22.9" to "1.22.10"
packages/core2-64-poky-linux/gstreamer1.0-libav: PKGV changed from 1.22.9
[default] to 1.22.10 [default]
packages/core2-64-poky-linux/gstreamer1.0-libav: SRC_URI changed from
"https://gstreamer.freedesktop.org/src/gst-libav/gst-libav-1.22.9.tar.xz; to
"https://gstreamer.freedesktop.org/src/gst-libav/gst-libav-1.22.10.tar.xz;
packages/core2-64-poky-linux/gstreamer1.0-libav: PV changed from "1.22.9" to
"1.22.10"
0001-gstreamer1.0-libav-upgrade-1.22.9-1.22.10.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195633):
https://lists.openembedded.org/g/openembedded-core/message/195633
Mute This Topic:
[OE-core] [AUH] lsof: upgrading to 4.99.3 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lsof* to *4.99.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-lsof-upgrade-4.98.0-4.99.3.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 58d5a11e0804ba67eba08091ea5dfe3cd043a232 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:34:36 +
Subject: [PATCH] lsof: upgrade 4.98.0 -> 4.99.3
---
.../lsof/files/remove-host-information.patch| 17 +
.../lsof/{lsof_4.98.0.bb => lsof_4.99.3.bb} | 2 +-
2 files changed, 14 insertions(+), 5 deletions(-)
rename meta/recipes-extended/lsof/{lsof_4.98.0.bb => lsof_4.99.3.bb} (96%)
diff --git a/meta/recipes-extended/lsof/files/remove-host-information.patch
b/meta/recipes-extended/lsof/files/remove-host-information.patch
index fb90366ffa..cc35ef9f10 100644
--- a/meta/recipes-extended/lsof/files/remove-host-information.patch
+++ b/meta/recipes-extended/lsof/files/remove-host-information.patch
@@ -1,3 +1,8 @@
+From ec8776e505b6aab29c31056374f3ebff4473d82a Mon Sep 17 00:00:00 2001
+From: Ross Burton
+Date: Wed, 30 Aug 2017 15:05:16 +0800
+Subject: [PATCH] lsof: remove host information from version.h
+
lsof doesn't embed the username or hostname in the build if SOURCE_DATE_EPOCH
is
defined, but this still embeds build paths. Delete all of the host details to
ensure that no host information is leaked into the binary.
@@ -5,10 +10,14 @@ ensure that no host information is leaked into the binary.
Upstream-Status: Inappropriate
Signed-off-by: Ross Burton
-diff --git a/dialects/linux/Makefile b/dialects/linux/Makefile
-index 176a4c2..ef5a633 100644
a/dialects/linux/Makefile
-+++ b/dialects/linux/Makefile
+---
+ lib/dialects/linux/Makefile | 69 ++---
+ 1 file changed, 11 insertions(+), 58 deletions(-)
+
+diff --git a/lib/dialects/linux/Makefile b/lib/dialects/linux/Makefile
+index f8adaa6..7a79ca7 100644
+--- a/lib/dialects/linux/Makefile
b/lib/dialects/linux/Makefile
@@ -83,64 +83,17 @@ ${LIB}: FRC
version.h:FRC
@echo Constructing version.h
diff --git a/meta/recipes-extended/lsof/lsof_4.98.0.bb
b/meta/recipes-extended/lsof/lsof_4.99.3.bb
similarity index 96%
rename from meta/recipes-extended/lsof/lsof_4.98.0.bb
rename to meta/recipes-extended/lsof/lsof_4.99.3.bb
index 835ce3b8df..fadafc86dd 100644
--- a/meta/recipes-extended/lsof/lsof_4.98.0.bb
+++ b/meta/recipes-extended/lsof/lsof_4.99.3.bb
@@ -8,7 +8,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=a48ac97a8550eff12395a2c0d6151510"
SRC_URI = "git://github.com/lsof-org/lsof;branch=master;protocol=https \
file://remove-host-information.patch"
-SRCREV = "546eb1c9910e7c137fdff551683c35a736021e05"
+SRCREV = "2e4c7a1a9bc7258dc5b6a3ab28ebca44174279a8"
S = "${WORKDIR}/git"
--
2.42.0
0001-lsof-upgrade-4.98.0-4.99.3.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1857 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (913 cached, 1 parsed). 1857 targets, 35
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-64 sysroot...done.
Removing 1 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-f7c43ef513e7232ac77b0e4be16e650a71aa97d7"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:f7c43ef513e7232ac77b0e4be16e650a71aa97d7"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 107 Local 96 Mirrors 0 Missed 11 Current 194 (89% match,
96% complete)
done.
NOTE: Executing Tasks
NOTE: Running setscene task 232 of 301
[OE-core] [AUH] rust-llvm: upgrading to 1.76.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust-llvm* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust-llvm failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1860 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1860 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% || ETA: 0:04:14 Adding changed files: 0% || ETA: 0:03:04 Adding changed files: 0% || ETA: 0:02:44 Adding changed files: 1% || ETA: 0:02:38 Adding changed files: 1% || ETA: 0:02:35 Adding changed files: 1% || ETA: 0:02:27 Adding changed files: 1% || ETA: 0:02:22 Adding changed files: 2% || ETA: 0:02:19 Adding changed files: 2% || ETA: 0:02:17 Adding changed files: 2% || ETA: 0:02:15 Adding changed files: 3% |# | ETA: 0:02:14 Adding changed files: 3% |# | ETA: 0:02:14 Adding changed files: 3% |# | ETA: 0:02:12 Adding changed files: 3% |# | ETA: 0:02:12 Adding changed files: 4% |# | ETA: 0:02:11 Adding changed files: 4% |# | ETA: 0:02:10 Adding changed files: 4% |# | ETA: 0:02:10 Adding changed files: 4% |# | ETA: 0:02:09 Adding changed files: 5% |# | ETA: 0:02:09 Adding changed files: 5% |# | ETA: 0:02:08 Adding changed files: 5% |## | ETA: 0:02:07 Adding changed files: 6% |## | ETA: 0:02:07 Adding changed files: 6% |## | ETA: 0:02:06 Adding changed files: 6% |## | ETA: 0:02:05 Adding changed files: 6% |## | ETA: 0:02:05 Adding changed files: 7% |## | ETA: 0:02:04 Adding changed files: 7% |## | ETA: 0:02:03 Adding changed files: 7% |## |
[OE-core] [AUH] cargo: upgrading to 1.76.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cargo* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe cargo failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1858 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 3 seconds Loading cache...done. Loaded 1858 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% || ETA: 0:05:20 Adding changed files: 0% || ETA: 0:03:49 Adding changed files: 0% || ETA: 0:03:21 Adding changed files: 1% || ETA: 0:03:17 Adding changed files: 1% || ETA: 0:03:15 Adding changed files: 1% || ETA: 0:03:04 Adding changed files: 1% || ETA: 0:02:57 Adding changed files: 2% || ETA: 0:02:54 Adding changed files: 2% || ETA: 0:02:49 Adding changed files: 2% || ETA: 0:02:46 Adding changed files: 3% |# | ETA: 0:02:44 Adding changed files: 3% |# | ETA: 0:02:43 Adding changed files: 3% |# | ETA: 0:02:41 Adding changed files: 3% |# | ETA: 0:02:40 Adding changed files: 4% |# | ETA: 0:02:40 Adding changed files: 4% |# | ETA: 0:02:39 Adding changed files: 4% |# | ETA: 0:02:38 Adding changed files: 4% |# | ETA: 0:02:37 Adding changed files: 5% |# | ETA: 0:02:37 Adding changed files: 5% |# | ETA: 0:02:36 Adding changed files: 5% |## | ETA: 0:02:36 Adding changed files: 6% |## | ETA: 0:02:35 Adding changed files: 6% |## | ETA: 0:02:34 Adding changed files: 6% |## | ETA: 0:02:33 Adding changed files: 6% |## | ETA: 0:02:32 Adding changed files: 7% |## | ETA: 0:02:31 Adding changed files: 7% |## | ETA: 0:02:36 Adding changed files: 7% |## | ETA:
[OE-core] [AUH] ruby: upgrading to 3.3.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ruby* to *3.3.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe ruby failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 1% || ETA: 0:00:17 Adding changed files: 2% || ETA: 0:00:12 Adding changed files: 4% |# | ETA: 0:00:11 Adding changed files: 5% |# | ETA: 0:00:10 Adding changed files: 6% |## | ETA: 0:00:09 Adding changed files: 8% |## | ETA: 0:00:09 Adding changed files: 9% |### | ETA: 0:00:08 Adding changed files: 10% |### | ETA: 0:00:08 Adding changed files: 12% || ETA: 0:00:08 Adding changed files: 13% || ETA: 0:00:08 Adding changed files: 15% |# | ETA: 0:00:08 Adding changed files: 16% |# | ETA: 0:00:08 Adding changed files: 17% |## | ETA: 0:00:08 Adding changed files: 19% |## | ETA: 0:00:07 Adding changed files: 20% |### | ETA: 0:00:07 Adding changed files: 21% |### | ETA: 0:00:07 Adding changed files: 23% || ETA: 0:00:07 Adding changed files: 24% || ETA: 0:00:06 Adding changed files: 25% |# | ETA: 0:00:06 Adding changed files: 27% |# | ETA: 0:00:06 Adding changed files: 28% |## | ETA: 0:00:06 Adding changed files: 30% |## | ETA: 0:00:06 Adding changed files: 31% |### | ETA: 0:00:06 Adding changed files: 32% |### | ETA: 0:00:05 Adding changed files: 34% || ETA: 0:00:05 Adding changed files: 35% || ETA: 0:00:05 Adding changed files: 36% |# | ETA: 0:00:05 Adding changed files: 38% |# | ETA: 0:00:05
[OE-core] [AUH] xz: upgrading to 5.4.6 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *xz* to *5.4.6* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade xz -V 5.4.6 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-3db2ca1c9290d09e9f0a716b414c5682ce7a3a94" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:3db2ca1c9290d09e9f0a716b414c5682ce7a3a94" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-3db2ca1c9290d09e9f0a716b414c5682ce7a3a94" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:3db2ca1c9290d09e9f0a716b414c5682ce7a3a94" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks WARNING: Failed to fetch URL https://tukaani.org/xz/xz-5.4.6.tar.gz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 2 tasks of which 0 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds NOTE: The errors for this build are stored in /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215115739.txt You can send the errors to a reports server by running: send-error-report /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215115739.txt [-s server] NOTE: The contents of these logs will be posted in public if you use the above command with the default server. Please ensure you remove any identifying or proprietary information when prompted before sending. INFO: Extracting current version source... INFO: Adding local source files to srctree... INFO: Extracting upgraded version source... INFO: Fetching https://tukaani.org/xz/xz-5.4.6.tar.gz... ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export SSL_CERT_FILE="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; export GIT_SSL_CAINFO="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; export ftp_proxy="http://proxy.yocto.io:5187/;; export FTP_PROXY="http://proxy.yocto.io:5187/;; export PATH="/home/pokybuild/yocto-worker/auh/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/scripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-d6co23lc/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-d6co23lc/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-d6co23lc/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipe tool-d6co23lc/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-d6co23lc/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-d6co23lc/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/hosttools"; export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp --user-agent='Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0' -O
[OE-core] [AUH] python3-yamllint: upgrading to 1.34.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-yamllint* to *1.34.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-yamllint-upgrade-1.33.0-1.34.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 478afd488dec9ddf2bd4e2f254c792d9154034a8 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:43:08 +
Subject: [PATCH] python3-yamllint: upgrade 1.33.0 -> 1.34.0
---
.../{python3-yamllint_1.33.0.bb => python3-yamllint_1.34.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-yamllint_1.33.0.bb =>
python3-yamllint_1.34.0.bb} (81%)
diff --git a/meta/recipes-devtools/python/python3-yamllint_1.33.0.bb
b/meta/recipes-devtools/python/python3-yamllint_1.34.0.bb
similarity index 81%
rename from meta/recipes-devtools/python/python3-yamllint_1.33.0.bb
rename to meta/recipes-devtools/python/python3-yamllint_1.34.0.bb
index 7e51fc9395..b3b29a0264 100644
--- a/meta/recipes-devtools/python/python3-yamllint_1.33.0.bb
+++ b/meta/recipes-devtools/python/python3-yamllint_1.34.0.bb
@@ -7,7 +7,7 @@ inherit pypi setuptools3
PYPI_PACKAGE = "yamllint"
-SRC_URI[sha256sum] =
"2dceab9ef2d99518a2fcf4ffc964d44250ac4459be1ba3ca315118e4a1a81f7d"
+SRC_URI[sha256sum] =
"7f0a6a41e8aab3904878da4ae34b6248b6bc74634e0d3a90f0fb2d7e723a3d4f"
DEPENDS += "${PYTHON_PN}-setuptools-scm-native"
RDEPENDS:${PN} += "${PYTHON_PN}-pathspec ${PYTHON_PN}-pyyaml"
--
2.42.0
packages/core2-64-poky-linux/python3-yamllint: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/y/yamllint/yamllint-1.33.0.tar.gz;downloadfilename=yamllint-1.33.0.tar.gz;
to
"https://files.pythonhosted.org/packages/source/y/yamllint/yamllint-1.34.0.tar.gz;downloadfilename=yamllint-1.34.0.tar.gz;
packages/core2-64-poky-linux/python3-yamllint: PV changed from "1.33.0" to
"1.34.0"
packages/core2-64-poky-linux/python3-yamllint: PKGV changed from 1.33.0
[default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-dbg: PV changed
from "1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-dbg: PKGV
changed from 1.33.0 [default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-dev: PV changed
from "1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-dev: PKGV
changed from 1.33.0 [default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-doc: PV changed
from "1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-doc: PKGV
changed from 1.33.0 [default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-locale: PV
changed from "1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-locale: PKGV
changed from 1.33.0 [default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-src: PV changed
from "1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-src: PKGV
changed from 1.33.0 [default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-staticdev: PV
changed from "1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint-staticdev: PKGV
changed from 1.33.0 [default] to 1.34.0 [default]
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint: PV changed from
"1.33.0" to "1.34.0"
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint: PKGSIZE changed
from 332055 to 341328 (+3%)
packages/core2-64-poky-linux/python3-yamllint/python3-yamllint: PKGV changed
from 1.33.0 [default] to 1.34.0 [default]
Changes to packages/core2-64-poky-linux/python3-yamllint (sysroot):
/usr/lib/python3.12/site-packages/yamllint-1.33.0.dist-info moved to
/usr/lib/python3.12/site-packages/yamllint-1.34.0.dist-info
0001-python3-yamllint-upgrade-1.33.0-1.34.0.patch
Description: Binary data
Changes to packages/core2-64-poky-linux/python3-yamllint (sysroot):
/usr/lib/python3.12/site-packages/yamllint-1.33.0.dist-info moved to
/usr/lib/python3.12/site-packages/yamllint-1.34.0.dist-info
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all
[OE-core] [AUH] man-pages: upgrading to 6.06 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *man-pages* to *6.06* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-man-pages-upgrade-6.05.01-6.06.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From d31ddf5e37d4771171aaee911cdc7cb32c1917f0 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 11:36:26 +
Subject: [PATCH] man-pages: upgrade 6.05.01 -> 6.06
---
...man-pages_6.05.01.bb => man-pages_6.06.bb} | 109 +-
1 file changed, 105 insertions(+), 4 deletions(-)
rename meta/recipes-extended/man-pages/{man-pages_6.05.01.bb =>
man-pages_6.06.bb} (28%)
diff --git a/meta/recipes-extended/man-pages/man-pages_6.05.01.bb
b/meta/recipes-extended/man-pages/man-pages_6.06.bb
similarity index 28%
rename from meta/recipes-extended/man-pages/man-pages_6.05.01.bb
rename to meta/recipes-extended/man-pages/man-pages_6.06.bb
index f0eb1a6132..43f0d1fa54 100644
--- a/meta/recipes-extended/man-pages/man-pages_6.05.01.bb
+++ b/meta/recipes-extended/man-pages/man-pages_6.06.bb
@@ -1,12 +1,113 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- README
+# +++ README
+# @@ -17,6 +17,7 @@
+#
+# Files
+# CONTRIBUTING
+# + CONTRIBUTING.d/*
+# Instructions for reporting bugs and contributing.
+#
+# INSTALL
+# @@ -35,15 +36,12 @@
+# Change log. Includes most relevant changes. However, it's not
+# as complete as the git(1) log.
+#
+# - Makefile, share/mk/*
+# + GNUmakefile, share/mk/*
+# Build system. For help, consult the file, and run
+# 'make help'.
+#
+# lsm
+# Linux software map. See also
+#
+# History
+# Tarballs
+# @@ -83,7 +81,7 @@
+# .
+# + .
+#
+# Downstream packages
+# Arch man-pages
+# --- LICENSES/BSD-2-Clause.txt
+# +++ LICENSES/BSD-2-Clause.txt
+# @@ -1,4 +1,4 @@
+# -Copyright (c)
+# +Copyright (c)
+#
+# Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
+#
+# --- LICENSES/BSD-3-Clause.txt
+# +++ LICENSES/BSD-3-Clause.txt
+# @@ -1,4 +1,4
[OE-core] [AUH] python3-trove-classifiers: upgrading to 2024.1.31 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-trove-classifiers* to
*2024.1.31* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-trove-classifiers-upgrade-2024.1.8-2024.1.31.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 24d2c6f853bfa82e411fb00a2bfbff91e9bd5e4f Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:32:34 +
Subject: [PATCH] python3-trove-classifiers: upgrade 2024.1.8 -> 2024.1.31
---
...fiers_2024.1.8.bb => python3-trove-classifiers_2024.1.31.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-trove-classifiers_2024.1.8.bb =>
python3-trove-classifiers_2024.1.31.bb} (87%)
diff --git a/meta/recipes-devtools/python/python3-trove-classifiers_2024.1.8.bb
b/meta/recipes-devtools/python/python3-trove-classifiers_2024.1.31.bb
similarity index 87%
rename from meta/recipes-devtools/python/python3-trove-classifiers_2024.1.8.bb
rename to meta/recipes-devtools/python/python3-trove-classifiers_2024.1.31.bb
index 9e7e61a37e..332ab3bf40 100644
--- a/meta/recipes-devtools/python/python3-trove-classifiers_2024.1.8.bb
+++ b/meta/recipes-devtools/python/python3-trove-classifiers_2024.1.31.bb
@@ -3,7 +3,7 @@ HOMEPAGE = "https://github.com/pypa/trove-classifiers;
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
-SRC_URI[sha256sum] =
"6e36caf430ff6485c4b57a4c6b364a13f6a898d16b9417c6c37467e59c14b05a"
+SRC_URI[sha256sum] =
"bfdfe60bbf64985c524416afb637ecc79c558e0beb4b7f52b0039e01044b0229"
inherit pypi python_setuptools_build_meta ptest
--
2.42.0
0001-python3-trove-classifiers-upgrade-2024.1.8-2024.1.31.patch
Description: Binary data
packages/core2-64-poky-linux/python3-trove-classifiers: PKGV changed from
2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/t/trove-classifiers/trove-classifiers-2024.1.8.tar.gz;downloadfilename=trove-classifiers-2024.1.8.tar.gz
file://run-ptest" to
"https://files.pythonhosted.org/packages/source/t/trove-classifiers/trove-classifiers-2024.1.31.tar.gz;downloadfilename=trove-classifiers-2024.1.31.tar.gz
file://run-ptest"
packages/core2-64-poky-linux/python3-trove-classifiers: PV changed from
"2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-dbg:
PV changed from "2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-dbg:
PKGV changed from 2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-dev:
PV changed from "2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-dev:
PKGV changed from 2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-doc:
PV changed from "2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-doc:
PKGV changed from 2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-locale:
PV changed from "2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-locale:
PKGV changed from 2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-ptest:
PV changed from "2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-ptest:
PKGV changed from 2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-src:
PV changed from "2024.1.8" to "2024.1.31"
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-src:
PKGV changed from 2024.1.8 [default] to 2024.1.31 [default]
packages/core2-64-poky-linux/python3-trove-classifiers/python3-trove-classifiers-staticdev:
PV changed from "2024.1.8" to "2024.1.31"
[OE-core] [AUH] python3-beartype: upgrading to 0.17.2 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-beartype* to *0.17.2*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-beartype-upgrade-0.17.0-0.17.2.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 8a0220f259915076dfeb3439437f7bb4e052e9a5 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:56:05 +
Subject: [PATCH] python3-beartype: upgrade 0.17.0 -> 0.17.2
---
.../{python3-beartype_0.17.0.bb => python3-beartype_0.17.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-beartype_0.17.0.bb =>
python3-beartype_0.17.2.bb} (75%)
diff --git a/meta/recipes-devtools/python/python3-beartype_0.17.0.bb
b/meta/recipes-devtools/python/python3-beartype_0.17.2.bb
similarity index 75%
rename from meta/recipes-devtools/python/python3-beartype_0.17.0.bb
rename to meta/recipes-devtools/python/python3-beartype_0.17.2.bb
index 7b14a3794b..05fd74543b 100644
--- a/meta/recipes-devtools/python/python3-beartype_0.17.0.bb
+++ b/meta/recipes-devtools/python/python3-beartype_0.17.2.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "https://beartype.readthedocs.io;
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=e71f94261c1b39896cacacfeaf60560e"
-SRC_URI[sha256sum] =
"3226fbba8c53b4e698acdb47dcaf3c0640151c4d405618c281e6631f4112947d"
+SRC_URI[sha256sum] =
"e911e1ae7de4bccd15745f7643609d8732f64de5c2fb844e89cbbed1c5a8d495"
inherit setuptools3 pypi
--
2.42.0
0001-python3-beartype-upgrade-0.17.0-0.17.2.patch
Description: Binary data
packages/core2-64-poky-linux/python3-beartype: PKGV changed from 0.17.0
[default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/b/beartype/beartype-0.17.0.tar.gz;downloadfilename=beartype-0.17.0.tar.gz;
to
"https://files.pythonhosted.org/packages/source/b/beartype/beartype-0.17.2.tar.gz;downloadfilename=beartype-0.17.2.tar.gz;
packages/core2-64-poky-linux/python3-beartype: PV changed from "0.17.0" to
"0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype-dbg: PKGV
changed from 0.17.0 [default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype/python3-beartype-dbg: PV changed
from "0.17.0" to "0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype-dev: PKGV
changed from 0.17.0 [default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype/python3-beartype-dev: PV changed
from "0.17.0" to "0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype-doc: PKGV
changed from 0.17.0 [default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype/python3-beartype-doc: PV changed
from "0.17.0" to "0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype-locale: PKGV
changed from 0.17.0 [default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype/python3-beartype-locale: PV
changed from "0.17.0" to "0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype-src: PKGV
changed from 0.17.0 [default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype/python3-beartype-src: PV changed
from "0.17.0" to "0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype-staticdev: PKGV
changed from 0.17.0 [default] to 0.17.2 [default]
packages/core2-64-poky-linux/python3-beartype/python3-beartype-staticdev: PV
changed from "0.17.0" to "0.17.2"
packages/core2-64-poky-linux/python3-beartype/python3-beartype: PKGSIZE changed
from 4449116 to 4478721 (+1%)
packages/core2-64-poky-linux/python3-beartype/python3-beartype: FILELIST:
directory renamed /usr/lib/python3.12/site-packages/beartype-0.17.0.dist-info
-> /usr/lib/python3.12/site-packages/beartype-0.17.2.dist-info, removed
"/usr/lib/python3.12/site-packages/beartype/_check/forward/__pycache__/fwdtype.cpython-312.pyc
/usr/lib/python3.12/site-packages/beartype/_util/hint/pep/proposal/pep484/__pycache__/utilpep484ref.cpython-312.pyc
/usr/lib/python3.12/site-packages/beartype/_check/forward/__pycache__/fwdref.cpython-312.pyc
/usr/lib/python3.12/site-packages/beartype/_check/code/_codescope.py
[OE-core] [AUH] rust: upgrading to 1.76.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1861 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1861 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-8b3825b16a5ea263dd8fd0ee1de903f09ea83409" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:8b3825b16a5ea263dd8fd0ee1de903f09ea83409" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 9 Mirrors 0 Missed 1 Current 18 (90% match, 96% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% || ETA: 0:04:30 Adding changed files: 0% || ETA: 0:03:12 Adding changed files: 0% || ETA: 0:02:48 Adding changed files: 1% || ETA: 0:02:41 Adding changed files: 1% || ETA: 0:02:38 Adding changed files: 1% || ETA: 0:02:29 Adding changed files: 1% || ETA: 0:02:24 Adding changed files: 2% || ETA: 0:02:20 Adding changed files: 2% || ETA: 0:02:17 Adding changed files: 2% || ETA: 0:02:16 Adding changed files: 3% |# | ETA: 0:02:15 Adding changed files: 3% |# | ETA: 0:02:14 Adding changed files: 3% |# | ETA: 0:02:12 Adding changed files: 3% |# | ETA: 0:02:12 Adding changed files: 4% |# | ETA: 0:02:11 Adding changed files: 4% |# | ETA: 0:02:11 Adding changed files: 4% |# | ETA: 0:02:10 Adding changed files: 4% |# | ETA: 0:02:10 Adding changed files: 5% |# | ETA: 0:02:09 Adding changed files: 5% |# | ETA: 0:02:08 Adding changed files: 5% |## | ETA: 0:02:08 Adding changed files: 6% |## | ETA: 0:02:07 Adding changed files: 6% |## | ETA: 0:02:06 Adding changed files: 6% |## | ETA: 0:02:06 Adding changed files: 6% |## | ETA: 0:02:05 Adding changed files: 7% |## | ETA: 0:02:04 Adding changed files: 7% |## | ETA: 0:02:04 Adding changed files: 7% |## | ETA:
[OE-core] [AUH] python3-pip: upgrading to 24.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pip* to *24.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pip-upgrade-23.3.2-24.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 6a11a4d5a0067dd2987f31b25122b1aaaff2408f Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:14:09 +
Subject: [PATCH] python3-pip: upgrade 23.3.2 -> 24.0
---
.../python/python3-pip/no_shebang_mangling.patch | 8
.../python/{python3-pip_23.3.2.bb => python3-pip_24.0.bb} | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
rename meta/recipes-devtools/python/{python3-pip_23.3.2.bb =>
python3-pip_24.0.bb} (97%)
diff --git a/meta/recipes-devtools/python/python3-pip/no_shebang_mangling.patch
b/meta/recipes-devtools/python/python3-pip/no_shebang_mangling.patch
index b59f4888da..8d03a8d0b5 100644
--- a/meta/recipes-devtools/python/python3-pip/no_shebang_mangling.patch
+++ b/meta/recipes-devtools/python/python3-pip/no_shebang_mangling.patch
@@ -1,4 +1,4 @@
-From 915bf32cd117cd86cc0d4b96bc9490b1c7119ffd Mon Sep 17 00:00:00 2001
+From ef0b3b1dd02802d35ab68f9b445997f4006ec68c Mon Sep 17 00:00:00 2001
From: Richard Purdie
Date: Wed, 23 Feb 2022 12:27:06 +
Subject: [PATCH] python3-pip: Don't change shebang
@@ -14,10 +14,10 @@ Upstream-Status: Inappropriate [OE specific config]
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/pip/_vendor/distlib/scripts.py
b/src/pip/_vendor/distlib/scripts.py
-index d270624..42c0d10 100644
+index cfa45d2..313f499 100644
--- a/src/pip/_vendor/distlib/scripts.py
+++ b/src/pip/_vendor/distlib/scripts.py
-@@ -137,6 +137,8 @@ class ScriptMaker(object):
+@@ -144,6 +144,8 @@ class ScriptMaker(object):
See also: http://www.in-ulm.de/~mascheck/various/shebang/#length
https://hg.mozilla.org/mozilla-central/file/tip/mach
"""
@@ -26,7 +26,7 @@ index d270624..42c0d10 100644
if os.name != 'posix':
simple_shebang = True
else:
-@@ -348,7 +350,7 @@ class ScriptMaker(object):
+@@ -362,7 +364,7 @@ class ScriptMaker(object):
return
match = FIRST_LINE_RE.match(first_line.replace(b'\r\n', b'\n'))
diff --git a/meta/recipes-devtools/python/python3-pip_23.3.2.bb
b/meta/recipes-devtools/python/python3-pip_24.0.bb
similarity index 97%
rename from meta/recipes-devtools/python/python3-pip_23.3.2.bb
rename to meta/recipes-devtools/python/python3-pip_24.0.bb
index 0f2ab9288b..be4a29500a 100644
--- a/meta/recipes-devtools/python/python3-pip_23.3.2.bb
+++ b/meta/recipes-devtools/python/python3-pip_24.0.bb
@@ -33,7 +33,7 @@ inherit pypi python_setuptools_build_meta
SRC_URI += "file://no_shebang_mangling.patch"
-SRC_URI[sha256sum] =
"7fd9972f96db22c8077a1ee2691b172c8089b17a5652a44494a9ecb0d78f9149"
+SRC_URI[sha256sum] =
"ea9bd1a847e8c5774a5777bb398c19e80bcd4e2aa16a4b301b718fe6f593aba2"
do_install:append() {
rm -f ${D}/${bindir}/pip
--
2.42.0
packages/core2-64-poky-linux/python3-pip: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/p/pip/pip-23.3.2.tar.gz;downloadfilename=pip-23.3.2.tar.gz
file://no_shebang_mangling.patch" to
"https://files.pythonhosted.org/packages/source/p/pip/pip-24.0.tar.gz;downloadfilename=pip-24.0.tar.gz
file://no_shebang_mangling.patch"
packages/core2-64-poky-linux/python3-pip: PV changed from "23.3.2" to "24.0"
packages/core2-64-poky-linux/python3-pip: PKGV changed from 23.3.2 [default] to
24.0 [default]
packages/core2-64-poky-linux/python3-pip/python3-pip-dbg: PV changed from
"23.3.2" to "24.0"
packages/core2-64-poky-linux/python3-pip/python3-pip-dbg: PKGV changed from
23.3.2 [default] to 24.0 [default]
packages/core2-64-poky-linux/python3-pip/python3-pip-dev: PV changed from
"23.3.2" to "24.0"
packages/core2-64-poky-linux/python3-pip/python3-pip-dev: PKGV changed from
23.3.2 [default] to 24.0 [default]
packages/core2-64-poky-linux/python3-pip/python3-pip-doc: PV changed from
"23.3.2" to "24.0"
packages/core2-64-poky-linux/python3-pip/python3-pip-doc: PKGV changed from
23.3.2 [default] to 24.0 [default]
packages/core2-64-poky-linux/python3-pip/python3-pip-locale: PV changed from
"23.3.2" to
[OE-core] [AUH] python3-cryptography: upgrading to 42.0.2 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-cryptography* to *42.0.2* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe python3-cryptography failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-6276d3b636a6c0959cee8d7d9e84174ea8a229ed" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:6276d3b636a6c0959cee8d7d9e84174ea8a229ed" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-6276d3b636a6c0959cee8d7d9e84174ea8a229ed" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:6276d3b636a6c0959cee8d7d9e84174ea8a229ed" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 37% |# | ETA: 0:00:00 Adding changed files: 74% |## | ETA: 0:00:00 Adding changed files: 100% || Time: 0:00:00 INFO: Extracting current version source... INFO: Adding local source files to srctree... INFO: Extracting upgraded version source... INFO: Fetching https://files.pythonhosted.org/packages/source/c/cryptography/cryptography-42.0.2.tar.gz;downloadfilename=cryptography-42.0.2.tar.gz... INFO: Rebasing devtool onto 8de4b5a4988e2fd05532b680ca2585e0082403ca WARNING: Command 'git rebase 8de4b5a4988e2fd05532b680ca2585e0082403ca' failed: Auto-merging src/rust/cryptography-cffi/build.rs CONFLICT (content): Merge conflict in src/rust/cryptography-cffi/build.rs You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/python3-cryptography INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/python3-cryptography/python3-cryptography_42.0.2.bb Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195583): https://lists.openembedded.org/g/openembedded-core/message/195583 Mute This Topic: https://lists.openembedded.org/mt/104377478/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] python3-lxml: upgrading to 5.1.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-lxml* to *5.1.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-lxml -V 5.1.0 NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-a515a43988dda33301940865c6f7e770f3d23e04" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:a515a43988dda33301940865c6f7e770f3d23e04" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 11 Local 11 Mirrors 0 Missed 0 Current 22 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 113 tasks of which 110 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-a515a43988dda33301940865c6f7e770f3d23e04" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:a515a43988dda33301940865c6f7e770f3d23e04" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 3 Local 2 Mirrors 0 Missed 1 Current 4 (66% match, 85% complete) done. NOTE: Executing Tasks WARNING: Failed to fetch URL https://files.pythonhosted.org/packages/source/l/lxml/lxml-5.1.0.zip;downloadfilename=lxml-5.1.0.zip, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 22 tasks of which 20 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds NOTE: The errors for this build are stored in /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215081136.txt You can send the errors to a reports server by running: send-error-report /home/pokybuild/yocto-worker/auh/build/build/tmp/log/error-report/error_report_20240215081136.txt [-s server] NOTE: The contents of these logs will be posted in public if you use the above command with the default server. Please ensure you remove any identifying or proprietary information when prompted before sending. INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching https://files.pythonhosted.org/packages/source/l/lxml/lxml-5.1.0.zip;downloadfilename=lxml-5.1.0.zip... ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export SSL_CERT_FILE="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; export GIT_SSL_CAINFO="/home/pokybuild/yocto-worker/auh/build/buildtools/sysroots/x86_64-pokysdk-linux/etc/ssl/certs/ca-certificates.crt"; export ftp_proxy="http://proxy.yocto.io:5187/;; export FTP_PROXY="http://proxy.yocto.io:5187/;; export PATH="/home/pokybuild/yocto-worker/auh/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/scripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-up417kw2/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-up417kw2/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-up417kw2/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipe tool-up417kw2/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-up417kw2/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/tmp/work/recipetool-up417kw2/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/tmp/hosttools"; export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp --user-agent='Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0' -O
[OE-core] [AUH] liburi-perl: upgrading to 5.27 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *liburi-perl* to *5.27* has
Succeeded.
Next steps:
- apply the patch: git am 0001-liburi-perl-upgrade-5.25-5.27.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 01826a7917b5194050e15dc1abf9f189aefb7d88 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:51:04 +
Subject: [PATCH] liburi-perl: upgrade 5.25 -> 5.27
---
.../perl/liburi-perl/0001-Skip-TODO-test-cases-that-fail.patch | 2 +-
.../perl/{liburi-perl_5.25.bb => liburi-perl_5.27.bb} | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/perl/{liburi-perl_5.25.bb => liburi-perl_5.27.bb}
(94%)
diff --git
a/meta/recipes-devtools/perl/liburi-perl/0001-Skip-TODO-test-cases-that-fail.patch
b/meta/recipes-devtools/perl/liburi-perl/0001-Skip-TODO-test-cases-that-fail.patch
index ed1f25125f..e874e93a2b 100644
---
a/meta/recipes-devtools/perl/liburi-perl/0001-Skip-TODO-test-cases-that-fail.patch
+++
b/meta/recipes-devtools/perl/liburi-perl/0001-Skip-TODO-test-cases-that-fail.patch
@@ -1,4 +1,4 @@
-From 5a4271456104bdf027644c81c3a208cde5cf522e Mon Sep 17 00:00:00 2001
+From b7689095cb4920226d19abf834de16a638029b75 Mon Sep 17 00:00:00 2001
From: Tim Orling
Date: Thu, 17 Nov 2022 16:33:20 -0800
Subject: [PATCH] Skip TODO test cases that fail
diff --git a/meta/recipes-devtools/perl/liburi-perl_5.25.bb
b/meta/recipes-devtools/perl/liburi-perl_5.27.bb
similarity index 94%
rename from meta/recipes-devtools/perl/liburi-perl_5.25.bb
rename to meta/recipes-devtools/perl/liburi-perl_5.27.bb
index 0305955524..e5db7b3cfe 100644
--- a/meta/recipes-devtools/perl/liburi-perl_5.25.bb
+++ b/meta/recipes-devtools/perl/liburi-perl_5.27.bb
@@ -12,7 +12,7 @@ SRC_URI =
"${CPAN_MIRROR}/authors/id/O/OA/OALDERS/URI-${PV}.tar.gz \
file://0001-Skip-TODO-test-cases-that-fail.patch \
"
-SRC_URI[sha256sum] =
"ef61941da09fff2503cea3692c4f2fc48c0e4442486e2a28345cb32d44d0d271"
+SRC_URI[sha256sum] =
"11962d8a8a8496906e5d34774affc235a1c95c112d390c0b4171f3e91e9e2a97"
S = "${WORKDIR}/URI-${PV}"
--
2.42.0
packages/core2-64-poky-linux/liburi-perl: PKGV changed from 5.25 [default] to
5.27 [default]
packages/core2-64-poky-linux/liburi-perl: SRC_URI changed from
"https://search.cpan.org/CPAN/authors/id/O/OA/OALDERS/URI-5.25.tar.gz
file://0001-Skip-TODO-test-cases-that-fail.patch file://ptest-perl/run-ptest"
to "https://search.cpan.org/CPAN/authors/id/O/OA/OALDERS/URI-5.27.tar.gz
file://0001-Skip-TODO-test-cases-that-fail.patch file://ptest-perl/run-ptest"
packages/core2-64-poky-linux/liburi-perl: PV changed from "5.25" to "5.27"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-dbg: PKGV changed from
5.25 [default] to 5.27 [default]
packages/core2-64-poky-linux/liburi-perl/liburi-perl-dbg: PV changed from
"5.25" to "5.27"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-dev: PKGV changed from
5.25 [default] to 5.27 [default]
packages/core2-64-poky-linux/liburi-perl/liburi-perl-dev: PV changed from
"5.25" to "5.27"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-doc: PKGSIZE changed from
95701 to 104194 (+9%)
packages/core2-64-poky-linux/liburi-perl/liburi-perl-doc: FILELIST: added
"/usr/share/man/man3/URI::geo.3"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-doc: PKGV changed from
5.25 [default] to 5.27 [default]
packages/core2-64-poky-linux/liburi-perl/liburi-perl-doc: PV changed from
"5.25" to "5.27"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-locale: PKGV changed from
5.25 [default] to 5.27 [default]
packages/core2-64-poky-linux/liburi-perl/liburi-perl-locale: PV changed from
"5.25" to "5.27"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-ptest: PKGSIZE changed
from 133030 to 137377 (+3%)
packages/core2-64-poky-linux/liburi-perl/liburi-perl-ptest: FILELIST: added
"/usr/lib/liburi-perl/ptest/t/geo_construct.t
/usr/lib/liburi-perl/ptest/t/geo_point.t
/usr/lib/liburi-perl/ptest/t/geo_basic.t"
packages/core2-64-poky-linux/liburi-perl/liburi-perl-ptest: PKGV changed from
5.25 [default] to 5.27 [default]
packages/core2-64-poky-linux/liburi-perl/liburi-perl-ptest: PV changed from
"5.25" to "5.27"
[OE-core] [AUH] python3-poetry-core: upgrading to 1.9.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-poetry-core* to
*1.9.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-poetry-core-upgrade-1.8.1-1.9.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 7441a91a0d58936eb42a90698ec8e8d80f4d72ad Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:16:50 +
Subject: [PATCH] python3-poetry-core: upgrade 1.8.1 -> 1.9.0
---
...ython3-poetry-core_1.8.1.bb => python3-poetry-core_1.9.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-poetry-core_1.8.1.bb =>
python3-poetry-core_1.9.0.bb} (94%)
diff --git a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
similarity index 94%
rename from meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
rename to meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
index fcb6d30ee0..dfb29c4b86 100644
--- a/meta/recipes-devtools/python/python3-poetry-core_1.8.1.bb
+++ b/meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb
@@ -15,7 +15,7 @@ LIC_FILES_CHKSUM = "\
file://src/poetry/core/_vendor/tomli/LICENSE;md5=f0879d17df0110d1aa8c8c9f46f5
\
"
-SRC_URI[sha256sum] =
"67a76c671da2a70e55047cddda83566035b701f7e463b32a2abfeac6e2a16376"
+SRC_URI[sha256sum] =
"fa7a4001eae8aa572ee84f35feb510b321bd652e5cf9293249d62853e1f935a2"
inherit python_poetry_core pypi
PYPI_ARCHIVE_NAME = "poetry_core-${PV}.${PYPI_PACKAGE_EXT}"
--
2.42.0
packages/core2-64-poky-linux/python3-poetry-core: PKGV changed from 1.8.1
[default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/p/poetry-core/poetry_core-1.8.1.tar.gz;downloadfilename=poetry_core-1.8.1.tar.gz;
to
"https://files.pythonhosted.org/packages/source/p/poetry-core/poetry_core-1.9.0.tar.gz;downloadfilename=poetry_core-1.9.0.tar.gz;
packages/core2-64-poky-linux/python3-poetry-core: PV changed from "1.8.1" to
"1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-dbg: PKGV
changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-dbg: PV
changed from "1.8.1" to "1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-dev: PKGV
changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-dev: PV
changed from "1.8.1" to "1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-doc: PKGV
changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-doc: PV
changed from "1.8.1" to "1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-locale:
PKGV changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-locale: PV
changed from "1.8.1" to "1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-src: PKGV
changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-src: PV
changed from "1.8.1" to "1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-staticdev:
PKGV changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core-staticdev:
PV changed from "1.8.1" to "1.9.0"
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core: PKGSIZE
changed from 2253119 to 2270767 (+1%)
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core: PKGV
changed from 1.8.1 [default] to 1.9.0 [default]
packages/core2-64-poky-linux/python3-poetry-core/python3-poetry-core: PV
changed from "1.8.1" to "1.9.0"
Changes to packages/core2-64-poky-linux/python3-poetry-core (sysroot):
/usr/lib/python3.12/site-packages/poetry_core-1.8.1.dist-info moved to
/usr/lib/python3.12/site-packages/poetry_core-1.9.0.dist-info
Changes to packages/x86_64-linux/python3-poetry-core-native (sysroot):
/usr/lib/python3.12/site-packages/poetry_core-1.8.1.dist-info moved to
[OE-core] [AUH] libdnf: upgrading to 0.73.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libdnf* to *0.73.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libdnf-upgrade-0.72.0-0.73.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From e9420e6a015514400cdcd6bd8197ca55e808409f Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:42:59 +
Subject: [PATCH] libdnf: upgrade 0.72.0 -> 0.73.0
---
...ke-drop-the-requirement-for-GTKDOC_SCA.patch | 10 --
...-for-both-libsolv-and-libsolvext-libdn.patch | 2 +-
.../0001-drop-FindPythonInstDir.cmake.patch | 6 ++
...riables-with-pkg-config-cmake-s-own-mo.patch | 2 +-
.../libdnf/libdnf/armarch.patch | 17 +
.../libdnf/enable_test_data_dir_set.patch | 2 +-
.../{libdnf_0.72.0.bb => libdnf_0.73.0.bb} | 2 +-
7 files changed, 23 insertions(+), 18 deletions(-)
rename meta/recipes-devtools/libdnf/{libdnf_0.72.0.bb => libdnf_0.73.0.bb}
(97%)
diff --git
a/meta/recipes-devtools/libdnf/libdnf/0001-FindGtkDoc.cmake-drop-the-requirement-for-GTKDOC_SCA.patch
b/meta/recipes-devtools/libdnf/libdnf/0001-FindGtkDoc.cmake-drop-the-requirement-for-GTKDOC_SCA.patch
index 791a32e748..8e2820c1b2 100644
---
a/meta/recipes-devtools/libdnf/libdnf/0001-FindGtkDoc.cmake-drop-the-requirement-for-GTKDOC_SCA.patch
+++
b/meta/recipes-devtools/libdnf/libdnf/0001-FindGtkDoc.cmake-drop-the-requirement-for-GTKDOC_SCA.patch
@@ -1,7 +1,7 @@
-From 9bb7630915c3e787732463a3e2064fe0e177101b Mon Sep 17 00:00:00 2001
+From 7d8c1916a2e4b7c1fb2a6020a3ea408a9dde6e06 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Thu, 24 Nov 2016 14:33:07 +0200
-Subject: [PATCH 1/4] FindGtkDoc.cmake: drop the requirement for
+Subject: [PATCH] FindGtkDoc.cmake: drop the requirement for
GTKDOC_SCANGOBJ_WRAPPER
For some reason cmake is not able to find it when building in openembedded,
@@ -9,12 +9,13 @@ and it's bundled with the source code anyway.
Upstream-Status: Submitted
[https://github.com/rpm-software-management/libdnf/pull/312]
Signed-off-by: Alexander Kanavin
+
---
cmake/modules/FindGtkDoc.cmake | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmake/modules/FindGtkDoc.cmake b/cmake/modules/FindGtkDoc.cmake
-index 92b2cc7..39f34bd 100644
+index 92b2cc7e..39f34bd5 100644
--- a/cmake/modules/FindGtkDoc.cmake
+++ b/cmake/modules/FindGtkDoc.cmake
@@ -52,7 +52,7 @@ find_program(GTKDOC_MKHTML_EXE gtkdoc-mkhtml PATH
"${GLIB_PREFIX}/bin")
@@ -26,6 +27,3 @@ index 92b2cc7..39f34bd 100644
VERSION_VAR GtkDoc_VERSION)
# ::
---
-2.11.0
-
diff --git
a/meta/recipes-devtools/libdnf/libdnf/0001-Get-parameters-for-both-libsolv-and-libsolvext-libdn.patch
b/meta/recipes-devtools/libdnf/libdnf/0001-Get-parameters-for-both-libsolv-and-libsolvext-libdn.patch
index 08d0859953..1f4d7110df 100644
---
a/meta/recipes-devtools/libdnf/libdnf/0001-Get-parameters-for-both-libsolv-and-libsolvext-libdn.patch
+++
b/meta/recipes-devtools/libdnf/libdnf/0001-Get-parameters-for-both-libsolv-and-libsolvext-libdn.patch
@@ -1,4 +1,4 @@
-From b87ae6860ea44996b677ad1c4a9793720b77c67c Mon Sep 17 00:00:00 2001
+From c6e71bca83cb956fde55529c3e5cf742915fc040 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Tue, 7 Feb 2017 12:16:03 +0200
Subject: [PATCH] Get parameters for both libsolv and libsolvext (libdnf is
diff --git
a/meta/recipes-devtools/libdnf/libdnf/0001-drop-FindPythonInstDir.cmake.patch
b/meta/recipes-devtools/libdnf/libdnf/0001-drop-FindPythonInstDir.cmake.patch
index d483dd410b..eda01bbba8 100644
---
a/meta/recipes-devtools/libdnf/libdnf/0001-drop-FindPythonInstDir.cmake.patch
+++
b/meta/recipes-devtools/libdnf/libdnf/0001-drop-FindPythonInstDir.cmake.patch
@@ -1,4 +1,4 @@
-From c0a465ccae395871ab10932975e37894220bc6a1 Mon Sep 17 00:00:00 2001
+From 8740e452af3ec4bac303c0e302c605c99e3031f4 Mon Sep 17 00:00:00 2001
From: Hongxu Jia
Date: Tue, 1 Jun 2021 10:23:59 +0800
Subject: [PATCH] drop FindPythonInstDir.cmake
@@ -21,6 +21,7 @@ Yocto setting
Upstream-Status: Inappropriate [Yocto specific]
Signed-off-by: Hongxu Jia
+
---
cmake/modules/FindPythonInstDir.cmake | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
@@ -37,6 +38,3 @@ index
[OE-core] [AUH] pkgconf: upgrading to 2.1.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pkgconf* to *2.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-pkgconf-upgrade-2.1.0-2.1.1.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 3d2ecf7d7089c733871c79c3b91f519e1c76cc2e Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:53:26 +
Subject: [PATCH] pkgconf: upgrade 2.1.0 -> 2.1.1
---
.../pkgconf/{pkgconf_2.1.0.bb => pkgconf_2.1.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/pkgconf/{pkgconf_2.1.0.bb => pkgconf_2.1.1.bb}
(96%)
diff --git a/meta/recipes-devtools/pkgconf/pkgconf_2.1.0.bb
b/meta/recipes-devtools/pkgconf/pkgconf_2.1.1.bb
similarity index 96%
rename from meta/recipes-devtools/pkgconf/pkgconf_2.1.0.bb
rename to meta/recipes-devtools/pkgconf/pkgconf_2.1.1.bb
index 1921f3a086..33d69451bb 100644
--- a/meta/recipes-devtools/pkgconf/pkgconf_2.1.0.bb
+++ b/meta/recipes-devtools/pkgconf/pkgconf_2.1.1.bb
@@ -20,7 +20,7 @@ SRC_URI = "\
file://pkg-config-native.in \
file://pkg-config-esdk.in \
"
-SRC_URI[sha256sum] =
"266d5861ee51c52bc710293a1d36622ae16d048d71ec56034a02eb9cf9677761"
+SRC_URI[sha256sum] =
"3a224f2accf091b77a5781316e27b9ee3ba82c083cc2e539e08940b68a44fec5"
inherit autotools
--
2.42.0
0001-pkgconf-upgrade-2.1.0-2.1.1.patch
Description: Binary data
packages/core2-64-poky-linux/pkgconf: PKGV changed from 2.1.0 [default] to
2.1.1 [default]
packages/core2-64-poky-linux/pkgconf: PV changed from "2.1.0" to "2.1.1"
packages/core2-64-poky-linux/pkgconf: SRC_URI changed from
"https://distfiles.ariadne.space/pkgconf/pkgconf-2.1.0.tar.xz
file://pkg-config-wrapper file://pkg-config-native.in
file://pkg-config-esdk.in" to
"https://distfiles.ariadne.space/pkgconf/pkgconf-2.1.1.tar.xz
file://pkg-config-wrapper file://pkg-config-native.in file://pkg-config-esdk.in"
packages/core2-64-poky-linux/pkgconf/pkgconf-dbg: PKGV changed from 2.1.0
[default] to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-dbg: PKGSIZE changed from 314232
to 315272 (+0%)
packages/core2-64-poky-linux/pkgconf/pkgconf-dbg: PV changed from "2.1.0" to
"2.1.1"
packages/core2-64-poky-linux/pkgconf/pkgconf-dev: PKGV changed from 2.1.0
[default] to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-dev: PKGSIZE changed from 24354 to
24495 (+1%)
packages/core2-64-poky-linux/pkgconf/pkgconf-dev: PV changed from "2.1.0" to
"2.1.1"
packages/core2-64-poky-linux/pkgconf/pkgconf-doc: PKGV changed from 2.1.0
[default] to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-doc: PKGSIZE changed from 29202 to
29201 (-0%)
packages/core2-64-poky-linux/pkgconf/pkgconf-doc: PV changed from "2.1.0" to
"2.1.1"
packages/core2-64-poky-linux/pkgconf/pkgconf-locale: PKGV changed from 2.1.0
[default] to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-locale: PV changed from "2.1.0" to
"2.1.1"
packages/core2-64-poky-linux/pkgconf/pkgconf-src: PKGV changed from 2.1.0
[default] to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-src: PKGSIZE changed from 273448
to 274832 (+1%)
packages/core2-64-poky-linux/pkgconf/pkgconf-src: PV changed from "2.1.0" to
"2.1.1"
packages/core2-64-poky-linux/pkgconf/pkgconf-staticdev: PKGV changed from 2.1.0
[default] to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf-staticdev: PV changed from "2.1.0"
to "2.1.1"
packages/core2-64-poky-linux/pkgconf/pkgconf: PKGV changed from 2.1.0 [default]
to 2.1.1 [default]
packages/core2-64-poky-linux/pkgconf/pkgconf: PV changed from "2.1.0" to "2.1.1"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195586):
https://lists.openembedded.org/g/openembedded-core/message/195586
Mute This Topic: https://lists.openembedded.org/mt/104377481/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] python3-certifi: upgrading to 2024.2.2 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-certifi* to
*2024.2.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-certifi-upgrade-2023.11.17-2024.2.2.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 235f0b2dadf1ea1dc7b2431b589feb40b4432068 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:58:35 +
Subject: [PATCH] python3-certifi: upgrade 2023.11.17 -> 2024.2.2
---
...ython3-certifi_2023.11.17.bb => python3-certifi_2024.2.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-certifi_2023.11.17.bb =>
python3-certifi_2024.2.2.bb} (86%)
diff --git a/meta/recipes-devtools/python/python3-certifi_2023.11.17.bb
b/meta/recipes-devtools/python/python3-certifi_2024.2.2.bb
similarity index 86%
rename from meta/recipes-devtools/python/python3-certifi_2023.11.17.bb
rename to meta/recipes-devtools/python/python3-certifi_2024.2.2.bb
index daed712362..4e61b8d9d4 100644
--- a/meta/recipes-devtools/python/python3-certifi_2023.11.17.bb
+++ b/meta/recipes-devtools/python/python3-certifi_2024.2.2.bb
@@ -7,7 +7,7 @@ HOMEPAGE = " http://certifi.io/;
LICENSE = "ISC"
LIC_FILES_CHKSUM = "file://LICENSE;md5=11618cb6a975948679286b1211bd573c"
-SRC_URI[sha256sum] =
"9b469f3a900bf28dc19b8cfbf8019bf47f7fdd1a65a1d4ffb98fc14166beb4d1"
+SRC_URI[sha256sum] =
"0569859f95fc761b18b45ef421b1290a0f65f147e92a1e5eb3e635f9a5e4e66f"
inherit pypi setuptools3
--
2.42.0
packages/core2-64-poky-linux/python3-certifi: PV changed from "2023.11.17" to
"2024.2.2"
packages/core2-64-poky-linux/python3-certifi: PKGV changed from 2023.11.17
[default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi: SRC_URI changed from
"https://files.pythonhosted.org/packages/source/c/certifi/certifi-2023.11.17.tar.gz;downloadfilename=certifi-2023.11.17.tar.gz;
to
"https://files.pythonhosted.org/packages/source/c/certifi/certifi-2024.2.2.tar.gz;downloadfilename=certifi-2024.2.2.tar.gz;
packages/core2-64-poky-linux/python3-certifi/python3-certifi-dbg: PV changed
from "2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi-dbg: PKGV changed
from 2023.11.17 [default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi/python3-certifi-dev: PV changed
from "2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi-dev: PKGV changed
from 2023.11.17 [default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi/python3-certifi-doc: PV changed
from "2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi-doc: PKGV changed
from 2023.11.17 [default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi/python3-certifi-locale: PV changed
from "2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi-locale: PKGV
changed from 2023.11.17 [default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi/python3-certifi-src: PV changed
from "2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi-src: PKGV changed
from 2023.11.17 [default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi/python3-certifi-staticdev: PV
changed from "2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi-staticdev: PKGV
changed from 2023.11.17 [default] to 2024.2.2 [default]
packages/core2-64-poky-linux/python3-certifi/python3-certifi: PV changed from
"2023.11.17" to "2024.2.2"
packages/core2-64-poky-linux/python3-certifi/python3-certifi: PKGSIZE changed
from 302536 to 305361 (+1%)
packages/core2-64-poky-linux/python3-certifi/python3-certifi: PKGV changed from
2023.11.17 [default] to 2024.2.2 [default]
Changes to packages/core2-64-poky-linux/python3-certifi (sysroot):
/usr/lib/python3.12/site-packages/certifi-2024.2.2.dist-info was added
/usr/lib/python3.12/site-packages/certifi-2024.2.2.dist-info/LICENSE was added
/usr/lib/python3.12/site-packages/certifi-2024.2.2.dist-info/METADATA was
added
/usr/lib/python3.12/site-packages/certifi-2024.2.2.dist-info/RECORD was added
[OE-core] [AUH] python3-dtschema: upgrading to 2023.11 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to
*2023.11* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-dtschema-upgrade-2023.7-2023.11.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From a6878e23694fa8a5fdadb3d8c2f820d587dcadbb Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 08:02:19 +
Subject: [PATCH] python3-dtschema: upgrade 2023.7 -> 2023.11
---
.../{python3-dtschema_2023.7.bb => python3-dtschema_2023.11.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-dtschema_2023.7.bb =>
python3-dtschema_2023.11.bb} (85%)
diff --git a/meta/recipes-devtools/python/python3-dtschema_2023.7.bb
b/meta/recipes-devtools/python/python3-dtschema_2023.11.bb
similarity index 85%
rename from meta/recipes-devtools/python/python3-dtschema_2023.7.bb
rename to meta/recipes-devtools/python/python3-dtschema_2023.11.bb
index c1dc3e019a..5453d96f8a 100644
--- a/meta/recipes-devtools/python/python3-dtschema_2023.7.bb
+++ b/meta/recipes-devtools/python/python3-dtschema_2023.11.bb
@@ -7,7 +7,7 @@ inherit pypi setuptools3
PYPI_PACKAGE = "dtschema"
-SRC_URI[sha256sum] =
"de7cd73a35244cf76a8cdd9919bbeb31f362aa5744f3c76c80e0e612489dd0c0"
+SRC_URI[sha256sum] =
"cf9a449ea743c0a955cf6034ef246668fa5ea177684977c61fef7604af5f273b"
DEPENDS += "python3-setuptools-scm-native"
RDEPENDS:${PN} += "\
--
2.42.0
0001-python3-dtschema-upgrade-2023.7-2023.11.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1861 entries from dependency cache.
Parsing recipes...done.
Parsing of 914 .bb files complete (913 cached, 1 parsed). 1857 targets, 35
skipped, 0 masked, 0 errors.
Removing 1 recipes from the core2-64 sysroot...done.
Removing 1 recipes from the qemux86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.7.2"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.3+snapshot-6276d3b636a6c0959cee8d7d9e84174ea8a229ed"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp
workspace=
"tmp-auh-upgrades:6276d3b636a6c0959cee8d7d9e84174ea8a229ed"
Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing
build without monitoring pressure
Sstate summary: Wanted 366 Local 356 Mirrors 0 Missed 10 Current 434 (97%
match, 98% complete)
done.
NOTE: Executing Tasks
NOTE: Running setscene task 508 of 800
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_populate_lic_setscene)
NOTE: Running setscene task 510 of 800
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_deploy_source_date_epoch_setscene)
NOTE: recipe python3-dtschema-2023.11-r0: task do_populate_lic_setscene: Started
NOTE: recipe python3-dtschema-2023.11-r0: task
do_deploy_source_date_epoch_setscene: Started
NOTE: recipe python3-dtschema-2023.11-r0: task
do_deploy_source_date_epoch_setscene: Succeeded
NOTE: recipe python3-dtschema-2023.11-r0: task do_populate_lic_setscene:
Succeeded
NOTE: Running setscene task 800 of 800
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_recipe_qa_setscene)
NOTE: recipe python3-dtschema-2023.11-r0: task do_recipe_qa_setscene: Started
NOTE: recipe python3-dtschema-2023.11-r0: task do_recipe_qa_setscene: Succeeded
NOTE: Setscene tasks completed
NOTE: Running task 1680 of 2266
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_fetch)
NOTE: recipe python3-dtschema-2023.11-r0: task do_fetch: Started
NOTE: recipe python3-dtschema-2023.11-r0: task do_fetch: Succeeded
NOTE: Running task 2020 of 2266
(/home/pokybuild/yocto-worker/auh/build/meta/recipes-devtools/python/python3-dtschema_2023.11.bb:do_unpack)
NOTE: Running task 2021 of 2266
[OE-core] [AUH] librepo: upgrading to 1.17.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *librepo* to *1.17.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe librepo failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-568238c65d91610a69f9c3679eee293f8e29cc5f" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:568238c65d91610a69f9c3679eee293f8e29cc5f" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Rebasing devtool onto ae727d99086f70f39fba5695af5460e1da908c1b WARNING: Command 'git rebase ae727d99086f70f39fba5695af5460e1da908c1b' failed: Auto-merging CMakeLists.txt CONFLICT (content): Merge conflict in CMakeLists.txt You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/librepo INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/librepo/librepo_1.17.0.bb Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195580): https://lists.openembedded.org/g/openembedded-core/message/195580 Mute This Topic: https://lists.openembedded.org/mt/104377475/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] go: upgrading to 1.22.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go* to *1.22.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1858 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-3cd69b84ee2688fb874202377d962cf21e79dd45" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:3cd69b84ee2688fb874202377d962cf21e79dd45" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1858 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-3cd69b84ee2688fb874202377d962cf21e79dd45" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:3cd69b84ee2688fb874202377d962cf21e79dd45" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 1% || ETA: 0:00:07 Adding changed files: 3% |# | ETA: 0:00:05 Adding changed files: 5% |# | ETA: 0:00:04 Adding changed files: 6% |## | ETA: 0:00:04 Adding changed files: 8% |### | ETA: 0:00:04 Adding changed files: 10% |### | ETA: 0:00:04 Adding changed files: 12% || ETA: 0:00:04 Adding changed files: 13% || ETA: 0:00:03 Adding changed files: 15% |# | ETA: 0:00:03 Adding changed files: 17% |## | ETA: 0:00:03 Adding changed files: 18% |## | ETA: 0:00:03 Adding changed files: 20% |### | ETA: 0:00:03 Adding changed files: 22% || ETA: 0:00:03 Adding changed files: 24% || ETA: 0:00:03 Adding changed files: 25% |# | ETA: 0:00:03 Adding changed files: 27% |# | ETA: 0:00:03 Adding changed files: 29% |## | ETA: 0:00:03 Adding changed files: 30% |### | ETA: 0:00:03 Adding changed files: 32% |### | ETA: 0:00:03 Adding changed files: 34% || ETA: 0:00:03 Adding changed files: 36% || ETA: 0:00:03 Adding changed files: 37% |# | ETA: 0:00:02 Adding changed files: 39% |## | ETA: 0:00:02 Adding changed files: 41% |## | ETA: 0:00:02 Adding changed files: 42% |### | ETA: 0:00:02 Adding changed files: 44% || ETA: 0:00:02 Adding changed files: 46% || ETA: 0:00:02 Adding changed files: 48% |# | ETA: 0:00:02 Adding changed files: 49% |#
[OE-core] [AUH] meson: upgrading to 1.3.2 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *1.3.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-1.3.1-1.3.2.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 940103ec9fff34b8dcd010e5005eb637b7b7b276 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:46:31 +
Subject: [PATCH] meson: upgrade 1.3.1 -> 1.3.2
---
.../meson/meson/0001-Make-CPU-family-warnings-fatal.patch | 2 +-
...1-python-module-do-not-manipulate-the-environment-when.patch | 2 +-
.../meson/0002-Support-building-allarch-recipes-again.patch | 2 +-
meta/recipes-devtools/meson/{meson_1.3.1.bb => meson_1.3.2.bb} | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/meson/{meson_1.3.1.bb => meson_1.3.2.bb} (98%)
diff --git
a/meta/recipes-devtools/meson/meson/0001-Make-CPU-family-warnings-fatal.patch
b/meta/recipes-devtools/meson/meson/0001-Make-CPU-family-warnings-fatal.patch
index 8ea7c35950..24b2831f33 100644
---
a/meta/recipes-devtools/meson/meson/0001-Make-CPU-family-warnings-fatal.patch
+++
b/meta/recipes-devtools/meson/meson/0001-Make-CPU-family-warnings-fatal.patch
@@ -1,4 +1,4 @@
-From b77cbe67df5fa0998946503f207c256ee740bb5f Mon Sep 17 00:00:00 2001
+From 5ff1b47c36984eb8ee90b790306fb59705353782 Mon Sep 17 00:00:00 2001
From: Ross Burton
Date: Tue, 3 Jul 2018 13:59:09 +0100
Subject: [PATCH] Make CPU family warnings fatal
diff --git
a/meta/recipes-devtools/meson/meson/0001-python-module-do-not-manipulate-the-environment-when.patch
b/meta/recipes-devtools/meson/meson/0001-python-module-do-not-manipulate-the-environment-when.patch
index 2e0a4b1bbe..0116217605 100644
---
a/meta/recipes-devtools/meson/meson/0001-python-module-do-not-manipulate-the-environment-when.patch
+++
b/meta/recipes-devtools/meson/meson/0001-python-module-do-not-manipulate-the-environment-when.patch
@@ -1,4 +1,4 @@
-From e85683698aa3556bf14fc6d35f2c067f16af520b Mon Sep 17 00:00:00 2001
+From 3c29e08bf8bde06a350148ac88637b2f3cdaf86d Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Mon, 19 Nov 2018 14:24:26 +0100
Subject: [PATCH] python module: do not manipulate the environment when calling
diff --git
a/meta/recipes-devtools/meson/meson/0002-Support-building-allarch-recipes-again.patch
b/meta/recipes-devtools/meson/meson/0002-Support-building-allarch-recipes-again.patch
index a8396f30bb..665d46d4f0 100644
---
a/meta/recipes-devtools/meson/meson/0002-Support-building-allarch-recipes-again.patch
+++
b/meta/recipes-devtools/meson/meson/0002-Support-building-allarch-recipes-again.patch
@@ -1,4 +1,4 @@
-From 6fb8db54929b40e1fd7ac949ef44f0d37df0bae9 Mon Sep 17 00:00:00 2001
+From eb04c466340465b4b86f29fef2cdc7b813e8bafa Mon Sep 17 00:00:00 2001
From: Peter Kjellerstedt
Date: Thu, 26 Jul 2018 16:32:49 +0200
Subject: [PATCH] Support building allarch recipes again
diff --git a/meta/recipes-devtools/meson/meson_1.3.1.bb
b/meta/recipes-devtools/meson/meson_1.3.2.bb
similarity index 98%
rename from meta/recipes-devtools/meson/meson_1.3.1.bb
rename to meta/recipes-devtools/meson/meson_1.3.2.bb
index 3a4bb14f09..98b600996c 100644
--- a/meta/recipes-devtools/meson/meson_1.3.1.bb
+++ b/meta/recipes-devtools/meson/meson_1.3.2.bb
@@ -15,7 +15,7 @@ SRC_URI =
"${GITHUB_BASE_URI}/download/${PV}/meson-${PV}.tar.gz \
file://0001-Make-CPU-family-warnings-fatal.patch \
file://0002-Support-building-allarch-recipes-again.patch \
"
-SRC_URI[sha256sum] =
"6020568bdede1643d4fb41e28215be38eff5d52da28ac7d125457c59e0032ad7"
+SRC_URI[sha256sum] =
"492eb450c8b073024276f916f5adbb3c4bb7e90e9e6ec124efda064f3d9b5baa"
inherit python_setuptools_build_meta github-releases
--
2.42.0
packages/core2-64-poky-linux/meson: PKGV changed from 1.3.1 [default] to 1.3.2
[default]
packages/core2-64-poky-linux/meson: SRC_URI changed from
"https://github.com/mesonbuild/meson/releases//download/1.3.1/meson-1.3.1.tar.gz
file://meson-setup.py file://meson-wrapper
file://0001-python-module-do-not-manipulate-the-environment-when.patch
file://0001-Make-CPU-family-warnings-fatal.patch
file://0002-Support-building-allarch-recipes-again.patch" to
[OE-core] [AUH] git: upgrading to 2.43.2 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.43.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-git-upgrade-2.43.0-2.43.2.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 49da048da4f631927be5d590b35dfad460c795c7 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:32:58 +
Subject: [PATCH] git: upgrade 2.43.0 -> 2.43.2
---
...-do-not-force-RHEL-7-specific-build-.patch | 4 ++--
meta/recipes-devtools/git/git/fixsort.patch | 23 ---
.../git/{git_2.43.0.bb => git_2.43.2.bb} | 2 +-
3 files changed, 18 insertions(+), 11 deletions(-)
rename meta/recipes-devtools/git/{git_2.43.0.bb => git_2.43.2.bb} (98%)
diff --git
a/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch
b/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch
index d80d082ba3..59526f1bcd 100644
---
a/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch
+++
b/meta/recipes-devtools/git/git/0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch
@@ -1,4 +1,4 @@
-From c0c5241abdc113acbe6bcd960686cea414bce357 Mon Sep 17 00:00:00 2001
+From ac7e40abdbe61d5b0ccf960ecc282d1a92306619 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Mon, 7 Feb 2022 10:13:15 +0100
Subject: [PATCH] config.mak.uname: do not force RHEL-7 specific build settings
@@ -14,7 +14,7 @@ Signed-off-by: Alexander Kanavin
1 file changed, 4 deletions(-)
diff --git a/config.mak.uname b/config.mak.uname
-index 259d151..136ae3b 100644
+index 3bb03f4..b5ed7d6 100644
--- a/config.mak.uname
+++ b/config.mak.uname
@@ -64,10 +64,6 @@ ifeq ($(uname_S),Linux)
diff --git a/meta/recipes-devtools/git/git/fixsort.patch
b/meta/recipes-devtools/git/git/fixsort.patch
index 07a487e8ca..d395f7d5d0 100644
--- a/meta/recipes-devtools/git/git/fixsort.patch
+++ b/meta/recipes-devtools/git/git/fixsort.patch
@@ -1,13 +1,16 @@
-[PATCH] generate-configlist.sh: Fix determinism issue
+From 3e4877a529f0aa0667a5fd2d4a48f3826da9f78e Mon Sep 17 00:00:00 2001
+From: Richard Purdie
+Date: Wed, 17 Feb 2021 17:57:13 +
+Subject: [PATCH] [PATCH] generate-configlist.sh: Fix determinism issue
-Currently git binaries are not entirely reproducible, at least partly
+Currently git binaries are not entirely reproducible, at least partly
due to config-list.h differing in order depending on the system's
locale settings. Under different locales, the entries:
"sendemail.identity",
"sendemail..*",
-would differ in order for example and this leads to differences in
+would differ in order for example and this leads to differences in
the debug symbols for the binaries.
This can be fixed by specifying the C locale for the sort in the
@@ -16,11 +19,15 @@ shell script generating the header.
Signed-off-by: Richard Purdie
Upstream-Status: Submitted
[https://public-inbox.org/git/f029a942dd3d50d85e60bd37d8e454524987842f.ca...@linuxfoundation.org/T/#u]
-Index: git-2.30.0/generate-configlist.sh
-===
git-2.30.0.orig/generate-configlist.sh
-+++ git-2.30.0/generate-configlist.sh
-@@ -9,7 +9,7 @@ static const char *config_name_list[] =
+---
+ generate-configlist.sh | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/generate-configlist.sh b/generate-configlist.sh
+index 8692fe5..e67ccac 100755
+--- a/generate-configlist.sh
b/generate-configlist.sh
+@@ -9,7 +9,7 @@ static const char *config_name_list[] = {
EOF
grep -h '^[a-zA-Z].*\..*::$' Documentation/*config.txt
Documentation/config/*.txt |
sed '/deprecated/d; s/::$//; s/, */\n/g' |
diff --git a/meta/recipes-devtools/git/git_2.43.0.bb
b/meta/recipes-devtools/git/git_2.43.2.bb
similarity index 98%
rename from meta/recipes-devtools/git/git_2.43.0.bb
rename to meta/recipes-devtools/git/git_2.43.2.bb
index f913290081..74c9a514e4 100644
--- a/meta/recipes-devtools/git/git_2.43.0.bb
+++ b/meta/recipes-devtools/git/git_2.43.2.bb
@@ -160,4 +160,4 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
"
EXTRA_OEMAKE += "NO_GETTEXT=1"
-SRC_URI[tarball.sha256sum] =
[OE-core] [AUH] go-runtime: upgrading to 1.22.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-runtime* to *1.22.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go-runtime failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-3cd69b84ee2688fb874202377d962cf21e79dd45" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:3cd69b84ee2688fb874202377d962cf21e79dd45" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-3cd69b84ee2688fb874202377d962cf21e79dd45" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:3cd69b84ee2688fb874202377d962cf21e79dd45" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 1% || ETA: 0:00:07 Adding changed files: 3% |# | ETA: 0:00:05 Adding changed files: 5% |# | ETA: 0:00:04 Adding changed files: 6% |## | ETA: 0:00:04 Adding changed files: 8% |### | ETA: 0:00:04 Adding changed files: 10% |### | ETA: 0:00:04 Adding changed files: 12% || ETA: 0:00:03 Adding changed files: 13% || ETA: 0:00:03 Adding changed files: 15% |# | ETA: 0:00:03 Adding changed files: 17% |## | ETA: 0:00:03 Adding changed files: 18% |## | ETA: 0:00:03 Adding changed files: 20% |### | ETA: 0:00:03 Adding changed files: 22% || ETA: 0:00:03 Adding changed files: 24% || ETA: 0:00:03 Adding changed files: 25% |# | ETA: 0:00:03 Adding changed files: 27% |# | ETA: 0:00:03 Adding changed files: 29% |## | ETA: 0:00:03 Adding changed files: 30% |### | ETA: 0:00:03 Adding changed files: 32% |### | ETA: 0:00:03 Adding changed files: 34% || ETA: 0:00:02 Adding changed files: 36% || ETA: 0:00:03 Adding changed files: 37% |# | ETA: 0:00:02 Adding changed files: 39% |## | ETA: 0:00:02 Adding changed files: 41% |## | ETA: 0:00:02 Adding changed files: 42% |### | ETA: 0:00:02 Adding changed files: 44% || ETA: 0:00:02 Adding changed files: 46% || ETA: 0:00:02 Adding changed files: 48% |# | ETA: 0:00:02 Adding changed files: 49%
[OE-core] [AUH] ccache: upgrading to 4.9.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.9.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ccache-upgrade-4.9-4.9.1.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From f57b1640c14556cfbed5bda5ac0d78b05e7bcca1 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:48:10 +
Subject: [PATCH] ccache: upgrade 4.9 -> 4.9.1
---
.../ccache/{ccache_4.9.bb => ccache_4.9.1.bb} | 26 +--
.../0001-xxhash.h-Fix-build-with-gcc-12.patch | 2 +-
2 files changed, 25 insertions(+), 3 deletions(-)
rename meta/recipes-devtools/ccache/{ccache_4.9.bb => ccache_4.9.1.bb} (50%)
diff --git a/meta/recipes-devtools/ccache/ccache_4.9.bb
b/meta/recipes-devtools/ccache/ccache_4.9.1.bb
similarity index 50%
rename from meta/recipes-devtools/ccache/ccache_4.9.bb
rename to meta/recipes-devtools/ccache/ccache_4.9.1.bb
index 8550470e3f..c21987ded4 100644
--- a/meta/recipes-devtools/ccache/ccache_4.9.bb
+++ b/meta/recipes-devtools/ccache/ccache_4.9.1.bb
@@ -1,3 +1,25 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- LICENSE.adoc
+# +++ LICENSE.adoc
+# @@ -35,7 +35,7 @@
+#
+#
+# Copyright (C) 2002-2007 Andrew Tridgell
+# -Copyright (C) 2009-2023 Joel Rosdahl and other contributors
+# +Copyright (C) 2009-2024 Joel Rosdahl and other contributors
+#
+#
+#
+#
+#
+
SUMMARY = "a fast C/C++ compiler cache"
DESCRIPTION = "ccache is a compiler cache. It speeds up recompilation \
by caching the result of previous compilations and detecting when the \
@@ -7,14 +29,14 @@ HOMEPAGE = "http://ccache.samba.org;
SECTION = "devel"
LICENSE = "GPL-3.0-or-later"
-LIC_FILES_CHKSUM = "file://LICENSE.adoc;md5=11b0b581dd56bbac4f5de214d47927ca"
+LIC_FILES_CHKSUM = "file://LICENSE.adoc;md5=9896d6f0aee4d89b9e5ff0afaae0af06"
DEPENDS = "zstd"
SRC_URI = "${GITHUB_BASE_URI}/download/v${PV}/${BP}.tar.gz \
file://0001-xxhash.h-Fix-build-with-gcc-12.patch \
"
-SRC_URI[sha256sum] =
"866b2223d59333640f0e7a003cbb85b32d9ca3c9445bd9e3cf142942e69dd3ec"
+SRC_URI[sha256sum] =
"12834ecaaaf2db069dda1d1d991f91c19e3274cc04a471af5b64195def17e90f"
inherit cmake github-releases
diff --git
a/meta/recipes-devtools/ccache/files/0001-xxhash.h-Fix-build-with-gcc-12.patch
b/meta/recipes-devtools/ccache/files/0001-xxhash.h-Fix-build-with-gcc-12.patch
index e65b830257..ff98156c22 100644
---
a/meta/recipes-devtools/ccache/files/0001-xxhash.h-Fix-build-with-gcc-12.patch
+++
b/meta/recipes-devtools/ccache/files/0001-xxhash.h-Fix-build-with-gcc-12.patch
@@ -1,4 +1,4 @@
-From d17fdacf4892a15fafb56b0890ece05b485e89fb Mon Sep 17 00:00:00 2001
+From 08364b8e61dbb85adb9a7ed7a6504d8b6f74c57d Mon Sep 17 00:00:00 2001
From: Mingli Yu
Date: Mon, 6 Jun 2022 17:53:20 +0800
Subject: [PATCH] xxhash.h: Fix build with gcc-12
--
2.42.0
packages/core2-64-poky-linux/ccache/ccache-dbg: PKGSIZE changed from 33606768
to 33772656 (+0%)
packages/core2-64-poky-linux/ccache/ccache-dbg: PKGV changed from 4.9 [default]
to 4.9.1 [default]
packages/core2-64-poky-linux/ccache/ccache-dbg: PV changed from "4.9" to "4.9.1"
packages/core2-64-poky-linux/ccache/ccache-dev: PKGV changed from 4.9 [default]
to 4.9.1 [default]
packages/core2-64-poky-linux/ccache/ccache-dev: PV changed from "4.9" to "4.9.1"
packages/core2-64-poky-linux/ccache/ccache-doc: PKGV changed from 4.9 [default]
to 4.9.1 [default]
packages/core2-64-poky-linux/ccache/ccache-doc: PV changed from "4.9" to "4.9.1"
packages/core2-64-poky-linux/ccache/ccache-locale: PKGV changed from 4.9
[default] to 4.9.1 [default]
packages/core2-64-poky-linux/ccache/ccache-locale: PV changed from "4.9" to
"4.9.1"
packages/core2-64-poky-linux/ccache/ccache-src: PKGSIZE changed from 2249863 to
2250219 (+0%)
packages/core2-64-poky-linux/ccache/ccache-src: PKGV changed from 4.9 [default]
to 4.9.1 [default]
packages/core2-64-poky-linux/ccache/ccache-src: PV changed from
[OE-core] [AUH] dpkg: upgrading to 1.22.4 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dpkg* to *1.22.4* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe dpkg failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-0cd8bc141d7256eda5af2482b6233098ce907020" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:0cd8bc141d7256eda5af2482b6233098ce907020" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds INFO: Extracting current version source... INFO: SRC_URI contains some conditional appends/prepends - will create branches to represent these INFO: Extracting upgraded version source... INFO: Rebasing devtool onto 4baf1e5485b6eaf4eb4347bfb9c4923fd2737488 WARNING: Command 'git rebase 4baf1e5485b6eaf4eb4347bfb9c4923fd2737488' failed: Auto-merging data/ostable Auto-merging data/tupletable CONFLICT (content): Merge conflict in data/tupletable You will need to resolve conflicts in order to complete the upgrade. INFO: Rebasing devtool-override-class-native onto 4baf1e5485b6eaf4eb4347bfb9c4923fd2737488 WARNING: Command 'git rebase 4baf1e5485b6eaf4eb4347bfb9c4923fd2737488' failed: Auto-merging data/ostable Auto-merging data/tupletable CONFLICT (content): Merge conflict in data/tupletable You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/dpkg INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/dpkg/dpkg_1.22.4.bb Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195576): https://lists.openembedded.org/g/openembedded-core/message/195576 Mute This Topic: https://lists.openembedded.org/mt/104377471/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] elfutils: upgrading to 0.190 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *elfutils* to *0.190* has
Succeeded.
Next steps:
- apply the patch: git am 0001-elfutils-upgrade-0.189-0.190.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 542f640e17fd291f51ba06a19b28102eda88bc7a Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 07:27:57 +
Subject: [PATCH] elfutils: upgrade 0.189 -> 0.190
---
.../{elfutils_0.189.bb => elfutils_0.190.bb} | 2 +-
...001-Add-helper-function-for-basename.patch | 117 --
.../elfutils/files/0001-dso-link-change.patch | 12 +-
...libasm-may-link-with-libbz2-if-found.patch | 6 +-
...-check-data_list.data.d.d_buf-before.patch | 6 +-
...-skip-the-test-when-gcc-not-deployed.patch | 2 +-
...m-compile-test_nlist-with-standard-C.patch | 6 +-
...against-upcoming-gcc-14-Werror-callo.patch | 6 +-
...cvt_gunhash-if-dest-and-src-are-same.patch | 8 +-
.../elfutils/files/0003-fixheadercheck.patch | 6 +-
.../elfutils/files/0003-musl-utils.patch | 6 +-
.../0006-Fix-build-on-aarch64-musl.patch | 2 +-
.../elfutils/files/ptest.patch| 10 +-
13 files changed, 113 insertions(+), 76 deletions(-)
rename meta/recipes-devtools/elfutils/{elfutils_0.189.bb => elfutils_0.190.bb}
(98%)
diff --git a/meta/recipes-devtools/elfutils/elfutils_0.189.bb
b/meta/recipes-devtools/elfutils/elfutils_0.190.bb
similarity index 98%
rename from meta/recipes-devtools/elfutils/elfutils_0.189.bb
rename to meta/recipes-devtools/elfutils/elfutils_0.190.bb
index 076ba47358..8c54c78fc1 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.189.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.190.bb
@@ -27,7 +27,7 @@ SRC_URI =
"https://sourceware.org/elfutils/ftp/${PV}/${BP}.tar.bz2 \
SRC_URI:append:libc-musl = " \
file://0003-musl-utils.patch \
"
-SRC_URI[sha256sum] =
"39bd8f1a338e2b7cd4abc3ff11a0eddc6e690f69578a57478d8179b4148708c8"
+SRC_URI[sha256sum] =
"8e00a3a9b5f04bc1dc273ae86281d2d26ed412020b391ffcc23198f10231d692"
inherit autotools gettext ptest pkgconfig
diff --git
a/meta/recipes-devtools/elfutils/files/0001-Add-helper-function-for-basename.patch
b/meta/recipes-devtools/elfutils/files/0001-Add-helper-function-for-basename.patch
index 3e6033fd75..d5bd15770a 100644
---
a/meta/recipes-devtools/elfutils/files/0001-Add-helper-function-for-basename.patch
+++
b/meta/recipes-devtools/elfutils/files/0001-Add-helper-function-for-basename.patch
@@ -1,4 +1,4 @@
-From 666372a5d8d5a23203c70d583904097c9e49c5a0 Mon Sep 17 00:00:00 2001
+From f4d9a4715412df3efeb2e874cfa1473976b8c427 Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Sat, 9 Dec 2023 18:23:03 -0800
Subject: [PATCH] Add helper function for basename
@@ -12,27 +12,31 @@ libraries which have POSIX implementation only.
Upstream-Status: Submitted
[https://sourceware.org/pipermail/elfutils-devel/2023q4/006727.html]
[1]
https://git.musl-libc.org/cgit/musl/commit/?id=725e17ed6dff4d0cd22487bb64470881e86a92e7
Signed-off-by: Khem Raj
+
---
lib/Makefile.am | 2 +-
lib/libeu.h | 1 +
- lib/{libeu.h => xbasename.c} | 31 ++--
+ lib/xbasename.c | 39
libdw/dwarf_getsrc_file.c| 3 ++-
libdwfl/core-file.c | 3 ++-
libdwfl/dwfl_module_getsrc_file.c| 3 ++-
libdwfl/dwfl_segment_report_module.c | 3 ++-
- libdwfl/find-debuginfo.c | 7 ---
+ libdwfl/find-debuginfo.c | 7 ++---
libdwfl/link_map.c | 3 ++-
libdwfl/linux-kernel-modules.c | 3 ++-
- src/addr2line.c | 5 +++--
- src/ar.c | 5 +++--
- src/nm.c | 4 ++--
+ src/addr2line.c | 5 ++--
+ src/ar.c | 5 ++--
+ src/nm.c | 4 +--
src/stack.c | 3 ++-
src/strip.c | 2 +-
- tests/show-die-info.c| 2 +-
- tests/varlocs.c | 2 +-
- 17 files changed, 42 insertions(+), 40 deletions(-)
- copy lib/{libeu.h =>
[OE-core] [AUH] dnf: upgrading to 4.19.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dnf* to *4.19.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dnf-upgrade-4.18.2-4.19.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From f5ebc905917919aec0560ef533e410eb5c5b528e Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:58:37 +
Subject: [PATCH] dnf: upgrade 4.18.2 -> 4.19.0
---
...01-Corretly-install-tmpfiles.d-configuration.patch | 7 ++-
...ot-hardcode-etc-and-systemd-unit-directories.patch | 4 ++--
.../dnf/dnf/0001-dnf-write-the-log-lock-to-root.patch | 2 +-
.../0001-set-python-path-for-completion_helper.patch | 8 +++-
.../0005-Do-not-prepend-installroot-to-logdir.patch | 10 --
...not-set-PYTHON_INSTALL_DIR-by-running-python.patch | 2 +-
.../dnf/dnf/0030-Run-python-scripts-using-env.patch | 11 ---
.../dnf/{dnf_4.18.2.bb => dnf_4.19.0.bb} | 2 +-
8 files changed, 18 insertions(+), 28 deletions(-)
rename meta/recipes-devtools/dnf/{dnf_4.18.2.bb => dnf_4.19.0.bb} (98%)
diff --git
a/meta/recipes-devtools/dnf/dnf/0001-Corretly-install-tmpfiles.d-configuration.patch
b/meta/recipes-devtools/dnf/dnf/0001-Corretly-install-tmpfiles.d-configuration.patch
index 6692b41a16..e2185fab4a 100644
---
a/meta/recipes-devtools/dnf/dnf/0001-Corretly-install-tmpfiles.d-configuration.patch
+++
b/meta/recipes-devtools/dnf/dnf/0001-Corretly-install-tmpfiles.d-configuration.patch
@@ -1,7 +1,7 @@
-From 05e059cd4e9910c00b32d377f4f98e3c8dde6bc6 Mon Sep 17 00:00:00 2001
+From 4aaddad69af40f46d99f643b8c31fe8c743553ed Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Thu, 26 Jan 2017 16:36:20 +0200
-Subject: [PATCH 4/5] Corretly install tmpfiles.d configuration
+Subject: [PATCH] Corretly install tmpfiles.d configuration
Upstream-Status: Inappropriate [oe-core specific]
Signed-off-by: Alexander Kanavin
@@ -17,6 +17,3 @@ index f69c773e..3eb6d0e8 100644
@@ -1 +1 @@
-INSTALL (FILES dnf.conf DESTINATION /usr/lib/tmpfiles.d/)
+INSTALL (FILES dnf.conf DESTINATION ${SYSCONFDIR}/tmpfiles.d/)
---
-2.14.2
-
diff --git
a/meta/recipes-devtools/dnf/dnf/0001-Do-not-hardcode-etc-and-systemd-unit-directories.patch
b/meta/recipes-devtools/dnf/dnf/0001-Do-not-hardcode-etc-and-systemd-unit-directories.patch
index cb09f17a56..32fa62d4f7 100644
---
a/meta/recipes-devtools/dnf/dnf/0001-Do-not-hardcode-etc-and-systemd-unit-directories.patch
+++
b/meta/recipes-devtools/dnf/dnf/0001-Do-not-hardcode-etc-and-systemd-unit-directories.patch
@@ -1,4 +1,4 @@
-From ffb7942cc73c3d2c6aa7c689cdaf9bc0bcbc144b Mon Sep 17 00:00:00 2001
+From fb22fbbc78a61e23a9f248eeb4bc7eedbe492676 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Thu, 26 Jan 2017 16:25:47 +0200
Subject: [PATCH] Do not hardcode /etc and systemd unit directories
@@ -11,7 +11,7 @@ Signed-off-by: Alexander Kanavin
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
-index 73552967..38cf4fbf 100644
+index 4aee99fb..9e2e9e9e 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -3,8 +3,8 @@ CMAKE_MINIMUM_REQUIRED (VERSION 2.4)
diff --git
a/meta/recipes-devtools/dnf/dnf/0001-dnf-write-the-log-lock-to-root.patch
b/meta/recipes-devtools/dnf/dnf/0001-dnf-write-the-log-lock-to-root.patch
index eb0309d81a..8539c185df 100644
--- a/meta/recipes-devtools/dnf/dnf/0001-dnf-write-the-log-lock-to-root.patch
+++ b/meta/recipes-devtools/dnf/dnf/0001-dnf-write-the-log-lock-to-root.patch
@@ -1,4 +1,4 @@
-From 3bd0faf58cc9ad531e6b63d5660c4b8316e8daed Mon Sep 17 00:00:00 2001
+From 3a0901359983cf60f5e27b2d0b0989ad173e348b Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Tue, 28 Apr 2020 15:55:00 +0200
Subject: [PATCH] dnf: write the log lock to root
diff --git
a/meta/recipes-devtools/dnf/dnf/0001-set-python-path-for-completion_helper.patch
b/meta/recipes-devtools/dnf/dnf/0001-set-python-path-for-completion_helper.patch
index 448f6408bc..85c6d68af5 100644
---
a/meta/recipes-devtools/dnf/dnf/0001-set-python-path-for-completion_helper.patch
+++
b/meta/recipes-devtools/dnf/dnf/0001-set-python-path-for-completion_helper.patch
@@ -1,16 +1,17 @@
-From 7e79b3b67fd5cecd7380e7e365fd88eca63b5bfa Mon Sep 17 00:00:00 2001
+From
[OE-core] [AUH] ovmf: upgrading to edk2-stable202311 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202311* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-ovmf-upgrade-edk2-stable202308-edk2-stable202311.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- >From 7955af7c496836e1f077ab349e6a96a06ec7b103 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Thu, 15 Feb 2024 06:20:16 + Subject: [PATCH] ovmf: upgrade edk2-stable202308 -> edk2-stable202311 --- ...ovmf-update-path-to-native-BaseTools.patch | 10 ++- ...ile-adjust-to-build-in-under-bitbake.patch | 6 +- .../ovmf/ovmf/0003-debug-prefix-map.patch | 24 --- .../ovmf/ovmf/0004-reproducible.patch | 18 +++--- ...005-Committing-changes-from-do_patch.patch | 64 +++ meta/recipes-core/ovmf/ovmf_git.bb| 5 +- 6 files changed, 92 insertions(+), 35 deletions(-) create mode 100644 meta/recipes-core/ovmf/ovmf/0005-Committing-changes-from-do_patch.patch diff --git a/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch b/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch index 490d9e8046..ffae28b271 100644 --- a/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch +++ b/meta/recipes-core/ovmf/ovmf/0001-ovmf-update-path-to-native-BaseTools.patch @@ -1,7 +1,7 @@ -From d8df6b6433351763e1db791dd84d432983d2b249 Mon Sep 17 00:00:00 2001 +From e99b283d0ef0f05319a6b63d935b882111c6fe8f Mon Sep 17 00:00:00 2001 From: Ricardo Neri Date: Thu, 9 Jun 2016 02:23:01 -0700 -Subject: [PATCH 1/4] ovmf: update path to native BaseTools +Subject: [PATCH] ovmf: update path to native BaseTools BaseTools is a set of utilities to build EDK-based firmware. These utilities are used during the build process. Thus, they need to be built natively. @@ -11,12 +11,13 @@ with the appropriate location before building. Signed-off-by: Ricardo Neri Upstream-Status: Inappropriate [oe-core cross compile specific] + --- OvmfPkg/build.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh -index b0334fb76e..094f86f096 100755 +index 279f0d099a..285f061bf4 100755 --- a/OvmfPkg/build.sh +++ b/OvmfPkg/build.sh @@ -24,7 +24,7 @@ then @@ -28,6 +29,3 @@ index b0334fb76e..094f86f096 100755 echo $EDK_TOOLS_PATH source edksetup.sh BaseTools else --- -2.30.2 - diff --git a/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch b/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch index eeedc9e20f..f4852369c4 100644 --- a/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch +++ b/meta/recipes-core/ovmf/ovmf/0002-BaseTools-makefile-adjust-to-build-in-under-bitbake.patch @@ -1,4 +1,4 @@ -From ac9df4fb92965f1f95a5bdbde5f2f86d0c569711 Mon Sep 17 00:00:00 2001 +From 3812bc4c45e826f313c93e24039b2795875564f3 Mon Sep 17 00:00:00 2001 From: Ricardo Neri Date: Fri, 26 Jul 2019 17:34:26 -0400 Subject: [PATCH] BaseTools: makefile: adjust to build in under bitbake @@ -13,6 +13,7 @@ to fight against how upstream wants to configure the build. Signed-off-by: Ricardo Neri Upstream-Status: Inappropriate [needs to be converted to in-recipe fixups] + --- BaseTools/Source/C/Makefiles/header.makefile | 15 +++ 1 file changed, 7 insertions(+), 8 deletions(-) @@ -64,6 +65,3 @@ index d369908a09..22c670f316 100644 ifeq ($(HOST_ARCH), IA32) # # Snow Leopard is a 32-bit and 64-bit environment. uname -m returns i386, but gcc defaults --- -2.30.2 - diff --git a/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch b/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch index c0c763c1cf..86361c5b7d 100644 --- a/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch +++ b/meta/recipes-core/ovmf/ovmf/0003-debug-prefix-map.patch @@ -1,7 +1,7 @@ -From 03e536b20d0b72cf078052f6748de8df3836625c Mon Sep 17 00:00:00 2001 +From 9f1d683e53a9e4c7745d525cddf5cbf462e09ef8 Mon Sep 17 00:00:00 2001 From: Alexander Kanavin Date: Mon, 14 Jun 2021 19:56:28 +0200 -Subject: [PATCH 3/4] debug prefix map
[OE-core] [AUH] zlib: upgrading to 1.3.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *zlib* to *1.3.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe zlib failed. NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded 1857 entries from dependency cache. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-843fab59ebf53e9208cb7fb666aa374d0b819e9b" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:843fab59ebf53e9208cb7fb666aa374d0b819e9b" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 10 Local 10 Mirrors 0 Missed 0 Current 20 (100% match, 100% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 103 tasks of which 100 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds Loading cache...done. Loaded 1857 entries from dependency cache. Parsing recipes...done. Parsing of 915 .bb files complete (913 cached, 2 parsed). 1858 targets, 35 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.7.2" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.3+snapshot-843fab59ebf53e9208cb7fb666aa374d0b819e9b" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp workspace= "tmp-auh-upgrades:843fab59ebf53e9208cb7fb666aa374d0b819e9b" Initialising tasks...NOTE: The /proc/pressure files can't be read. Continuing build without monitoring pressure Sstate summary: Wanted 1 Local 0 Mirrors 0 Missed 1 Current 0 (0% match, 0% complete) done. NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 3 tasks of which 0 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 100% || Time: 0:00:00 INFO: Extracting current version source... INFO: Adding local source files to srctree... INFO: Extracting upgraded version source... INFO: Fetching https://zlib.net/zlib-1.3.1.tar.gz... INFO: Rebasing devtool onto 9307d19df4aee56788834f142fcdeaee74c9262e WARNING: Command 'git rebase 9307d19df4aee56788834f142fcdeaee74c9262e' failed: Auto-merging configure CONFLICT (content): Merge conflict in configure You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/workspace/sources/zlib INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/workspace/recipes/zlib/zlib_1.3.1.bb Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195568): https://lists.openembedded.org/g/openembedded-core/message/195568 Mute This Topic: https://lists.openembedded.org/mt/104377463/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] btrfs-tools: upgrading to 6.7.1 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.7.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.5.3-6.7.1.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From d7bb17b078b6d76944cd6165913a12cbc5884d33 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:43:34 +
Subject: [PATCH] btrfs-tools: upgrade 6.5.3 -> 6.7.1
---
...-a-possibility-to-specify-where-python-modules-ar.patch | 7 ---
.../{btrfs-tools_6.5.3.bb => btrfs-tools_6.7.1.bb} | 2 +-
2 files changed, 5 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.5.3.bb =>
btrfs-tools_6.7.1.bb} (98%)
diff --git
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
index 5846f04d1a..c3c7c81adf 100644
---
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
+++
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-Add-a-possibility-to-specify-where-python-modules-ar.patch
@@ -1,4 +1,4 @@
-From d3adfc21c9cc264bd191722f102963cbc4794259 Mon Sep 17 00:00:00 2001
+From bbc17e1b2ae4bdb6b0b517209899d6cf31fdb985 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Wed, 23 May 2018 21:20:35 +0300
Subject: [PATCH] Add a possibility to specify where python modules are
@@ -6,15 +6,16 @@ Subject: [PATCH] Add a possibility to specify where python
modules are
Upstream-Status: Inappropriate [oe-core specific to solve multilib use case]
Signed-off-by: Alexander Kanavin
+
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
-index 1697794c..8ab38818 100644
+index 374f59b9..ed083f6b 100644
--- a/Makefile
+++ b/Makefile
-@@ -651,7 +651,7 @@ endif
+@@ -959,7 +959,7 @@ endif
ifeq ($(PYTHON_BINDINGS),1)
install_python: libbtrfsutil_python
$(Q)cd libbtrfsutil/python; \
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.5.3.bb
b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.7.1.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.5.3.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.7.1.bb
index 6455efd1bc..0cf91c9f13 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.5.3.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.7.1.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
SRC_URI =
"git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master;protocol=https
\
file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-SRCREV = "a45c360b64660477c726e192d9e92ceb73a50f80"
+SRCREV = "60abf7a90776c2405f616182ef6129474bbcb109"
S = "${WORKDIR}/git"
PACKAGECONFIG ??= " \
--
2.42.0
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PV changed from
"6.5.3" to "6.7.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGV changed from
6.5.3 [default] to 6.7.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGSIZE changed from
24927624 to 25060264 (+1%)
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PV changed from
"6.5.3" to "6.7.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-dev: PKGV changed from
6.5.3 [default] to 6.7.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-doc: PV changed from
"6.5.3" to "6.7.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-doc: PKGV changed from
6.5.3 [default] to 6.7.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-locale: PV changed from
"6.5.3" to "6.7.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-locale: PKGV changed from
6.5.3 [default] to 6.7.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PV changed from
"6.5.3" to "6.7.1"
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PKGV changed from
6.5.3 [default] to 6.7.1 [default]
packages/core2-64-poky-linux/btrfs-tools/btrfs-tools-src: PKGSIZE changed from
4123002 to 4155369 (+1%)
[OE-core] [AUH] update-rc.d: upgrading to b8f950105010270a768aa12245d6abf166346015 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *update-rc.d* to *b8f950105010270a768aa12245d6abf166346015* has Succeeded. Next steps: - apply the patch: git am 0001-update-rc.d-upgrade-to-latest-revision.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- >From 1eb53f877bd13a6f98fcd7378278677ee55b0a58 Mon Sep 17 00:00:00 2001 From: Upgrade Helper Date: Thu, 15 Feb 2024 06:37:20 + Subject: [PATCH] update-rc.d: upgrade to latest revision --- meta/recipes-core/update-rc.d/update-rc.d_0.8.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb b/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb index 043cb3f13e..ba622fe716 100644 --- a/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb +++ b/meta/recipes-core/update-rc.d/update-rc.d_0.8.bb @@ -7,7 +7,7 @@ LICENSE = "GPL-2.0-or-later" LIC_FILES_CHKSUM = "file://update-rc.d;beginline=5;endline=15;md5=d40a07c27f535425934bb5001f2037d9" SRC_URI = "git://git.yoctoproject.org/update-rc.d;branch=master;protocol=https" -SRCREV = "8636cf478d426b568c1be11dbd9346f67e03adac" +SRCREV = "b8f950105010270a768aa12245d6abf166346015" UPSTREAM_CHECK_COMMITS = "1" -- 2.42.0 0001-update-rc.d-upgrade-to-latest-revision.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195569): https://lists.openembedded.org/g/openembedded-core/message/195569 Mute This Topic: https://lists.openembedded.org/mt/104377464/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] createrepo-c: upgrading to 1.0.4 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *createrepo-c* to *1.0.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-createrepo-c-upgrade-1.0.3-1.0.4.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 53d26df5db679bef4a59e97196c95365c12a2de1 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:51:44 +
Subject: [PATCH] createrepo-c: upgrade 1.0.3 -> 1.0.4
---
...01-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch | 6 ++
.../createrepo-c/0001-include-rpm-rpmstring.h.patch | 4 ++--
.../{createrepo-c_1.0.3.bb => createrepo-c_1.0.4.bb}| 2 +-
3 files changed, 5 insertions(+), 7 deletions(-)
rename meta/recipes-devtools/createrepo-c/{createrepo-c_1.0.3.bb =>
createrepo-c_1.0.4.bb} (96%)
diff --git
a/meta/recipes-devtools/createrepo-c/createrepo-c/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch
b/meta/recipes-devtools/createrepo-c/createrepo-c/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch
index b63fe53944..fc74208a7e 100644
---
a/meta/recipes-devtools/createrepo-c/createrepo-c/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch
+++
b/meta/recipes-devtools/createrepo-c/createrepo-c/0001-Do-not-set-PYTHON_INSTALL_DIR-by-running-python.patch
@@ -1,4 +1,4 @@
-From 6f8f6d151b831b60f6e7892aa9294a6361353c72 Mon Sep 17 00:00:00 2001
+From 5c55a3e3411a6ba53c8d631f5db73e4e51995669 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Fri, 30 Dec 2016 18:31:02 +0200
Subject: [PATCH] Do not set PYTHON_INSTALL_DIR by running python
@@ -6,6 +6,7 @@ Subject: [PATCH] Do not set PYTHON_INSTALL_DIR by running python
Upstream-Status: Inappropriate [oe-core specific]
Signed-off-by: Alexander Kanavin
Signed-off-by: Wang Mingyu
+
---
src/python/CMakeLists.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -23,6 +24,3 @@ index a31b14d..01fd8ca 100644
INCLUDE_DIRECTORIES (${PYTHON_INCLUDE_PATH})
MESSAGE(STATUS "Python install dir is ${PYTHON_INSTALL_DIR}")
---
-2.25.1
-
diff --git
a/meta/recipes-devtools/createrepo-c/createrepo-c/0001-include-rpm-rpmstring.h.patch
b/meta/recipes-devtools/createrepo-c/createrepo-c/0001-include-rpm-rpmstring.h.patch
index b7e5710b39..6fe881df61 100644
---
a/meta/recipes-devtools/createrepo-c/createrepo-c/0001-include-rpm-rpmstring.h.patch
+++
b/meta/recipes-devtools/createrepo-c/createrepo-c/0001-include-rpm-rpmstring.h.patch
@@ -1,4 +1,4 @@
-From eb66326c3fc6e942282d01ddd56659c78ed7400b Mon Sep 17 00:00:00 2001
+From a25b76d58bed0aeb7c38d7701edf720178c153ab Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Fri, 13 Jan 2023 13:21:51 -0800
Subject: [PATCH] include rpm/rpmstring.h
@@ -17,7 +17,7 @@ Signed-off-by: Khem Raj
1 file changed, 1 insertion(+)
diff --git a/src/xml_file.c b/src/xml_file.c
-index d2400b8..871109c 100644
+index 44b38f9..de5176b 100644
--- a/src/xml_file.c
+++ b/src/xml_file.c
@@ -19,6 +19,7 @@
diff --git a/meta/recipes-devtools/createrepo-c/createrepo-c_1.0.3.bb
b/meta/recipes-devtools/createrepo-c/createrepo-c_1.0.4.bb
similarity index 96%
rename from meta/recipes-devtools/createrepo-c/createrepo-c_1.0.3.bb
rename to meta/recipes-devtools/createrepo-c/createrepo-c_1.0.4.bb
index cfd406650c..f498bcb655 100644
--- a/meta/recipes-devtools/createrepo-c/createrepo-c_1.0.3.bb
+++ b/meta/recipes-devtools/createrepo-c/createrepo-c_1.0.4.bb
@@ -9,7 +9,7 @@ SRC_URI =
"git://github.com/rpm-software-management/createrepo_c;branch=master;p
file://0001-include-rpm-rpmstring.h.patch \
"
-SRCREV = "f5b5cb3d7389da979b9f05d72ab13979a8c2dccf"
+SRCREV = "4ade5ea5c4c636f045f29a2d8d8a57241fc5d24e"
S = "${WORKDIR}/git"
--
2.42.0
packages/core2-64-poky-linux/createrepo-c/createrepo-c-bash-completion: PKGV
changed from 1.0.3 [default] to 1.0.4 [default]
packages/core2-64-poky-linux/createrepo-c/createrepo-c-bash-completion: PV
changed from "1.0.3" to "1.0.4"
packages/core2-64-poky-linux/createrepo-c/createrepo-c-dbg: PKGV changed from
1.0.3 [default] to 1.0.4 [default]
packages/core2-64-poky-linux/createrepo-c/createrepo-c-dbg: PV changed from
"1.0.3" to "1.0.4"
packages/core2-64-poky-linux/createrepo-c/createrepo-c-dbg: FILELIST: removed
[OE-core] [AUH] glib-2.0: upgrading to 2.78.4 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-2.0* to *2.78.4* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-glib-2.0-upgrade-2.78.3-2.78.4.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 31249503e6a91d548991c791a1a1996e08cead01 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:01:31 +
Subject: [PATCH] glib-2.0: upgrade 2.78.3 -> 2.78.4
---
...t-write-bindir-into-pkg-config-files.patch | 2 +-
...0001-Fix-DATADIRNAME-on-uclibc-Linux.patch | 2 +-
...-gio-querymodules-as-libexec_PROGRAM.patch | 2 +-
...ng-about-deprecated-paths-in-schemas.patch | 2 +-
...-correctly-when-building-with-mingw3.patch | 4 ++--
...ces.c-comment-out-a-build-host-only-.patch | 2 +-
...on-Run-atomics-test-on-clang-as-well.patch | 4 ++--
...ot-enable-pidfd-features-on-native-g.patch | 4 ++--
...dcode-python-path-into-various-tools.patch | 2 +-
.../glib-2.0/glib-2.0/memory-monitor.patch| 14 ++---
.../glib-2.0/glib-2.0/native-gtkdoc.patch | 21 ---
.../glib-2.0/glib-2.0/relocate-modules.patch | 2 +-
...{glib-2.0_2.78.3.bb => glib-2.0_2.78.4.bb} | 5 +++--
13 files changed, 22 insertions(+), 44 deletions(-)
delete mode 100644 meta/recipes-core/glib-2.0/glib-2.0/native-gtkdoc.patch
rename meta/recipes-core/glib-2.0/{glib-2.0_2.78.3.bb => glib-2.0_2.78.4.bb}
(91%)
diff --git
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Do-not-write-bindir-into-pkg-config-files.patch
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Do-not-write-bindir-into-pkg-config-files.patch
index 0e5f371cb5..ab37ea4809 100644
---
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Do-not-write-bindir-into-pkg-config-files.patch
+++
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Do-not-write-bindir-into-pkg-config-files.patch
@@ -1,4 +1,4 @@
-From cf7df91cc8c3b4811235ef8aec144c5f0cf90bdb Mon Sep 17 00:00:00 2001
+From adeda9fffb7e27dcdede443fffecec243874a696 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Fri, 15 Feb 2019 11:17:27 +0100
Subject: [PATCH] Do not write $bindir into pkg-config files
diff --git
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Fix-DATADIRNAME-on-uclibc-Linux.patch
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Fix-DATADIRNAME-on-uclibc-Linux.patch
index 1254466063..15e9208720 100644
---
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Fix-DATADIRNAME-on-uclibc-Linux.patch
+++
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Fix-DATADIRNAME-on-uclibc-Linux.patch
@@ -1,4 +1,4 @@
-From b907a6681c4c24e5d3745538d9fcd471cf1c4c4a Mon Sep 17 00:00:00 2001
+From f24506838dd89e11514fe272bf9f06c8a170f432 Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Sat, 15 Mar 2014 22:42:29 -0700
Subject: [PATCH] Fix DATADIRNAME on uclibc/Linux
diff --git
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Install-gio-querymodules-as-libexec_PROGRAM.patch
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Install-gio-querymodules-as-libexec_PROGRAM.patch
index 50d369c24e..7a4fae8f30 100644
---
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Install-gio-querymodules-as-libexec_PROGRAM.patch
+++
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Install-gio-querymodules-as-libexec_PROGRAM.patch
@@ -1,4 +1,4 @@
-From 6e2ddcb5465d10618345b12e0b4471ead0f14304 Mon Sep 17 00:00:00 2001
+From bf65bc4317e18babafd5d8d0f7deb544b0dcfea2 Mon Sep 17 00:00:00 2001
From: Jussi Kukkonen
Date: Tue, 22 Mar 2016 15:14:58 +0200
Subject: [PATCH] Install gio-querymodules as libexec_PROGRAM
diff --git
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Remove-the-warning-about-deprecated-paths-in-schemas.patch
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Remove-the-warning-about-deprecated-paths-in-schemas.patch
index f810574d97..80fa9af595 100644
---
a/meta/recipes-core/glib-2.0/glib-2.0/0001-Remove-the-warning-about-deprecated-paths-in-schemas.patch
+++
b/meta/recipes-core/glib-2.0/glib-2.0/0001-Remove-the-warning-about-deprecated-paths-in-schemas.patch
@@ -1,4 +1,4 @@
-From c8c223045821cac97f798cfa63f19853621a8a2a Mon Sep 17 00:00:00 2001
+From 543a25f3d7925134e4e498f94b8b67ab2269850f Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Fri, 12 Jun 2015 17:08:46 +0300
Subject: [PATCH] Remove the warning
[OE-core] [AUH] systemd-boot: upgrading to 255.3 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *255.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-systemd-boot-upgrade-255.1-255.3.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 286646e8969fb7064a6900c3467d2a865256aadc Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:24:24 +
Subject: [PATCH] systemd-boot: upgrade 255.1 -> 255.3
---
.../systemd/{systemd-boot_255.1.bb => systemd-boot_255.3.bb}| 0
meta/recipes-core/systemd/systemd.inc | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/systemd/{systemd-boot_255.1.bb =>
systemd-boot_255.3.bb} (100%)
diff --git a/meta/recipes-core/systemd/systemd-boot_255.1.bb
b/meta/recipes-core/systemd/systemd-boot_255.3.bb
similarity index 100%
rename from meta/recipes-core/systemd/systemd-boot_255.1.bb
rename to meta/recipes-core/systemd/systemd-boot_255.3.bb
diff --git a/meta/recipes-core/systemd/systemd.inc
b/meta/recipes-core/systemd/systemd.inc
index 1417e0150f..fc320c89b4 100644
--- a/meta/recipes-core/systemd/systemd.inc
+++ b/meta/recipes-core/systemd/systemd.inc
@@ -15,7 +15,7 @@ LICENSE:libsystemd = "LGPL-2.1-or-later"
LIC_FILES_CHKSUM = "file://LICENSE.GPL2;md5=751419260aa954499f7abaabaa882bbe \
file://LICENSE.LGPL2.1;md5=4fbd65380cdd255951079008b364516c"
-SRCREV = "2018ccef6645ce00c784369a22dc4e98f6d7061d"
+SRCREV = "27fc7a03218464ae9b3395120574b4c06e4c8322"
SRCBRANCH = "v255-stable"
SRC_URI =
"git://github.com/systemd/systemd-stable.git;protocol=https;branch=${SRCBRANCH}"
--
2.42.0
0001-systemd-boot-upgrade-255.1-255.3.patch
Description: Binary data
packages/core2-64-poky-linux/systemd-boot: PV changed from "255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot: PKGV changed from 255.1 [default] to
255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot-dbg: PV changed from
"255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot-dbg: PKGV changed from
255.1 [default] to 255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot-dev: PV changed from
"255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot-dev: PKGV changed from
255.1 [default] to 255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot-doc: PV changed from
"255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot-doc: PKGV changed from
255.1 [default] to 255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot-locale: PV changed from
"255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot-locale: PKGV changed
from 255.1 [default] to 255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot-src: PV changed from
"255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot-src: PKGV changed from
255.1 [default] to 255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot-staticdev: PV changed
from "255.1" to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot-staticdev: PKGV changed
from 255.1 [default] to 255.3 [default]
packages/core2-64-poky-linux/systemd-boot/systemd-boot: PV changed from "255.1"
to "255.3"
packages/core2-64-poky-linux/systemd-boot/systemd-boot: PKGV changed from 255.1
[default] to 255.3 [default]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195563):
https://lists.openembedded.org/g/openembedded-core/message/195563
Mute This Topic: https://lists.openembedded.org/mt/104377458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] ofono: upgrading to 2.4 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ofono* to *2.4* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-ofono-upgrade-2.3-2.4.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 804bfba72b8b9f8b0cd256d2885ece0701ab06ec Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 05:41:02 +
Subject: [PATCH] ofono: upgrade 2.3 -> 2.4
---
...mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch | 6 ++
...im-Fix-build-with-ell-0.39-by-restoring-unlikely-m.patch | 5 +++--
.../ofono/{ofono_2.3.bb => ofono_2.4.bb}| 2 +-
3 files changed, 6 insertions(+), 7 deletions(-)
rename meta/recipes-connectivity/ofono/{ofono_2.3.bb => ofono_2.4.bb} (95%)
diff --git
a/meta/recipes-connectivity/ofono/ofono/0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
b/meta/recipes-connectivity/ofono/ofono/0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
index 8a5a300adc..f5def3b222 100644
---
a/meta/recipes-connectivity/ofono/ofono/0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
+++
b/meta/recipes-connectivity/ofono/ofono/0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
@@ -1,4 +1,4 @@
-From 22b52db4842611ac31a356f023fc09595384e2ad Mon Sep 17 00:00:00 2001
+From 4c72571b6dde16406fce49906b0d69aa193adfef Mon Sep 17 00:00:00 2001
From: Khem Raj
Date: Thu, 23 May 2019 18:11:22 -0700
Subject: [PATCH] mbim: add an optional TEMP_FAILURE_RETRY macro copy
@@ -7,6 +7,7 @@ Fixes build on musl which does not provide this macro
Upstream-Status: Submitted
[https://lists.ofono.org/pipermail/ofono/2019-May/019370.html]
Signed-off-by: Khem Raj
+
---
drivers/mbimmodem/mbim-private.h | 9 +
1 file changed, 9 insertions(+)
@@ -31,6 +32,3 @@ index e159235..51693ea 100644
enum mbim_control_message {
MBIM_OPEN_MSG = 0x1,
MBIM_CLOSE_MSG = 0x2,
---
-2.21.0
-
diff --git
a/meta/recipes-connectivity/ofono/ofono/0002-mbim-Fix-build-with-ell-0.39-by-restoring-unlikely-m.patch
b/meta/recipes-connectivity/ofono/ofono/0002-mbim-Fix-build-with-ell-0.39-by-restoring-unlikely-m.patch
index 3655b3fd66..eb2573b697 100644
---
a/meta/recipes-connectivity/ofono/ofono/0002-mbim-Fix-build-with-ell-0.39-by-restoring-unlikely-m.patch
+++
b/meta/recipes-connectivity/ofono/ofono/0002-mbim-Fix-build-with-ell-0.39-by-restoring-unlikely-m.patch
@@ -1,4 +1,4 @@
-From 76e4054801350ebd4a44057379431a33d460ad0f Mon Sep 17 00:00:00 2001
+From 79f62dd09cb33ac5022cfa28a967dc482749c725 Mon Sep 17 00:00:00 2001
From: Martin Jansa
Date: Wed, 21 Apr 2021 11:01:34 +
Subject: [PATCH] mbim: Fix build with ell-0.39 by restoring unlikely macro
@@ -7,12 +7,13 @@ Subject: [PATCH] mbim: Fix build with ell-0.39 by restoring
unlikely macro
Upstream-Status: Pending
Signed-off-by: Martin Jansa
+
---
drivers/mbimmodem/mbim-private.h | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/mbimmodem/mbim-private.h
b/drivers/mbimmodem/mbim-private.h
-index 51693eae..d917312c 100644
+index 51693ea..d917312 100644
--- a/drivers/mbimmodem/mbim-private.h
+++ b/drivers/mbimmodem/mbim-private.h
@@ -30,6 +30,10 @@
diff --git a/meta/recipes-connectivity/ofono/ofono_2.3.bb
b/meta/recipes-connectivity/ofono/ofono_2.4.bb
similarity index 95%
rename from meta/recipes-connectivity/ofono/ofono_2.3.bb
rename to meta/recipes-connectivity/ofono/ofono_2.4.bb
index db5c8173de..dae5cc3c25 100644
--- a/meta/recipes-connectivity/ofono/ofono_2.3.bb
+++ b/meta/recipes-connectivity/ofono/ofono_2.4.bb
@@ -13,7 +13,7 @@ SRC_URI = "\
file://0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch \
file://0002-mbim-Fix-build-with-ell-0.39-by-restoring-unlikely-m.patch \
"
-SRC_URI[sha256sum] =
"658f9c16aec09c56bd36424982afc6ef292c0942b3a9e8ffefdda5974f01dac3"
+SRC_URI[sha256sum] =
"93580adc1afd1890dc516efb069de0c5cdfef014415256ddfb28ab172df2d11d"
inherit autotools pkgconfig update-rc.d systemd gobject-introspection-data
--
2.42.0
0001-ofono-upgrade-2.3-2.4.patch
Description: Binary data
NOTE: Reconnecting to bitbake server...
Loading cache...done.
Loaded 1858 entries from dependency cache.
Parsing
[OE-core] [AUH] libxml2: upgrading to 2.12.5 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxml2* to *2.12.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxml2-upgrade-2.11.5-2.12.5.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 67e56e4d287a174de592270e2907299cb0d664b3 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:15:23 +
Subject: [PATCH] libxml2: upgrade 2.11.5 -> 2.12.5
---
.../libxml/libxml2/install-tests.patch| 8 +--
.../{libxml2_2.11.5.bb => libxml2_2.12.5.bb} | 50 +--
2 files changed, 50 insertions(+), 8 deletions(-)
rename meta/recipes-core/libxml/{libxml2_2.11.5.bb => libxml2_2.12.5.bb} (69%)
diff --git a/meta/recipes-core/libxml/libxml2/install-tests.patch
b/meta/recipes-core/libxml/libxml2/install-tests.patch
index 14ccce5873..e1d5bf0402 100644
--- a/meta/recipes-core/libxml/libxml2/install-tests.patch
+++ b/meta/recipes-core/libxml/libxml2/install-tests.patch
@@ -1,4 +1,4 @@
-From 3fc716357ce1372d9418dc86f24315b34d9808de Mon Sep 17 00:00:00 2001
+From c3aa7884fcde42ded54d61b7df7aa14e22cb29c4 Mon Sep 17 00:00:00 2001
From: Ross Burton
Date: Mon, 5 Dec 2022 17:02:32 +
Subject: [PATCH] add yocto-specific install-ptest target
@@ -13,11 +13,11 @@ Signed-off-by: Ross Burton
1 file changed, 10 insertions(+)
diff --git a/Makefile.am b/Makefile.am
-index 5bc4018..57d27af 100644
+index 0a49d37..1097c63 100644
--- a/Makefile.am
+++ b/Makefile.am
-@@ -26,6 +26,16 @@ check_PROGRAMS = \
- testlimits \
+@@ -27,6 +27,16 @@ check_PROGRAMS = \
+ testparser \
testrecurse
+ptestdir=$(libexecdir)
diff --git a/meta/recipes-core/libxml/libxml2_2.11.5.bb
b/meta/recipes-core/libxml/libxml2_2.12.5.bb
similarity index 69%
rename from meta/recipes-core/libxml/libxml2_2.11.5.bb
rename to meta/recipes-core/libxml/libxml2_2.12.5.bb
index 44336c25e1..36a80fff3f 100644
--- a/meta/recipes-core/libxml/libxml2_2.11.5.bb
+++ b/meta/recipes-core/libxml/libxml2_2.12.5.bb
@@ -1,13 +1,55 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- Copyright
+# +++ Copyright
+# @@ -1,4 +1,4 @@
+# -Except where otherwise noted in the source code (e.g. the files hash.c,
+# +Except where otherwise noted in the source code (e.g. the files dict.c,
+# list.c and the trio files, which are covered by a similar licence but
+# with different Copyright notices) all the files are:
+#
+# --- hash.c
+# +++ hash.c
+# @@ -1,10 +1,10 @@
+# - * Copyright (C) 2000,2012 Bjorn Reese and Daniel Veillard.
+# *
+# - * Permission to use, copy, modify, and distribute this software for any
+# - * purpose with or without fee is hereby granted, provided that the above
+# - * copyright notice and this permission notice appear in all copies.
+# - *
+# - * THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
+# - * WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
+# - * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE AUTHORS AND
+# - * CONTRIBUTORS ACCEPT NO RESPONSIBILITY IN ANY CONCEIVABLE MANNER.
+# + * See Copyright for the status of this software.
+# + */
+# +
+# +#define IN_LIBXML
+# +#include "libxml.h"
+# +
+# +#include
+# +#include
+# +
+#
+#
+
SUMMARY = "XML C Parser Library and Toolkit"
DESCRIPTION = "The XML Parser Library allows for manipulation of XML files.
Libxml2 exports Push and Pull type parser interfaces for both XML and HTML. It
can do DTD validation at parse time, on a parsed document instance or with an
arbitrary DTD. Libxml2 includes complete XPath, XPointer and Xinclude
implementations. It also has a SAX like interface, which is designed to be
compatible with Expat."
HOMEPAGE = "https://gitlab.gnome.org/GNOME/libxml2;
BUGTRACKER = "http://bugzilla.gnome.org/buglist.cgi?product=libxml2;
SECTION = "libs"
LICENSE = "MIT"
-LIC_FILES_CHKSUM = "file://Copyright;md5=2044417e2e5006b65a8b9067b683fcf1 \
-
[OE-core] [AUH] ttyrun: upgrading to 2.31.0 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ttyrun* to *2.31.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ttyrun-upgrade-2.30.0-2.31.0.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From d429dbcb2ebf56fc89b30dbaa1890e9e213ea25d Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 06:34:46 +
Subject: [PATCH] ttyrun: upgrade 2.30.0 -> 2.31.0
---
meta/recipes-core/ttyrun/{ttyrun_2.30.0.bb => ttyrun_2.31.0.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/ttyrun/{ttyrun_2.30.0.bb => ttyrun_2.31.0.bb} (93%)
diff --git a/meta/recipes-core/ttyrun/ttyrun_2.30.0.bb
b/meta/recipes-core/ttyrun/ttyrun_2.31.0.bb
similarity index 93%
rename from meta/recipes-core/ttyrun/ttyrun_2.30.0.bb
rename to meta/recipes-core/ttyrun/ttyrun_2.31.0.bb
index 73c6c58c9d..122dd9d8e7 100644
--- a/meta/recipes-core/ttyrun/ttyrun_2.30.0.bb
+++ b/meta/recipes-core/ttyrun/ttyrun_2.31.0.bb
@@ -7,7 +7,7 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=f5118f167b055bfd7c3450803f1847af"
SRC_URI =
"git://github.com/ibm-s390-linux/s390-tools;protocol=https;branch=master"
-SRCREV = "c217f6be6addd4d008f110efa53fbec79681dbfd"
+SRCREV = "6f15ed326491a17d83ca60cd2bda47fb5e8a0175"
S = "${WORKDIR}/git"
--
2.42.0
0001-ttyrun-upgrade-2.30.0-2.31.0.patch
Description: Binary data
packages/core2-64-poky-linux/ttyrun: PV changed from "2.30.0" to "2.31.0"
packages/core2-64-poky-linux/ttyrun: PKGV changed from 2.30.0 [default] to
2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-dbg: PKGSIZE changed from 18256 to
18264 (+0%)
packages/core2-64-poky-linux/ttyrun/ttyrun-dbg: PV changed from "2.30.0" to
"2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-dbg: PKGV changed from 2.30.0
[default] to 2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-dev: PV changed from "2.30.0" to
"2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-dev: PKGV changed from 2.30.0
[default] to 2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-doc: PV changed from "2.30.0" to
"2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-doc: PKGV changed from 2.30.0
[default] to 2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-locale: PV changed from "2.30.0" to
"2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-locale: PKGV changed from 2.30.0
[default] to 2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-src: PV changed from "2.30.0" to
"2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-src: PKGV changed from 2.30.0
[default] to 2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun-staticdev: PV changed from "2.30.0"
to "2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun-staticdev: PKGV changed from 2.30.0
[default] to 2.31.0 [default]
packages/core2-64-poky-linux/ttyrun/ttyrun: PV changed from "2.30.0" to "2.31.0"
packages/core2-64-poky-linux/ttyrun/ttyrun: PKGV changed from 2.30.0 [default]
to 2.31.0 [default]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195564):
https://lists.openembedded.org/g/openembedded-core/message/195564
Mute This Topic: https://lists.openembedded.org/mt/104377459/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] ell: upgrading to 0.62 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ell* to *0.62* has Succeeded.
Next steps:
- apply the patch: git am 0001-ell-upgrade-0.61-0.62.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 54805db3e8db6ae04f6ed27e76636a8abd0f86d6 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 05:56:42 +
Subject: [PATCH] ell: upgrade 0.61 -> 0.62
---
meta/recipes-core/ell/{ell_0.61.bb => ell_0.62.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/ell/{ell_0.61.bb => ell_0.62.bb} (89%)
diff --git a/meta/recipes-core/ell/ell_0.61.bb
b/meta/recipes-core/ell/ell_0.62.bb
similarity index 89%
rename from meta/recipes-core/ell/ell_0.61.bb
rename to meta/recipes-core/ell/ell_0.62.bb
index 5472714646..c6ec91afb4 100644
--- a/meta/recipes-core/ell/ell_0.61.bb
+++ b/meta/recipes-core/ell/ell_0.62.bb
@@ -15,7 +15,7 @@ DEPENDS = "dbus"
inherit autotools pkgconfig
SRC_URI =
"https://mirrors.edge.kernel.org/pub/linux/libs/${BPN}/${BPN}-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"c21ba3530d530c736f9b3e6acc954d4404c1ce4abaf2a4694e46ecec17653fa0"
+SRC_URI[sha256sum] =
"f1efae12085610049714dc509c6fab3478925801609ad4232ce873b7daf1e03d"
do_configure:prepend () {
mkdir -p ${S}/build-aux
--
2.42.0
packages/core2-64-poky-linux/ell/ell-dbg: PKGV changed from 0.61 [default] to
0.62 [default]
packages/core2-64-poky-linux/ell/ell-dbg: PKGSIZE changed from 1712064 to
1718568 (+0%)
packages/core2-64-poky-linux/ell/ell-dbg: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell/ell-dev: PKGV changed from 0.61 [default] to
0.62 [default]
packages/core2-64-poky-linux/ell/ell-dev: PKGSIZE changed from 119717 to 120713
(+1%)
packages/core2-64-poky-linux/ell/ell-dev: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell/ell-doc: PKGV changed from 0.61 [default] to
0.62 [default]
packages/core2-64-poky-linux/ell/ell-doc: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell/ell-locale: PKGV changed from 0.61 [default]
to 0.62 [default]
packages/core2-64-poky-linux/ell/ell-locale: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell/ell-src: PKGV changed from 0.61 [default] to
0.62 [default]
packages/core2-64-poky-linux/ell/ell-src: PKGSIZE changed from 1393061 to
1397958 (+0%)
packages/core2-64-poky-linux/ell/ell-src: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell/ell-staticdev: PKGV changed from 0.61
[default] to 0.62 [default]
packages/core2-64-poky-linux/ell/ell-staticdev: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell/ell: PKGV changed from 0.61 [default] to 0.62
[default]
packages/core2-64-poky-linux/ell/ell: PV changed from "0.61" to "0.62"
packages/core2-64-poky-linux/ell: PKGV changed from 0.61 [default] to 0.62
[default]
packages/core2-64-poky-linux/ell: SRC_URI changed from
"https://mirrors.edge.kernel.org/pub/linux/libs/ell/ell-0.61.tar.xz; to
"https://mirrors.edge.kernel.org/pub/linux/libs/ell/ell-0.62.tar.xz;
packages/core2-64-poky-linux/ell: PV changed from "0.61" to "0.62"
0001-ell-upgrade-0.61-0.62.patch
Description: Binary data
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195560):
https://lists.openembedded.org/g/openembedded-core/message/195560
Mute This Topic: https://lists.openembedded.org/mt/104377455/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] openssh: upgrading to 9.6p1 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *openssh* to *9.6p1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-openssh-upgrade-9.5p1-9.6p1.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From f26fbc3ee9cd4feabd898b8706b8952b8e0e3ac0 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 05:49:38 +
Subject: [PATCH] openssh: upgrade 9.5p1 -> 9.6p1
---
...h-log-input-and-output-files-on-erro.patch | 10 +---
...tional-support-for-systemd-sd_notify.patch | 18 +++---
.../add-test-support-for-busybox.patch| 57 +++
...igned-overflow-in-pointer-arithmatic.patch | 6 +-
.../{openssh_9.5p1.bb => openssh_9.6p1.bb}| 2 +-
5 files changed, 47 insertions(+), 46 deletions(-)
rename meta/recipes-connectivity/openssh/{openssh_9.5p1.bb =>
openssh_9.6p1.bb} (99%)
diff --git
a/meta/recipes-connectivity/openssh/openssh/0001-regress-banner.sh-log-input-and-output-files-on-erro.patch
b/meta/recipes-connectivity/openssh/openssh/0001-regress-banner.sh-log-input-and-output-files-on-erro.patch
index 2c14014fed..3f8b8b3b97 100644
---
a/meta/recipes-connectivity/openssh/openssh/0001-regress-banner.sh-log-input-and-output-files-on-erro.patch
+++
b/meta/recipes-connectivity/openssh/openssh/0001-regress-banner.sh-log-input-and-output-files-on-erro.patch
@@ -1,4 +1,4 @@
-From f5a4dacc987ca548fc86577c2dba121c86da3c34 Mon Sep 17 00:00:00 2001
+From c521081ae72b2235fb74cca0dfef2d0e3df28ad4 Mon Sep 17 00:00:00 2001
From: Mikko Rapeli
Date: Mon, 11 Sep 2023 09:55:21 +0100
Subject: [PATCH] regress/banner.sh: log input and output files on error
@@ -35,14 +35,13 @@ return value: 1
See: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15178
Signed-off-by: Mikko Rapeli
+
---
regress/banner.sh | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
-Upstream-Status: Denied [https://github.com/openssh/openssh-portable/pull/437]
-
diff --git a/regress/banner.sh b/regress/banner.sh
-index a84feb5a..de84957a 100644
+index a84feb5..de84957 100644
--- a/regress/banner.sh
+++ b/regress/banner.sh
@@ -32,7 +32,9 @@ for s in 0 10 100 1000 1 10 ; do
@@ -56,6 +55,3 @@ index a84feb5a..de84957a 100644
done
trace "test suppress banner (-q)"
---
-2.34.1
-
diff --git
a/meta/recipes-connectivity/openssh/openssh/0001-systemd-Add-optional-support-for-systemd-sd_notify.patch
b/meta/recipes-connectivity/openssh/openssh/0001-systemd-Add-optional-support-for-systemd-sd_notify.patch
index acda8f1ce9..afb48a7e15 100644
---
a/meta/recipes-connectivity/openssh/openssh/0001-systemd-Add-optional-support-for-systemd-sd_notify.patch
+++
b/meta/recipes-connectivity/openssh/openssh/0001-systemd-Add-optional-support-for-systemd-sd_notify.patch
@@ -1,4 +1,4 @@
-From be187435911cde6cc3cef6982a508261074f1e56 Mon Sep 17 00:00:00 2001
+From 9ffd0580e773579d7a03da56c5b9cc36e3eb891c Mon Sep 17 00:00:00 2001
From: Matt Jolly
Date: Thu, 2 Feb 2023 21:05:40 +1100
Subject: [PATCH] systemd: Add optional support for systemd `sd_notify`
@@ -9,16 +9,17 @@ patch based on Jakub Jelen's original
patch
Upstream-Status: Submitted
[https://github.com/openssh/openssh-portable/pull/375/commits/be187435911cde6cc3cef6982a508261074f1e56]
Signed-off-by: Xiangyu Chen
+
---
configure.ac | 24
sshd.c | 13 +
2 files changed, 37 insertions(+)
diff --git a/configure.ac b/configure.ac
-index 22fee70f..486c189f 100644
+index 379cd74..a7d0e92 100644
--- a/configure.ac
+++ b/configure.ac
-@@ -4835,6 +4835,29 @@ AC_SUBST([GSSLIBS])
+@@ -4842,6 +4842,29 @@ AC_SUBST([GSSLIBS])
AC_SUBST([K5LIBS])
AC_SUBST([CHANNELLIBS])
@@ -48,7 +49,7 @@ index 22fee70f..486c189f 100644
# Looking for programs, paths and files
PRIVSEP_PATH=/var/empty
-@@ -5634,6 +5657,7 @@ echo " libldns support: $LDNS_MSG"
+@@ -5650,6 +5673,7 @@ echo " libldns support: $LDNS_MSG"
echo " Solaris process contract support: $SPC_MSG"
echo " Solaris project support: $SP_MSG"
echo " Solaris privilege support: $SPP_MSG"
@@ -57,7 +58,7 @@ index 22fee70f..486c189f 100644
echo "
[OE-core] [AUH] efivar: upgrading to 39 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *efivar* to *39* has Succeeded.
Next steps:
- apply the patch: git am 0001-efivar-upgrade-38-39.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 1d7faf19be309858a8ab481285f1810fdb1775a5 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 05:07:14 +
Subject: [PATCH] efivar: upgrade 38 -> 39
---
.../efivar/0001-docs-do-not-build-efisecdb-manpage.patch | 3 ++-
meta/recipes-bsp/efivar/efivar_38.bb | 4 +++-
2 files changed, 5 insertions(+), 2 deletions(-)
diff --git
a/meta/recipes-bsp/efivar/efivar/0001-docs-do-not-build-efisecdb-manpage.patch
b/meta/recipes-bsp/efivar/efivar/0001-docs-do-not-build-efisecdb-manpage.patch
index cb30d3c430..af82513b21 100644
---
a/meta/recipes-bsp/efivar/efivar/0001-docs-do-not-build-efisecdb-manpage.patch
+++
b/meta/recipes-bsp/efivar/efivar/0001-docs-do-not-build-efisecdb-manpage.patch
@@ -1,4 +1,4 @@
-From f39a1481a9e465387901d52b07ae56dedcc3838b Mon Sep 17 00:00:00 2001
+From f81093c62b76b1626fc09a858964b72cb6404fc1 Mon Sep 17 00:00:00 2001
From: Alexander Kanavin
Date: Sun, 16 Jan 2022 18:25:33 +0100
Subject: [PATCH] docs: do not build efisecdb manpage
@@ -7,6 +7,7 @@ It requires mandoc, which oe-core does not have.
Upstream-Status: Inappropriate [oe-core specific]
Signed-off-by: Alexander Kanavin
+
---
docs/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/efivar/efivar_38.bb
b/meta/recipes-bsp/efivar/efivar_38.bb
index d88eb3fef5..3500acf88b 100644
--- a/meta/recipes-bsp/efivar/efivar_38.bb
+++ b/meta/recipes-bsp/efivar/efivar_38.bb
@@ -10,7 +10,7 @@ COMPATIBLE_HOST = "(i.86|x86_64|arm|aarch64).*-linux"
SRC_URI = "git://github.com/rhinstaller/efivar.git;branch=main;protocol=https \
file://0001-docs-do-not-build-efisecdb-manpage.patch \
"
-SRCREV = "90e88b221e8bc60dc50f3246051369b8f580c0d0"
+SRCREV = "c47820c37ac26286559ec004de07d48d05f3308c"
PV .= "+39+git"
S = "${WORKDIR}/git"
@@ -32,3 +32,5 @@ BBCLASSEXTEND = "native"
RRECOMMENDS:${PN}:class-target = "kernel-module-efivarfs"
CLEANBROKEN = "1"
+
+PV = "39"
--
2.42.0
0001-efivar-upgrade-38-39.patch
Description: Binary data
packages/core2-64-poky-linux/efivar/efivar-dbg: PV changed from "38+39+git" to
"39"
packages/core2-64-poky-linux/efivar/efivar-dbg: PKGSIZE changed from 1144568 to
1141256 (-0%)
packages/core2-64-poky-linux/efivar/efivar-dbg: FILELIST: removed
"/usr/lib/.debug/libefisec.so.1.38 /usr/lib/.debug/libefiboot.so.1.38
/usr/lib/.debug/libefivar.so.1.38", added "/usr/lib/.debug/libefisec.so.1.39
/usr/lib/.debug/libefiboot.so.1.39 /usr/lib/.debug/libefivar.so.1.39"
packages/core2-64-poky-linux/efivar/efivar-dbg: PKGV changed from
38+39+git0+90e88b221e to 39 [default]
packages/core2-64-poky-linux/efivar/efivar-dev: PV changed from "38+39+git" to
"39"
packages/core2-64-poky-linux/efivar/efivar-dev: PKGSIZE changed from 67885 to
67853 (-0%)
packages/core2-64-poky-linux/efivar/efivar-dev: PKGV changed from
38+39+git0+90e88b221e to 39 [default]
packages/core2-64-poky-linux/efivar/efivar-doc: PV changed from "38+39+git" to
"39"
packages/core2-64-poky-linux/efivar/efivar-doc: PKGV changed from
38+39+git0+90e88b221e to 39 [default]
packages/core2-64-poky-linux/efivar/efivar-locale: PV changed from "38+39+git"
to "39"
packages/core2-64-poky-linux/efivar/efivar-locale: PKGV changed from
38+39+git0+90e88b221e to 39 [default]
packages/core2-64-poky-linux/efivar/efivar-src: PV changed from "38+39+git" to
"39"
packages/core2-64-poky-linux/efivar/efivar-src: PKGSIZE changed from 490931 to
490953 (+0%)
packages/core2-64-poky-linux/efivar/efivar-src: PKGV changed from
38+39+git0+90e88b221e to 39 [default]
packages/core2-64-poky-linux/efivar/efivar-staticdev: PV changed from
"38+39+git" to "39"
packages/core2-64-poky-linux/efivar/efivar-staticdev: PKGV changed from
38+39+git0+90e88b221e to 39 [default]
packages/core2-64-poky-linux/efivar/efivar: PV changed from "38+39+git" to "39"
packages/core2-64-poky-linux/efivar/efivar: FILELIST: removed
"/usr/lib/libefisec.so.1.38 /usr/lib/libefiboot.so.1.38
/usr/lib/libefivar.so.1.38", added
[OE-core] [AUH] bind: upgrading to 9.18.24 SUCCEEDED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bind* to *9.18.24* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bind-upgrade-9.18.21-9.18.24.patch
- check the changes to upstream patches and summarize them in the commit
message,
- compile an image that contains the package
- perform some basic sanity tests
- amend the patch and sign it off: git commit -s --reset-author --amend
- send it to the appropriate mailing list
Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-- >8 --
>From 082de050671d3212eb50df1125ff3fda485bd971 Mon Sep 17 00:00:00 2001
From: Upgrade Helper
Date: Thu, 15 Feb 2024 05:19:07 +
Subject: [PATCH] bind: upgrade 9.18.21 -> 9.18.24
---
...1-avoid-start-failure-with-bind-user.patch | 8 +-
...d-V-and-start-log-hide-build-options.patch | 4 +-
...ching-for-json-headers-searches-sysr.patch | 4 +-
.../recipes-connectivity/bind/bind/conf.patch | 138 --
...t.d-add-support-for-read-only-rootfs.patch | 13 +-
.../bind/make-etc-initd-bind-stop-work.patch | 20 +--
.../bind/{bind_9.18.21.bb => bind_9.18.24.bb} | 2 +-
7 files changed, 120 insertions(+), 69 deletions(-)
rename meta/recipes-connectivity/bind/{bind_9.18.21.bb => bind_9.18.24.bb}
(97%)
diff --git
a/meta/recipes-connectivity/bind/bind/0001-avoid-start-failure-with-bind-user.patch
b/meta/recipes-connectivity/bind/bind/0001-avoid-start-failure-with-bind-user.patch
index ec1bc7b567..c45da02ac0 100644
---
a/meta/recipes-connectivity/bind/bind/0001-avoid-start-failure-with-bind-user.patch
+++
b/meta/recipes-connectivity/bind/bind/0001-avoid-start-failure-with-bind-user.patch
@@ -1,4 +1,4 @@
-From 31dde3562f287429eea94b77250d184818b49063 Mon Sep 17 00:00:00 2001
+From dbbb43ee107b2a614104b6880bf8557ed73dc577 Mon Sep 17 00:00:00 2001
From: Chen Qi
Date: Mon, 15 Oct 2018 16:55:09 +0800
Subject: [PATCH] avoid start failure with bind user
@@ -6,12 +6,13 @@ Subject: [PATCH] avoid start failure with bind user
Upstream-Status: Pending
Signed-off-by: Chen Qi
+
---
init.d | 1 +
1 file changed, 1 insertion(+)
diff --git a/init.d b/init.d
-index b2eec60..6e03936 100644
+index 95e8909..771d349 100644
--- a/init.d
+++ b/init.d
@@ -57,6 +57,7 @@ case "$1" in
@@ -22,6 +23,3 @@ index b2eec60..6e03936 100644
chmod 0640 /etc/bind/rndc.key
fi
if [ -f /var/run/named/named.pid ]; then
---
-2.7.4
-
diff --git
a/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
b/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
index 4c10f33f04..057540df74 100644
---
a/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
+++
b/meta/recipes-connectivity/bind/bind/0001-named-lwresd-V-and-start-log-hide-build-options.patch
@@ -1,4 +1,4 @@
-From 4e83392e840fa7b05e778710b8c202d102477a13 Mon Sep 17 00:00:00 2001
+From 65650ece1254e4f4ce92f17a6e078924fcea31e9 Mon Sep 17 00:00:00 2001
From: Hongxu Jia
Date: Mon, 27 Aug 2018 21:24:20 +0800
Subject: [PATCH] `named/lwresd -V' and start log hide build options
@@ -21,7 +21,7 @@ Signed-off-by: Armin Kuster
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
-index bf20690..c5d330f 100644
+index d8bfd85..d3be5a0 100644
--- a/configure.ac
+++ b/configure.ac
@@ -35,7 +35,7 @@ AC_DEFINE([PACKAGE_VERSION_EXTRA],
["][bind_VERSION_EXTRA]["], [BIND 9 Extra par
diff --git
a/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
b/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
index 38d07cae39..462418810c 100644
---
a/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
+++
b/meta/recipes-connectivity/bind/bind/bind-ensure-searching-for-json-headers-searches-sysr.patch
@@ -1,4 +1,4 @@
-From 5ae30329f168c1e8d2e0c3831988a4f3e9096e39 Mon Sep 17 00:00:00 2001
+From ca74b2646432db9993c6ac659726dcea135ceaf3 Mon Sep 17 00:00:00 2001
From: Paul Gortmaker
Date: Tue, 9 Jun 2015 11:22:00 -0400
Subject: [PATCH] bind: ensure searching for json headers searches sysroot
@@ -33,7 +33,7 @@ Signed-off-by: Paul Gortmaker
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
-index 2ab8ddd..92fe983 100644
+index 8aa7a90..d8bfd85 100644
--- a/configure.ac
+++ b/configure.ac
@@ -761,7 +761,7 @@ AS_CASE([$with_lmdb],
diff --git
Re: [OE-core] [PATCH 0/6] devtool: ide: Improve VSCode support
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote: > These patches improve the VSCode support in devtool ide-sdk from > Adrian Freihofer. > > I added a generic C++ configuration for the VScode > extension while awaiting for autotools support. > > A refactoring is proposed for the meson class. Without absolute compiler > paths, the linter inside VSCode will not be able to find the > cross-compiler. Let me know if you have any concerns about this > refactoring. > > The other bug fixes are relatively minor and make the tool work for some edge > cases. I noticed none of the patches in this series have Signed-off-by lines which needs to be fixed before we can merge them. Patchtest should be along shortly to say that too! I need to think about and test the meson one a bit more as absolute paths can be a source of problems. I've not looked into the others in detail yet. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19): https://lists.openembedded.org/g/openembedded-core/message/19 Mute This Topic: https://lists.openembedded.org/mt/104376742/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 6/6] devtool: code: Provide a generic C++ configuration
By default, the cpptools VSCode extension will use the host's headers
and flags for linting. This results in a lot of include errors and
misleading definitions. Even though this generic configuration doesn't
include all the depenendencies, it is a proper fallback for recipe
classes we do not accurately cover, with at least the right sysroot.
Additionally, ide-sdk automatically detects and provides a launch.json
configuration for autotools recipes so we should recommend the C++
extensions for them.
If the recipe is of another class (like Python), then the configuration
will be generated but probably useless to the user. We'd need a mecanism
to know if the recipe contains C/C++ but I'm not aware of any
class-agnostic way to do it.
---
scripts/lib/devtool/ide_plugins/ide_code.py | 25 -
scripts/lib/devtool/ide_sdk.py | 3 +++
2 files changed, 18 insertions(+), 10 deletions(-)
diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
b/scripts/lib/devtool/ide_plugins/ide_code.py
index 7b683c74086..51cf2c8a736 100644
--- a/scripts/lib/devtool/ide_plugins/ide_code.py
+++ b/scripts/lib/devtool/ide_plugins/ide_code.py
@@ -157,31 +157,33 @@ class IdeVSCode(IdeBase):
IdeBase.update_json_file(
self.dot_code_dir(modified_recipe), settings_file, settings_dict)
+def __vscode_extensions_generic(self, modified_recipe, recommendations):
+recommendations += [
+"ms-vscode.cpptools",
+"ms-vscode.cpptools-extension-pack",
+"ms-vscode.cpptools-themes"
+]
+
def __vscode_extensions_cmake(self, modified_recipe, recommendations):
if modified_recipe.build_tool is not BuildTool.CMAKE:
return
recommendations += [
"twxs.cmake",
-"ms-vscode.cmake-tools",
-"ms-vscode.cpptools",
-"ms-vscode.cpptools-extension-pack",
-"ms-vscode.cpptools-themes"
+"ms-vscode.cmake-tools"
]
def __vscode_extensions_meson(self, modified_recipe, recommendations):
if modified_recipe.build_tool is not BuildTool.MESON:
return
recommendations += [
-'mesonbuild.mesonbuild',
-"ms-vscode.cpptools",
-"ms-vscode.cpptools-extension-pack",
-"ms-vscode.cpptools-themes"
+'mesonbuild.mesonbuild'
]
def vscode_extensions(self, modified_recipe):
recommendations = []
self.__vscode_extensions_cmake(modified_recipe, recommendations)
self.__vscode_extensions_meson(modified_recipe, recommendations)
+self.__vscode_extensions_generic(modified_recipe, recommendations)
extensions_file = 'extensions.json'
IdeBase.update_json_file(
self.dot_code_dir(modified_recipe), extensions_file,
{"recommendations": recommendations})
@@ -194,8 +196,11 @@ class IdeVSCode(IdeBase):
properties_dict["configurationProvider"] = "ms-vscode.cmake-tools"
elif modified_recipe.build_tool is BuildTool.MESON:
properties_dict["configurationProvider"] = "mesonbuild.mesonbuild"
-else: # no C/C++ build
-return
+else:
+# Provide a generic linting configuration
+# We provide a C++ configuration with the proper sysroot
+properties_dict["compilerPath"] =
os.path.join(modified_recipe.staging_bindir_toolchain,
modified_recipe.cxx.split()[0])
+properties_dict["compilerArgs"] = modified_recipe.cxx.split()[1:]
properties_dicts = {
"configurations": [
diff --git a/scripts/lib/devtool/ide_sdk.py b/scripts/lib/devtool/ide_sdk.py
index 1e36f2b2093..c82b150a83e 100755
--- a/scripts/lib/devtool/ide_sdk.py
+++ b/scripts/lib/devtool/ide_sdk.py
@@ -345,6 +345,7 @@ class RecipeModified:
self.base_libdir = recipe_d.getVar('base_libdir')
self.bblayers = recipe_d.getVar('BBLAYERS').split()
self.bpn = recipe_d.getVar('BPN')
+self.cxx = recipe_d.getVar('CXX')
self.d = recipe_d.getVar('D')
self.fakerootcmd = recipe_d.getVar('FAKEROOTCMD')
self.fakerootenv = recipe_d.getVar('FAKEROOTENV')
@@ -361,6 +362,8 @@ class RecipeModified:
recipe_d.getVar('RECIPE_SYSROOT'))
self.recipe_sysroot_native = os.path.realpath(
recipe_d.getVar('RECIPE_SYSROOT_NATIVE'))
+self.staging_bindir_toolchain = os.path.realpath(
+recipe_d.getVar('STAGING_BINDIR_TOOLCHAIN'))
self.staging_incdir = os.path.realpath(
recipe_d.getVar('STAGING_INCDIR'))
self.strip_cmd = recipe_d.getVar('STRIP')
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195554):
https://lists.openembedded.org/g/openembedded-core/message/195554
Mute This Topic: https://lists.openembedded.org/mt/104376747/21656
Group Owner:
[OE-core] [PATCH 5/6] meson: use absolute cross-compiler paths
Among the files generated by meson is compile_commands.json. It is not
used by bitbake during the build. However, if the devtool workspace is
opened inside an IDE, that IDE can use compile_commands.json to
configure linting and code completion. This is notably relied on by the
new devtool ide-sdk command.
The problem is that the IDE using compile_commands.json does not know
the $PATH set-up by bitbake, so it won't find the compiler. This results
in linting errors, like missing headers. We can fix this by expliciting
the absolute compiler paths in meson.cross.
The compile_commands.json specification expressly states:
"All paths specified in the command or file fields must be either
absolute or relative to this directory."
Link: https://clang.llvm.org/docs/JSONCompilationDatabase.html
An alternative way to implement this is to directly change CXX inside
bitbake.conf to make all recipes use absolute compiler paths.Since this
would affect all recipes, so I would like to have the maintainers'
opinion on this. It could make sense to use absolute compiler paths for
all toolchain binaries, we already do so for the sysroot
TOOLCHAIN_OPTIONS.
Discussions have been opened with meson/ninja maintainers to implement
this at their level:
- https://github.com/ninja-build/ninja/issues/2383
- https://github.com/mesonbuild/meson/issues/12834
These tools have even less information on the environment so it makes
sense for Yocto to provide the absolute paths.
---
meta/classes-recipe/meson-routines.bbclass | 6 ++
meta/classes-recipe/meson.bbclass | 7 +--
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/meta/classes-recipe/meson-routines.bbclass
b/meta/classes-recipe/meson-routines.bbclass
index a944a8fff1c..9925465ed8f 100644
--- a/meta/classes-recipe/meson-routines.bbclass
+++ b/meta/classes-recipe/meson-routines.bbclass
@@ -10,6 +10,12 @@ def meson_array(var, d):
items = d.getVar(var).split()
return repr(items[0] if len(items) == 1 else items)
+def meson_array_abspath(var, d):
+import shutil
+items = d.getVar(var).split()
+items[0] = shutil.which(items[0]) or items[0]
+return repr(items[0] if len(items) == 1 else items)
+
# Map our ARCH values to what Meson expects:
# http://mesonbuild.com/Reference-tables.html#cpu-families
def meson_cpu_family(var, d):
diff --git a/meta/classes-recipe/meson.bbclass
b/meta/classes-recipe/meson.bbclass
index a849e872976..d8496854df4 100644
--- a/meta/classes-recipe/meson.bbclass
+++ b/meta/classes-recipe/meson.bbclass
@@ -64,10 +64,13 @@ addtask write_config before do_configure
do_write_config[vardeps] += "CC CXX AR NM STRIP READELF OBJCOPY CFLAGS
CXXFLAGS LDFLAGS RUSTC RUSTFLAGS EXEWRAPPER_ENABLED"
do_write_config() {
# This needs to be Py to split the args into single-element lists
+# The generated compile_commands.json file can be used by external IDEs
+# which do not know the $PATH set-up by bitbake. They need the absolute
+# compiler paths.
cat >${WORKDIR}/meson.cross <
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195553):
https://lists.openembedded.org/g/openembedded-core/message/195553
Mute This Topic: https://lists.openembedded.org/mt/104376746/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 4/6] devtool: ide: vscode: Configure read-only files
When debugging or browsing files, the user may fall into external
sources from other packages in the sysroot or dbg-rootfs. Modifying them
will only lead to confusion since they will be overwritten by Yocto. The
user should open them in a separate devtool modify session if they want
to make changes. Meanwhile, we should prevent write access to them.
---
scripts/lib/devtool/ide_plugins/ide_code.py | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
b/scripts/lib/devtool/ide_plugins/ide_code.py
index c063b7d0590..7b683c74086 100644
--- a/scripts/lib/devtool/ide_plugins/ide_code.py
+++ b/scripts/lib/devtool/ide_plugins/ide_code.py
@@ -125,7 +125,7 @@ class IdeVSCode(IdeBase):
settings_dict["cmake.configureOnOpen"] = True
settings_dict["cmake.sourceDirectory"] = modified_recipe.real_srctree
-def vscode_settings(self, modified_recipe):
+def vscode_settings(self, modified_recipe, image_recipe):
files_excludes = {
"**/.git/**": True,
"**/oe-logs/**": True,
@@ -138,9 +138,16 @@ class IdeVSCode(IdeBase):
"**/oe-workdir/**",
"**/source-date-epoch/**"
]
+files_readonly = {
+modified_recipe.recipe_sysroot + '/**': True,
+modified_recipe.recipe_sysroot_native + '/**': True,
+}
+if image_recipe.rootfs_dbg is not None:
+files_readonly[image_recipe.rootfs_dbg + '/**'] = True
settings_dict = {
"files.watcherExclude": files_excludes,
"files.exclude": files_excludes,
+"files.readonlyInclude": files_readonly,
"python.analysis.exclude": python_exclude
}
self.__vscode_settings_cmake(settings_dict, modified_recipe)
@@ -425,7 +432,7 @@ class IdeVSCode(IdeBase):
self.vscode_tasks_fallback(args, modified_recipe)
def setup_modified_recipe(self, args, image_recipe, modified_recipe):
-self.vscode_settings(modified_recipe)
+self.vscode_settings(modified_recipe, image_recipe)
self.vscode_extensions(modified_recipe)
self.vscode_c_cpp_properties(modified_recipe)
if args.target:
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195552):
https://lists.openembedded.org/g/openembedded-core/message/195552
Mute This Topic: https://lists.openembedded.org/mt/104376745/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 2/6] devtool: ide_sdk: Use bitbake's python3 for generated scripts
The generated scripts use the sys.path configuration found inside
bitbake. It can be a different python version than the one used on the
host through the IDE.
For instance, when running the generated script
deploy_target_cmake-example-core2-64 from an eSDK generated on another
machine, I got the following exception:
AssertionError: SRE module mismatch
We need to match the sys.executable to the sys.path.
---
scripts/lib/devtool/ide_sdk.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/lib/devtool/ide_sdk.py b/scripts/lib/devtool/ide_sdk.py
index db2e95616be..a82ab572998 100755
--- a/scripts/lib/devtool/ide_sdk.py
+++ b/scripts/lib/devtool/ide_sdk.py
@@ -751,7 +751,7 @@ class RecipeModified:
does not need to start a bitbake server. All information from tinfoil
is hard-coded in the generated script.
"""
-cmd_lines = ['#!/usr/bin/env python3']
+cmd_lines = ['#!%s' % str(sys.executable)]
cmd_lines.append('import sys')
cmd_lines.append('devtool_sys_path = %s' % str(sys.path))
cmd_lines.append('devtool_sys_path.reverse()')
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195550):
https://lists.openembedded.org/g/openembedded-core/message/195550
Mute This Topic: https://lists.openembedded.org/mt/104376743/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 0/6] devtool: ide: Improve VSCode support
These patches improve the VSCode support in devtool ide-sdk from Adrian Freihofer. I added a generic C++ configuration for the VScode extension while awaiting for autotools support. A refactoring is proposed for the meson class. Without absolute compiler paths, the linter inside VSCode will not be able to find the cross-compiler. Let me know if you have any concerns about this refactoring. The other bug fixes are relatively minor and make the tool work for some edge cases. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195549): https://lists.openembedded.org/g/openembedded-core/message/195549 Mute This Topic: https://lists.openembedded.org/mt/104376742/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/6] devtool: ide: Fix topdir exception for fallback mode
An exception was raised because we did not have the topdir attribute
which was used in fallback mode (non cmake/meson recipes).
Already in the merge queue in Adrian's latest patches.
---
scripts/lib/devtool/ide_sdk.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/lib/devtool/ide_sdk.py b/scripts/lib/devtool/ide_sdk.py
index 3986dc1436a..db2e95616be 100755
--- a/scripts/lib/devtool/ide_sdk.py
+++ b/scripts/lib/devtool/ide_sdk.py
@@ -366,6 +366,7 @@ class RecipeModified:
self.target_arch = recipe_d.getVar('TARGET_ARCH')
self.topdir = recipe_d.getVar('TOPDIR')
self.workdir = os.path.realpath(recipe_d.getVar('WORKDIR'))
+self.topdir = os.path.realpath(recipe_d.getVar('TOPDIR'))
self.__init_exported_variables(recipe_d)
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195548):
https://lists.openembedded.org/g/openembedded-core/message/195548
Mute This Topic: https://lists.openembedded.org/mt/104376741/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 3/6] devtool: code: Add source mapping for debug source files
When launching the debug configuration, the source files from the debug
rootfs were openened in the editor instead of the local workspace files.
We add an exception to properly map them to the file being developed and
compiled by the IDE integration. This also more closely matches what the
user would expect compared to native development.
This is also true for the devtool fallback mode.
---
scripts/lib/devtool/ide_plugins/ide_code.py | 1 +
scripts/lib/devtool/ide_sdk.py | 1 +
2 files changed, 2 insertions(+)
diff --git a/scripts/lib/devtool/ide_plugins/ide_code.py
b/scripts/lib/devtool/ide_plugins/ide_code.py
index b2193130d2e..c063b7d0590 100644
--- a/scripts/lib/devtool/ide_plugins/ide_code.py
+++ b/scripts/lib/devtool/ide_plugins/ide_code.py
@@ -234,6 +234,7 @@ class IdeVSCode(IdeBase):
if gdb_cross_config.image_recipe.rootfs_dbg:
launch_config['additionalSOLibSearchPath'] =
modified_recipe.solib_search_path_str(
gdb_cross_config.image_recipe)
+src_file_map[os.path.join("/usr/src/debug", modified_recipe.pn,
modified_recipe.pv)] = "${workspaceFolder}"
src_file_map["/usr/src/debug"] = os.path.join(
gdb_cross_config.image_recipe.rootfs_dbg, "usr", "src",
"debug")
else:
diff --git a/scripts/lib/devtool/ide_sdk.py b/scripts/lib/devtool/ide_sdk.py
index a82ab572998..1e36f2b2093 100755
--- a/scripts/lib/devtool/ide_sdk.py
+++ b/scripts/lib/devtool/ide_sdk.py
@@ -356,6 +356,7 @@ class RecipeModified:
'PACKAGE_DEBUG_SPLIT_STYLE')
self.path = recipe_d.getVar('PATH')
self.pn = recipe_d.getVar('PN')
+self.pv = recipe_d.getVar('PV')
self.recipe_sysroot = os.path.realpath(
recipe_d.getVar('RECIPE_SYSROOT'))
self.recipe_sysroot_native = os.path.realpath(
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195551):
https://lists.openembedded.org/g/openembedded-core/message/195551
Mute This Topic: https://lists.openembedded.org/mt/104376744/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 2/2] musl: fix strftime crash
Apply a patch proposed by Rich to fix the init crashes
Signed-off-by: Khem Raj
---
...akage-in-last-commit-uninitialized-p.patch | 41 +++
meta/recipes-core/musl/musl_git.bb| 1 +
2 files changed, 42 insertions(+)
create mode 100644
meta/recipes-core/musl/musl/0001-strftime-fix-breakage-in-last-commit-uninitialized-p.patch
diff --git
a/meta/recipes-core/musl/musl/0001-strftime-fix-breakage-in-last-commit-uninitialized-p.patch
b/meta/recipes-core/musl/musl/0001-strftime-fix-breakage-in-last-commit-uninitialized-p.patch
new file mode 100644
index 000..b6ef5423de6
--- /dev/null
+++
b/meta/recipes-core/musl/musl/0001-strftime-fix-breakage-in-last-commit-uninitialized-p.patch
@@ -0,0 +1,41 @@
+From 46562816d15ecd66fab7ee916a3684de29b9789a Mon Sep 17 00:00:00 2001
+From: Khem Raj
+Date: Mon, 12 Feb 2024 14:40:53 -0800
+Subject: [PATCH] strftime: fix breakage in last commit (uninitialized pointer
+ access)
+
+commit f47a5d400b8ffa26cfc5b345dbff52fec94ac7f3 overlooked that
+strtoul was responsible for setting p to a const-laundered copy of the
+format string pointer f, even in the case where there was no number to
+parse. by making the call conditional on isdigit, that copy was lost.
+
+the logic here is a mess and should be cleaned up, but for now, this
+seems to be the least invasive change that undoes the breakage.
+
+Upstream-Status: Submitted [Rich Felker (musl maintainer) is the proposer of
this patch]
+Signed-off-by: Khem Raj
+---
+ src/time/strftime.c | 7 ++-
+ 1 file changed, 6 insertions(+), 1 deletion(-)
+
+diff --git a/src/time/strftime.c b/src/time/strftime.c
+index ef590903..c40246db 100644
+--- a/src/time/strftime.c
b/src/time/strftime.c
+@@ -234,7 +234,12 @@ size_t __strftime_l(char *restrict s, size_t n, const
char *restrict f, const st
+ pad = 0;
+ if (*f == '-' || *f == '_' || *f == '0') pad = *f++;
+ if ((plus = (*f == '+'))) f++;
+- width = isdigit(*f) ? strtoul(f, , 10) : 0;
++ if (isdigit(*f)) {
++ width = strtoul(f, , 10);
++ } else {
++ width = 0;
++ p = (void *)f;
++ }
+ if (*p == 'C' || *p == 'F' || *p == 'G' || *p == 'Y') {
+ if (!width && p!=f) width = 1;
+ } else {
+--
+2.43.1
+
diff --git a/meta/recipes-core/musl/musl_git.bb
b/meta/recipes-core/musl/musl_git.bb
index fb2b188e010..190e16a6e1d 100644
--- a/meta/recipes-core/musl/musl_git.bb
+++ b/meta/recipes-core/musl/musl_git.bb
@@ -13,6 +13,7 @@ PV = "${BASEVER}+git"
SRC_URI = "git://git.musl-libc.org/musl;branch=master \
file://0001-Make-dynamic-linker-a-relative-symlink-to-libc.patch \
file://0002-ldso-Use-syslibdir-and-libdir-as-default-pathes-to-l.patch \
+
file://0001-strftime-fix-breakage-in-last-commit-uninitialized-p.patch \
"
S = "${WORKDIR}/git"
--
2.43.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195547):
https://lists.openembedded.org/g/openembedded-core/message/195547
Mute This Topic: https://lists.openembedded.org/mt/104376686/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/2] musl: Update to latest tip of trunk
Do not use https protocol for fetching
Musl author confirms that https protocol is not well supported yet on
musl git host, currently we experience this problem intermittently on
some build hosts where the fetching fails.
fatal: protocol error: bad line length character: erro
WARNING: Failed to fetch URL
git://git.etalabs.net/git/musl;branch=master;protocol=https
Brings these changes
* cf91e9b3 fix erroneous feature test macro check for ppoll
* 39838619 syslog: use C locale for timestamp generation
* 8b704868 stdc-predef.h: prevent redefining __STDC_UTF_{16,32}__ macros
* 407aea62 riscv: add TLSDESC support
* 2e1bb87a install.sh: avoid creating symlinks with restricted permissions
* 0e330722 sqrtl: fix invalid use of a non-constant-expression as static
initializer
* bd3138b7 riscv: correct symbol version of __vdso_flush_icache
* 15aa7abd elf.h: add NT_RISCV_CSR and NT_RISCV_VECTOR constants
* 25c41236 elf.h: update RISC-V relocation types
* 81cced6e add preadv2 and pwritev2 syscall wrappers, flag value macros
* f247462b expose ppoll in default feature profile
* 07af0181 move ppoll from src/linux to src/select reflecting future
standardization
* 11fb3832 remove INT_MAX limit on the n argument to snprintf/swprintf
* f47a5d40 strftime: don't attempt to parse field width without seeing a digit
* f314e133 mntent: fields are delimited only by tabs or spaces, not general
whitespace
* ee1d39bc mntent: unescape octal sequences
* e17b9d74 ldso: fix TLSDESC addend processing on archs with backwards
descriptors
* 039d3c34 ldso: convert TLSDESC_BACKWARDS from "#ifdef" to "if" logic
* 7b6a6516 byte-based printf family: emit a nul byte for %lc with argument zero
* 8c086e76 remove arbitrary limit from dns result parsing
* 2265a4c9 pass AT_NO_AUTOMOUNT when emulating fstatat via statx
* 2d84486a __year_to_secs: fix dangling pointer
* c5459df1 timer_create: volatile static -> static volatile
* 7bb11f75 ensure valid setxid return value in an unexpected error case
* 7f3a2925 synccall: add separate exit_sem to fix thread release logic bug
* 5baf2d92 ldso: use __ehdr_start if available to locate its own ELF headers
* 725e17ed remove non-prototype declaration of basename from string.h
* 6be76895 elf.h: add typedefs for Elf64_Relr and Elf32_Relr
Signed-off-by: Khem Raj
Signed-off-by: Khem Raj
---
...ic-linker-a-relative-symlink-to-libc.patch | 12 +++---
...ir-and-libdir-as-default-pathes-to-l.patch | 10 ++---
...pedefs-for-Elf64_Relr-and-Elf32_Relr.patch | 37 ---
meta/recipes-core/musl/musl_git.bb| 5 +--
4 files changed, 13 insertions(+), 51 deletions(-)
delete mode 100644
meta/recipes-core/musl/musl/0003-elf.h-add-typedefs-for-Elf64_Relr-and-Elf32_Relr.patch
diff --git
a/meta/recipes-core/musl/musl/0001-Make-dynamic-linker-a-relative-symlink-to-libc.patch
b/meta/recipes-core/musl/musl/0001-Make-dynamic-linker-a-relative-symlink-to-libc.patch
index 8b097f32768..06ab27f0eb4 100644
---
a/meta/recipes-core/musl/musl/0001-Make-dynamic-linker-a-relative-symlink-to-libc.patch
+++
b/meta/recipes-core/musl/musl/0001-Make-dynamic-linker-a-relative-symlink-to-libc.patch
@@ -1,4 +1,4 @@
-From f95b6fd0475a95c00e886219271cb5c93838e3c3 Mon Sep 17 00:00:00 2001
+From 665ecc610c261d5e98710aa0c6ccf6e4991eaf58 Mon Sep 17 00:00:00 2001
From: Amarnath Valluri
Date: Wed, 18 Jan 2017 16:14:37 +0200
Subject: [PATCH 1/2] Make dynamic linker a relative symlink to libc
@@ -35,7 +35,7 @@ index e8cc4436..466d9afd 100644
install-libs: $(ALL_LIBS:lib/%=$(DESTDIR)$(libdir)/%) $(if
$(SHARED_LIBS),$(DESTDIR)$(LDSO_PATHNAME),)
diff --git a/tools/install.sh b/tools/install.sh
-index d913b60b..b6a7f797 100755
+index 855a8ca2..a2e6a5eb 100755
--- a/tools/install.sh
+++ b/tools/install.sh
@@ -6,18 +6,20 @@
@@ -61,15 +61,15 @@ index d913b60b..b6a7f797 100755
m) mode=$OPTARG ;;
?) usage ;;
esac
-@@ -48,7 +50,7 @@ trap 'rm -f "$tmp"' EXIT INT QUIT TERM HUP
- umask 077
+@@ -49,7 +51,7 @@ umask 077
if test "$symlink" ; then
+ umask 000
-ln -s "$1" "$tmp"
+ln $symlinkflags "$1" "$tmp"
+ umask 077
else
cat < "$1" > "$tmp"
- chmod "$mode" "$tmp"
--
-2.37.2
+2.43.0
diff --git
a/meta/recipes-core/musl/musl/0002-ldso-Use-syslibdir-and-libdir-as-default-pathes-to-l.patch
b/meta/recipes-core/musl/musl/0002-ldso-Use-syslibdir-and-libdir-as-default-pathes-to-l.patch
index 59bfae5a27c..04630b32ee9 100644
---
a/meta/recipes-core/musl/musl/0002-ldso-Use-syslibdir-and-libdir-as-default-pathes-to-l.patch
+++
b/meta/recipes-core/musl/musl/0002-ldso-Use-syslibdir-and-libdir-as-default-pathes-to-l.patch
@@ -1,4 +1,4 @@
-From 3cce8716c6c3ae2e0c835caeac3780ec35090b2d Mon Sep 17 00:00:00 2001
+From e27de983ef70257ca1fd7f5096eea41613612ecf Mon Sep 17 00:00:00 2001
From: Serhey Popovych
Date: Tue, 11 Dec 2018 05:44:20 -0500
Subject: [PATCH 2/2] ldso: Use syslibdir and libdir as default pathes to
@@ -36,10 +36,10 @@ index 466d9afd..d2f458fa 100644
LDFLAGS_ALL = $(LDFLAGS_AUTO) $(LDFLAGS)
Re: [oe-core][PATCH] mesa: update 23.3.5 -> 24.0.0
On Thu, Feb 15 2024 at 11:25:24 AM +00:00:00, Ross Burton wrote: Mesa 24.0.0 is - as clearly indicated on the web site - a development snapshot. 24.0.1 is now out, can you upgrade to that? Thank you. I didn't see that mentioned in the gitlab tag. I sent the mesa-24.0.1 update as a follow up because 24.0.0 is already in master. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195545): https://lists.openembedded.org/g/openembedded-core/message/195545 Mute This Topic: https://lists.openembedded.org/mt/104358245/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[oe-core][PATCH] mesa: update 24.0.0 -> 24.0.1
Signed-off-by: Markus Volk
---
.../mesa/{mesa-gl_24.0.0.bb => mesa-gl_24.0.1.bb} | 0
meta/recipes-graphics/mesa/mesa.inc | 2 +-
meta/recipes-graphics/mesa/{mesa_24.0.0.bb => mesa_24.0.1.bb} | 0
3 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/mesa/{mesa-gl_24.0.0.bb => mesa-gl_24.0.1.bb}
(100%)
rename meta/recipes-graphics/mesa/{mesa_24.0.0.bb => mesa_24.0.1.bb} (100%)
diff --git a/meta/recipes-graphics/mesa/mesa-gl_24.0.0.bb
b/meta/recipes-graphics/mesa/mesa-gl_24.0.1.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_24.0.0.bb
rename to meta/recipes-graphics/mesa/mesa-gl_24.0.1.bb
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index fabc52f0e7..cdac01d3aa 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -20,7 +20,7 @@ SRC_URI =
"https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
file://0001-gallium-Fix-build-with-llvm-17.patch \
"
-SRC_URI[sha256sum] =
"dc7e8c077bc5884df95478263b34bdebb7e88e600689cb56fb07be2b8c304c36"
+SRC_URI[sha256sum] =
"f387192b08c471c545590dd12230a2a343244804b5fe866fec6aea02eab57613"
UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P\d+(\.\d+)+)"
diff --git a/meta/recipes-graphics/mesa/mesa_24.0.0.bb
b/meta/recipes-graphics/mesa/mesa_24.0.1.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa_24.0.0.bb
rename to meta/recipes-graphics/mesa/mesa_24.0.1.bb
--
2.43.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195544):
https://lists.openembedded.org/g/openembedded-core/message/195544
Mute This Topic: https://lists.openembedded.org/mt/104376164/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v4 3/3] cups: use LOCALE_PATHS to split localized HTML templates
On 6 Dec 2023, at 16:06, Jonathan GUILLOT via lists.openembedded.org
wrote:
> +LOCALE_PATHS += "${datadir}/cups/templates”
This doesn’t quite do what you expect. Listing the packages generated by cups I
see:
cups-locale-da:
/usr/share/cups/templates/da/add-class.tmpl
/usr/share/cups/templates/da/add-printer.tmpl
/usr/share/cups/templates/da/admin.tmpl
Which is good. But I also see:
cups-locale-add-class.tmpl:
/usr/share/cups/templates/add-class.tmpl
cups-locale-add-printer.tmpl:
/usr/share/cups/templates/add-printer.tmpl
cups-locale-admin.tmpl:
/usr/share/cups/templates/admin.tmpl
That doesn’t look right!
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195543):
https://lists.openembedded.org/g/openembedded-core/message/195543
Mute This Topic: https://lists.openembedded.org/mt/104312268/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] valgrind: Skip 22 arm64 ptests
From: Randy MacLeod With the 3.22 upgrade 21 additional tests fail on qemuarm64. Skip them until the problems are resolved. Tracked by: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15399 Signed-off-by: Randy MacLeod --- .../valgrind/valgrind/remove-for-aarch64 | 27 --- 1 file changed, 24 insertions(+), 3 deletions(-) diff --git a/meta/recipes-devtools/valgrind/valgrind/remove-for-aarch64 b/meta/recipes-devtools/valgrind/valgrind/remove-for-aarch64 index 4477f39132..04f159d701 100644 --- a/meta/recipes-devtools/valgrind/valgrind/remove-for-aarch64 +++ b/meta/recipes-devtools/valgrind/valgrind/remove-for-aarch64 @@ -1,7 +1,9 @@ +drd/tests/annotate_sem drd/tests/boost_thread gdbserver_tests/hgtls +helgrind/tests/hg05_race2 +helgrind/tests/tc20_verifywrap memcheck/tests/dw4 -memcheck/tests/leak_cpp_interior memcheck/tests/varinfo1 memcheck/tests/varinfo2 memcheck/tests/varinfo3 @@ -9,5 +11,24 @@ memcheck/tests/varinfo4 memcheck/tests/varinfo5 memcheck/tests/varinfo6 memcheck/tests/varinforestrict -helgrind/tests/hg05_race2 -helgrind/tests/tc20_verifywrap +memcheck/tests/atomic_incs +memcheck/tests/bug464969_d_demangle +memcheck/tests/cxx17_aligned_new +memcheck/tests/demangle +memcheck/tests/linux/timerfd-syscall +memcheck/tests/long_namespace_xml +memcheck/tests/mismatches +memcheck/tests/mismatches_xml +memcheck/tests/new_aligned_delete_default +memcheck/tests/new_delete_mismatch_size +memcheck/tests/new_nothrow +memcheck/tests/realloc_size_zero_mismatch +memcheck/tests/sized_aligned_new_delete_args +memcheck/tests/sized_aligned_new_delete_misaligned1 +memcheck/tests/sized_aligned_new_delete_misaligned1_xml +memcheck/tests/sized_aligned_new_delete_misaligned2 +memcheck/tests/sized_aligned_new_delete_misaligned2_xml +memcheck/tests/sized_aligned_new_delete_misaligned3 +memcheck/tests/sized_aligned_new_delete_misaligned3_xml +memcheck/tests/sized_delete +none/tests/bigcode -- 2.43.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195542): https://lists.openembedded.org/g/openembedded-core/message/195542 Mute This Topic: https://lists.openembedded.org/mt/104375747/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 20/21] overlayfs: add missing closing parenthesis in selftest
From: "bar...@tkos.co.il"
Cc: Vyacheslav Yurkov
Signed-off-by: Baruch Siach
Signed-off-by: Richard Purdie
(cherry picked from commit aebd526cdfea738745e57183b1015fd327bd94df)
Signed-off-by: Steve Sakoman
---
meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb
b/meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb
index 50cba9514b..20f4213a62 100644
--- a/meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb
+++ b/meta-selftest/recipes-test/overlayfs-user/overlayfs-user.bb
@@ -18,5 +18,5 @@ do_install() {
FILES:${PN} += "\
${exec_prefix} \
-${sysconfdir \
+${sysconfdir} \
"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195540):
https://lists.openembedded.org/g/openembedded-core/message/195540
Mute This Topic: https://lists.openembedded.org/mt/104375667/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 21/21] multilib_global.bbclass: fix parsing error with no kernel module split
From: Chen Qi
The problem could be reproduced with the following settings:
MACHINE = "qemux86-64"
KERNEL_SPLIT_MODULES = "0"
require conf/multilib.conf
MULTILIBS ?= "multilib:lib32"
DEFAULTTUNE:virtclass-multilib-lib32 ?= "core2-32"
The error message is as below:
bb.data_smart.ExpansionError: Failure expanding variable
KERNEL_VERSION_PKG_NAME, expression was
${@legitimize_package_name(d.getVar('KERNEL_VERSION'))} which triggered
exception TypeError: expected string or bytes-like object
The variable dependency chain for the failure is: KERNEL_VERSION_PKG_NAME ->
RPROVIDES:kernel-modules
This is because multilib_virtclass_handler_global function in
multilib_global.bbclass deletes KERNEL_VERSION. So we need to handle
such situation. We'll also need to delete KERNEL_VERSION_PKG_NAME
to avoid this parsing error.
Signed-off-by: Chen Qi
Signed-off-by: Richard Purdie
(cherry picked from commit 43dd497bc161ac44faecfdff052db03679dbb4f8)
Signed-off-by: Steve Sakoman
---
meta/classes/multilib_global.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/multilib_global.bbclass
b/meta/classes/multilib_global.bbclass
index dcd89b2f63..6095d278dd 100644
--- a/meta/classes/multilib_global.bbclass
+++ b/meta/classes/multilib_global.bbclass
@@ -195,6 +195,7 @@ python multilib_virtclass_handler_global () {
# from a copy of the datastore
localdata = bb.data.createCopy(d)
localdata.delVar("KERNEL_VERSION")
+localdata.delVar("KERNEL_VERSION_PKG_NAME")
variants = (e.data.getVar("MULTILIB_VARIANTS") or "").split()
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195541):
https://lists.openembedded.org/g/openembedded-core/message/195541
Mute This Topic: https://lists.openembedded.org/mt/104375668/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 18/21] udev-extraconf: fix unmount directories containing octal-escaped chars
From: Jonathan GUILLOT USB devices are auto-mounted in a directory named like theirs labels. Special characters like whitespace are octal-escaped in /proc/mounts output. Using directly this output file as an argument for umount failed and the mount directory can't be removed as still busy. Using printf allows these special characters to be unescaped. Signed-off-by: Jonathan GUILLOT Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 37f17625d931a06888388682dc2b1f5a2d298125) Signed-off-by: Steve Sakoman --- meta/recipes-core/udev/udev-extraconf/mount.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/udev/udev-extraconf/mount.sh b/meta/recipes-core/udev/udev-extraconf/mount.sh index b7e86dbc0e..6cb0a9fea8 100644 --- a/meta/recipes-core/udev/udev-extraconf/mount.sh +++ b/meta/recipes-core/udev/udev-extraconf/mount.sh @@ -196,7 +196,7 @@ if [ "$ACTION" = "remove" ] || [ "$ACTION" = "change" ] && [ -x "$UMOUNT" ] && [ logger "mount.sh/remove" "cleaning up $DEVNAME, was mounted by the auto-mounter" for mnt in `cat /proc/mounts | grep "$DEVNAME" | cut -f 2 -d " " ` do -$UMOUNT $mnt +$UMOUNT "`printf $mnt`" done # Remove mount directory created by the auto-mounter # and clean up our tmp cache file -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195538): https://lists.openembedded.org/g/openembedded-core/message/195538 Mute This Topic: https://lists.openembedded.org/mt/104375665/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 19/21] pseudo: Update to pull in gcc14 fix and missing statvfs64 intercept
From: Richard Purdie
rpm 4.19 now builds with LFS64 support enabled by default,
so it calls statvfs64() to get the space available on the
filesystem it is installing packages into. This is not
getting caught by pseudo, so rpm is checking the host's
root filesystem, rather than the filesystem where the
build is happening.
Merge in that fix and a gcc14 fix.
Signed-off-by: Richard Purdie
(cherry picked from commit f6d021c860b2b99f46c604149317b326f493022d)
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/pseudo/files/glibc238.patch | 13 -
meta/recipes-devtools/pseudo/pseudo_git.bb| 2 +-
2 files changed, 1 insertion(+), 14 deletions(-)
diff --git a/meta/recipes-devtools/pseudo/files/glibc238.patch
b/meta/recipes-devtools/pseudo/files/glibc238.patch
index 76ca8c11eb..da4b8caee3 100644
--- a/meta/recipes-devtools/pseudo/files/glibc238.patch
+++ b/meta/recipes-devtools/pseudo/files/glibc238.patch
@@ -44,19 +44,6 @@ Index: git/pseudo_util.c
#include
#include
-Index: git/pseudolog.c
-===
git.orig/pseudolog.c
-+++ git/pseudolog.c
-@@ -8,7 +8,7 @@
- */
- /* We need _XOPEN_SOURCE for strptime(), but if we define that,
- * we then don't get S_IFSOCK... _GNU_SOURCE turns on everything. */
--#define _GNU_SOURCE
-+#define _DEFAULT_SOURCE
-
- #include
- #include
Index: git/pseudo_client.c
===
--- git.orig/pseudo_client.c
diff --git a/meta/recipes-devtools/pseudo/pseudo_git.bb
b/meta/recipes-devtools/pseudo/pseudo_git.bb
index 699cab11c6..025cf0fc9c 100644
--- a/meta/recipes-devtools/pseudo/pseudo_git.bb
+++ b/meta/recipes-devtools/pseudo/pseudo_git.bb
@@ -14,7 +14,7 @@ SRC_URI:append:class-nativesdk = " \
file://older-glibc-symbols.patch"
SRC_URI[prebuilt.sha256sum] =
"ed9f456856e9d86359f169f46a70ad7be4190d6040282b84c8d97b99072485aa"
-SRCREV = "a8453eea4d902bbb0e01c786f1cb4a178c3bbee3"
+SRCREV = "516a0a3c4b46f046895d27bfa019d685fe462dfa"
S = "${WORKDIR}/git"
PV = "1.9.0+git"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195539):
https://lists.openembedded.org/g/openembedded-core/message/195539
Mute This Topic: https://lists.openembedded.org/mt/104375666/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 17/21] externalsrc: fix task dependency for do_populate_lic
From: Julien Stephan
do_populate_lic dependencies are defined inside license.bbclass such as:
addtask populate_lic after do_patch before do_build
but externalsrc deletes the do_patch task, so the only dependency left for
do_populate_lic is "before do_build"
On a devtool context, when doing devtool modify, sources are extracted inside
build/workspace/sources/${BPN}/ and local files inside
build/workspace/sources/${BPN}/oe-local-files
When building the recipe after a devtool modify, do_unpack is called again to
unpack (possibly modified) local files from
build/workspace/sources/${BPN}/oe-local-files into ${WORKDIR}.
Since the only left dependency for do_populate_lic is do_build, the
do_populate_lic can be called BEFORE do_unpack. Most of the time this is not a
problem, because license files are generally located inside ${S}, which
corresponds to build/workspace/sources/${BPN} (and is already unpacked),
but this can lead to an issue if recipe sets LIC_FILES_CHKSUM to look for
files in ${WORKDIR} (example from init-ifupdown_1.0.bb):
LIC_FILES_CHKSUM =
"file://${WORKDIR}/copyright;md5=3dd6192d306f582dee7687da3d8748ab"
So devtool modify init-ifupdown && bitbake init-ifupdown gives the following
error:
WARNING: init-ifupdown-1.0-r0 do_populate_lic: Could not copy license file
<...>/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0/copyright to
<...>/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0/license-destdir/qemux86_64/init-ifupdown/copyright:
[Errno 2] No such file or directory:
'<...>/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0/copyright'
ERROR: init-ifupdown-1.0-r0 do_populate_lic: QA Issue: init-ifupdown:
LIC_FILES_CHKSUM points to an invalid file:
<...>/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0/copyright
[license-checksum]
ERROR: init-ifupdown-1.0-r0 do_populate_lic: Fatal QA errors were found,
failing task.
ERROR: Logfile of failure stored in:
<...>/build/tmp/work/qemux86_64-poky-linux/init-ifupdown/1.0/temp/log.do_populate_lic.838584
ERROR: Task
(<...>/poky/meta/recipes-core/init-ifupdown/init-ifupdown_1.0.bb:do_populate_lic)
failed with exit code '1'
Fix this by forcing the do_populate_lic task to run after do_unpack
Signed-off-by: Julien Stephan
Signed-off-by: Richard Purdie
(cherry picked from commit ea6a0cccdd274534809df62a0a196bf83489a1e5)
Signed-off-by: Steve Sakoman
---
meta/classes/externalsrc.bbclass | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
index a54f316aa0..70e27a8d35 100644
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -104,6 +104,7 @@ python () {
# If we deltask do_patch, there's no dependency to ensure do_unpack
gets run, so add one
# Note that we cannot use d.appendVarFlag() here because deps is
expected to be a list object, not a string
d.setVarFlag('do_configure', 'deps', (d.getVarFlag('do_configure',
'deps', False) or []) + ['do_unpack'])
+d.setVarFlag('do_populate_lic', 'deps',
(d.getVarFlag('do_populate_lic', 'deps', False) or []) + ['do_unpack'])
for task in d.getVar("SRCTREECOVEREDTASKS").split():
if local_srcuri and task in fetch_tasks:
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195537):
https://lists.openembedded.org/g/openembedded-core/message/195537
Mute This Topic: https://lists.openembedded.org/mt/104375656/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 16/21] reproducible: Fix race with externalsrc/devtool over lockfile
From: Richard Purdie We occasionally see races over the lockfile used by externalsrc/devtool when walking files for the source_date_epock calculation. Skip this file if present to avoid the issues and fix a real issue where SDE could be contaminated too. [YOCTO #14921] Signed-off-by: Richard Purdie (cherry picked from commit 4bc0eb4bd90e6e6e46581a8ed367212bdd910a26) Signed-off-by: Steve Sakoman --- meta/lib/oe/reproducible.py | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/lib/oe/reproducible.py b/meta/lib/oe/reproducible.py index 9ac75c02e3..448befce33 100644 --- a/meta/lib/oe/reproducible.py +++ b/meta/lib/oe/reproducible.py @@ -131,6 +131,9 @@ def get_source_date_epoch_from_youngest_file(d, sourcedir): files = [f for f in files if not f[0] == '.'] for fname in files: +if fname == "singletask.lock": + # Ignore externalsrc/devtool lockfile [YOCTO #14921] + continue filename = os.path.join(root, fname) try: mtime = int(os.lstat(filename).st_mtime) -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195536): https://lists.openembedded.org/g/openembedded-core/message/195536 Mute This Topic: https://lists.openembedded.org/mt/104375654/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 15/21] allarch: Fix allarch corner case
From: Richard Purdie
Most of the allarch code is conditional and only set if the recipe remains
marked
as allarch. The qemu wrapper handling is not handled in the same way however and
is unconditional.
Move the code to some slightly uglier inline python to allow it to be
conditional
and match the way the rest of the code works.
Signed-off-by: Richard Purdie
(cherry picked from commit dfd704f1741dccd9a85338c5d45dee4be079064d)
Signed-off-by: Steve Sakoman
---
meta/classes-recipe/allarch.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes-recipe/allarch.bbclass
b/meta/classes-recipe/allarch.bbclass
index 9138f40ed8..e429b92437 100644
--- a/meta/classes-recipe/allarch.bbclass
+++ b/meta/classes-recipe/allarch.bbclass
@@ -63,9 +63,9 @@ python () {
d.appendVarFlag("emit_pkgdata", "vardepsexclude", " MULTILIB_VARIANTS")
d.appendVarFlag("write_specfile", "vardepsexclude", " MULTILIBS")
d.appendVarFlag("do_package", "vardepsexclude", " package_do_shlibs")
+
+d.setVar("qemu_wrapper_cmdline", "def qemu_wrapper_cmdline(data,
rootfs_path, library_paths):\nreturn 'false'")
elif bb.data.inherits_class('packagegroup', d) and not
bb.data.inherits_class('nativesdk', d):
bb.error("Please ensure recipe %s sets PACKAGE_ARCH before inherit
packagegroup" % d.getVar("FILE"))
}
-def qemu_wrapper_cmdline(data, rootfs_path, library_paths):
-return 'false'
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195535):
https://lists.openembedded.org/g/openembedded-core/message/195535
Mute This Topic: https://lists.openembedded.org/mt/104375653/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 14/21] gstreamer: upgrade 1.22.8 -> 1.22.9
From: Wang Mingyu
Changelog:
https://gstreamer.freedesktop.org/releases/1.22
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 30b3835c367ff1de00d24cddf3bd920ea29f15c5)
Signed-off-by: Steve Sakoman
---
.../{gst-devtools_1.22.8.bb => gst-devtools_1.22.9.bb} | 2 +-
...treamer1.0-libav_1.22.8.bb => gstreamer1.0-libav_1.22.9.bb} | 2 +-
.../{gstreamer1.0-omx_1.22.8.bb => gstreamer1.0-omx_1.22.9.bb} | 2 +-
...lugins-bad_1.22.8.bb => gstreamer1.0-plugins-bad_1.22.9.bb} | 2 +-
...gins-base_1.22.8.bb => gstreamer1.0-plugins-base_1.22.9.bb} | 2 +-
...gins-good_1.22.8.bb => gstreamer1.0-plugins-good_1.22.9.bb} | 2 +-
...gins-ugly_1.22.8.bb => gstreamer1.0-plugins-ugly_1.22.9.bb} | 3 ++-
...eamer1.0-python_1.22.8.bb => gstreamer1.0-python_1.22.9.bb} | 2 +-
...tsp-server_1.22.8.bb => gstreamer1.0-rtsp-server_1.22.9.bb} | 2 +-
...treamer1.0-vaapi_1.22.8.bb => gstreamer1.0-vaapi_1.22.9.bb} | 2 +-
.../{gstreamer1.0_1.22.8.bb => gstreamer1.0_1.22.9.bb} | 2 +-
11 files changed, 12 insertions(+), 11 deletions(-)
rename meta/recipes-multimedia/gstreamer/{gst-devtools_1.22.8.bb =>
gst-devtools_1.22.9.bb} (95%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-libav_1.22.8.bb =>
gstreamer1.0-libav_1.22.9.bb} (91%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-omx_1.22.8.bb =>
gstreamer1.0-omx_1.22.9.bb} (95%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-bad_1.22.8.bb
=> gstreamer1.0-plugins-bad_1.22.9.bb} (98%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-base_1.22.8.bb
=> gstreamer1.0-plugins-base_1.22.9.bb} (98%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-good_1.22.8.bb
=> gstreamer1.0-plugins-good_1.22.9.bb} (97%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-ugly_1.22.8.bb
=> gstreamer1.0-plugins-ugly_1.22.9.bb} (94%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-python_1.22.8.bb =>
gstreamer1.0-python_1.22.9.bb} (91%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-rtsp-server_1.22.8.bb
=> gstreamer1.0-rtsp-server_1.22.9.bb} (90%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-vaapi_1.22.8.bb =>
gstreamer1.0-vaapi_1.22.9.bb} (95%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0_1.22.8.bb =>
gstreamer1.0_1.22.9.bb} (97%)
diff --git a/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.8.bb
b/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.9.bb
similarity index 95%
rename from meta/recipes-multimedia/gstreamer/gst-devtools_1.22.8.bb
rename to meta/recipes-multimedia/gstreamer/gst-devtools_1.22.9.bb
index 16a2dd85ce..f60234b528 100644
--- a/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.8.bb
+++ b/meta/recipes-multimedia/gstreamer/gst-devtools_1.22.9.bb
@@ -12,7 +12,7 @@ SRC_URI =
"https://gstreamer.freedesktop.org/src/gst-devtools/gst-devtools-${PV}
file://0001-connect-has-a-different-signature-on-musl.patch \
"
-SRC_URI[sha256sum] =
"cd634056fcb16d035b3df5953ec85ae8bd56c68f29920b720ef920ca71ea76a7"
+SRC_URI[sha256sum] =
"02e29400b44e9cc603aa6444dee5726b57edabef6455e6d0921ffed6f13840ee"
DEPENDS = "json-glib glib-2.0 glib-2.0-native gstreamer1.0
gstreamer1.0-plugins-base"
RRECOMMENDS:${PN} = "git"
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.8.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.9.bb
similarity index 91%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.8.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.9.bb
index 7c75173989..10536acc87 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.8.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-libav_1.22.9.bb
@@ -12,7 +12,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=69333daa044cb77e486cc36129f7a770 \
"
SRC_URI =
"https://gstreamer.freedesktop.org/src/gst-libav/gst-libav-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"be39349bc07ab4cdbd9a5fd6ea9848c601c7560ba5a0577ad5200b83bd424981"
+SRC_URI[sha256sum] =
"192f7d27d21c1e7c72c339a2647a9b0c247fedc62ea5029115f8c3e22ebb87d8"
S = "${WORKDIR}/gst-libav-${PV}"
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.8.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.9.bb
similarity index 95%
rename from meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.8.bb
rename to meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.9.bb
index 5aa9c9cc41..05d64748bb 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.8.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.22.9.bb
@@ -10,7 +10,7 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=4fbd65380cdd255951079008b364516c \
SRC_URI = "https://gstreamer.freedesktop.org/src/gst-omx/gst-omx-${PV}.tar.xz;
-SRC_URI[sha256sum] =
"94df10e7713618f0c8a4223f6e047f2d8f0ccecba1d585618e791f13037762df"
+SRC_URI[sha256sum] =
[OE-core][nanbield 13/21] cpio: upgrade 2.14 -> 2.15
From: Wang Mingyu
Changelog:
==
* Fix operation of --no-absolute-filenames --make-directories
* Restore access and modification times of symlinks in copy-in
and copy-pass modes.
0001-configure-Include-needed-header-for-major-minor-macr.patch
revmoed since it's included in 2.15
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit c4fb7512a5b1c13234e3733cba1c4bf246c77861)
Signed-off-by: Steve Sakoman
---
.../cpio/{cpio_2.14.bb => cpio_2.15.bb} | 3 +-
...e-needed-header-for-major-minor-macr.patch | 48 ---
2 files changed, 1 insertion(+), 50 deletions(-)
rename meta/recipes-extended/cpio/{cpio_2.14.bb => cpio_2.15.bb} (94%)
delete mode 100644
meta/recipes-extended/cpio/files/0001-configure-Include-needed-header-for-major-minor-macr.patch
diff --git a/meta/recipes-extended/cpio/cpio_2.14.bb
b/meta/recipes-extended/cpio/cpio_2.15.bb
similarity index 94%
rename from meta/recipes-extended/cpio/cpio_2.14.bb
rename to meta/recipes-extended/cpio/cpio_2.15.bb
index 560038d2a6..55e9add5cd 100644
--- a/meta/recipes-extended/cpio/cpio_2.14.bb
+++ b/meta/recipes-extended/cpio/cpio_2.15.bb
@@ -7,12 +7,11 @@ LICENSE = "GPL-3.0-only"
LIC_FILES_CHKSUM = "file://COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949"
SRC_URI = "${GNU_MIRROR}/cpio/cpio-${PV}.tar.gz \
-
file://0001-configure-Include-needed-header-for-major-minor-macr.patch \
file://run-ptest \
file://test.sh \
"
-SRC_URI[sha256sum] =
"145a340fd9d55f0b84779a44a12d5f79d77c99663967f8cfa168d7905ca52454"
+SRC_URI[sha256sum] =
"efa50ef983137eefc0a02fdb51509d624b5e3295c980aa127ceee4183455499e"
inherit autotools gettext texinfo ptest
diff --git
a/meta/recipes-extended/cpio/files/0001-configure-Include-needed-header-for-major-minor-macr.patch
b/meta/recipes-extended/cpio/files/0001-configure-Include-needed-header-for-major-minor-macr.patch
deleted file mode 100644
index 95ece0bbf3..00
---
a/meta/recipes-extended/cpio/files/0001-configure-Include-needed-header-for-major-minor-macr.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-From 8179be21e664cedb2e9d238cc2f6d04965e97275 Mon Sep 17 00:00:00 2001
-From: Sergey Poznyakoff
-Date: Thu, 11 May 2023 10:18:44 +0300
-Subject: [PATCH] configure: Include needed header for major/minor macros
-
-This helps in avoiding the warning about implicit function declaration
-which is elevated as error with newer compilers e.g. clang 16
-
-Signed-off-by: Khem Raj
-
-Upstream-Status: Backport
-Signed-off-by: Ross Burton
- configure.ac | 18 --
- 1 file changed, 16 insertions(+), 2 deletions(-)
-
-diff --git a/configure.ac b/configure.ac
-index de479e7..c601029 100644
a/configure.ac
-+++ b/configure.ac
-@@ -43,8 +43,22 @@ AC_TYPE_UID_T
- AC_CHECK_TYPE(gid_t, int)
-
- AC_HEADER_DIRENT
--AX_COMPILE_CHECK_RETTYPE([major], [0])
--AX_COMPILE_CHECK_RETTYPE([minor], [0])
-+AX_COMPILE_CHECK_RETTYPE([major], [0], [
-+#include
-+#ifdef MAJOR_IN_MKDEV
-+# include
-+#endif
-+#ifdef MAJOR_IN_SYSMACROS
-+# include
-+#endif])
-+AX_COMPILE_CHECK_RETTYPE([minor], [0], [
-+#include
-+#ifdef MAJOR_IN_MKDEV
-+# include
-+#endif
-+#ifdef MAJOR_IN_SYSMACROS
-+# include
-+#endif])
-
- AC_CHECK_FUNCS([fchmod fchown])
- # This is needed for mingw build
---
-2.34.1
-
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195533):
https://lists.openembedded.org/g/openembedded-core/message/195533
Mute This Topic: https://lists.openembedded.org/mt/104375649/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 12/21] at-spi2-core: upgrade 2.50.0 -> 2.50.1
From: Wang Mingyu
Changelog:
atk-adaptor: Fix critical when no table cell array is returned.
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 9bed9f07aea6c425748c8908641ce8a99fd5162f)
Signed-off-by: Steve Sakoman
---
.../atk/{at-spi2-core_2.50.0.bb => at-spi2-core_2.50.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/atk/{at-spi2-core_2.50.0.bb =>
at-spi2-core_2.50.1.bb} (95%)
diff --git a/meta/recipes-support/atk/at-spi2-core_2.50.0.bb
b/meta/recipes-support/atk/at-spi2-core_2.50.1.bb
similarity index 95%
rename from meta/recipes-support/atk/at-spi2-core_2.50.0.bb
rename to meta/recipes-support/atk/at-spi2-core_2.50.1.bb
index 57958fb7f5..6996ebebcd 100644
--- a/meta/recipes-support/atk/at-spi2-core_2.50.0.bb
+++ b/meta/recipes-support/atk/at-spi2-core_2.50.1.bb
@@ -11,7 +11,7 @@ MAJ_VER = "${@oe.utils.trim_version("${PV}", 2)}"
SRC_URI = "${GNOME_MIRROR}/${BPN}/${MAJ_VER}/${BPN}-${PV}.tar.xz"
-SRC_URI[sha256sum] =
"e9f5a8c8235c9dd963b2171de9120301129c677dde933955e1df618b949c4adc"
+SRC_URI[sha256sum] =
"5727b5c0687ac57ba8040e79bd6731b714a36b8fcf32190f236b8fb3698789e7"
DEPENDS = " \
dbus \
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195532):
https://lists.openembedded.org/g/openembedded-core/message/195532
Mute This Topic: https://lists.openembedded.org/mt/104375647/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 11/21] xserver-xorg: 21.1.9 -> 21.1.11
From: Kai Kang
Update xserver-xorg from 21.1.9 to 21.1.11.
Release Notes of 21.1.11 [1]:
This release contains fixes for the issues reported in today's security
advisory: https://lists.x.org/archives/xorg/2024-January/061525.html
* CVE-2023-6816
* CVE-2024-0229
* CVE-2024-21885
* CVE-2024-21886
* CVE-2024-0408
* CVE-2024-0409
Additionally, it also contains a fix for XRandR to allow for multiple virtual
monitors on a physical display.
Release Notes of 21.1.10 [2]:
This release contains fixes for CVE-2023-6377 and CVE-2023-6478 as
reported in today's security advisory:
https://lists.x.org/archives/xorg-announce/2023-December/003435.html
[1]: https://lists.x.org/archives/xorg/2024-January/061526.html
[2]: https://lists.x.org/archives/xorg/2023-December/061518.html
Signed-off-by: Kai Kang
Signed-off-by: Richard Purdie
(cherry picked from commit fc9da07bd181ee6f7ae51a5b6db40af0b94cd046)
Signed-off-by: Steve Sakoman
---
.../{xserver-xorg_21.1.9.bb => xserver-xorg_21.1.11.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_21.1.9.bb =>
xserver-xorg_21.1.11.bb} (92%)
diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.9.bb
b/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.11.bb
similarity index 92%
rename from meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.9.bb
rename to meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.11.bb
index 43c06181e3..6506d775ca 100644
--- a/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.9.bb
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg_21.1.11.bb
@@ -3,7 +3,7 @@ require xserver-xorg.inc
SRC_URI +=
"file://0001-xf86pciBus.c-use-Intel-ddx-only-for-pre-gen4-hardwar.patch \
file://0001-Avoid-duplicate-definitions-of-IOPortBase.patch \
"
-SRC_URI[sha256sum] =
"ff697be2011b4c4966b7806929e51b7a08e9d33800d505305d26d9ccde4b533a"
+SRC_URI[sha256sum] =
"1d3dadbd57fb86b16a018e9f5f957aeeadf744f56c0553f55737628d06d326ef"
# These extensions are now integrated into the server, so declare the migration
# path for in-place upgrades.
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195531):
https://lists.openembedded.org/g/openembedded-core/message/195531
Mute This Topic: https://lists.openembedded.org/mt/104375645/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 10/21] linux-firmware: upgrade 20231030 -> 20231211
From: Alexander Sverdlin
Signed-off-by: Alexander Sverdlin
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 0caafdbbf4e7dc84b919afe14f7cb8c46a9e4ac2)
Signed-off-by: Steve Sakoman
---
...nux-firmware_20231030.bb => linux-firmware_20231211.bb} | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20231030.bb =>
linux-firmware_20231211.bb} (99%)
diff --git a/meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
similarity index 99%
rename from meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
rename to meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
index b1f5247975..0ed4d91f8a 100644
--- a/meta/recipes-kernel/linux-firmware/linux-firmware_20231030.bb
+++ b/meta/recipes-kernel/linux-firmware/linux-firmware_20231211.bb
@@ -151,7 +151,7 @@ LIC_FILES_CHKSUM =
"file://LICENCE.Abilis;md5=b5ee3f410780e56711ad48eadc22b8bc \
"
# WHENCE checksum is defined separately to ease overriding it if
# class-devupstream is selected.
-WHENCE_CHKSUM = "ceb5248746d24d165b603e71b288cf75"
+WHENCE_CHKSUM = "3113c4ea08e5171555f3bf49eceb5b07"
# These are not common licenses, set NO_GENERIC_LICENSE for them
# so that the license files will be copied from fetched source
@@ -237,7 +237,7 @@ SRC_URI:class-devupstream =
"git://git.kernel.org/pub/scm/linux/kernel/git/firmw
# Pin this to the 20220509 release, override this in local.conf
SRCREV:class-devupstream ?= "b19cbdca78ab2adfd210c91be15a22568e8b8cae"
-SRC_URI[sha256sum] =
"c98d200fc4a3120de1a594713ce34e135819dff23e883a4ed387863ba25679c7"
+SRC_URI[sha256sum] =
"96af7e4b5eabd37869cdb3dcbb7ab36911106d39b76e799fa1caab16a9dbe8bb"
inherit allarch
@@ -248,7 +248,8 @@ do_compile() {
}
do_install() {
-oe_runmake 'DESTDIR=${D}'
'FIRMWAREDIR=${nonarch_base_libdir}/firmware' install
+# install-nodedup avoids rdfind dependency
+oe_runmake 'DESTDIR=${D}'
'FIRMWAREDIR=${nonarch_base_libdir}/firmware' install-nodedup
cp GPL-2 LICEN[CS]E.* WHENCE ${D}${nonarch_base_libdir}/firmware/
}
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195530):
https://lists.openembedded.org/g/openembedded-core/message/195530
Mute This Topic: https://lists.openembedded.org/mt/104375643/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 07/21] cve_check: cleanup logging
From: Ross Burton
Primarily list the number of patches found, useful when debugging.
Also clean up some bad escaping that caused warnings and use
re.IGNORECASE instead of manually doing case-insenstive rang matches.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked from commit 10acc75b7f3387b968bacd51aade6a8dc11a463f)
Signed-off-by: Steve Sakoman
---
meta/lib/oe/cve_check.py | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/meta/lib/oe/cve_check.py b/meta/lib/oe/cve_check.py
index b5fc5364dc..ed5c714cb8 100644
--- a/meta/lib/oe/cve_check.py
+++ b/meta/lib/oe/cve_check.py
@@ -79,20 +79,19 @@ def get_patched_cves(d):
import re
import oe.patch
-pn = d.getVar("PN")
-cve_match = re.compile("CVE:( CVE\-\d{4}\-\d+)+")
+cve_match = re.compile(r"CVE:( CVE-\d{4}-\d+)+")
# Matches the last "CVE--ID" in the file name, also if written
# in lowercase. Possible to have multiple CVE IDs in a single
# file name, but only the last one will be detected from the file name.
# However, patch files contents addressing multiple CVE IDs are supported
# (cve_match regular expression)
-
-cve_file_name_match = re.compile(".*([Cc][Vv][Ee]\-\d{4}\-\d+)")
+cve_file_name_match = re.compile(r".*(CVE-\d{4}-\d+)", re.IGNORECASE)
patched_cves = set()
-bb.debug(2, "Looking for patches that solves CVEs for %s" % pn)
-for url in oe.patch.src_patches(d):
+patches = oe.patch.src_patches(d)
+bb.debug(2, "Scanning %d patches for CVEs" % len(patches))
+for url in patches:
patch_file = bb.fetch.decodeurl(url)[2]
# Check patch file name for CVE ID
@@ -100,7 +99,7 @@ def get_patched_cves(d):
if fname_match:
cve = fname_match.group(1).upper()
patched_cves.add(cve)
-bb.debug(2, "Found CVE %s from patch file name %s" % (cve,
patch_file))
+bb.debug(2, "Found %s from patch file name %s" % (cve, patch_file))
# Remote patches won't be present and compressed patches won't be
# unpacked, so say we're not scanning them
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195526):
https://lists.openembedded.org/g/openembedded-core/message/195526
Mute This Topic: https://lists.openembedded.org/mt/104375639/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 09/21] glibc: stable 2.38 branch updates
From: Benjamin Bara Pull in fixes for CVE-2023-6246, CVE-2023-6779 and CVE-2023-6780. Signed-off-by: Benjamin Bara Signed-off-by: Steve Sakoman --- meta/recipes-core/glibc/glibc-version.inc | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/glibc/glibc-version.inc b/meta/recipes-core/glibc/glibc-version.inc index eaa6d53181..212f960cb5 100644 --- a/meta/recipes-core/glibc/glibc-version.inc +++ b/meta/recipes-core/glibc/glibc-version.inc @@ -1,6 +1,6 @@ SRCBRANCH ?= "release/2.38/master" PV = "2.38+git" -SRCREV_glibc ?= "44f757a6364a546359809d48c76b3debd26e77d4" +SRCREV_glibc ?= "d37c2b20a4787463d192b32041c3406c2bd91de0" SRCREV_localedef ?= "e0eca29583b9e0f62645c4316ced93cf4e4e26e1" GLIBC_GIT_URI ?= "git://sourceware.org/git/glibc.git;protocol=https" @@ -13,3 +13,6 @@ CVE_STATUS[CVE-2023-4806] = "fixed-version: Fixed in stable branch updates" CVE_STATUS[CVE-2023-5156] = "fixed-version: Fixed in stable branch updates" CVE_STATUS[CVE-2023-4527] = "fixed-version: Fixed in stable branch updates" CVE_STATUS[CVE-2023-0687] = "fixed-version: Fixed in stable branch updates" +CVE_STATUS[CVE-2023-6246] = "fixed-version: Fixed in stable branch updates" +CVE_STATUS[CVE-2023-6779] = "fixed-version: Fixed in stable branch updates" +CVE_STATUS[CVE-2023-6780] = "fixed-version: Fixed in stable branch updates" -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195529): https://lists.openembedded.org/g/openembedded-core/message/195529 Mute This Topic: https://lists.openembedded.org/mt/104375642/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 08/21] gtk: Set CVE_PRODUCT
From: Robert Joslyn
The CPE vendor is "gnome" and the CPE product is "gtk" for both gtk+3
and gtk4 recipes. Set CVE_PRODUCT so we properly match the NVD database.
Signed-off-by: Robert Joslyn
Signed-off-by: Richard Purdie
(cherry picked from commit 253f5f745d66acefcc739f1c9ad2dd46be630e47)
Signed-off-by: Steve Sakoman
---
meta/recipes-gnome/gtk+/gtk+3_3.24.38.bb | 2 ++
meta/recipes-gnome/gtk+/gtk4_4.12.3.bb | 2 ++
2 files changed, 4 insertions(+)
diff --git a/meta/recipes-gnome/gtk+/gtk+3_3.24.38.bb
b/meta/recipes-gnome/gtk+/gtk+3_3.24.38.bb
index 37fa0a7290..c23c46a689 100644
--- a/meta/recipes-gnome/gtk+/gtk+3_3.24.38.bb
+++ b/meta/recipes-gnome/gtk+/gtk+3_3.24.38.bb
@@ -13,3 +13,5 @@ LIC_FILES_CHKSUM =
"file://COPYING;md5=5f30f0716dfdd0d91eb439ebec522ec2 \
file://gtk/gtk.h;endline=25;md5=1d8dc0fccdbfa26287a271dce88af737 \
file://gdk/gdk.h;endline=25;md5=c920ce39dc88c6f06d3e7c50e08086f2 \
file://tests/testgtk.c;endline=25;md5=cb732daee1d82af7a2bf953cf3cf26f1"
+
+CVE_PRODUCT = "gnome:gtk"
diff --git a/meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
b/meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
index 001b06934e..2c85e7e75f 100644
--- a/meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
+++ b/meta/recipes-gnome/gtk+/gtk4_4.12.3.bb
@@ -41,6 +41,8 @@ SRC_URI[sha256sum] =
"148ce262f6c86487455fb1d9793c3f58bc3e1da477a29617fadb0420f5
S = "${WORKDIR}/gtk-${PV}"
+CVE_PRODUCT = "gnome:gtk"
+
inherit meson gettext pkgconfig gi-docgen update-alternatives gsettings
features_check gobject-introspection
# TBD: nativesdk
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195528):
https://lists.openembedded.org/g/openembedded-core/message/195528
Mute This Topic: https://lists.openembedded.org/mt/104375641/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 05/21] gcc: Update status of CVE-2023-4039
From: Simone Weiß This is fixed via a patch added in gcc-13.2.inc already, but still reported e.g. for libgcc as it is not defining an own source but use the shared gcc-source. Signed-off-by: Simone Weiß Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 301d45eacfd4ae6bddfb13207e2af9e8b4662bc8) Signed-off-by: Steve Sakoman --- meta/recipes-devtools/gcc/gcc-13.2.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-devtools/gcc/gcc-13.2.inc b/meta/recipes-devtools/gcc/gcc-13.2.inc index 359db1e278..32fddd11c2 100644 --- a/meta/recipes-devtools/gcc/gcc-13.2.inc +++ b/meta/recipes-devtools/gcc/gcc-13.2.inc @@ -115,3 +115,4 @@ EXTRA_OECONF_PATHS = "\ " CVE_STATUS[CVE-2021-37322] = "cpe-incorrect: Is a binutils 2.26 issue, not gcc" +CVE_STATUS[CVE-2023-4039] = "fixed-version: Fixed via CVE-2023-4039.patch included here. Set the status explictly to deal with all recipes that share the gcc-source" -- 2.34.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195527): https://lists.openembedded.org/g/openembedded-core/message/195527 Mute This Topic: https://lists.openembedded.org/mt/104375640/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 06/21] cve_check: handle CVE_STATUS being set to the empty string
From: Ross Burton
Handle CVE_STATUS[...] being set to an empty string just as if it was
not set at all.
This is needed for evaluated CVE_STATUS values to work, i.e. when
setting not-applicable-config if a PACKAGECONFIG is disabled.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked from commit 2c9f20f746251505d9d09262600199ffa87731a2)
Signed-off-by: Steve Sakoman
---
meta/lib/oe/cve_check.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oe/cve_check.py b/meta/lib/oe/cve_check.py
index 3fa77bf9a7..b5fc5364dc 100644
--- a/meta/lib/oe/cve_check.py
+++ b/meta/lib/oe/cve_check.py
@@ -231,7 +231,7 @@ def decode_cve_status(d, cve):
Convert CVE_STATUS into status, detail and description.
"""
status = d.getVarFlag("CVE_STATUS", cve)
-if status is None:
+if not status:
return ("", "", "")
status_split = status.split(':', 1)
@@ -240,7 +240,7 @@ def decode_cve_status(d, cve):
status_mapping = d.getVarFlag("CVE_CHECK_STATUSMAP", detail)
if status_mapping is None:
-bb.warn('Invalid detail %s for CVE_STATUS[%s] = "%s", fallback to
Unpatched' % (detail, cve, status))
+bb.warn('Invalid detail "%s" for CVE_STATUS[%s] = "%s", fallback to
Unpatched' % (detail, cve, status))
status_mapping = "Unpatched"
return (status_mapping, detail, description)
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195525):
https://lists.openembedded.org/g/openembedded-core/message/195525
Mute This Topic: https://lists.openembedded.org/mt/104375637/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 04/21] libssh2: backport fix for CVE-2023-48795
From: Ross Burton
Backport the upstream fix for CVE-2023-48795.
Signed-off-by: Ross Burton
Signed-off-by: Richard Purdie
(cherry picked from commit 314fa19c5e07fa632ff0434a6adbb97de1319a02)
Signed-off-by: Steve Sakoman
---
.../libssh2/libssh2/CVE-2023-48795.patch | 466 ++
.../recipes-support/libssh2/libssh2_1.11.0.bb | 1 +
2 files changed, 467 insertions(+)
create mode 100644 meta/recipes-support/libssh2/libssh2/CVE-2023-48795.patch
diff --git a/meta/recipes-support/libssh2/libssh2/CVE-2023-48795.patch
b/meta/recipes-support/libssh2/libssh2/CVE-2023-48795.patch
new file mode 100644
index 00..ab0f419ac5
--- /dev/null
+++ b/meta/recipes-support/libssh2/libssh2/CVE-2023-48795.patch
@@ -0,0 +1,466 @@
+From d4634630432594b139b3af6b9f254b890c0f275d Mon Sep 17 00:00:00 2001
+From: Michael Buckley
+Date: Thu, 30 Nov 2023 15:08:02 -0800
+Subject: [PATCH] src: add 'strict KEX' to fix CVE-2023-48795 "Terrapin Attack"
+
+Refs:
+https://terrapin-attack.com/
+https://seclists.org/oss-sec/2023/q4/292
+https://osv.dev/list?ecosystem==CVE-2023-48795
+https://github.com/advisories/GHSA-45x7-px36-x8w8
+https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-48795
+
+Fixes #1290
+Closes #1291
+
+CVE: CVE-2023-48795
+Upstream-Status: Backport
+Signed-off-by: Ross Burton
+---
+ src/kex.c | 63 +++
+ src/libssh2_priv.h | 18 +++---
+ src/packet.c | 83 +++---
+ src/packet.h | 2 +-
+ src/session.c | 3 ++
+ src/transport.c| 12 ++-
+ 6 files changed, 149 insertions(+), 32 deletions(-)
+
+diff --git a/src/kex.c b/src/kex.c
+index d4034a0a..b4b748ca 100644
+--- a/src/kex.c
b/src/kex.c
+@@ -3037,6 +3037,13 @@ kex_method_extension_negotiation = {
+ 0,
+ };
+
++static const LIBSSH2_KEX_METHOD
++kex_method_strict_client_extension = {
++"kex-strict-c-...@openssh.com",
++NULL,
++0,
++};
++
+ static const LIBSSH2_KEX_METHOD *libssh2_kex_methods[] = {
+ #if LIBSSH2_ED25519
+ _method_ssh_curve25519_sha256,
+@@ -3055,6 +3062,7 @@ static const LIBSSH2_KEX_METHOD *libssh2_kex_methods[] =
{
+ _method_diffie_helman_group1_sha1,
+ _method_diffie_helman_group_exchange_sha1,
+ _method_extension_negotiation,
++_method_strict_client_extension,
+ NULL
+ };
+
+@@ -3307,13 +3315,13 @@ static int kexinit(LIBSSH2_SESSION * session)
+ return 0;
+ }
+
+-/* kex_agree_instr
++/* _libssh2_kex_agree_instr
+ * Kex specific variant of strstr()
+ * Needle must be preceded by BOL or ',', and followed by ',' or EOL
+ */
+-static unsigned char *
+-kex_agree_instr(unsigned char *haystack, size_t haystack_len,
+-const unsigned char *needle, size_t needle_len)
++unsigned char *
++_libssh2_kex_agree_instr(unsigned char *haystack, size_t haystack_len,
++ const unsigned char *needle, size_t needle_len)
+ {
+ unsigned char *s;
+ unsigned char *end_haystack;
+@@ -3398,7 +3406,7 @@ static int kex_agree_hostkey(LIBSSH2_SESSION * session,
+ while(s && *s) {
+ unsigned char *p = (unsigned char *) strchr((char *) s, ',');
+ size_t method_len = (p ? (size_t)(p - s) : strlen((char *) s));
+-if(kex_agree_instr(hostkey, hostkey_len, s, method_len)) {
++if(_libssh2_kex_agree_instr(hostkey, hostkey_len, s, method_len))
{
+ const LIBSSH2_HOSTKEY_METHOD *method =
+ (const LIBSSH2_HOSTKEY_METHOD *)
+ kex_get_method_by_name((char *) s, method_len,
+@@ -3432,9 +3440,9 @@ static int kex_agree_hostkey(LIBSSH2_SESSION * session,
+ }
+
+ while(hostkeyp && (*hostkeyp) && (*hostkeyp)->name) {
+-s = kex_agree_instr(hostkey, hostkey_len,
+-(unsigned char *) (*hostkeyp)->name,
+-strlen((*hostkeyp)->name));
++s = _libssh2_kex_agree_instr(hostkey, hostkey_len,
++ (unsigned char *) (*hostkeyp)->name,
++ strlen((*hostkeyp)->name));
+ if(s) {
+ /* So far so good, but does it suit our purposes? (Encrypting vs
+Signing) */
+@@ -3468,6 +3476,12 @@ static int kex_agree_kex_hostkey(LIBSSH2_SESSION *
session, unsigned char *kex,
+ {
+ const LIBSSH2_KEX_METHOD **kexp = libssh2_kex_methods;
+ unsigned char *s;
++const unsigned char *strict =
++(unsigned char *)"kex-strict-s-...@openssh.com";
++
++if(_libssh2_kex_agree_instr(kex, kex_len, strict, 28)) {
++session->kex_strict = 1;
++}
+
+ if(session->kex_prefs) {
+ s = (unsigned char *) session->kex_prefs;
+@@ -3475,7 +3489,7 @@ static int kex_agree_kex_hostkey(LIBSSH2_SESSION *
session, unsigned char *kex,
+ while(s && *s) {
+ unsigned char *q, *p = (unsigned char *) strchr((char *) s, ',');
+ size_t method_len = (p ? (size_t)(p - s)
[OE-core][nanbield 02/21] tiff: fix CVE-2023-52355 and CVE-2023-52356
From: Yogita Urade CVE-2023-52355: An out-of-memory flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFRasterScanlineSize64() API. This flaw allows a remote attacker to cause a denial of service via a crafted input with a size smaller than 379 KB. Issue fixed by providing a documentation update. CVE-2023-52356: A segment fault (SEGV) flaw was found in libtiff that could be triggered by passing a crafted tiff file to the TIFFReadRGBATileExt() API. This flaw allows a remote attacker to cause a heap-buffer overflow, leading to a denial of service. References: https://nvd.nist.gov/vuln/detail/CVE-2023-52355 https://security-tracker.debian.org/tracker/CVE-2023-52355 https://gitlab.com/libtiff/libtiff/-/issues/621 https://gitlab.com/libtiff/libtiff/-/merge_requests/553 https://nvd.nist.gov/vuln/detail/CVE-2023-52356 https://gitlab.com/libtiff/libtiff/-/issues/622 https://gitlab.com/libtiff/libtiff/-/merge_requests/546 Signed-off-by: Yogita Urade Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit 831d7a2fffb3dec94571289292f0940bc7ecd70a) Signed-off-by: Steve Sakoman --- .../libtiff/tiff/CVE-2023-52355-0001.patch| 238 ++ .../libtiff/tiff/CVE-2023-52355-0002.patch| 28 +++ .../libtiff/tiff/CVE-2023-52356.patch | 49 meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 3 + 4 files changed, 318 insertions(+) create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2023-52355-0001.patch create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2023-52355-0002.patch create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2023-52356.patch diff --git a/meta/recipes-multimedia/libtiff/tiff/CVE-2023-52355-0001.patch b/meta/recipes-multimedia/libtiff/tiff/CVE-2023-52355-0001.patch new file mode 100644 index 00..f5520fcafd --- /dev/null +++ b/meta/recipes-multimedia/libtiff/tiff/CVE-2023-52355-0001.patch @@ -0,0 +1,238 @@ +From 335947359ce2dd3862cd9f7c49f92eba065dfed4 Mon Sep 17 00:00:00 2001 +From: Su_Laus +Date: Thu, 1 Feb 2024 13:06:08 + +Subject: [PATCH] manpage: Update TIFF documentation about TIFFOpenOptions.rst + and TIFFOpenOptionsSetMaxSingleMemAlloc() usage and some other small fixes. + +CVE: CVE-2023-52355 +Upstream-Status: Backport [https://gitlab.com/libtiff/libtiff/-/commit/335947359ce2dd3862cd9f7c49f92eba065dfed4] + +Signed-off-by: Yogita Urade +--- + doc/functions/TIFFDeferStrileArrayWriting.rst | 5 +++ + doc/functions/TIFFError.rst | 3 ++ + doc/functions/TIFFOpen.rst| 13 +++--- + doc/functions/TIFFOpenOptions.rst | 44 ++- + doc/functions/TIFFStrileQuery.rst | 5 +++ + doc/libtiff.rst | 31 - + 6 files changed, 91 insertions(+), 10 deletions(-) + +diff --git a/doc/functions/TIFFDeferStrileArrayWriting.rst b/doc/functions/TIFFDeferStrileArrayWriting.rst +index 60ee746..705aebc 100644 +--- a/doc/functions/TIFFDeferStrileArrayWriting.rst b/doc/functions/TIFFDeferStrileArrayWriting.rst +@@ -61,6 +61,11 @@ Diagnostics + All error messages are directed to the :c:func:`TIFFErrorExtR` routine. + Likewise, warning messages are directed to the :c:func:`TIFFWarningExtR` routine. + ++Note ++ ++ ++This functionality was introduced with libtiff 4.1. ++ + See also + + +diff --git a/doc/functions/TIFFError.rst b/doc/functions/TIFFError.rst +index 99924ad..cf4b37c 100644 +--- a/doc/functions/TIFFError.rst b/doc/functions/TIFFError.rst +@@ -65,6 +65,9 @@ or :c:func:`TIFFClientOpenExt`. + Furthermore, a **custom defined data structure** *user_data* for the + error handler can be given along. + ++Please refer to :doc:`/functions/TIFFOpenOptions` for how to setup the ++application-specific handler introduced with libtiff 4.5. ++ + Note + + +diff --git a/doc/functions/TIFFOpen.rst b/doc/functions/TIFFOpen.rst +index db79d7b..adc474f 100644 +--- a/doc/functions/TIFFOpen.rst b/doc/functions/TIFFOpen.rst +@@ -94,8 +94,9 @@ TIFF structure without closing the file handle and afterwards the + file should be closed using its file descriptor *fd*. + + :c:func:`TIFFOpenExt` (added in libtiff 4.5) is like :c:func:`TIFFOpen`, +-but options, such as re-entrant error and warning handlers may be passed +-with the *opts* argument. The *opts* argument may be NULL. ++but options, such as re-entrant error and warning handlers and a limit in byte ++that libtiff internal memory allocation functions are allowed to request per call ++may be passed with the *opts* argument. The *opts* argument may be NULL. + Refer to :doc:`TIFFOpenOptions` for allocating and filling the *opts* argument + parameters. The allocated memory for :c:type:`TIFFOpenOptions` + can be released straight after successful execution of the related +@@ -105,9 +106,7 @@ can be released straight after successful execution of the related + but opens a TIFF file with a
[OE-core][nanbield 03/21] zlib: ignore CVE-2023-6992
From: Peter Marko
This CVE is for iCPE cloudflare:zlib.
Alternative to ignoring would be to limit CVE_PRODUCT, but
historic CVEs already have two - gnu:zlib and zlib:zlib.
So limiting it could miss future CVEs.
Signed-off-by: Peter Marko
Signed-off-by: Richard Purdie
(cherry picked from commit 9f953a1cd832f03f0b3666168addf45fd4fc8d14)
Signed-off-by: Steve Sakoman
---
meta/recipes-core/zlib/zlib_1.3.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/zlib/zlib_1.3.bb
b/meta/recipes-core/zlib/zlib_1.3.bb
index 1ed18172fa..ede75f90bd 100644
--- a/meta/recipes-core/zlib/zlib_1.3.bb
+++ b/meta/recipes-core/zlib/zlib_1.3.bb
@@ -47,3 +47,4 @@ do_install_ptest() {
BBCLASSEXTEND = "native nativesdk"
CVE_STATUS[CVE-2023-45853] = "not-applicable-config: we don't build minizip"
+CVE_STATUS[CVE-2023-6992] = "cpe-incorrect: this CVE is for cloudflare zlib"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195523):
https://lists.openembedded.org/g/openembedded-core/message/195523
Mute This Topic: https://lists.openembedded.org/mt/104375635/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][nanbield 00/21] Patch review
Please review this set of changes for nanbield and have comments back by
end of day Monday, February 19
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6568
The following changes since commit 0584d01f623e1f9b0fef4dfa95dd66de6cbfb7b3:
build-appliance-image: Update to nanbield head revision (2024-02-08 03:49:03
-1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/nanbield-nut
https://git.openembedded.org/openembedded-core-contrib/log/?h=stable/nanbield-nut
Alexander Sverdlin (1):
linux-firmware: upgrade 20231030 -> 20231211
Benjamin Bara (1):
glibc: stable 2.38 branch updates
Chen Qi (1):
multilib_global.bbclass: fix parsing error with no kernel module split
Jonathan GUILLOT (1):
udev-extraconf: fix unmount directories containing octal-escaped chars
Julien Stephan (1):
externalsrc: fix task dependency for do_populate_lic
Kai Kang (1):
xserver-xorg: 21.1.9 -> 21.1.11
Peter Marko (1):
zlib: ignore CVE-2023-6992
Richard Purdie (3):
allarch: Fix allarch corner case
reproducible: Fix race with externalsrc/devtool over lockfile
pseudo: Update to pull in gcc14 fix and missing statvfs64 intercept
Robert Joslyn (1):
gtk: Set CVE_PRODUCT
Ross Burton (3):
libssh2: backport fix for CVE-2023-48795
cve_check: handle CVE_STATUS being set to the empty string
cve_check: cleanup logging
Simone Weiß (1):
gcc: Update status of CVE-2023-4039
Wang Mingyu (3):
at-spi2-core: upgrade 2.50.0 -> 2.50.1
cpio: upgrade 2.14 -> 2.15
gstreamer: upgrade 1.22.8 -> 1.22.9
Yogita Urade (2):
tiff: fix CVE-2023-6228
tiff: fix CVE-2023-52355 and CVE-2023-52356
bar...@tkos.co.il (1):
overlayfs: add missing closing parenthesis in selftest
.../overlayfs-user/overlayfs-user.bb | 2 +-
meta/classes-recipe/allarch.bbclass | 4 +-
meta/classes/externalsrc.bbclass | 1 +
meta/classes/multilib_global.bbclass | 1 +
meta/lib/oe/cve_check.py | 17 +-
meta/lib/oe/reproducible.py | 3 +
meta/recipes-core/glibc/glibc-version.inc | 5 +-
.../recipes-core/udev/udev-extraconf/mount.sh | 2 +-
meta/recipes-core/zlib/zlib_1.3.bb| 1 +
meta/recipes-devtools/gcc/gcc-13.2.inc| 1 +
.../pseudo/files/glibc238.patch | 13 -
meta/recipes-devtools/pseudo/pseudo_git.bb| 2 +-
.../cpio/{cpio_2.14.bb => cpio_2.15.bb} | 3 +-
...e-needed-header-for-major-minor-macr.patch | 48 --
meta/recipes-gnome/gtk+/gtk+3_3.24.38.bb | 2 +
meta/recipes-gnome/gtk+/gtk4_4.12.3.bb| 2 +
...xorg_21.1.9.bb => xserver-xorg_21.1.11.bb} | 2 +-
...20231030.bb => linux-firmware_20231211.bb} | 7 +-
...tools_1.22.8.bb => gst-devtools_1.22.9.bb} | 2 +-
...1.22.8.bb => gstreamer1.0-libav_1.22.9.bb} | 2 +-
...x_1.22.8.bb => gstreamer1.0-omx_1.22.9.bb} | 2 +-
bb => gstreamer1.0-plugins-bad_1.22.9.bb} | 2 +-
...bb => gstreamer1.0-plugins-base_1.22.9.bb} | 2 +-
...bb => gstreamer1.0-plugins-good_1.22.9.bb} | 2 +-
...bb => gstreamer1.0-plugins-ugly_1.22.9.bb} | 3 +-
22.8.bb => gstreamer1.0-python_1.22.9.bb} | 2 +-
bb => gstreamer1.0-rtsp-server_1.22.9.bb} | 2 +-
...1.22.8.bb => gstreamer1.0-vaapi_1.22.9.bb} | 2 +-
...er1.0_1.22.8.bb => gstreamer1.0_1.22.9.bb} | 2 +-
.../libtiff/tiff/CVE-2023-52355-0001.patch| 238 +
.../libtiff/tiff/CVE-2023-52355-0002.patch| 28 ++
.../libtiff/tiff/CVE-2023-52356.patch | 49 ++
.../libtiff/tiff/CVE-2023-6228.patch | 31 ++
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 4 +
...-core_2.50.0.bb => at-spi2-core_2.50.1.bb} | 2 +-
.../libssh2/libssh2/CVE-2023-48795.patch | 466 ++
.../recipes-support/libssh2/libssh2_1.11.0.bb | 1 +
37 files changed, 864 insertions(+), 94 deletions(-)
rename meta/recipes-extended/cpio/{cpio_2.14.bb => cpio_2.15.bb} (94%)
delete mode 100644
meta/recipes-extended/cpio/files/0001-configure-Include-needed-header-for-major-minor-macr.patch
rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_21.1.9.bb =>
xserver-xorg_21.1.11.bb} (92%)
rename meta/recipes-kernel/linux-firmware/{linux-firmware_20231030.bb =>
linux-firmware_20231211.bb} (99%)
rename meta/recipes-multimedia/gstreamer/{gst-devtools_1.22.8.bb =>
gst-devtools_1.22.9.bb} (95%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-libav_1.22.8.bb =>
gstreamer1.0-libav_1.22.9.bb} (91%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-omx_1.22.8.bb =>
gstreamer1.0-omx_1.22.9.bb} (95%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-bad_1.22.8.bb
=> gstreamer1.0-plugins-bad_1.22.9.bb} (98%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-base_1.22.8.bb
=> gstreamer1.0-plugins-base_1.22.9.bb} (98%)
rename meta/recipes-multimedia/gstreamer/{gstreamer1.0-plugins-good_1.22.8.bb
=>
[OE-core][nanbield 01/21] tiff: fix CVE-2023-6228
From: Yogita Urade
CVE-2023-6228:
An issue was found in the tiffcp utility distributed by the
libtiff package where a crafted TIFF file on processing may
cause a heap-based buffer overflow leads to an application
crash.
References:
https://nvd.nist.gov/vuln/detail/CVE-2023-6228
https://gitlab.com/libtiff/libtiff/-/issues/606
Signed-off-by: Yogita Urade
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 55735e0d75820d59e569a630679f9ac403c7fdbe)
Signed-off-by: Steve Sakoman
---
.../libtiff/tiff/CVE-2023-6228.patch | 31 +++
meta/recipes-multimedia/libtiff/tiff_4.6.0.bb | 1 +
2 files changed, 32 insertions(+)
create mode 100644 meta/recipes-multimedia/libtiff/tiff/CVE-2023-6228.patch
diff --git a/meta/recipes-multimedia/libtiff/tiff/CVE-2023-6228.patch
b/meta/recipes-multimedia/libtiff/tiff/CVE-2023-6228.patch
new file mode 100644
index 00..2020508fdf
--- /dev/null
+++ b/meta/recipes-multimedia/libtiff/tiff/CVE-2023-6228.patch
@@ -0,0 +1,31 @@
+From 1e7d217a323eac701b134afc4ae39b6bdfdbc96a Mon Sep 17 00:00:00 2001
+From: Su_Laus
+Date: Wed, 17 Jan 2024 06:57:08 +
+Subject: [PATCH] codec of input image is available, independently from codec
+ check of output image and return with error if not.
+
+Fixes #606.
+
+CVE: CVE-2023-6228
+Upstream-Status: Backport
[https://gitlab.com/libtiff/libtiff/-/commit/1e7d217a323eac701b134afc4ae39b6bdfdbc96a]
+
+Signed-off-by: Yogita Urade
+---
+ tools/tiffcp.c | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/tools/tiffcp.c b/tools/tiffcp.c
+index aff0626..a4f7f6b 100644
+--- a/tools/tiffcp.c
b/tools/tiffcp.c
+@@ -846,6 +846,8 @@ static int tiffcp(TIFF *in, TIFF *out)
+ if (!TIFFIsCODECConfigured(compression))
+ return FALSE;
+ TIFFGetFieldDefaulted(in, TIFFTAG_COMPRESSION, _compression);
++if (!TIFFIsCODECConfigured(input_compression))
++ return FALSE;
+ TIFFGetFieldDefaulted(in, TIFFTAG_PHOTOMETRIC, _photometric);
+ if (input_compression == COMPRESSION_JPEG)
+ {
+--
+2.40.0
diff --git a/meta/recipes-multimedia/libtiff/tiff_4.6.0.bb
b/meta/recipes-multimedia/libtiff/tiff_4.6.0.bb
index 4c472f8ef6..eb8a096f19 100644
--- a/meta/recipes-multimedia/libtiff/tiff_4.6.0.bb
+++ b/meta/recipes-multimedia/libtiff/tiff_4.6.0.bb
@@ -12,6 +12,7 @@ SRC_URI =
"http://download.osgeo.org/libtiff/tiff-${PV}.tar.gz \
file://CVE-2023-6277-At-image-reading-compare-data-size-of-some-tags-data.patch
\
file://CVE-2023-6277-At-image-reading-compare-data-size-of-some-tags-data-2.patch
\
file://CVE-2023-6277-Apply-1-suggestion-s-to-1-file-s.patch \
+ file://CVE-2023-6228.patch \
"
SRC_URI[sha256sum] =
"88b3979e6d5c7e32b50d7ec72fb15af724f6ab2cbf7e10880c360a77e4b5d99a"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195521):
https://lists.openembedded.org/g/openembedded-core/message/195521
Mute This Topic: https://lists.openembedded.org/mt/104375633/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] create-spdx-2.2: Correct the default value of SPDX_NAMESPACE_PREFIX
On Tue, Feb 13, 2024 at 6:33 PM wrote:
>
> From: BELOUARGA Mohamed
>
> This patch corrects the default value of SPDX_NAMESPACE_PREFIX as the previous
> value is not expected to exist.
> It adds also the documentation of the variable SPDX_NAMESPACE_PREFIX.
> This patch can also be linked to the bug:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=15398
>
> Signed-off-by: BELOUARGA Mohamed
> ---
> documentation/ref-manual/variables.rst | 5 +
> meta/classes/create-spdx-2.2.bbclass | 2 +-
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/documentation/ref-manual/variables.rst
> b/documentation/ref-manual/variables.rst
> index 6f7d6ff01e..907575ba82 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -7913,6 +7913,11 @@ system and gives an overview of their function and
> contents.
>image), compared to just using the :ref:`ref-classes-create-spdx` class
>with no option.
>
> + :term:`SPDX_NAMESPACE_PREFIX`
> + This option could be used in order to change the prefix of
> ``spdxDocument``
> + and the prefix of ``documentNamespace``. It is set by default to:
> + ``https://spdx.org/spdxdocs`` .
> +
> :term:`SPDX_PRETTY`
>This option makes the SPDX output more human-readable, using
>identation and newlines, instead of the default output in a
> diff --git a/meta/classes/create-spdx-2.2.bbclass
> b/meta/classes/create-spdx-2.2.bbclass
> index 486efadba9..dedaffc043 100644
> --- a/meta/classes/create-spdx-2.2.bbclass
> +++ b/meta/classes/create-spdx-2.2.bbclass
> @@ -28,7 +28,7 @@ SPDX_ARCHIVE_SOURCES ??= "0"
> SPDX_ARCHIVE_PACKAGED ??= "0"
>
> SPDX_UUID_NAMESPACE ??= "sbom.openembedded.org"
> -SPDX_NAMESPACE_PREFIX ??= "http://spdx.org/spdxdoc;
> +SPDX_NAMESPACE_PREFIX ??= "https://spdx.org/spdxdocs;
Per the spec [1], the recommended form is
"http://[CreatorWebsite]/[pathToSpdx]/[DocumentName]-[UUID];. If a
creator doesn't own a website for publishing, "spdx.org/spdxdocs" can
used for CreatorWebsite. Therefore, while the "spdxdocs" is required,
https:// isn't. I'd prefer to keep it that way in case anyone wants to
use that prefix to decide if the document can be downloaded or not.
[1]:
https://spdx.github.io/spdx-spec/v2.2.2/document-creation-information/#652-intent
> SPDX_PRETTY ??= "0"
>
> SPDX_LICENSES ??= "${COREBASE}/meta/files/spdx-licenses.json"
> --
> 2.25.1
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195519):
https://lists.openembedded.org/g/openembedded-core/message/195519
Mute This Topic: https://lists.openembedded.org/mt/104345729/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [oe-core][master][PATCH] busybox: Use ISO 13400 timings in zcip
On Thu, 2024-02-15 at 16:06 +0100, Jan-Simon Möller wrote: > Am Freitag, 9. Februar 2024, 15:17:13 CET schrieb Richard Purdie via > lists.openembedded.org: > > On Wed, 2024-02-07 at 13:21 +0530, akash hadke wrote: > > > > I think a few of us are torn on this. If it were accepted upstream, I'd > > probably take it. Whilst it is still pending, I'm less sure. > > > > Having "embedded" targeted features in OE-Core is desirable in many > > ways. In this case the target usage is probably quite niche. > > > > I'd like to see if anyone else would find this useful? Does AGL want to > > use this for example? > > We (AGL) would wait for upstream busybox feedback to > http://lists.busybox.net/pipermail/busybox/2024-February/090611.html > > And go from there. Thanks, in that case I think OE-Core will follow on that as I don't think this is going to be enabled to tested in most of our userbase. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195518): https://lists.openembedded.org/g/openembedded-core/message/195518 Mute This Topic: https://lists.openembedded.org/mt/104214735/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 1/5] meta/conf/templates/default/conf-description.txt: add a template description
On Wed, 2024-01-31 at 13:39 +0100, Alexander Kanavin wrote: > Existing conf-notes.txt is not adequate in situations where the user > needs to select a config template from several, or get an overview of them and > is interested only in a brief explanation of what the template is for, > but not extended multi-paragraph instructions for how to use it. > > Such descriptions can be provided via conf-description.txt and > this patch adds such a description for the oe-core default template. > > Updates to the tools and a tool for selecting templates which > will make specific use of the description will follow. > > Signed-off-by: Alexander Kanavin > --- > meta/conf/templates/default/conf-description.txt | 1 + > 1 file changed, 1 insertion(+) > create mode 100644 meta/conf/templates/default/conf-description.txt > > diff --git a/meta/conf/templates/default/conf-description.txt > b/meta/conf/templates/default/conf-description.txt > new file mode 100644 > index 000..e49172fa0ce > --- /dev/null > +++ b/meta/conf/templates/default/conf-description.txt > @@ -0,0 +1 @@ > +This is the default build configuration for the openembedded-core layer. I know this feedback is long delayed so my apologies for that. I think I'm ok with the idea of this but I believe the naming isn't quite right. "notes" does suggest something longer, so that is fine. My worry is that in the metadata we have the SUMMARY and DESCRIPTION variables. The former is the short one, the latter is the longer. If developers see: conf-notes.txt conf-description.txt then they don't know which is the "short" one. If you however you have: conf-notes.txt conf-summary.txt then I think that is much clearer? I think I'm therefore ok with the idea but I'd like to suggest using "summary" instead of "description"... Cheers Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195517): https://lists.openembedded.org/g/openembedded-core/message/195517 Mute This Topic: https://lists.openembedded.org/mt/104073816/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] gcc: Oe-selftest failures analysis - x86-64
On Thu, 2024-02-15 at 10:29 +, Sadineni, Harish via lists.openembedded.org wrote: > > Hi all, > > We are analysing the test failures reported by the autobilder > athttps://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/qemux86-64-tc/testresults.json > The autobuilder result summary as follows: > === > qemux86-64 PTest Result Summary > === > --- > Recipe | Passed | Failed | Skipped | > --- > gcc | 124420 | 37 | 23809 | > gcc-g++ | 196231 | 39 | 17314 | > gcc-libatomic | 27 | 1 | 27 | > gcc-libgomp | 3407 | 16 | 1981 | > gcc-libitm | 24 | 1 | 24 > | > gcc-libstdc++-v3 | 9705 | 32 | 5464 | > > We started with 'gcc.dg' module failures(13 failues, listed below) reported > inhttps://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/testresult-report.txt. > ptestresult.gcc.gcc.dg/analyzer/data-model-4.c (test for excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O0 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O1 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O2 (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O2 -flto > -fno-use-linker-plugin -flto-partition=none (test for excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -O3 -g (test for > excess errors) > ptestresult.gcc.gcc.dg/analyzer/torture/conftest-1.c -Os (test for > excess errors) > ptestresult.gcc.gcc.dg/pr56837.c scan-tree-dump-times optimized "memset > ..c, 68, 16384.;" 1 > ptestresult.gcc.gcc.dg/vect/vect-ifcvt-18.c scan-tree-dump vect > "vectorized 3 loops" > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-10.c (test for excess errors) > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-16f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-17f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > ptestresult.gcc.gcc.dg/vect/vect-simd-clone-18f.c scan-tree-dump-times > vect "[\\n\\r] [^\\n]* = foo\\.simdclone" 2 > > Out of these, except 'gcc.gcc.dg/vect/vect-simd-clone-10.c' all others are > fialed in gcc upstream. > > We've analyzed the failed case 'vect-simd-clone-10.c' and find the root > cause, it is the bug is in gcc test suite. > GCC Bug raised -https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113899 > > We are working on other module failures (g++,libatomic...), keep you posted > here. This looks like a good start, thanks for working on this! Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195516): https://lists.openembedded.org/g/openembedded-core/message/195516 Mute This Topic: https://lists.openembedded.org/mt/104370247/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] openssh: Add a work around for ICE on mips
Unfortunately the new openssh version has an ICE on mips. This looks similar to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
Given how long these have been open, workaround the issue by disabling the
compiler
hardening options on mips.
It is likely better to do this than have the open CVEs for everyone
as we can't upgrade.
Signed-off-by: Richard Purdie
---
meta/recipes-connectivity/openssh/openssh_9.6p1.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
index 6366cefdf96..fcd96f707f8 100644
--- a/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
+++ b/meta/recipes-connectivity/openssh/openssh_9.6p1.bb
@@ -81,6 +81,9 @@ EXTRA_OECONF = "'LOGIN_PROGRAM=${base_bindir}/login' \
# musl doesn't implement wtmp/utmp and logwtmp
EXTRA_OECONF:append:libc-musl = " --disable-wtmp --disable-lastlog"
+# Work around ICE on mips starting in 9.6p1
+EXTRA_OECONF:append:mips = " --without-hardening"
+
# Since we do not depend on libbsd, we do not want configure to use it
# just because it finds libutil.h. But, specifying --disable-libutil
# causes compile errors, so...
--
2.40.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#195515):
https://lists.openembedded.org/g/openembedded-core/message/195515
Mute This Topic: https://lists.openembedded.org/mt/104372858/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] qemuarm64: maximise the emulated CPU capabilities
On 15 Feb 2024, at 06:40, Mikko Rapeli wrote: > optee xtests are triggering a reproducible RCU stall in our testing with > --cpu max,pauth-impdef=on and qemu-system 8.2.1 from Debian unstable. > This does not happen with --cpu cortex-a57 on this qemu-machine version. > [sigh] Can you file a bug against optee about this? Cheers, Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195514): https://lists.openembedded.org/g/openembedded-core/message/195514 Mute This Topic: https://lists.openembedded.org/mt/104335663/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [kirkstone][PATCH v2] shadow: backport patch to fix CVE-2023-29383
Hi, Any idea furhter, what could be the issue? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195513): https://lists.openembedded.org/g/openembedded-core/message/195513 Mute This Topic: https://lists.openembedded.org/mt/98361235/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe-core][PATCH] mesa: update 23.3.5 -> 24.0.0
On Thu, 15 Feb 2024 at 12:44, Richard Purdie wrote: > > Mesa 24.0.0 is - as clearly indicated on the web site - a development > > snapshot. 24.0.1 is now out, can you upgrade to that? > > FWIW I did take this knowing that it was a development snapshot and > they we'd be very likely to be able to update to the .1 before release! > > The timing of this and the llvm release is always tricky. Mesa upstream does describe .0 releases this as 'development' in release notes but that description isn't hand written and comes from a template somewhere. .0 are always preceded by multiple release candidates[1], and .1 always follows quickly. I don't think there's a real problem taking .0. [1] https://gitlab.freedesktop.org/mesa/mesa/-/tags Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195512): https://lists.openembedded.org/g/openembedded-core/message/195512 Mute This Topic: https://lists.openembedded.org/mt/104358245/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe-core][PATCH] mesa: update 23.3.5 -> 24.0.0
On Thu, 2024-02-15 at 11:25 +, Ross Burton wrote: > Mesa 24.0.0 is - as clearly indicated on the web site - a development > snapshot. 24.0.1 is now out, can you upgrade to that? FWIW I did take this knowing that it was a development snapshot and they we'd be very likely to be able to update to the .1 before release! The timing of this and the llvm release is always tricky. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195511): https://lists.openembedded.org/g/openembedded-core/message/195511 Mute This Topic: https://lists.openembedded.org/mt/104358245/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [oe-core][PATCH] mesa: update 23.3.5 -> 24.0.0
Mesa 24.0.0 is - as clearly indicated on the web site - a development snapshot.
24.0.1 is now out, can you upgrade to that?
Ross
> On 14 Feb 2024, at 18:14, Markus Volk via lists.openembedded.org
> wrote:
>
> - refresh 0001-meson.build-check-for-all-linux-host_os-combinations.patch
> - rework VIDEO_CODECS. mesa now provides options for 'all' and 'all_free'
> Adjust accordingly.
> Free codecs are built by default:
>Codecs : av1dec av1enc vp9dec
> If LICENSE_FLAGS_ACCEPTED contains 'commercial' all supported codecs are
> built:
>Codecs : vc1dec h264dec h264enc h265dec h265enc
> av1dec av1enc vp9dec
>
> Signed-off-by: Markus Volk
> ---
> ...ld-check-for-all-linux-host_os-combinations.patch | 12 ++--
> .../mesa/{mesa-gl_23.3.5.bb => mesa-gl_24.0.0.bb}| 0
> meta/recipes-graphics/mesa/mesa.inc | 8
> .../mesa/{mesa_23.3.5.bb => mesa_24.0.0.bb} | 0
> 4 files changed, 10 insertions(+), 10 deletions(-)
> rename meta/recipes-graphics/mesa/{mesa-gl_23.3.5.bb => mesa-gl_24.0.0.bb}
> (100%)
> rename meta/recipes-graphics/mesa/{mesa_23.3.5.bb => mesa_24.0.0.bb} (100%)
>
> diff --git
> a/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
>
> b/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
> index fadd6ee201..b0be8d0feb 100644
> ---
> a/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
> +++
> b/meta/recipes-graphics/mesa/files/0001-meson.build-check-for-all-linux-host_os-combinations.patch
> @@ -23,21 +23,21 @@ diff --git a/meson.build b/meson.build
> index 35cc5f1..9a49c0d 100644
> --- a/meson.build
> +++ b/meson.build
> -@@ -121,7 +121,7 @@ with_any_opengl = with_opengl or with_gles1 or with_gles2
> +@@ -128,7 +128,7 @@
> # Only build shared_glapi if at least one OpenGL API is enabled
> with_shared_glapi = with_shared_glapi and with_any_opengl
>
> --system_has_kms_drm = ['openbsd', 'netbsd', 'freebsd', 'gnu/kfreebsd',
> 'dragonfly', 'linux', 'sunos', 'android'].contains(host_machine.system())
> -+system_has_kms_drm = ['openbsd', 'netbsd', 'freebsd', 'gnu/kfreebsd',
> 'dragonfly', 'linux', 'sunos', 'android'].contains(host_machine.system()) or
> host_machine.system().startswith('linux')
> +-system_has_kms_drm = ['openbsd', 'netbsd', 'freebsd', 'gnu/kfreebsd',
> 'dragonfly', 'linux', 'sunos', 'android',
> 'managarm'].contains(host_machine.system())
> ++system_has_kms_drm = ['openbsd', 'netbsd', 'freebsd', 'gnu/kfreebsd',
> 'dragonfly', 'linux', 'sunos', 'android',
> 'managarm'].contains(host_machine.system()) or
> host_machine.system().startswith('linux')
>
> gallium_drivers = get_option('gallium-drivers')
> if gallium_drivers.contains('auto')
> -@@ -956,7 +956,7 @@ if cc.has_function('fmemopen')
> +@@ -998,7 +998,7 @@
> endif
>
> # TODO: this is very incomplete
> --if ['linux', 'cygwin', 'gnu', 'freebsd', 'gnu/kfreebsd', 'haiku',
> 'android'].contains(host_machine.system())
> -+if ['linux', 'cygwin', 'gnu', 'freebsd', 'gnu/kfreebsd',
> 'haiku'].contains(host_machine.system()) or
> host_machine.system().startswith('linux')
> +-if ['linux', 'cygwin', 'gnu', 'freebsd', 'gnu/kfreebsd', 'haiku',
> 'android', 'managarm'].contains(host_machine.system())
> ++if ['linux', 'cygwin', 'gnu', 'freebsd', 'gnu/kfreebsd', 'haiku',
> 'android', 'managarm'].contains(host_machine.system()) or
> host_machine.system().startswith('linux')
>pre_args += '-D_GNU_SOURCE'
> elif host_machine.system() == 'sunos'
>pre_args += '-D__EXTENSIONS__'
> diff --git a/meta/recipes-graphics/mesa/mesa-gl_23.3.5.bb
> b/meta/recipes-graphics/mesa/mesa-gl_24.0.0.bb
> similarity index 100%
> rename from meta/recipes-graphics/mesa/mesa-gl_23.3.5.bb
> rename to meta/recipes-graphics/mesa/mesa-gl_24.0.0.bb
> diff --git a/meta/recipes-graphics/mesa/mesa.inc
> b/meta/recipes-graphics/mesa/mesa.inc
> index 3a7b91f637..fabc52f0e7 100644
> --- a/meta/recipes-graphics/mesa/mesa.inc
> +++ b/meta/recipes-graphics/mesa/mesa.inc
> @@ -20,7 +20,7 @@ SRC_URI =
> "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
>file://0001-gallium-Fix-build-with-llvm-17.patch \
> "
>
> -SRC_URI[sha256sum] =
> "69ccb1278641ff5bad71ca0f866188aeb1a92aadc4dbb9d35f50aebec5b8b50f"
> +SRC_URI[sha256sum] =
> "dc7e8c077bc5884df95478263b34bdebb7e88e600689cb56fb07be2b8c304c36"
>
> UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P\d+(\.\d+)+)"
>
> @@ -81,12 +81,12 @@ def strip_comma(s):
>
> PACKAGECONFIG = " \
> gallium \
> + video-codecs \
> ${@bb.utils.filter('DISTRO_FEATURES', 'x11 vulkan wayland', d)} \
> ${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'opengl egl gles gbm
> virgl', '', d)} \
> ${@bb.utils.contains('DISTRO_FEATURES', 'x11 opengl', 'dri3', '', d)} \
> ${@bb.utils.contains('DISTRO_FEATURES', 'x11 vulkan', 'dri3', '', d)} \
>
Re: [OE-core] [PATCH 1/2] create-spdx-2.2: Correct the default value of SPDX_NAMESPACE_PREFIX
> -Original Message- > From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Alexandre Belloni via > lists.openembedded.org > Sent: den 15 februari 2024 10:26 > To: belouargamoha...@gmail.com > Cc: openembedded-core@lists.openembedded.org; > f.lahoud...@technologyandstrategy.com; BELOUARGA Mohamed > > Subject: Re: [OE-core] [PATCH 1/2] create-spdx-2.2: Correct the default > value of SPDX_NAMESPACE_PREFIX > > Hello, > > This is 1/2, but I couldn't find a 2/2. The 2/2 patch was sent to d...@lists.yoctoproject.org. //Peter -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195509): https://lists.openembedded.org/g/openembedded-core/message/195509 Mute This Topic: https://lists.openembedded.org/mt/104362313/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 2/3] rust/cargo: Build fixes to rust for rv32 target
On Tue, 6 Feb 2024 at 19:49, Khem Raj wrote: > diff --git a/meta/recipes-devtools/rust/files/rv32-rustix-libc-backend.patch > b/meta/recipes-devtools/rust/files/rv32-rustix-libc-backend.patch > new file mode 100644 > index 000..462a651428f > --- /dev/null > +++ b/meta/recipes-devtools/rust/files/rv32-rustix-libc-backend.patch > @@ -0,0 +1,32 @@ > +Use FICLONE from linux_raw_sys module > + > +Upstream-Status: Pending > +Signed-off-by: Khem Raj > +--- a/vendor/rustix/src/backend/libc/c.rs > b/vendor/rustix/src/backend/libc/c.rs Please do send this upstream, weekly pending stats increased because of it, and I'm obsessed with not letting that happen :) Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#195508): https://lists.openembedded.org/g/openembedded-core/message/195508 Mute This Topic: https://lists.openembedded.org/mt/104203999/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
