[OE-core] [AUH] liburcu: upgrading to 0.14.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *liburcu* to *0.14.0* has Succeeded. Next steps: - apply the patch: git am 0001-liburcu-upgrade-0.13.2-0.14.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 packages/core2-32-poky-linux/liburcu: PV changed from "0.13.2" to "0.14.0" packages/core2-32-poky-linux/liburcu: SRC_URI changed from "http://lttng.org/files/urcu/userspace-rcu-0.13.2.tar.bz2; to "http://lttng.org/files/urcu/userspace-rcu-0.14.0.tar.bz2; packages/core2-32-poky-linux/liburcu: PKGV changed from 0.13.2 [default] to 0.14.0 [default] packages/core2-32-poky-linux/liburcu/liburcu-dbg: PKGSIZE changed from 756152 to 790928 (+5%) packages/core2-32-poky-linux/liburcu/liburcu-dbg: PV changed from "0.13.2" to "0.14.0" packages/core2-32-poky-linux/liburcu/liburcu-dbg: FILELIST: removed "/usr/lib/.debug/liburcu-bp.so.8.0.0 /usr/lib/.debug/liburcu-mb.so.8.0.0 /usr/lib/.debug/liburcu-cds.so.8.0.0 /usr/lib/.debug/liburcu-qsbr.so.8.0.0 /usr/lib/.debug/liburcu-common.so.8.0.0 /usr/lib/.debug/liburcu-memb.so.8.0.0 /usr/lib/.debug/liburcu.so.8.0.0 /usr/lib/.debug/liburcu-signal.so.8.0.0", added "/usr/lib/.debug/liburcu-mb.so.8.1.0 /usr/lib/.debug/liburcu-bp.so.8.1.0 /usr/lib/.debug/liburcu-common.so.8.1.0 /usr/lib/.debug/liburcu-qsbr.so.8.1.0 /usr/lib/.debug/liburcu-cds.so.8.1.0 /usr/lib/.debug/liburcu-memb.so.8.1.0 /usr/lib/.debug/liburcu-signal.so.8.1.0 /usr/lib/.debug/liburcu.so.8.1.0" packages/core2-32-poky-linux/liburcu/liburcu-dbg: PKGV changed from 0.13.2 [default] to 0.14.0 [default] packages/core2-32-poky-linux/liburcu/liburcu-dev: PKGSIZE changed from 369524 to 382475 (+4%) packages/core2-32-poky-linux/liburcu/liburcu-dev: PV changed from "0.13.2" to "0.14.0" packages/core2-32-poky-linux/liburcu/liburcu-dev: FILELIST: added "/usr/include/urcu/urcu-poll.h /usr/include/urcu/assert.h" packages/core2-32-poky-linux/liburcu/liburcu-dev: PKGV changed from 0.13.2 [default] to 0.14.0 [default] packages/core2-32-poky-linux/liburcu/liburcu-doc: PKGSIZE changed from 165312 to 166595 (+1%) packages/core2-32-poky-linux/liburcu/liburcu-doc: PV changed from "0.13.2" to "0.14.0" packages/core2-32-poky-linux/liburcu/liburcu-doc: PKGV changed from 0.13.2 [default] to 0.14.0 [default] packages/core2-32-poky-linux/liburcu/liburcu-locale: PV changed from "0.13.2" to "0.14.0" packages/core2-32-poky-linux/liburcu/liburcu-locale: PKGV changed from 0.13.2 [default] to 0.14.0 [default] packages/core2-32-poky-linux/liburcu/liburcu-src: PKGSIZE changed from 431068 to 451744 (+5%) packages/core2-32-poky-linux/liburcu/liburcu-src: PV changed from "0.13.2" to "0.14.0" packages/core2-32-poky-linux/liburcu/liburcu-src: FILELIST: directory renamed /usr/src/debug/liburcu/0.13.2-r0/include/urcu/uatomic -> /usr/src/debug/liburcu/0.14.0-r0/include/urcu/uatomic, directory renamed /usr/src/debug/liburcu/0.13.2-r0/include/urcu/static -> /usr/src/debug/liburcu/0.14.0-r0/include/urcu/static, removed "/usr/src/debug/liburcu/0.13.2-r0/include/urcu/lfstack.h /usr/src/debug/liburcu/0.13.2-r0/include/urcu/wfstack.h /usr/src/debug/liburcu/0.13.2-r0/include/urcu/rculfstack.h /usr/src/debug/liburcu/0.13.2-r0/include/urcu/rculfqueue.h /usr/src/debug/liburcu/0.13.2-r0/src/rculfhash-mm-mmap.c /usr/src/debug/liburcu/0.13.2-r0/include/urcu/wfcqueue.h /usr/src/debug/liburcu/0.13.2-r0/src/urcu-pointer.c /usr/src/debug/liburcu/0.13.2-r0/src/lfstack.c /usr/src/debug/liburcu/0.13.2-r0/src/wfstack.c /usr/src/debug/liburcu/0.13.2-r0/include/urcu/urcu-bp.h /usr/src/debug/liburcu/0.13.2-r0/include/urcu/wfqueue.h /usr/src/debug/liburcu/0.13.2-r0/src/urcu-wait.h /usr/src/debug/libur cu/0.13.2-r0/include/urcu/ref.h /usr/src/debug/liburcu/0.13.2-r0/src/compat_futex.c /usr/src/debug/liburcu/0.13.2-r0/src/rculfhash-mm-chunk.c /usr/src/debug/liburcu/0.13.2-r0/src/rculfhash-mm-order.c /usr/src/debug/liburcu/0.13.2-r0/include/urcu/call-rcu.h /usr/src/debug/liburcu/0.13.2-r0/src/rculfstack.c /usr/src/debug/liburcu/0.13.2-r0/src/rculfqueue.c /usr/src/debug/liburcu/0.13.2-r0/src/compat-getcpu.h /usr/src/debug/liburcu/0.13.2-r0/include/urcu/urcu-signal.h /usr/src/debug/liburcu/0.13.2-r0/src/urcu-defer-impl.h /usr/src/debug/liburcu/0.13.2-r0/src/wfcqueue.c
[OE-core] [AUH] dtc: upgrading to 1.7.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dtc* to *1.7.0* has Succeeded. Next steps: - apply the patch: git am 0001-dtc-upgrade-1.6.1-1.7.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 packages/core2-32-poky-linux/dtc/dtc-dbg: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-dbg: PKGSIZE changed from 616168 to 623368 (+1%) packages/core2-32-poky-linux/dtc/dtc-dbg: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-dev: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-dev: PKGSIZE changed from 80359 to 81390 (+1%) packages/core2-32-poky-linux/dtc/dtc-dev: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-doc: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-doc: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-locale: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-locale: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-misc: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-misc: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-src: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-src: PKGSIZE changed from 567703 to 573932 (+1%) packages/core2-32-poky-linux/dtc/dtc-src: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-staticdev: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc-staticdev: PKGSIZE changed from 0 to 144876 (+100%) packages/core2-32-poky-linux/dtc/dtc-staticdev: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc/dtc-staticdev: FILELIST: added "/usr/lib/libfdt.a" packages/core2-32-poky-linux/dtc/dtc: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc/dtc: PKGSIZE changed from 275787 to 275883 (+0%) packages/core2-32-poky-linux/dtc/dtc: PKGV changed from 1.6.1 [default] to 1.7.0 [default] packages/core2-32-poky-linux/dtc: SRC_URI changed from "git://git.kernel.org/pub/scm/utils/dtc/dtc.git;branch=master file://0001-fdtdump-fix-Werror-int-to-pointer-cast.patch" to "git://git.kernel.org/pub/scm/utils/dtc/dtc.git;branch=main" packages/core2-32-poky-linux/dtc: PV changed from "1.6.1" to "1.7.0" packages/core2-32-poky-linux/dtc: PKGV changed from 1.6.1 [default] to 1.7.0 [default] Changes to packages/core2-32-poky-linux/dtc (sysroot): /usr/lib/libfdt.a was added 0001-dtc-upgrade-1.6.1-1.7.0.patch Description: Binary data packages/core2-32-poky-linux/dtc/dtc-staticdev: FILELIST: added "/usr/lib/libfdt.a" packages/core2-32-poky-linux/dtc/dtc-staticdev: PKGSIZE changed from 0 to 144876 (+100%) Changes to packages/core2-32-poky-linux/dtc (sysroot): /usr/lib/libfdt.a was added -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177261): https://lists.openembedded.org/g/openembedded-core/message/177261 Mute This Topic: https://lists.openembedded.org/mt/96996951/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] wireless-regdb: upgrading to 2023.02.13 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *wireless-regdb* to *2023.02.13* has Succeeded. Next steps: - apply the patch: git am 0001-wireless-regdb-upgrade-2022.08.12-2023.02.13.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 packages/all-poky-linux/wireless-regdb: SRC_URI changed from "https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2022.08.12.tar.xz; to "https://www.kernel.org/pub/software/network/wireless-regdb/wireless-regdb-2023.02.13.tar.xz; packages/all-poky-linux/wireless-regdb: PKGV changed from 2022.08.12 [default] to 2023.02.13 [default] packages/all-poky-linux/wireless-regdb: PV changed from "2022.08.12" to "2023.02.13" packages/all-poky-linux/wireless-regdb/wireless-regdb-src: PKGV changed from 2022.08.12 [default] to 2023.02.13 [default] packages/all-poky-linux/wireless-regdb/wireless-regdb-src: PV changed from "2022.08.12" to "2023.02.13" packages/all-poky-linux/wireless-regdb/wireless-regdb-static: PKGSIZE changed from 5774 to 5858 (+1%) packages/all-poky-linux/wireless-regdb/wireless-regdb-static: PKGV changed from 2022.08.12 [default] to 2023.02.13 [default] packages/all-poky-linux/wireless-regdb/wireless-regdb-static: PV changed from "2022.08.12" to "2023.02.13" packages/all-poky-linux/wireless-regdb/wireless-regdb: PKGSIZE changed from 6787 to 6871 (+1%) packages/all-poky-linux/wireless-regdb/wireless-regdb: PKGV changed from 2022.08.12 [default] to 2023.02.13 [default] packages/all-poky-linux/wireless-regdb/wireless-regdb: PV changed from "2022.08.12" to "2023.02.13" 0001-wireless-regdb-upgrade-2022.08.12-2023.02.13.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177263): https://lists.openembedded.org/g/openembedded-core/message/177263 Mute This Topic: https://lists.openembedded.org/mt/96996953/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] libva-initial: upgrading to 2.17.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libva-initial* to *2.17.0* has Failed (devtool error). Detailed error information: The following devtool command failed: finish -f libva-initial /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva NOTE: Starting bitbake server... WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 896 .bb files complete (895 cached, 1 parsed). 1696 targets, 37 skipped, 0 masked, 0 errors. Summary: There was 1 WARNING message. INFO: No patches or local source files needed updating INFO: Cleaning sysroot for recipe libva-initial... ERROR: Command 'bitbake -c clean libva-initial' failed, output: WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1696 entries from dependency cache. Parsing recipes... Summary: There was 1 WARNING message. Summary: There were 2 ERROR messages, returning a non-zero exit code. If you wish, you may specify -n/--no-clean to skip running this command when resetting Next steps: - apply the patch: git am 0001-libva-initial-upgrade-2.16.0-2.17.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 0001-libva-initial-upgrade-2.16.0-2.17.0.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177259): https://lists.openembedded.org/g/openembedded-core/message/177259 Mute This Topic: https://lists.openembedded.org/mt/96996949/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] dos2unix: upgrading to 7.4.4 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dos2unix* to *7.4.4* has Succeeded. Next steps: - apply the patch: git am 0001-dos2unix-upgrade-7.4.3-7.4.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 packages/core2-32-poky-linux/dos2unix/dos2unix-dbg: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix-dbg: PKGSIZE changed from 177868 to 178108 (+0%) packages/core2-32-poky-linux/dos2unix/dos2unix-dbg: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix/dos2unix-dev: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix-dev: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix/dos2unix-doc: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix-doc: PKGSIZE changed from 194047 to 195604 (+1%) packages/core2-32-poky-linux/dos2unix/dos2unix-doc: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix/dos2unix-locale: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix-locale: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix/dos2unix-src: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix-src: PKGSIZE changed from 192350 to 192420 (+0%) packages/core2-32-poky-linux/dos2unix/dos2unix-src: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix/dos2unix-staticdev: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix-staticdev: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix/dos2unix: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix/dos2unix: PKGV changed from 7.4.3 [default] to 7.4.4 [default] packages/core2-32-poky-linux/dos2unix: PV changed from "7.4.3" to "7.4.4" packages/core2-32-poky-linux/dos2unix: PKGV changed from 7.4.3 [default] to 7.4.4 [default] 0001-dos2unix-upgrade-7.4.3-7.4.4.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177268): https://lists.openembedded.org/g/openembedded-core/message/177268 Mute This Topic: https://lists.openembedded.org/mt/96996958/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] zstd: upgrading to 1.5.4 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *zstd* to *1.5.4* has Succeeded. Next steps: - apply the patch: git am 0001-zstd-upgrade-1.5.2-1.5.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 0001-zstd-upgrade-1.5.2-1.5.4.patch Description: Binary data packages/core2-32-poky-linux/zstd: PKGV changed from 1.5.2 [default] to 1.5.4 [default] packages/core2-32-poky-linux/zstd: PV changed from "1.5.2" to "1.5.4" packages/core2-32-poky-linux/zstd/libzstd: FILELIST: removed "/usr/lib/libzstd.so.1.5.2", added "/usr/lib/libzstd.so.1.5.4" packages/core2-32-poky-linux/zstd/libzstd: PKGSIZE changed from 759308 to 763232 (+1%) packages/core2-32-poky-linux/zstd/libzstd: PKGV changed from 1.5.2 [default] to 1.5.4 [default] packages/core2-32-poky-linux/zstd/libzstd: PV changed from "1.5.2" to "1.5.4" Changes to packages/core2-32-poky-linux/zstd (sysroot): /usr/lib/libzstd.so.1 changed symlink target from libzstd.so.1.5.2 to libzstd.so.1.5.4 /usr/lib/libzstd.so changed symlink target from libzstd.so.1.5.2 to libzstd.so.1.5.4 /usr/lib/libzstd.so.1.5.2 moved to /usr/lib/libzstd.so.1.5.4 packages/core2-32-poky-linux/zstd/zstd-dbg: FILELIST: removed "/usr/lib/.debug/libzstd.so.1.5.2", added "/usr/lib/.debug/libzstd.so.1.5.4" packages/core2-32-poky-linux/zstd/zstd-dbg: PKGSIZE changed from 14520484 to 15041084 (+4%) packages/core2-32-poky-linux/zstd/zstd-dbg: PKGV changed from 1.5.2 [default] to 1.5.4 [default] packages/core2-32-poky-linux/zstd/zstd-dbg: PV changed from "1.5.2" to "1.5.4" packages/core2-32-poky-linux/zstd/zstd-dev: PKGSIZE changed from 178541 to 200334 (+12%) packages/core2-32-poky-linux/zstd/zstd-dev: PKGV changed from 1.5.2 [default] to 1.5.4 [default] packages/core2-32-poky-linux/zstd/zstd-dev: PV changed from "1.5.2" to "1.5.4" packages/core2-32-poky-linux/zstd/zstd-doc: PKGSIZE changed from 31045 to 34326 (+11%) packages/core2-32-poky-linux/zstd/zstd-doc: PKGV changed from 1.5.2 [default] to 1.5.4 [default] packages/core2-32-poky-linux/zstd/zstd-doc: PV changed from "1.5.2" to "1.5.4" packages/core2-32-poky-linux/zstd/zstd-locale: PKGV changed from 1.5.2 [default] to 1.5.4 [default] packages/core2-32-poky-linux/zstd/zstd-locale: PV changed from "1.5.2" to "1.5.4" packages/core2-32-poky-linux/zstd/zstd-src: FILELIST: directory renamed /usr/src/debug/zstd/1.5.2-r0/lib/decompress -> /usr/src/debug/zstd/1.5.4-r0/lib/decompress, directory renamed /usr/src/debug/zstd/1.5.2-r0/contrib/pzstd -> /usr/src/debug/zstd/1.5.4-r0/contrib/pzstd, directory renamed /usr/src/debug/zstd/1.5.2-r0/lib/compress -> /usr/src/debug/zstd/1.5.4-r0/lib/compress, directory renamed /usr/src/debug/zstd/1.5.2-r0/lib/legacy -> /usr/src/debug/zstd/1.5.4-r0/lib/legacy, directory renamed /usr/src/debug/zstd/1.5.2-r0/contrib/pzstd/utils -> /usr/src/debug/zstd/1.5.4-r0/contrib/pzstd/utils, directory renamed /usr/src/debug/zstd/1.5.2-r0/lib/dictBuilder -> /usr/src/debug/zstd/1.5.4-r0/lib/dictBuilder, directory renamed /usr/src/debug/zstd/1.5.2-r0/lib -> /usr/src/debug/zstd/1.5.4-r0/lib, removed "/usr/src/debug/zstd/1.5.2-r0/programs/timefn.h /usr/src/debug/zstd/1.5.2-r0/lib/common/zstd_trace.h /usr/src/debug/zstd/1.5.2-r0/lib/common/bitstream.h /usr/src/debug/zstd/1.5.2-r0/programs /timefn.c /usr/src/debug/zstd/1.5.2-r0/programs/dibio.h /usr/src/debug/zstd/1.5.2-r0/programs/datagen.h /usr/src/debug/zstd/1.5.2-r0/programs/benchfn.c /usr/src/debug/zstd/1.5.2-r0/lib/common/error_private.c /usr/src/debug/zstd/1.5.2-r0/programs/datagen.c /usr/src/debug/zstd/1.5.2-r0/programs/dibio.c /usr/src/debug/zstd/1.5.2-r0/lib/common/error_private.h /usr/src/debug/zstd/1.5.2-r0/programs/benchfn.h /usr/src/debug/zstd/1.5.2-r0/programs/fileio.c /usr/src/debug/zstd/1.5.2-r0/programs/fileio.h /usr/src/debug/zstd/1.5.2-r0/lib/common/pool.h /usr/src/debug/zstd/1.5.2-r0/lib/common/threading.c /usr/src/debug/zstd/1.5.2-r0/lib/common/pool.c /usr/src/debug/zstd/1.5.2-r0/lib/common/huf.h /usr/src/debug/zstd/1.5.2-r0/lib/common/threading.h /usr/src/debug/zstd/1.5.2-r0/lib/common/cpu.h /usr/src/debug/zstd/1.5.2-r0/programs/zstdcli.c /usr/src/debug/zstd/1.5.2-r0/lib/common/zstd_internal.h /usr/src/debug/zstd/1.5.2-r0/programs/util.c
[OE-core] [AUH] gnutls: upgrading to 3.8.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gnutls* to *3.8.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe gnutls failed. NOTE: Starting bitbake server... NOTE: Reconnecting to bitbake server... NOTE: Previous bitbake instance shutting down?, waiting to retry... (00:22:39.975815) NOTE: Directory listing: ['bitbake-cookerdaemon.log', 'sstate-cache', 'buildhistory', 'upgrade-helper', 'workspace', 'conf', 'tmp', 'cache', 'downloads'] NOTE: Retrying server connection (#1)... (00:22:40.106908) WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Summary: There was 1 WARNING message. WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Removing 1 recipes from the x86_64 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-bbd150a101ed0eae501303aadc7d5efc3621dd31" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:bbd150a101ed0eae501303aadc7d5efc3621dd31" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 21 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 896 .bb files complete (894 cached, 2 parsed). 1694 targets, 37 skipped, 0 masked, 0 errors. Summary: There was 1 WARNING message. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-bbd150a101ed0eae501303aadc7d5efc3621dd31" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:bbd150a101ed0eae501303aadc7d5efc3621dd31" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 17 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 83 tasks of which 81 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: 2% || ETA: 0:00:08 Adding changed files: 5% |# | ETA: 0:00:06 Adding changed files: 8% |## | ETA: 0:00:05 Adding changed files: 10% |### | ETA: 0:00:04 Adding changed files: 13% || ETA: 0:00:03 Adding changed files: 16% |# | ETA: 0:00:03 Adding changed files: 18% |## | ETA: 0:00:03 Adding changed files: 21% |### | ETA: 0:00:02 Adding changed files: 24% || ETA: 0:00:02 Adding changed files: 26% |# | ETA: 0:00:02 Adding changed files: 29% |## | ETA: 0:00:02 Adding changed files: 32% |### | ETA: 0:00:02 Adding changed files: 34% || ETA: 0:00:02 Adding changed files: 37% |# | ETA: 0:00:02 Adding changed files: 40% |## | ETA: 0:00:01 Adding changed files: 42% |### | ETA:
[OE-core] [AUH] linux-firmware: upgrading to 20230210 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *linux-firmware* to *20230210* has Succeeded. Next steps: - apply the patch: git am 0001-linux-firmware-upgrade-20230117-20230210.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 packages/all-poky-linux/linux-firmware: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware: SRC_URI changed from "https://cdn.kernel.org/pub/linux/kernel/firmware/linux-firmware-20230117.tar.xz; to "https://cdn.kernel.org/pub/linux/kernel/firmware/linux-firmware-20230210.tar.xz; packages/all-poky-linux/linux-firmware/linux-firmware-adsp-sst-license: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-adsp-sst-license: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-adsp-sst: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-adsp-sst: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-amdgpu-license: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-amdgpu-license: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-amdgpu: PKGSIZE changed from 72109590 to 74723142 (+4%) packages/all-poky-linux/linux-firmware/linux-firmware-amdgpu: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-amdgpu: FILELIST: added "/lib/firmware/amdgpu/gc_11_0_1_imu.bin /lib/firmware/amdgpu/vcn_4_0_2.bin /lib/firmware/amdgpu/gc_11_0_1_pfp.bin /lib/firmware/amdgpu/gc_11_0_1_mes.bin /lib/firmware/amdgpu/psp_13_0_4_ta.bin /lib/firmware/amdgpu/sdma_6_0_1.bin /lib/firmware/amdgpu/psp_13_0_4_toc.bin /lib/firmware/amdgpu/gc_11_0_1_mec.bin /lib/firmware/amdgpu/gc_11_0_1_rlc.bin /lib/firmware/amdgpu/dcn_3_1_4_dmcub.bin /lib/firmware/amdgpu/gc_11_0_1_mes1.bin /lib/firmware/amdgpu/gc_11_0_1_me.bin" packages/all-poky-linux/linux-firmware/linux-firmware-amdgpu: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-amlogic-vdec-license: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-amlogic-vdec-license: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-amlogic-vdec: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-amlogic-vdec: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ar3k-license: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-ar3k-license: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ar3k: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-ar3k: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ar9170: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-ar9170: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ath10k-license: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-ath10k-license: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ath10k: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-ath10k: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ath11k: PKGV changed from 20230117 [default] to 20230210 [default] packages/all-poky-linux/linux-firmware/linux-firmware-ath11k: PV changed from "20230117" to "20230210" packages/all-poky-linux/linux-firmware/linux-firmware-ath3k: PKGV changed from 20230117 [default] to 20230210 [default]
[OE-core] [AUH] freetype: upgrading to 2.13.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *freetype* to *2.13.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade freetype -V 2.13.0 NOTE: Starting bitbake server... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... (20:31:49.443175) WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Summary: There was 1 WARNING message. WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-4124f15670621ea75bbb97133f7bdaacbc0611fc" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:4124f15670621ea75bbb97133f7bdaacbc0611fc" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 21 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 896 .bb files complete (894 cached, 2 parsed). 1694 targets, 37 skipped, 0 masked, 0 errors. Summary: There was 1 WARNING message. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-4124f15670621ea75bbb97133f7bdaacbc0611fc" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:4124f15670621ea75bbb97133f7bdaacbc0611fc" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 17 (100% match, 100% complete) NOTE: Executing Tasks WARNING: Failed to fetch URL https://download.savannah.nongnu.org/releases/freetype/freetype-2.13.0.tar.xz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 82 tasks of which 81 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching https://download.savannah.nongnu.org/releases/freetype/freetype-2.13.0.tar.xz... 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 PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-suk07v0q/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-suk07v0q/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-suk07v0q/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-suk07v0q/work/recipe-sysroot-native/usr/bin:/home/ pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-suk07v0q/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-suk07v0q/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools"; export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O
[OE-core] [AUH] libwpe: upgrading to 1.14.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libwpe* to *1.14.1* has Succeeded. Next steps: - apply the patch: git am 0001-libwpe-upgrade-1.14.0-1.14.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 packages/core2-32-poky-linux/libwpe: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe: SRC_URI changed from "https://wpewebkit.org/releases/libwpe-1.14.0.tar.xz; to "https://wpewebkit.org/releases/libwpe-1.14.1.tar.xz; packages/core2-32-poky-linux/libwpe: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe-dbg: PKGSIZE changed from 235224 to 235268 (+0%) packages/core2-32-poky-linux/libwpe/libwpe-dbg: FILELIST: removed "/usr/lib/.debug/libwpe-1.0.so.1.8.0", added "/usr/lib/.debug/libwpe-1.0.so.1.8.1" packages/core2-32-poky-linux/libwpe/libwpe-dbg: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe-dbg: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe-dev: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe-dev: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe-doc: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe-doc: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe-locale: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe-locale: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe-src: PKGSIZE changed from 252302 to 252324 (+0%) packages/core2-32-poky-linux/libwpe/libwpe-src: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe-src: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe-staticdev: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe-staticdev: PV changed from "1.14.0" to "1.14.1" packages/core2-32-poky-linux/libwpe/libwpe: FILELIST: removed "/usr/lib/libwpe-1.0.so.1.8.0", added "/usr/lib/libwpe-1.0.so.1.8.1" packages/core2-32-poky-linux/libwpe/libwpe: PKGV changed from 1.14.0 [default] to 1.14.1 [default] packages/core2-32-poky-linux/libwpe/libwpe: PV changed from "1.14.0" to "1.14.1" Changes to packages/core2-32-poky-linux/libwpe (sysroot): /usr/lib/libwpe-1.0.so.1 changed symlink target from libwpe-1.0.so.1.8.0 to libwpe-1.0.so.1.8.1 /usr/lib/libwpe-1.0.so.1.8.0 moved to /usr/lib/libwpe-1.0.so.1.8.1 packages/core2-32-poky-linux/libwpe/libwpe: FILELIST: removed "/usr/lib/libwpe-1.0.so.1.8.0", added "/usr/lib/libwpe-1.0.so.1.8.1" Changes to packages/core2-32-poky-linux/libwpe (sysroot): /usr/lib/libwpe-1.0.so.1 changed symlink target from libwpe-1.0.so.1.8.0 to libwpe-1.0.so.1.8.1 /usr/lib/libwpe-1.0.so.1.8.0 moved to /usr/lib/libwpe-1.0.so.1.8.1 0001-libwpe-upgrade-1.14.0-1.14.1.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177262): https://lists.openembedded.org/g/openembedded-core/message/177262 Mute This Topic: https://lists.openembedded.org/mt/96996952/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] rust: upgrading to 1.67.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust* to *1.67.1* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-rust-upgrade-1.67.0-1.67.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 WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 895 .bb files complete (891 cached, 4 parsed). 1693 targets, 38 skipped, 0 masked, 0 errors. Removing 1 recipes from the core2-32 sysroot...done. Removing 1 recipes from the qemux86 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "i686-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-c2c8a267c0f2a5ae5ca6d20edf991b52bd5df293" TUNE_FEATURES= "m32 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:c2c8a267c0f2a5ae5ca6d20edf991b52bd5df293" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 40 Local 19 Mirrors 0 Missed 21 Current 138 (47% match, 88% complete) Removing 1 stale sstate objects for arch x86_64...done. Removing 2 stale sstate objects for arch qemux86...done. Removing 4 stale sstate objects for arch core2-32...done. NOTE: Executing Tasks NOTE: Setscene tasks completed NOTE: Running task 417 of 745 (virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/rust-llvm_1.67.0.bb:do_fetch) NOTE: Running task 447 of 745 (virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/rust_1.67.1.bb:do_fetch) NOTE: Running task 611 of 745 (virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/cargo_1.67.0.bb:do_fetch) NOTE: Running task 643 of 745 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/libstd-rs_1.67.0.bb:do_fetch) NOTE: Running task 664 of 745 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/rust-llvm_1.67.0.bb:do_fetch) NOTE: Running task 670 of 745 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/rust_1.67.1.bb:do_fetch) NOTE: recipe rust-llvm-1.67.0-r0: task do_fetch: Started NOTE: recipe libstd-rs-1.67.0-r0: task do_fetch: Started NOTE: recipe rust-1.67.1-r0: task do_fetch: Started WARNING: libstd-rs-1.67.0-r0 do_fetch: Checksum mismatch for local file /home/pokybuild/yocto-worker/auh/build/build/build/downloads/rustc-1.67.0-src.tar.xz Cleaning and trying again. WARNING: libstd-rs-1.67.0-r0 do_fetch: Renaming /home/pokybuild/yocto-worker/auh/build/build/build/downloads/rustc-1.67.0-src.tar.xz to /home/pokybuild/yocto-worker/auh/build/build/build/downloads/rustc-1.67.0-src.tar.xz_bad-checksum_9ef8cf88a1d35d319808daf2f193aadca9ed9bcae1d4d5db8946a448c9432c6d NOTE: recipe rust-llvm-native-1.67.0-r0: task do_fetch: Started NOTE: recipe rust-native-1.67.1-r0: task do_fetch: Started NOTE: recipe cargo-native-1.67.0-r0: task do_fetch: Started NOTE: recipe rust-1.67.1-r0: task do_fetch: Succeeded NOTE: Running task 675 of 745 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/rust_1.67.1.bb:do_unpack) NOTE: recipe rust-native-1.67.1-r0: task do_fetch: Succeeded NOTE: Running task 676 of 745 (virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/rust_1.67.1.bb:do_unpack) NOTE: recipe rust-1.67.1-r0: task do_unpack: Started NOTE: recipe rust-native-1.67.1-r0: task do_unpack: Started WARNING: libstd-rs-1.67.0-r0 do_fetch: Checksum failure encountered with download of https://static.rust-lang.org/dist/rustc-1.67.0-src.tar.xz;name=rust - will attempt other sources if available NOTE: recipe rust-1.67.1-r0: task do_unpack: Succeeded NOTE: Running task 677 of 745
[OE-core] [AUH] sudo: upgrading to 1.9.13 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *sudo* to *1.9.13* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe sudo failed. NOTE: Starting bitbake server... WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Summary: There was 1 WARNING message. WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-fda099a90ac30701248690922ff3f5511cb92454" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:fda099a90ac30701248690922ff3f5511cb92454" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% match, 100% complete) 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 WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 896 .bb files complete (894 cached, 2 parsed). 1694 targets, 37 skipped, 0 masked, 0 errors. Summary: There was 1 WARNING message. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-fda099a90ac30701248690922ff3f5511cb92454" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:fda099a90ac30701248690922ff3f5511cb92454" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% complete) NOTE: No setscene tasks NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 2 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: 33% |### | ETA: 0:00:00 Adding changed files: 66% |### | ETA: 0:00:00 Adding changed files: 99% |### | 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://www.sudo.ws/dist/sudo-1.9.13.tar.gz... INFO: Rebasing devtool onto a58ae08c63d47644102b19a1c41d51aa769c1c31 WARNING: Command 'git rebase a58ae08c63d47644102b19a1c41d51aa769c1c31' failed: Auto-merging examples/sudo.conf.in CONFLICT (content): Merge conflict in examples/sudo.conf.in You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/sudo INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/sudo/sudo_1.9.13.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 (#177245): https://lists.openembedded.org/g/openembedded-core/message/177245 Mute This Topic: https://lists.openembedded.org/mt/96996934/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[OE-core] [AUH] libva: upgrading to 2.17.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libva* to *2.17.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-libva-upgrade-2.16.0-2.17.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 0001-libva-upgrade-2.16.0-2.17.0.patch Description: Binary data WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 895 .bb files complete (893 cached, 2 parsed). 1693 targets, 38 skipped, 0 masked, 0 errors. Removing 1 recipes from the core2-32 sysroot...done. Removing 1 recipes from the qemux86 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "i686-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-39d0f2ce9815f675d43a1bcab299f7fbd37cd8d5" TUNE_FEATURES= "m32 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:39d0f2ce9815f675d43a1bcab299f7fbd37cd8d5" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 109 Local 102 Mirrors 0 Missed 7 Current 267 (93% match, 98% complete) NOTE: Executing Tasks NOTE: Setscene tasks completed NOTE: Running task 1233 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_fetch) NOTE: Running task 1359 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_write_config) NOTE: recipe libva-2.17.0-r0: task do_fetch: Started NOTE: recipe libva-2.17.0-r0: task do_fetch: Succeeded NOTE: recipe libva-2.17.0-r0: task do_write_config: Started NOTE: Running task 1368 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_unpack) NOTE: Running task 1369 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_prepare_recipe_sysroot) NOTE: recipe libva-2.17.0-r0: task do_write_config: Succeeded NOTE: recipe libva-2.17.0-r0: task do_unpack: Started NOTE: recipe libva-2.17.0-r0: task do_prepare_recipe_sysroot: Started NOTE: recipe libva-2.17.0-r0: task do_unpack: Succeeded NOTE: Running task 1370 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_patch) NOTE: recipe libva-2.17.0-r0: task do_patch: Started NOTE: recipe libva-2.17.0-r0: task do_patch: Succeeded NOTE: Running task 1371 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_deploy_source_date_epoch) NOTE: Running task 1372 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_populate_lic) NOTE: recipe libva-2.17.0-r0: task do_prepare_recipe_sysroot: Succeeded NOTE: recipe libva-2.17.0-r0: task do_populate_lic: Started NOTE: recipe libva-2.17.0-r0: task do_deploy_source_date_epoch: Started NOTE: recipe libva-2.17.0-r0: task do_populate_lic: Succeeded NOTE: recipe libva-2.17.0-r0: task do_deploy_source_date_epoch: Succeeded NOTE: Running task 1373 of 1381 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/libva/libva_2.17.0.bb:do_configure) NOTE: recipe libva-2.17.0-r0: task do_configure: Started Log data follows: | DEBUG: Executing python function extend_recipe_sysroot | NOTE: Direct dependencies are ['/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-core/glibc/glibc_2.37.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/gcc/gcc-cross_12.2.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/gcc/gcc-runtime_12.2.bb:do_populate_sysroot',
[OE-core] [AUH] acpica: upgrading to 20221022 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *acpica* to *20221022* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade acpica -V 20221022 NOTE: Starting bitbake server... WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Summary: There was 1 WARNING message. WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-6a6ef2b0b92a2b1c58b17c6ec61ac885f552b067" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:6a6ef2b0b92a2b1c58b17c6ec61ac885f552b067" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% match, 100% complete) 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 WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 896 .bb files complete (894 cached, 2 parsed). 1694 targets, 37 skipped, 0 masked, 0 errors. Summary: There was 1 WARNING message. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-6a6ef2b0b92a2b1c58b17c6ec61ac885f552b067" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:6a6ef2b0b92a2b1c58b17c6ec61ac885f552b067" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% complete) NOTE: No setscene tasks NOTE: Executing Tasks WARNING: Failed to fetch URL https://acpica.org/sites/acpica/files/acpica-unix-20221022.tar.gz, attempting MIRRORS if available NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1 failed. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 2 seconds INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching https://acpica.org/sites/acpica/files/acpica-unix-20221022.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 PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-7ff6yut0/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-7ff6yut0/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-7ff6yut0/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-7ff6yut0/work/recipe-sysroot-native/usr/bin:/home/ pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-7ff6yut0/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-7ff6yut0/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools"; export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -O /home/pokybuild/yocto-worker/auh/build/build/build/downloads/acpica-unix-20221022.tar.gz.tmp -P
[OE-core] [AUH] mmc-utils: upgrading to d4c2910981ff99b983734426dfa99632fb81ac6b SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mmc-utils* to *d4c2910981ff99b983734426dfa99632fb81ac6b* has Succeeded. Next steps: - apply the patch: git am 0001-mmc-utils-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 packages/core2-32-poky-linux/mmc-utils: PKGV changed from 0.1+gitAUTOINC+c62dd8e415 [default] to 0.1+gitAUTOINC+d4c2910981 [default] packages/core2-32-poky-linux/mmc-utils: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGSIZE changed from 233712 to 235268 (+1%) packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGSIZE changed from 215101 to 216175 (+0%) packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGSIZE changed from 139044 to 143172 (+3%) packages/core2-32-poky-linux/mmc-utils/mmc-utils: PV changed from "0.1+gitAUTOINC+c62dd8e415" to "0.1+gitAUTOINC+d4c2910981" packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGV changed from 0.1+git0+c62dd8e415 to 0.1+git0+d4c2910981 0001-mmc-utils-upgrade-to-latest-revision.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177240): https://lists.openembedded.org/g/openembedded-core/message/177240 Mute This Topic: https://lists.openembedded.org/mt/96996929/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] log4cplus: upgrading to 2.1.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *log4cplus* to *2.1.0* has Succeeded. Next steps: - apply the patch: git am 0001-log4cplus-upgrade-2.0.8-2.1.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 packages/core2-32-poky-linux/log4cplus: PKGV changed from 2.0.8 [default] to 2.1.0 [default] packages/core2-32-poky-linux/log4cplus: SRC_URI changed from "https://downloads.sourceforge.net/project/log4cplus/log4cplus-stable/2.0.8/log4cplus-2.0.8.tar.gz; to "https://downloads.sourceforge.net/project/log4cplus/log4cplus-stable/2.1.0/log4cplus-2.1.0.tar.gz; packages/core2-32-poky-linux/log4cplus: PV changed from "2.0.8" to "2.1.0" packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: PKGV changed from 2.0.8 [default] to 2.1.0 [default] packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: FILELIST: removed "/usr/lib/.debug/liblog4cplusU-2.0.so.3.4.7 /usr/lib/.debug/liblog4cplus-2.0.so.3.4.7", added "/usr/lib/.debug/liblog4cplusU-2.1.so.9.0.0 /usr/lib/.debug/liblog4cplus-2.1.so.9.0.0" packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: PKGSIZE changed from 15067968 to 15280036 (+1%) packages/core2-32-poky-linux/log4cplus/log4cplus-dbg: PV changed from "2.0.8" to "2.1.0" packages/core2-32-poky-linux/log4cplus/log4cplus-dev: PKGV changed from 2.0.8 [default] to 2.1.0 [default] packages/core2-32-poky-linux/log4cplus/log4cplus-dev: FILELIST: added "/usr/include/log4cplus/exception.h" packages/core2-32-poky-linux/log4cplus/log4cplus-dev: PKGSIZE changed from 376078 to 379482 (+1%) packages/core2-32-poky-linux/log4cplus/log4cplus-dev: PV changed from "2.0.8" to "2.1.0" packages/core2-32-poky-linux/log4cplus/log4cplus-doc: PKGV changed from 2.0.8 [default] to 2.1.0 [default] packages/core2-32-poky-linux/log4cplus/log4cplus-doc: PV changed from "2.0.8" to "2.1.0" packages/core2-32-poky-linux/log4cplus/log4cplus-locale: PKGV changed from 2.0.8 [default] to 2.1.0 [default] packages/core2-32-poky-linux/log4cplus/log4cplus-locale: PV changed from "2.0.8" to "2.1.0" packages/core2-32-poky-linux/log4cplus/log4cplus-src: PKGV changed from 2.0.8 [default] to 2.1.0 [default] packages/core2-32-poky-linux/log4cplus/log4cplus-src: FILELIST: directory renamed /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/thread -> /usr/src/debug/log4cplus/2.1.0-r0/include/log4cplus/thread, directory renamed /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/internal -> /usr/src/debug/log4cplus/2.1.0-r0/include/log4cplus/internal, directory renamed /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/helpers -> /usr/src/debug/log4cplus/2.1.0-r0/include/log4cplus/helpers, directory renamed /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/spi -> /usr/src/debug/log4cplus/2.1.0-r0/include/log4cplus/spi, directory renamed /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/thread/impl -> /usr/src/debug/log4cplus/2.1.0-r0/include/log4cplus/thread/impl, directory renamed /usr/src/debug/log4cplus/2.0.8-r0/threadpool -> /usr/src/debug/log4cplus/2.1.0-r0/threadpool, removed "/usr/src/debug/log4cplus/2.0.8-r0/src/appender.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/snprintf.cxx / usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/nullappender.h /usr/src/debug/log4cplus/2.0.8-r0/src/hierarchylocker.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/layout.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/filter.cxx /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/callbackappender.h /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/clogger.h /usr/src/debug/log4cplus/2.0.8-r0/src/syncprims.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/loggingevent.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/log4judpappender.cxx /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/log4judpappender.h /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/loglevel.h /usr/src/debug/log4cplus/2.0.8-r0/src/lockfile.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/appenderattachableimpl.cxx /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/asyncappender.h /usr/src/debug/log4cplus/2.0.8-r0/include/log4cplus/consoleappender.h /usr/src/debug/log4cplus/2.0.8-r0/src/fileappender.cxx /usr/src/debug/log4cplus/2.0.8-r0 /src/nullappender.cxx /usr/src/debug/log4cplus/2.0.8-r0/src/mdc.cxx
[OE-core] [AUH] vulkan-samples: upgrading to 3df7dba1b1f428f24cd9a242af78540a518f4b67 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *3df7dba1b1f428f24cd9a242af78540a518f4b67* has Failed(other errors). Detailed error information: 'MACHINE=qemux86 bitbake vulkan-samples' failed WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 0 entries from dependency cache. Parsing recipes...done. Parsing of 895 .bb files complete (0 cached, 895 parsed). 1693 targets, 38 skipped, 0 masked, 0 errors. Removing 67 recipes from the core2-32 sysroot...done. Removing 78 recipes from the qemux86 sysroot...done. Summary: There was 1 WARNING message. Summary: There was 1 ERROR message, returning a non-zero exit code. ERROR: Nothing PROVIDES 'vulkan-samples' vulkan-samples was skipped: incompatible with host i686-poky-linux (not in COMPATIBLE_HOST) 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 (#177253): https://lists.openembedded.org/g/openembedded-core/message/177253 Mute This Topic: https://lists.openembedded.org/mt/96996943/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-cryptography-vectors: upgrading to 39.0.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-cryptography-vectors* to *39.0.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-cryptography-vectors-upgrade-39.0.0-39.0.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 0001-python3-cryptography-vectors-upgrade-39.0.0-39.0.1.patch Description: Binary data packages/core2-32-poky-linux/python3-cryptography-vectors: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors: SRC_URI changed from "https://files.pythonhosted.org/packages/source/c/cryptography_vectors/cryptography_vectors-39.0.0.tar.gz; to "https://files.pythonhosted.org/packages/source/c/cryptography_vectors/cryptography_vectors-39.0.1.tar.gz; packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-dbg: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-dbg: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-dev: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-dev: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-doc: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-doc: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-locale: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-locale: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-src: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-src: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-staticdev: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors-staticdev: PV changed from "39.0.0" to "39.0.1" packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors: PKGV changed from 39.0.0 [default] to 39.0.1 [default] packages/core2-32-poky-linux/python3-cryptography-vectors/python3-cryptography-vectors: PV changed from "39.0.0" to "39.0.1" Changes to packages/core2-32-poky-linux/python3-cryptography-vectors (sysroot): /usr/lib/python3.11/site-packages/cryptography_vectors-39.0.0.dist-info moved to /usr/lib/python3.11/site-packages/cryptography_vectors-39.0.1.dist-info Changes to packages/core2-32-poky-linux/python3-cryptography-vectors (sysroot): /usr/lib/python3.11/site-packages/cryptography_vectors-39.0.0.dist-info moved to /usr/lib/python3.11/site-packages/cryptography_vectors-39.0.1.dist-info -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177238): https://lists.openembedded.org/g/openembedded-core/message/177238 Mute This Topic: https://lists.openembedded.org/mt/96996927/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] piglit: upgrading to 590d81bb5fa219353104980108e9f1aa2b1d1b6b SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *piglit* to *590d81bb5fa219353104980108e9f1aa2b1d1b6b* has Succeeded. Next steps: - apply the patch: git am 0001-piglit-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 packages/core2-32-poky-linux/piglit: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit: PKGV changed from 1.0+gitrAUTOINC+acc0e009d0 [default] to 1.0+gitrAUTOINC+590d81bb5f [default] packages/core2-32-poky-linux/piglit/piglit-bash-completion: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-dbg: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-dev: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-dev: RRECOMMENDS: removed "piglit (['= 1.0+gitr0+acc0e009d0-r0'])", added "piglit (['= 1.0+gitr0+590d81bb5f-r0'])" packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-doc: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-locale: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-src: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-staticdev: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit-staticdev: RDEPENDS: removed "piglit-dev (['= 1.0+gitr0+acc0e009d0-r0'])", added "piglit-dev (['= 1.0+gitr0+590d81bb5f-r0'])" packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit: PV changed from "1.0+gitrAUTOINC+acc0e009d0" to "1.0+gitrAUTOINC+590d81bb5f" packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-dev: RRECOMMENDS: removed "piglit (['= 1.0+gitr0+acc0e009d0-r0'])", added "piglit (['= 1.0+gitr0+590d81bb5f-r0'])" packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f packages/core2-32-poky-linux/piglit/piglit-staticdev: RDEPENDS: removed "piglit-dev (['= 1.0+gitr0+acc0e009d0-r0'])", added "piglit-dev (['= 1.0+gitr0+590d81bb5f-r0'])" packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 1.0+gitr0+acc0e009d0 to 1.0+gitr0+590d81bb5f WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done.
[OE-core] [AUH] python3-numpy: upgrading to 1.24.2 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-numpy* to *1.24.2* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe python3-numpy failed. NOTE: Starting bitbake server... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... (16:09:45.168989) WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Summary: There was 1 WARNING message. WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-a96f3b8ebe20916b5086278c9d3ed888ce6e1a48" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:a96f3b8ebe20916b5086278c9d3ed888ce6e1a48" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 19 (100% match, 100% complete) 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 WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes...done. Parsing of 896 .bb files complete (894 cached, 2 parsed). 1694 targets, 37 skipped, 0 masked, 0 errors. Summary: There was 1 WARNING message. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "2.2.0" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "4.1+snapshot-a96f3b8ebe20916b5086278c9d3ed888ce6e1a48" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:a96f3b8ebe20916b5086278c9d3ed888ce6e1a48" workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af" Initialising tasks...done. Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0% complete) NOTE: No setscene tasks NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 2 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: 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://github.com/numpy/numpy/releases/download/v1.24.2/numpy-1.24.2.tar.gz... INFO: Rebasing devtool onto 50467edec486d8e1e28c1a25ed4c307192866165 WARNING: Command 'git rebase 50467edec486d8e1e28c1a25ed4c307192866165' failed: Auto-merging numpy/core/src/multiarray/arraytypes.c.src CONFLICT (content): Merge conflict in numpy/core/src/multiarray/arraytypes.c.src Auto-merging numpy/core/src/multiarray/common.h CONFLICT (content): Merge conflict in numpy/core/src/multiarray/common.h You will need to resolve conflicts in order to complete the upgrade. INFO: Using source tree as build directory since that would be the default for this recipe INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/python3-numpy INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/python3-numpy/python3-numpy_1.24.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 (#177233): https://lists.openembedded.org/g/openembedded-core/message/177233 Mute
[OE-core] [AUH] vala: upgrading to 0.56.4 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vala* to *0.56.4* has Succeeded. Next steps: - apply the patch: git am 0001-vala-upgrade-0.56.3-0.56.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 0001-vala-upgrade-0.56.3-0.56.4.patch Description: Binary data packages/core2-32-poky-linux/vala: SRC_URI changed from "http://ftp.gnome.org/pub/GNOME/sources/vala/0.56/vala-0.56.3.tar.xz; to "http://ftp.gnome.org/pub/GNOME/sources/vala/0.56/vala-0.56.4.tar.xz; packages/core2-32-poky-linux/vala: PKGV changed from 0.56.3 [default] to 0.56.4 [default] packages/core2-32-poky-linux/vala: PV changed from "0.56.3" to "0.56.4" Changes to packages/core2-32-poky-linux/vala (sysroot): /usr/share/vala-0.56/vapi/javascriptcoregtk-6.0.vapi was added /usr/share/vala-0.56/vapi/webkitgtk-6.0.deps was added /usr/share/vala-0.56/vapi/webkitgtk-6.0.vapi was added /usr/share/vala-0.56/vapi/webkitgtk-web-extension-6.0.deps was added /usr/share/vala-0.56/vapi/webkitgtk-web-extension-6.0.vapi was added packages/core2-32-poky-linux/vala/vala-dbg: PKGSIZE changed from 15454580 to 15513040 (+0%) packages/core2-32-poky-linux/vala/vala-dbg: PKGV changed from 0.56.3 [default] to 0.56.4 [default] packages/core2-32-poky-linux/vala/vala-dbg: PV changed from "0.56.3" to "0.56.4" packages/core2-32-poky-linux/vala/vala-dev: PKGSIZE changed from 439282 to 439364 (+0%) packages/core2-32-poky-linux/vala/vala-dev: PKGV changed from 0.56.3 [default] to 0.56.4 [default] packages/core2-32-poky-linux/vala/vala-dev: PV changed from "0.56.3" to "0.56.4" packages/core2-32-poky-linux/vala/vala-doc: PKGSIZE changed from 10319 to 10316 (-0%) packages/core2-32-poky-linux/vala/vala-doc: PKGV changed from 0.56.3 [default] to 0.56.4 [default] packages/core2-32-poky-linux/vala/vala-doc: PV changed from "0.56.3" to "0.56.4" packages/core2-32-poky-linux/vala/vala-locale: PKGV changed from 0.56.3 [default] to 0.56.4 [default] packages/core2-32-poky-linux/vala/vala-locale: PV changed from "0.56.3" to "0.56.4" packages/core2-32-poky-linux/vala/vala-src: PKGSIZE changed from 15767528 to 15772079 (+0%) packages/core2-32-poky-linux/vala/vala-src: FILELIST: directory renamed /usr/src/debug/vala/0.56.3-r0/vala -> /usr/src/debug/vala/0.56.4-r0/vala, directory renamed /usr/src/debug/vala/0.56.3-r0/gee -> /usr/src/debug/vala/0.56.4-r0/gee, directory renamed /usr/src/debug/vala/0.56.3-r0/vapigen -> /usr/src/debug/vala/0.56.4-r0/vapigen, directory renamed /usr/src/debug/vala/0.56.3-r0/codegen -> /usr/src/debug/vala/0.56.4-r0/codegen, directory renamed /usr/src/debug/vala/0.56.3-r0/compiler -> /usr/src/debug/vala/0.56.4-r0/compiler, directory renamed /usr/src/debug/vala/0.56.3-r0/gobject-introspection -> /usr/src/debug/vala/0.56.4-r0/gobject-introspection, removed "/usr/src/debug/vala/0.56.3-r0/ccode/valaccodeinitializerlist.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodecasestatement.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodecomment.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodebreakstatement.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodefunctiondeclarator.c /usr/src/debug/vala/0.56 .3-r0/ccode/valaccodeincludedirective.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodemodifiers.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodeelementaccess.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodedeclaration.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodeforstatement.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodeenum.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodeifstatement.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodestatement.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodedostatement.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodenewline.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodefunctioncall.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodelinedirective.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodetypedefinition.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodebinaryexpression.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodedefine.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodeassignment.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodeexpression.c /usr/src/debug/vala/0 .56.3-r0/ccode/valaccodecastexpression.c /usr/src/debug/vala/0.56.3-r0/ccode/valaccodemacroreplacement.c
[OE-core] [AUH] man-pages: upgrading to 6.03 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *man-pages* to *6.03* has Succeeded. Next steps: - apply the patch: git am 0001-man-pages-upgrade-6.02-6.03.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 packages/core2-32-poky-linux/man-pages: SRC_URI changed from "https://cdn.kernel.org/pub/linux/docs/man-pages/man-pages-6.02.tar.gz; to "https://cdn.kernel.org/pub/linux/docs/man-pages/man-pages-6.03.tar.gz; packages/core2-32-poky-linux/man-pages: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages-dbg: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages-dbg: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages-dev: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages-dev: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages-doc: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages-doc: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages-locale: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages-locale: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages-src: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages-src: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages-staticdev: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages-staticdev: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages: PKGSIZE changed from 7450162 to 7486541 (+0%) packages/core2-32-poky-linux/man-pages/man-pages: FILELIST: added "/usr/share/man/man3type/printf_arginfo_size_function.3type /usr/share/man/man3type/printf_va_arg_function.3type /usr/share/man/man3/arc4random_uniform.3 /usr/share/man/man3head/printf.h.3head /usr/share/man/man3const/PA_FLOAT.3const /usr/share/man/man3const/PA_FLAG_LONG_DOUBLE.3const /usr/share/man/man3const/PA_FLAG_PTR.3const /usr/share/man/man3/arc4random_buf.3 /usr/share/man/man3/register_printf_type.3 /usr/share/man/man3const/PA_WSTRING.3const /usr/share/man/man3/register_printf_modifier.3 /usr/share/man/man3const/PA_FLAG_LONG.3const /usr/share/man/man3const/PA_INT.3const /usr/share/man/man3/register_printf_specifier.3 /usr/share/man/man3const/PA_WCHAR.3const /usr/share/man/man3const/PA_POINTER.3const /usr/share/man/man3const/PA_FLAG_LONG_LONG.3const /usr/share/man/man3const/PA_FLAG_SHORT.3const /usr/share/man/man3/arc4random.3 /usr/share/man/man3const/PA_DOUBLE.3const /usr/share/man/man3const/PA_STRING.3const /us r/share/man/man3/powerof2.3 /usr/share/man/man3const/PA_CHAR.3const /usr/share/man/man3const/PA_LAST.3const /usr/share/man/man3/roundup.3 /usr/share/man/man3type/printf_function.3type /usr/share/man/man3type/printf_info.3type" packages/core2-32-poky-linux/man-pages/man-pages: PV changed from "6.02" to "6.03" packages/core2-32-poky-linux/man-pages/man-pages: PKGV changed from 6.02 [default] to 6.03 [default] packages/core2-32-poky-linux/man-pages/man-pages: FILELIST: added "/usr/share/man/man3type/printf_function.3type /usr/share/man/man3const/PA_POINTER.3const /usr/share/man/man3const/PA_STRING.3const /usr/share/man/man3/arc4random_buf.3 /usr/share/man/man3const/PA_DOUBLE.3const /usr/share/man/man3/roundup.3 /usr/share/man/man3const/PA_FLAG_SHORT.3const /usr/share/man/man3const/PA_LAST.3const /usr/share/man/man3type/printf_arginfo_size_function.3type /usr/share/man/man3head/printf.h.3head /usr/share/man/man3/powerof2.3 /usr/share/man/man3/arc4random_uniform.3 /usr/share/man/man3const/PA_FLOAT.3const /usr/share/man/man3const/PA_WCHAR.3const /usr/share/man/man3type/printf_info.3type /usr/share/man/man3type/printf_va_arg_function.3type /usr/share/man/man3const/PA_INT.3const /usr/share/man/man3/arc4random.3 /usr/share/man/man3const/PA_FLAG_LONG.3const /usr/share/man/man3const/PA_FLAG_LONG_DOUBLE.3const
[OE-core] [AUH] ruby: upgrading to 3.2.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ruby* to *3.2.1* has Succeeded. Next steps: - apply the patch: git am 0001-ruby-upgrade-3.2.0-3.2.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 0001-ruby-upgrade-3.2.0-3.2.1.patch Description: Binary data packages/core2-32-poky-linux/ruby: PV changed from "3.2.0" to "3.2.1" packages/core2-32-poky-linux/ruby: PKGV changed from 3.2.0 [default] to 3.2.1 [default] packages/core2-32-poky-linux/ruby: SRC_URI changed from "http://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.0.tar.gz file://0001-extmk-fix-cross-compilation-of-external-gems.patch file://0002-Obey-LDFLAGS-for-the-link-of-libruby.patch file://remove_has_include_macros.patch file://run-ptest file://0001-template-Makefile.in-do-not-write-host-cross-cc-item.patch file://0002-template-Makefile.in-filter-out-f-prefix-map.patch file://0003-rdoc-build-reproducible-documentation.patch file://0004-lib-mkmf.rb-sort-list-of-object-files-in-generated-M.patch file://0005-Mark-Gemspec-reproducible-change-fixing-784225-too.patch file://0006-Make-gemspecs-reproducible.patch file://0001-vm_dump.c-Define-REG_S1-and-REG_S2-for-musl-riscv.patch file://0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch" to "http://cache.ruby-lang.org/pub/ruby/3.2/ruby-3.2.1.tar.gz file://0001-extmk-fix-cross-compilation-of-external-gems.patch file://0002-Obey-LDFLAGS-for-the-link-of-libruby.patch file://remove_ has_include_macros.patch file://run-ptest file://0001-template-Makefile.in-do-not-write-host-cross-cc-item.patch file://0002-template-Makefile.in-filter-out-f-prefix-map.patch file://0003-rdoc-build-reproducible-documentation.patch file://0004-lib-mkmf.rb-sort-list-of-object-files-in-generated-M.patch file://0005-Mark-Gemspec-reproducible-change-fixing-784225-too.patch file://0006-Make-gemspecs-reproducible.patch file://0001-vm_dump.c-Define-REG_S1-and-REG_S2-for-musl-riscv.patch file://0001-fiddle-Use-C11-_Alignof-to-define-ALIGN_OF-when-poss.patch" packages/core2-32-poky-linux/ruby/ruby-dbg: FILELIST: removed "/usr/lib/.debug/libruby.so.3.2.0", added "/usr/lib/.debug/libruby.so.3.2.1" packages/core2-32-poky-linux/ruby/ruby-dbg: PV changed from "3.2.0" to "3.2.1" packages/core2-32-poky-linux/ruby/ruby-dbg: PKGSIZE changed from 8864044 to 8865120 (+0%) packages/core2-32-poky-linux/ruby/ruby-dbg: PKGV changed from 3.2.0 [default] to 3.2.1 [default] packages/core2-32-poky-linux/ruby/ruby-dev: FILELIST: removed "/usr/include/ruby-3.2.0/i686-linux-gnu/rb_mjit_min_header-3.2.0.h", added "/usr/include/ruby-3.2.0/i686-linux-gnu/rb_mjit_min_header-3.2.1.h" packages/core2-32-poky-linux/ruby/ruby-dev: PV changed from "3.2.0" to "3.2.1" packages/core2-32-poky-linux/ruby/ruby-dev: PKGSIZE changed from 2820083 to 2820650 (+0%) packages/core2-32-poky-linux/ruby/ruby-dev: PKGV changed from 3.2.0 [default] to 3.2.1 [default] packages/core2-32-poky-linux/ruby/ruby-doc: PV changed from "3.2.0" to "3.2.1" packages/core2-32-poky-linux/ruby/ruby-doc: PKGV changed from 3.2.0 [default] to 3.2.1 [default] packages/core2-32-poky-linux/ruby/ruby-locale: PV changed from "3.2.0" to "3.2.1" packages/core2-32-poky-linux/ruby/ruby-locale: PKGV changed from 3.2.0 [default] to 3.2.1 [default] packages/core2-32-poky-linux/ruby/ruby-ptest: FILELIST: directory renamed /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/src -> /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib/src, removed "/usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/build.rb /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/rust_ruby_example/build.rb /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/Cargo.toml /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/Cargo.lock", added "/usr/lib/ruby/ptest/test/coverage/main.rb /usr/lib/ruby/ptest/test/rubygems/bundler_test_gem.rb /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib/Cargo.lock /usr/lib/ruby/ptest/test/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib/Cargo.toml
[OE-core] [AUH] python3-typing-extensions: upgrading to 4.5.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-typing-extensions* to *4.5.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-typing-extensions-upgrade-4.4.0-4.5.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 packages/core2-32-poky-linux/python3-typing-extensions: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions: SRC_URI changed from "https://files.pythonhosted.org/packages/source/t/typing_extensions/typing_extensions-4.4.0.tar.gz; to "https://files.pythonhosted.org/packages/source/t/typing_extensions/typing_extensions-4.5.0.tar.gz; packages/core2-32-poky-linux/python3-typing-extensions: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-dbg: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-dbg: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-dev: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-dev: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-doc: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-doc: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-locale: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-locale: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-src: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-src: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-staticdev: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions-staticdev: PKGV changed from 4.4.0 [default] to 4.5.0 [default] packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions: PKGSIZE changed from 197979 to 207643 (+5%) packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions: PV changed from "4.4.0" to "4.5.0" packages/core2-32-poky-linux/python3-typing-extensions/python3-typing-extensions: PKGV changed from 4.4.0 [default] to 4.5.0 [default] Changes to packages/core2-32-poky-linux/python3-typing-extensions (sysroot): /usr/lib/python3.11/site-packages/typing_extensions-4.4.0.dist-info moved to /usr/lib/python3.11/site-packages/typing_extensions-4.5.0.dist-info Changes to packages/core2-32-poky-linux/python3-typing-extensions (sysroot): /usr/lib/python3.11/site-packages/typing_extensions-4.4.0.dist-info moved to /usr/lib/python3.11/site-packages/typing_extensions-4.5.0.dist-info 0001-python3-typing-extensions-upgrade-4.4.0-4.5.0.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177231): https://lists.openembedded.org/g/openembedded-core/message/177231 Mute This Topic: https://lists.openembedded.org/mt/96996920/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-setuptools: upgrading to 67.3.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-setuptools* to *67.3.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-setuptools-upgrade-67.2.0-67.3.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 packages/core2-32-poky-linux/python3-setuptools: SRC_URI changed from "https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-67.2.0.tar.gz file://0001-_distutils-sysconfig.py-make-it-possible-to-substite.patch" to "https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-67.3.1.tar.gz file://0001-_distutils-sysconfig.py-make-it-possible-to-substite.patch" packages/core2-32-poky-linux/python3-setuptools: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PKGSIZE changed from 1374947 to 1375615 (+0%) packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dbg: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dbg: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dev: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-dev: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-doc: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-doc: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-locale: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-locale: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-src: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-src: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-staticdev: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools-staticdev: PV changed from "67.2.0" to "67.3.1" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: FILELIST: directory renamed /usr/lib/python3.11/site-packages/setuptools-67.2.0.dist-info -> /usr/lib/python3.11/site-packages/setuptools-67.3.1.dist-info, added "/usr/lib/python3.11/site-packages/setuptools/_normalization.py /usr/lib/python3.11/site-packages/setuptools/__pycache__/_normalization.cpython-311.pyc" packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PKGV changed from 67.2.0 [default] to 67.3.1 [default] packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PKGSIZE changed from 5273357 to 5289283 (+0%) packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: PV changed from "67.2.0" to "67.3.1" Changes to packages/core2-32-poky-linux/python3-setuptools (sysroot): /usr/lib/python3.11/site-packages/setuptools-67.2.0.dist-info moved to /usr/lib/python3.11/site-packages/setuptools-67.3.1.dist-info /usr/lib/python3.11/site-packages/setuptools/_normalization.py was added /usr/lib/python3.11/site-packages/setuptools/__pycache__/_normalization.cpython-311.pyc was added Changes to packages/x86_64-linux/python3-setuptools-native (sysroot): /usr/lib/python3.11/site-packages/setuptools-67.2.0.dist-info moved to /usr/lib/python3.11/site-packages/setuptools-67.3.1.dist-info /usr/lib/python3.11/site-packages/setuptools/_normalization.py was added packages/core2-32-poky-linux/python3-setuptools/python3-setuptools: FILELIST: directory renamed /usr/lib/python3.11/site-packages/setuptools-67.2.0.dist-info -> /usr/lib/python3.11/site-packages/setuptools-67.3.1.dist-info,
[OE-core] [AUH] python3-hatchling: upgrading to 1.13.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-hatchling* to *1.13.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-hatchling-upgrade-1.12.2-1.13.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 packages/core2-32-poky-linux/python3-hatchling: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling: SRC_URI changed from "https://files.pythonhosted.org/packages/source/h/hatchling/hatchling-1.12.2.tar.gz; to "https://files.pythonhosted.org/packages/source/h/hatchling/hatchling-1.13.0.tar.gz; packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-dbg: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-dbg: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-dev: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-dev: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-doc: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-doc: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-locale: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-locale: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-src: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-src: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-staticdev: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling-staticdev: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling: PKGV changed from 1.12.2 [default] to 1.13.0 [default] packages/core2-32-poky-linux/python3-hatchling/python3-hatchling: PV changed from "1.12.2" to "1.13.0" packages/core2-32-poky-linux/python3-hatchling/python3-hatchling: PKGSIZE changed from 732189 to 733179 (+0%) Changes to packages/core2-32-poky-linux/python3-hatchling (sysroot): /usr/lib/python3.11/site-packages/hatchling-1.12.2.dist-info moved to /usr/lib/python3.11/site-packages/hatchling-1.13.0.dist-info Changes to packages/x86_64-linux/python3-hatchling-native (sysroot): /usr/lib/python3.11/site-packages/hatchling-1.12.2.dist-info moved to /usr/lib/python3.11/site-packages/hatchling-1.13.0.dist-info Changes to packages/core2-32-poky-linux/python3-hatchling (sysroot): /usr/lib/python3.11/site-packages/hatchling-1.12.2.dist-info moved to /usr/lib/python3.11/site-packages/hatchling-1.13.0.dist-info Changes to packages/x86_64-linux/python3-hatchling-native (sysroot): /usr/lib/python3.11/site-packages/hatchling-1.12.2.dist-info moved to /usr/lib/python3.11/site-packages/hatchling-1.13.0.dist-info 0001-python3-hatchling-upgrade-1.12.2-1.13.0.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177236): https://lists.openembedded.org/g/openembedded-core/message/177236 Mute This Topic: https://lists.openembedded.org/mt/96996925/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-runtime: upgrading to 1.20.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-runtime* to *1.20.1* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-go-runtime-upgrade-1.20-1.20.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 0001-go-runtime-upgrade-1.20-1.20.1.patch Description: Binary data WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes... Summary: There was 1 WARNING message. Summary: There were 2 ERROR messages, returning a non-zero exit code. ERROR: ParseError at /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/go/go_1.20.bb:1: Could not include required file go-1.20.inc ERROR: Parsing halted due to errors, see error messages above -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177232): https://lists.openembedded.org/g/openembedded-core/message/177232 Mute This Topic: https://lists.openembedded.org/mt/96996921/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] dpkg: upgrading to 1.21.20 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dpkg* to *1.21.20* has Succeeded. Next steps: - apply the patch: git am 0001-dpkg-upgrade-1.21.19-1.21.20.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 packages/core2-32-poky-linux/dpkg/dpkg-dbg: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-dbg: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-dev: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-dev: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-doc: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-doc: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-ast: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-ast: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-bs: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-bs: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-ca: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-ca: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-cs: PKGSIZE changed from 124640 to 170736 (+37%) packages/core2-32-poky-linux/dpkg/dpkg-locale-cs: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-cs: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-da: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-da: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-de: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-de: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-dz: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-dz: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-el: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-el: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-eo: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-eo: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-es: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-es: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-et: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-et: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-eu: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-eu: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-fr: PKGSIZE changed from 197226 to 309805 (+57%) packages/core2-32-poky-linux/dpkg/dpkg-locale-fr: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-fr: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-gl: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-gl: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-hu: PKGSIZE changed from 38208 to 58217 (+52%) packages/core2-32-poky-linux/dpkg/dpkg-locale-hu: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-hu: PV changed from "1.21.19" to "1.21.20" packages/core2-32-poky-linux/dpkg/dpkg-locale-id: PKGV changed from 1.21.19 [default] to 1.21.20 [default] packages/core2-32-poky-linux/dpkg/dpkg-locale-id: PV changed from "1.21.19" to "1.21.20"
[OE-core] [AUH] python3-hypothesis: upgrading to 6.68.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-hypothesis* to *6.68.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-hypothesis-upgrade-6.66.0-6.68.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 0001-python3-hypothesis-upgrade-6.66.0-6.68.1.patch Description: Binary data packages/core2-32-poky-linux/python3-hypothesis: SRC_URI changed from "https://files.pythonhosted.org/packages/source/h/hypothesis/hypothesis-6.66.0.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.68.1.tar.gz file://run-ptest file://test_binary_search.py file://test_rle.py" packages/core2-32-poky-linux/python3-hypothesis: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dbg: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-dev: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-doc: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-locale: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-locale: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-ptest: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-ptest: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-src: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-src: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-staticdev: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis-staticdev: PKGV changed from 6.66.0 [default] to 6.68.1 [default] packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis: PKGSIZE changed from 2777089 to 2776283 (-0%) packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis: PV changed from "6.66.0" to "6.68.1" packages/core2-32-poky-linux/python3-hypothesis/python3-hypothesis: PKGV changed from 6.66.0 [default] to 6.68.1 [default] Changes to packages/core2-32-poky-linux/python3-hypothesis (sysroot): /usr/lib/python3.11/site-packages/hypothesis-6.66.0.dist-info moved to /usr/lib/python3.11/site-packages/hypothesis-6.68.1.dist-info Changes to packages/core2-32-poky-linux/python3-hypothesis (sysroot): /usr/lib/python3.11/site-packages/hypothesis-6.66.0.dist-info moved to /usr/lib/python3.11/site-packages/hypothesis-6.68.1.dist-info -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177234): https://lists.openembedded.org/g/openembedded-core/message/177234 Mute This Topic: https://lists.openembedded.org/mt/96996923/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] git: upgrading to 2.39.2 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *git* to *2.39.2* has Succeeded. Next steps: - apply the patch: git am 0001-git-upgrade-2.39.1-2.39.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 packages/core2-32-poky-linux/git/git-bash-completion: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-bash-completion: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-dbg: PKGSIZE changed from 77937404 to 77964384 (+0%) packages/core2-32-poky-linux/git/git-dbg: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-dbg: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-dev: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-dev: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-doc: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-doc: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-locale: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-locale: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-perltools: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-perltools: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-src: PKGSIZE changed from 8951005 to 8953442 (+0%) packages/core2-32-poky-linux/git/git-src: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-src: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-staticdev: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-staticdev: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git-tk: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git-tk: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/git: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/git: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git/gitweb: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git/gitweb: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git: PV changed from "2.39.1" to "2.39.2" packages/core2-32-poky-linux/git: PKGV changed from 2.39.1 [default] to 2.39.2 [default] packages/core2-32-poky-linux/git: SRC_URI changed from "https://cdn.kernel.org/pub/software/scm/git/git-2.39.1.tar.gz;name=tarball file://fixsort.patch file://0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch" to "https://cdn.kernel.org/pub/software/scm/git/git-2.39.2.tar.gz;name=tarball file://fixsort.patch file://0001-config.mak.uname-do-not-force-RHEL-7-specific-build-.patch" 0001-git-upgrade-2.39.1-2.39.2.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177229): https://lists.openembedded.org/g/openembedded-core/message/177229 Mute This Topic: https://lists.openembedded.org/mt/96996918/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] e2fsprogs: upgrading to 1.47.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *e2fsprogs* to *1.47.0* has Succeeded. Next steps: - apply the patch: git am 0001-e2fsprogs-upgrade-1.46.5-1.47.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 packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-badblocks: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-badblocks: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dbg: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dbg: PKGSIZE changed from 4804616 to 4810340 (+0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dbg: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dev: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dev: PKGSIZE changed from 210779 to 211287 (+0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dev: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-doc: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-doc: PKGSIZE changed from 227894 to 229602 (+1%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-doc: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dumpe2fs: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-dumpe2fs: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2fsck: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2fsck: PKGSIZE changed from 402764 to 407340 (+1%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2fsck: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2scrub: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2scrub: PKGSIZE changed from 12691 to 12688 (-0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-e2scrub: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-ca: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-ca: PKGSIZE changed from 138307 to 138233 (-0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-ca: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-cs: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-cs: PKGSIZE changed from 188256 to 187318 (-0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-cs: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-da: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-da: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-de: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-de: PKGSIZE changed from 174982 to 174877 (-0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-de: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-eo: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-eo: PKGSIZE changed from 87698 to 87621 (-0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-eo: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-es: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-es: PKGSIZE changed from 193472 to 192760 (-0%) packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-es: PKGV changed from 1.46.5 [default] to 1.47.0 [default] packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-fi: PV changed from "1.46.5" to "1.47.0" packages/core2-32-poky-linux/e2fsprogs/e2fsprogs-locale-fi: PKGV changed from 1.46.5 [default] to 1.47.0 [default]
[OE-core] [AUH] openssl: upgrading to 3.0.8 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *openssl* to *3.0.8* has Succeeded. Next steps: - apply the patch: git am 0001-openssl-upgrade-3.0.7-3.0.8.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 packages/core2-32-poky-linux/openssl: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl: SRC_URI changed from "http://www.openssl.org/source/openssl-3.0.7.tar.gz file://run-ptest file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-co.patch file://afalg.patch file://0001-Configure-do-not-tweak-mips-cflags.patch file://CVE-2022-3996.patch" to "http://www.openssl.org/source/openssl-3.0.8.tar.gz file://run-ptest file://0001-buildinfo-strip-sysroot-and-debug-prefix-map-from-co.patch file://afalg.patch file://0001-Configure-do-not-tweak-mips-cflags.patch file://environment.d-openssl.sh" packages/core2-32-poky-linux/openssl: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/libcrypto: PKGSIZE changed from 4417432 to 4421528 (+0%) packages/core2-32-poky-linux/openssl/libcrypto: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/libcrypto: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/libssl: PKGSIZE changed from 713276 to 717372 (+1%) packages/core2-32-poky-linux/openssl/libssl: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/libssl: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/openssl-bin: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/openssl-bin: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/openssl-conf: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/openssl-conf: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/openssl-dbg: PKGSIZE changed from 529344404 to 538069696 (+2%) packages/core2-32-poky-linux/openssl/openssl-dbg: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/openssl-dbg: FILELIST: added "/usr/lib/openssl/ptest/test/.debug/trace_api_test" packages/core2-32-poky-linux/openssl/openssl-dbg: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/openssl-dev: PKGSIZE changed from 1963279 to 1963779 (+0%) packages/core2-32-poky-linux/openssl/openssl-dev: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/openssl-dev: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/openssl-doc: PKGSIZE changed from 13966832 to 14085993 (+1%) packages/core2-32-poky-linux/openssl/openssl-doc: PV changed from "3.0.7" to "3.0.8" packages/core2-32-poky-linux/openssl/openssl-doc: FILELIST: added "/usr/share/man/man3/OSSL_DISPATCH.3ssl /usr/share/doc/openssl/html/man3/OSSL_DISPATCH.html /usr/share/man/man3/BIO_dgram_get_mtu_overhead.3ssl /usr/share/man/man3/BIO_s_datagram.3ssl /usr/share/doc/openssl/html/man3/ECDSA_sign.html /usr/share/man/man3/OSSL_CALLBACK.3ssl /usr/share/man/man3/BIO_dgram_send_timedout.3ssl /usr/share/man/man3/OSSL_CMP_CTX_reset_geninfo_ITAVs.3ssl /usr/share/doc/openssl/html/man3/OSSL_CALLBACK.html /usr/share/doc/openssl/html/man3/OSSL_ITEM.html /usr/share/man/man3/BIO_dgram_recv_timedout.3ssl /usr/share/man/man3/BIO_ctrl_set_connected.3ssl /usr/share/doc/openssl/html/man3/EVP_PKEY_CTX_get0_pkey.html /usr/share/man/man3/EVP_PKEY_CTX_get0_peerkey.3ssl /usr/share/man/man3/OSSL_PASSPHRASE_CALLBACK.3ssl /usr/share/man/man3/EVP_PKEY_CTX_get0_pkey.3ssl /usr/share/doc/openssl/html/man7/EVP_ASYM_CIPHER-RSA.html /usr/share/doc/openssl/html/man3/OSSL_ALGORITHM.html /usr/share/man/man3/OSSL_ITEM.3ssl /usr/share/man/man3/BIO_new_dgram.3ssl /usr/share/doc/openssl/html/man3/BIO_s_datagram.html /usr/share/man/man3/OSSL_ALGORITHM.3ssl /usr/share/man/man3/BIO_dgram_get_peer.3ssl /usr/share/man/man7/EVP_ASYM_CIPHER-RSA.7ssl /usr/share/man/man3/BIO_dgram_set_peer.3ssl /usr/share/man/man3/BIO_ctrl_dgram_connect.3ssl" packages/core2-32-poky-linux/openssl/openssl-doc: PKGV changed from 3.0.7 [default] to 3.0.8 [default] packages/core2-32-poky-linux/openssl/openssl-engines: PV
[OE-core] [AUH] go: upgrading to 1.20.1 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go* to *1.20.1* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-go-upgrade-1.20-1.20.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 WARNING: Host distribution "almalinux-8.7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache...done. Loaded 1693 entries from dependency cache. Parsing recipes... Summary: There was 1 WARNING message. Summary: There were 2 ERROR messages, returning a non-zero exit code. ERROR: ParseError at /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/go/go-runtime_1.20.bb:1: Could not include required file go-1.20.inc ERROR: Parsing halted due to errors, see error messages above 0001-go-upgrade-1.20-1.20.1.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177235): https://lists.openembedded.org/g/openembedded-core/message/177235 Mute This Topic: https://lists.openembedded.org/mt/96996924/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] gnu-config: upgrading to 63acb96f92473ceb5e21d873d7c0aee266b3d6d3 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*63acb96f92473ceb5e21d873d7c0aee266b3d6d3* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
63acb96f92473ceb5e21d873d7c0aee266b3d6d3
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)... (15:01:17.124389)
WARNING: Host distribution "almalinux-8.7" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
Loading cache...done.
Loaded 1693 entries from dependency cache.
Summary: There was 1 WARNING message.
WARNING: Host distribution "almalinux-8.7" has not been validated with this
version of the build system; you may possibly experience unexpected failures.
It is recommended that you use a tested distribution.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "2.2.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.1+snapshot-e788029fc9226151021265f9c8f774045219f96b"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:e788029fc9226151021265f9c8f774045219f96b"
workspace= "master:44311c454d0b0856f58cfa6fa60669903b2ba3af"
Initialising tasks...done.
Sstate summary: Wanted 8 Local 0 Mirrors 0 Missed 8 Current 12 (0% match, 60%
complete)
Removing 6 stale sstate objects for arch x86_64...done.
NOTE: Executing Tasks
WARNING: Failed to find a git repository in WORKDIR:
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir
WARNING: gnu-config: the directory ${WORKDIR}/git
(/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/git)
pointed to by the S variable doesn't exist - please set S within the recipe to
point to where the source has been unpacked to
WARNING: No source unpacked to S - either the gnu-config recipe doesn't use any
source or the correct source directory could not be determined
NOTE: Tasks Summary: Attempted 56 tasks of which 51 didn't need to be rerun and
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
ERROR: Bitbake Fetcher Error: FetchError('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
PATH="/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/native-intercept:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/recipe-sysroot-native/usr/bin/x86_64-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/recipe-sysroot-native/usr/bin:/home/pokybuild/yoc
to-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
export HOME="/home/pokybuild"; git -c gc.autoDetach=false -c core.pager=cat
clone -n -s
/home/pokybuild/yocto-worker/auh/build/build/build/downloads/git2/git.sav
annah.gnu.org.git.config.git/
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20221007+gitAUTOINC+f992bcc082-r0/devtooltmp-cebxkha6/workdir/git/
failed with exit code 128,
[OE-core] [PATCH] create-spdx: Add check for variable contents along with quotes
This adds a check to ensure we that if a variable is
empty it gets an empty string, this also adds quotes
to indicate the variable contents.
"comment": "CUSTOM_SPECIAL=''"
or
"comment": "CUSTOM_SPECIAL= 'variable contents'"
Signed-off-by: Saul Wold
---
meta/classes/create-spdx-2.2.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes/create-spdx-2.2.bbclass
b/meta/classes/create-spdx-2.2.bbclass
index 28a42e009f6..8b18ada40a4 100644
--- a/meta/classes/create-spdx-2.2.bbclass
+++ b/meta/classes/create-spdx-2.2.bbclass
@@ -484,7 +484,10 @@ python do_create_spdx() {
if d.getVar("SPDX_CUSTOM_ANNOTATION_VARS"):
for var in d.getVar('SPDX_CUSTOM_ANNOTATION_VARS').split():
-recipe.annotations.append(create_annotation(d, var + "=" +
d.getVar(var)))
+if d.getVar(var):
+recipe.annotations.append(create_annotation(d, var + "= '" +
d.getVar(var) + "'"))
+else:
+recipe.annotations.append(create_annotation(d, var + "=''"))
# Some CVEs may be patched during the build process without incrementing
the version number,
# so querying for CVEs based on the CPE id can lead to false positives. To
account for this,
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177224):
https://lists.openembedded.org/g/openembedded-core/message/177224
Mute This Topic: https://lists.openembedded.org/mt/96996669/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 v2 0/4] scripts/resulttool/regression: add metadata filtering
On Tue, 2023-02-14 at 17:53 +0100, Alexis Lothoré via
lists.openembedded.org wrote:
> From: Alexis Lothoré
>
> This v2 does not contain any change in patches content, it only sets the From:
> field correctly. Sorry for the noise.
>
> This patch serie is a proposal linked to discussion initiated here:
> https://lists.yoctoproject.org/g/automated-testing/topic/96652823#1219
>
> After integration of some improvements on regression reporting, it has been
> observed that the regression report of version 4.2_M2 is way too big. When
> checking it, it appears that a big part of the report is composed of "missing
> tests" (regression detected because test status changed from "PASS" to
> "None").
> It is mostly due to oeselftest results, since oeselftest is run multiple time
> for a single build, but not with the same parameters (so not the same tests
> "sets"), so those test sets are not comparable.
>
> The proposed serie introduce OSELFTEST_METADATA appended to tests results when
> the TEST_TYPE is "oeselftest". An oeselftest result with those metadata looks
> like this:
> [...]
> "configuration": {
> "HOST_DISTRO": "fedora-36",
> "HOST_NAME": "fedora36-ty-3",
> "LAYERS": {
> [...]
> },
> "MACHINE": "qemux86",
> "STARTTIME": "20230126235248",
> "TESTSERIES": "qemux86",
> "TEST_TYPE": "oeselftest",
> "OESELFTEST_METADATA": {
> "run_all_tests": true,
> "run_tests": null,
> "skips": null,
> "machine": null,
> "select_tags": ["toolchain-user", "toolchain-system"],
> "exclude_tags": null
> }
> }
> [...]
>
> Additionally, the serie now makes resulttool look at a METADATA_MATCH_TABLE,
> which tells that when compared test results have a specific TEST_TYPE, it
> should
> look for some specific metadata to know if tests can be compared or not. It
> will
> then remove all the false positive in regression reports due to tests present
> in
> base results but not found in target results because of skipped tests/excluded
> tags
>
> * this serie prioritize retro-compatibility: if the base test is older (ie: it
> does not have the needed metadata), it will consider tests as "comparable"
> * additionally to tests added in oeqa test cases, some "best effort" manual
> testing has been done, with the following cases:
> - run a basic test (e.g: `oeselftest -r tinfoils`), collect test result,
> break
> test, collect result, ensure tests are compared. Change oeselftest
> parameters, ensure tests are not compared
> - collect base and target tests results from 4.2_M2 regression report,
> manually add new metadata to some tests, replay regression report, ensure
> that regressions are kept or discarded depending on the metadata
I think this is heading in the right direction. Firstly, can we put
some kind of test script into OE-Core for making debugging/testing this
easier?
I'm wondering if we can take some of the code from qa_send_email and
move it into OE-Core such that I could do something like:
show-regression-report 4.2_M1 4.2_M2
which would then resolve those two tags to commits, find the
testresults repo, fetch the data depth1 then call resulttool regression
on them.
I did that manually to experiment. I realised that if we do something
like:
if "MACHINE" in base_configuration and "MACHINE" in target_configuration:
if base_configuration["MACHINE"] != target_configuration["MACHINE"]:
print("Skipping")
return False
in metadata_matches() we can skip a lot of mismatched combinations even
with the older test results. I think we also should be able to use some
pattern matching to generate a dummy OESELFTEST_METADATA section for
older data which doesn't have it. For example, the presence of meta_ide
tests indicates one particular type of test. Combined with the MACHINE
match, this should let us compare old and new data? That would mean
metadata_matches() would need to see into the actual results too.
Does that make sense?
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177223):
https://lists.openembedded.org/g/openembedded-core/message/177223
Mute This Topic: https://lists.openembedded.org/mt/96964070/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] libssh2: Clean up ptest patch/coverage
Martin Jansa spotted patchreview.py reports Malformed Upstream-Status in a
patch in this recipe. The patch is not being applied since there is no ptest
override.
The test in question was also disabled due to an issue with new versions of
openssh.
Add a workaround for the broken test, enable it, drop the broken patch.
Signed-off-by: Richard Purdie
---
...nviroment-to-decide-if-a-test-is-bui.patch | 44 ---
.../libssh2/libssh2/fix-ssh2-test.patch | 23 ++
.../libssh2/{files => libssh2}/run-ptest | 3 +-
.../recipes-support/libssh2/libssh2_1.10.0.bb | 3 +-
4 files changed, 25 insertions(+), 48 deletions(-)
delete mode 100644
meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
create mode 100644 meta/recipes-support/libssh2/libssh2/fix-ssh2-test.patch
rename meta/recipes-support/libssh2/{files => libssh2}/run-ptest (67%)
diff --git
a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
deleted file mode 100644
index b1204e49eb8..000
---
a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
+++ /dev/null
@@ -1,44 +0,0 @@
-From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001
-From: Your Name
-Date: Mon, 28 Dec 2020 02:08:03 +
-Subject: [PATCH] Don't let host enviroment to decide if a test is build
-
-test ssh2.sh need sshd, for cross compile, we need it on target, so
-don't use SSHD on host to decide weither to build a test
-
-Upstream-Status: Inappropriate[oe specific]
-
-Signed-off-by: Changqing Li
-
- tests/Makefile.am | 6 +-
- 1 file changed, 1 insertion(+), 5 deletions(-)
-
-diff --git a/tests/Makefile.am b/tests/Makefile.am
-index dc0922f..6cbc35d 100644
a/tests/Makefile.am
-+++ b/tests/Makefile.am
-@@ -1,16 +1,12 @@
- AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include
-I$(top_builddir)/src
- LDADD = ../src/libssh2.la
-
--if SSHD
- noinst_PROGRAMS = ssh2
- ssh2_SOURCES = ssh2.c
--endif
-
- ctests = simple$(EXEEXT)
- TESTS = $(ctests) mansyntax.sh
--if SSHD
- TESTS += ssh2.sh
--endif
- check_PROGRAMS = $(ctests)
-
- TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT)
-@@ -38,4 +34,4 @@ if OPENSSL
- # EXTRA_DIST +=
test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c
- # EXTRA_DIST +=
test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c
- EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_openssh_key.c
--endif
-\ No newline at end of file
-+endif
diff --git a/meta/recipes-support/libssh2/libssh2/fix-ssh2-test.patch
b/meta/recipes-support/libssh2/libssh2/fix-ssh2-test.patch
new file mode 100644
index 000..ee916c42d43
--- /dev/null
+++ b/meta/recipes-support/libssh2/libssh2/fix-ssh2-test.patch
@@ -0,0 +1,23 @@
+In 8.8 OpenSSH disabled sha1 rsa-sha keys out of the box,
+so we need to re-enable them as a workaround for the test
+suite until upstream updates the tests.
+
+See: https://github.com/libssh2/libssh2/issues/630
+
+Upstream-Status: Backport [alternative fixes merged upstream]
+
+Patch taken from
https://github.com/mirror-rpm/libssh2/commit/47f7114f7d0780f3075bad51a71881f45cc933c5
+
+--- a/tests/ssh2.sh
b/tests/ssh2.sh
+@@ -25,7 +25,8 @@ $SSHD -f /dev/null -h "$srcdir"/etc/host
+ -o 'Port 4711' \
+ -o 'Protocol 2' \
+ -o "AuthorizedKeysFile $srcdir/etc/user.pub" \
+--o 'UsePrivilegeSeparation no' \
++-o 'HostKeyAlgorithms +ssh-rsa' \
++-o 'PubkeyAcceptedAlgorithms +ssh-rsa' \
+ -o 'StrictModes no' \
+ -D \
+ $libssh2_sshd_params &
+
diff --git a/meta/recipes-support/libssh2/files/run-ptest
b/meta/recipes-support/libssh2/libssh2/run-ptest
similarity index 67%
rename from meta/recipes-support/libssh2/files/run-ptest
rename to meta/recipes-support/libssh2/libssh2/run-ptest
index 9e2fce2d24a..5e7426f79df 100644
--- a/meta/recipes-support/libssh2/files/run-ptest
+++ b/meta/recipes-support/libssh2/libssh2/run-ptest
@@ -2,8 +2,7 @@
ptestdir=$(dirname "$(readlink -f "$0")")
cd tests
-# omit ssh2.sh until https://github.com/libssh2/libssh2/issues/630 is fixed
-for test in simple mansyntax.sh
+for test in simple mansyntax.sh ssh2.sh
do
./../test-driver --test-name $test --log-file ../$test.log --trs-file
../$test.trs --color-tests no --enable-hard-errors yes --expect-failure no --
./$test
done
diff --git a/meta/recipes-support/libssh2/libssh2_1.10.0.bb
b/meta/recipes-support/libssh2/libssh2_1.10.0.bb
index 072d6819c0c..d5513373b08 100644
--- a/meta/recipes-support/libssh2/libssh2_1.10.0.bb
+++ b/meta/recipes-support/libssh2/libssh2_1.10.0.bb
@@ -8,11 +8,10 @@ LICENSE = "BSD-3-Clause"
LIC_FILES_CHKSUM = "file://COPYING;md5=3e089ad0cf27edf1e7f261dfcd06acc7"
SRC_URI = "http://www.libssh2.org/download/${BP}.tar.gz \
+ file://fix-ssh2-test.patch \
Re: [OE-core] [PATCH v3 1/4] dtc: version bump and add python wrapper
Hello, The series caused different build failures: https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/6713/steps/11/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/6727/steps/11/logs/stdio | /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/git/pylibfdt/../setup.py --quiet --top-builddir /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/build build_ext --build-lib=/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/build/pylibfdt | In file included from /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/recipe-sysroot-native/usr/include/python3.11/Python.h:38, | from /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/git/pylibfdt/../pylibfdt/libfdt_wrap.c:168: | /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/recipe-sysroot-native/usr/include/python3.11/pyport.h:601:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." | 601 | #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." | | ^ | error: command '/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/recipe-sysroot-native/usr/bin/i686-pokysdk-linux/i686-pokysdk-linux-gcc' failed with exit code 1 | ninja: build stopped: subcommand failed. https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/4495/steps/11/logs/stdio WARNING: dtc-1.7.0+gitAUTOINC+039a99414e-r0 do_package_qa: QA Issue: File /usr/lib/python3.11/site-packages/_libfdt.cpython-311-aarch64-linux-gnu.so in package dtc-pylibfdt contains reference to TMPDIR https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/6703/steps/13/logs/stdio | FAILED: pylibfdt/_libfdt.so | /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/git/pylibfdt/../setup.py --quiet --top-builddir /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/build build_ext --build-lib=/home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/build/pylibfdt | In file included from /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/recipe-sysroot-native/usr/include/python3.11/Python.h:38, | from /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/git/pylibfdt/../pylibfdt/libfdt_wrap.c:168: | /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/recipe-sysroot-native/usr/include/python3.11/pyport.h:236:10: fatal error: sys/select.h: No such file or directory | 236 | #include | | ^~ | compilation terminated. | error: command '/home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/work/i686-nativesdk-mingw32-w64-mingw32/nativesdk-dtc/1.7.0+gitAUTOINC+039a99414e-r0/recipe-sysroot-native/usr/bin/i686-w64-mingw32/i686-w64-mingw32-gcc' failed with exit code 1 | ninja: build stopped: subcommand failed. https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2403/steps/12/logs/stdio AssertionError: The following deb packages are missing or different and not in exclusion list: /home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/deploy/deb/./core2-64/dtc-dbg_1.7.0+git0+039a99414e-r0_amd64.deb /home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/deploy/deb/./core2-64/dtc-pylibfdt_1.7.0+git0+039a99414e-r0_amd64.deb The following ipk packages are missing or different and not in exclusion list: /home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/deploy/ipk/./core2-64/dtc-dbg_1.7.0+git0+039a99414e-r0_core2-64.ipk /home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/deploy/ipk/./core2-64/dtc-pylibfdt_1.7.0+git0+039a99414e-r0_core2-64.ipk The following rpm packages are missing or different and not in exclusion list: /home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleB/tmp/deploy/rpm/./core2_64/dtc-dbg-1.7.0+git0+039a99414e-r0.core2_64.rpm
Re: [OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
On Wed, 2023-02-15 at 17:29 +, Richard Purdie via lists.openembedded.org wrote: > On Wed, 2023-02-15 at 18:18 +0100, Martin Jansa wrote: > > * I've noticed this, because patchreview.py reports Malformed > > Upstream-Status in this one now, but the QA check in insane.bbclass > > wasn't reporting it before > > > > * the reason why insane.bbclass doesn't report it is because: > > SRC_URI:append:ptest = " > > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" > > doesn't work and probably never did as "ptest" is not an override > > and patch-status-core checks only the .patch files which are really > > in SRC_URI. > > > > * I've added it directly to SRC_URI and it also didn't apply: > > http://errors.yoctoproject.org/Errors/Details/689955/ > > as the "endif" at the end was removed in 1.10.0 version: > > > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db > > > > after updating the patch to apply I got expected patch-status-core > > failure: > > http://errors.yoctoproject.org/Errors/Details/689956/ > > ERROR: QA Issue: Malformed Upstream-Status in patch > > > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > Please correct according to > > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status > > : > > Upstream-Status: Inappropriate[oe specific] [patch-status-core] > > > > * so the mystery is solved, but what should be do with this never-used > > patch, I think we should just delete it together with > > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed > > > > * it was originally added by Changqing Li in meta-oe with: > > > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 > > then imported to oe-core by Randy MacLeod with: > > > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 > > > > Signed-off-by: Martin Jansa > > --- > > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- > > 1 file changed, 7 insertions(+), 15 deletions(-) > > > > diff --git > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > index b1204e49eb..eb2658 100644 > > --- > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > +++ > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > @@ -1,24 +1,23 @@ > > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 > > -From: Your Name > > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 > > +From: Changqing Li > > Date: Mon, 28 Dec 2020 02:08:03 + > > Subject: [PATCH] Don't let host enviroment to decide if a test is build > > > > test ssh2.sh need sshd, for cross compile, we need it on target, so > > don't use SSHD on host to decide weither to build a test > > > > -Upstream-Status: Inappropriate[oe specific] > > +Upstream-Status: Inappropriate [oe specific] > > > > Signed-off-by: Changqing Li > > The patch is to fix ssh2.sh as a test. The test was disabled here: > > https://git.yoctoproject.org/poky/commit/meta/recipes-support/libssh2?id=af067d427fc1000c2dcce84c5578ea26f9048208 > > referencing: > > https://github.com/libssh2/libssh2/issues/630 > > which is now fixed. > > The autobuilder doesn't currently run the test: > > https://autobuilder.yocto.io/pub/non-release/20230215-12/testresults/qemux86-64-ptest/libssh2.log > > I don't know if the test still needs the patch to fix it. I did some tests and there is a patch to fix issue 630 which then does allow ssh2.sh to pass without this patch. We can therefore remove it. We should also add a patch to sort issue 630 and enable the test. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177220): https://lists.openembedded.org/g/openembedded-core/message/177220 Mute This Topic: https://lists.openembedded.org/mt/96987532/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] Can create-spdx handle multiple components per recipe
Thanks for confirming. I wouldn't expect OE to be able to have any knowledge of "sneaky" downloads of additional packages. I have an idea to enhance create-spdx.bbclass so sneaky recipes can fess-up and tell create-spdx about any additional packages they downloaded. If you could implement something like the following, it would help me. If not, I'll just have to combine the OE-produced SBOM with my own custom-produced SBOMs. The idea is: Idea: Enhance create-spdx.bbclass so a recipe can add multiple additional SBOM entries. For example, if recipeX is sneaky and downloads componentY without bitbake or OE knowing about it, then the recipe will have some way to tell create-spdx that it downloaded componentY at versionZ and also give its license information. If I had this, then I think we could enhance our webui-vue recipe to use this to report all the NPM packages. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177219): https://lists.openembedded.org/g/openembedded-core/message/177219 Mute This Topic: https://lists.openembedded.org/mt/96969479/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [kirkstone][PATCH] git: upgrade 2.35.5 -> 2.35.7
Upgrade git to latest 2.37.x release to address
security issues CVE-2022-23521 and CVE-2022-41903.
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/git/{git_2.35.5.bb => git_2.35.7.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/git/{git_2.35.5.bb => git_2.35.7.bb} (98%)
diff --git a/meta/recipes-devtools/git/git_2.35.5.bb
b/meta/recipes-devtools/git/git_2.35.7.bb
similarity index 98%
rename from meta/recipes-devtools/git/git_2.35.5.bb
rename to meta/recipes-devtools/git/git_2.35.7.bb
index be4e3ca1d3..1dd5915703 100644
--- a/meta/recipes-devtools/git/git_2.35.5.bb
+++ b/meta/recipes-devtools/git/git_2.35.7.bb
@@ -165,4 +165,4 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
"
EXTRA_OEMAKE += "NO_GETTEXT=1"
-SRC_URI[tarball.sha256sum] =
"2cca63fe7bebb5b4bf8efea7b46b12bb89c16ff9711b6b6d845928501d00d0a3"
+SRC_URI[tarball.sha256sum] =
"fc849272a95cc7457091221a645fcd753b3b1984767ee3323fb6a0aa944bbcb4"
--
2.33.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177218):
https://lists.openembedded.org/g/openembedded-core/message/177218
Mute This Topic: https://lists.openembedded.org/mt/96993658/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] classes/create-spdx-2.2: Report downloads as separate packages
Moves the downloaded items from SRC_URI into separate packages in the
recipe document. This is much better than the previous implementation
because:
1) It can report multiple download locations in SRC_URI, instead of
just the first one reported.
2) It prevents the assumption that the source files listed in the
recipe are the exact file from the source URL; in particular, files
that come from file:// SRC_URI entries, and source files that have
been patched were problematic, since these aren't from the upstream
source.
3) It allows the checksums to be specified
Signed-off-by: Joshua Watt
---
meta/classes/create-spdx-2.2.bbclass | 58
meta/lib/oe/sbom.py | 4 ++
meta/lib/oe/spdx.py | 13 +++
3 files changed, 67 insertions(+), 8 deletions(-)
diff --git a/meta/classes/create-spdx-2.2.bbclass
b/meta/classes/create-spdx-2.2.bbclass
index 28a42e009f..454dd7a7a0 100644
--- a/meta/classes/create-spdx-2.2.bbclass
+++ b/meta/classes/create-spdx-2.2.bbclass
@@ -406,6 +406,54 @@ def collect_dep_sources(d, dep_recipes):
return sources
+def add_download_packages(d, doc, recipe):
+import os.path
+from bb.fetch2 import decodeurl, CHECKSUM_LIST
+import bb.process
+import oe.spdx
+import oe.sbom
+
+for download_idx, src_uri in enumerate(d.getVar('SRC_URI').split()):
+f = bb.fetch2.FetchData(src_uri, d)
+
+for name in f.names:
+package = oe.spdx.SPDXPackage()
+package.name = "%s-source-%d" % (d.getVar("PN"), download_idx + 1)
+package.SPDXID = oe.sbom.get_download_spdxid(d, download_idx + 1)
+
+if f.type == "file":
+continue
+
+uri = f.type
+proto = getattr(f, "proto", None)
+if proto is not None:
+uri = uri + "+" + proto
+uri = uri + "://" + f.host + f.path
+
+if f.method.supports_srcrev():
+uri = uri + "@" + f.revisions[name]
+
+if f.method.supports_checksum(f):
+for checksum_id in CHECKSUM_LIST:
+if checksum_id.upper() not in
oe.spdx.SPDXPackage.ALLOWED_CHECKSUMS:
+continue
+
+expected_checksum = getattr(f, "%s_expected" % checksum_id)
+if expected_checksum is None:
+continue
+
+c = oe.spdx.SPDXChecksum()
+c.algorithm = checksum_id.upper()
+c.checksumValue = expected_checksum
+package.checksums.append(c)
+
+package.downloadLocation = uri
+doc.packages.append(package)
+doc.add_relationship(doc, "DESCRIBES", package)
+# In the future, we might be able to do more fancy dependencies,
+# but this should be sufficient for now
+doc.add_relationship(package, "BUILD_DEPENDENCY_OF", recipe)
+
python do_create_spdx() {
from datetime import datetime, timezone
import oe.sbom
@@ -458,14 +506,6 @@ python do_create_spdx() {
if bb.data.inherits_class("native", d) or bb.data.inherits_class("cross",
d):
recipe.annotations.append(create_annotation(d, "isNative"))
-for s in d.getVar('SRC_URI').split():
-if not s.startswith("file://"):
-s = s.split(';')[0]
-recipe.downloadLocation = s
-break
-else:
-recipe.downloadLocation = "NOASSERTION"
-
homepage = d.getVar("HOMEPAGE")
if homepage:
recipe.homepage = homepage
@@ -507,6 +547,8 @@ python do_create_spdx() {
doc.packages.append(recipe)
doc.add_relationship(doc, "DESCRIBES", recipe)
+add_download_packages(d, doc, recipe)
+
if process_sources(d) and include_sources:
recipe_archive = deploy_dir_spdx / "recipes" / (doc.name + ".tar.zst")
with optional_tarfile(recipe_archive, archive_sources) as archive:
diff --git a/meta/lib/oe/sbom.py b/meta/lib/oe/sbom.py
index bbf466bbad..22ed5070ea 100644
--- a/meta/lib/oe/sbom.py
+++ b/meta/lib/oe/sbom.py
@@ -14,6 +14,10 @@ def get_recipe_spdxid(d):
return "SPDXRef-%s-%s" % ("Recipe", d.getVar("PN"))
+def get_download_spdxid(d, idx):
+return "SPDXRef-Download-%s-%d" % (d.getVar("PN"), idx)
+
+
def get_package_spdxid(pkg):
return "SPDXRef-Package-%s" % pkg
diff --git a/meta/lib/oe/spdx.py b/meta/lib/oe/spdx.py
index c74ea68878..7aaf2af5ed 100644
--- a/meta/lib/oe/spdx.py
+++ b/meta/lib/oe/spdx.py
@@ -216,6 +216,18 @@ class SPDXPackageVerificationCode(SPDXObject):
class SPDXPackage(SPDXObject):
+ALLOWED_CHECKSUMS = [
+"SHA1",
+"SHA224",
+"SHA256",
+"SHA384",
+"SHA512",
+"MD2",
+"MD4",
+"MD5",
+"MD6",
+]
+
name = _String()
SPDXID = _String()
versionInfo = _String()
@@ -234,6 +246,7 @@ class SPDXPackage(SPDXObject):
Re: [OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
On Wed, Feb 15, 2023 at 12:46 PM Martin Jansa wrote: > > patchreview.py will care about the space (like insane.bbclass does) if > https://lists.openembedded.org/g/openembedded-core/message/177207 is merged > I see. thanks. I think this should be something every developer should then be able to run on the patchset they are about to post for review. Otherwise, it just add on to upstreaming friction that developer experiences and it won't scale. > On Wed, Feb 15, 2023 at 9:35 PM Khem Raj wrote: >> >> On Wed, Feb 15, 2023 at 11:26 AM Khem Raj wrote: >> > >> > On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa >> > wrote: >> > > >> > > * I've noticed this, because patchreview.py reports Malformed >> > > Upstream-Status in this one now, but the QA check in insane.bbclass >> > > wasn't reporting it before >> > > >> > > * the reason why insane.bbclass doesn't report it is because: >> > > SRC_URI:append:ptest = " >> > > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" >> > > doesn't work and probably never did as "ptest" is not an override >> > > and patch-status-core checks only the .patch files which are really >> > > in SRC_URI. >> > > >> > > * I've added it directly to SRC_URI and it also didn't apply: >> > > http://errors.yoctoproject.org/Errors/Details/689955/ >> > > as the "endif" at the end was removed in 1.10.0 version: >> > > >> > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db >> > > >> > > after updating the patch to apply I got expected patch-status-core >> > > failure: >> > > http://errors.yoctoproject.org/Errors/Details/689956/ >> > > ERROR: QA Issue: Malformed Upstream-Status in patch >> > > >> > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch >> > > Please correct according to >> > > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status >> > > : >> > > Upstream-Status: Inappropriate[oe specific] [patch-status-core] >> > > >> > > * so the mystery is solved, but what should be do with this never-used >> > > patch, I think we should just delete it together with >> > > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed >> > > >> > > * it was originally added by Changqing Li in meta-oe with: >> > > >> > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 >> > > then imported to oe-core by Randy MacLeod with: >> > > >> > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 >> > > >> > > Signed-off-by: Martin Jansa >> > > --- >> > > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- >> > > 1 file changed, 7 insertions(+), 15 deletions(-) >> > > >> > > diff --git >> > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch >> > > >> > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch >> > > index b1204e49eb..eb2658 100644 >> > > --- >> > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch >> > > +++ >> > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch >> > > @@ -1,24 +1,23 @@ >> > > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 >> > > -From: Your Name >> > > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 >> > > +From: Changqing Li >> > > Date: Mon, 28 Dec 2020 02:08:03 + >> > > Subject: [PATCH] Don't let host enviroment to decide if a test is build >> > > >> > > test ssh2.sh need sshd, for cross compile, we need it on target, so >> > > don't use SSHD on host to decide weither to build a test >> > > >> > > -Upstream-Status: Inappropriate[oe specific] >> > > +Upstream-Status: Inappropriate [oe specific] >> > >> > Since we are already using a special token '[' to separate reason from >> > status, I always wondered if having this space before '[' is something >> > that could be ignored. >> > >> >> I see that scripts/contrib/patchreview.py does not care for space, >> that answers my question. Maybe it would be >> good to tabulate reason as well perhaps. >> >> > > >> > > Signed-off-by: Changqing Li >> > > - >> > > --- >> > > - tests/Makefile.am | 6 +- >> > > - 1 file changed, 1 insertion(+), 5 deletions(-) >> > > + tests/Makefile.am | 4 >> > > + 1 file changed, 4 deletions(-) >> > > >> > > diff --git a/tests/Makefile.am b/tests/Makefile.am >> > > -index dc0922f..6cbc35d 100644 >> > > +index 27ddc2d..13de8ab 100644 >> > > --- a/tests/Makefile.am >> > > +++ b/tests/Makefile.am >> > > -@@ -1,16 +1,12 @@ >> > > +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz >> > > AM_CPPFLAGS =
Re: [OE-core] Can create-spdx handle multiple components per recipe
Joseph, Currently create-spdx will only report on the recipe itself and the packages it produces. It's been a long standing TODO to make reporting of sub-components like NPM packages and rust crates better, but we haven't gotten there yet, partially because I'm not very familiar with these technologies. If you have some experience, it would be great to get some input on how to best handle these things. One of the biggest problems is that often these technologies do "sneaky" downloads of packages that we don't know about in the recipe, and thus can't really report on. We largely fixed this in rust by making user enumerate the crates they use in SRC_URI (with some tooling to help automatically generate the list), but it looks from the recipe you've linked to, this is what is happening in webui-vue. Because of this its going to be extra hard to report on any components, since we simply aren't aware they exist (at the recipe level). On Tue, Feb 14, 2023 at 2:27 PM Joseph Reynolds wrote: > > Team, > > Thanks again for continuing to improve Yocto/OE. > > I have a question about the capabilities of the create-spdx.bbclass. I > understand it will can an sBOM entry for each recipe. > > Can create-spdx.bbclass handle multiple components per recipe? For > example, my bitbake recipe produces a web application which packages > many HTML components. I would like to have the recipe included in the > SBOM together with the components which are packaged into the web > application files. Is there a way to do that? > > Specifically, the OpenBMC web application uses various NPM compoents to > provide it functionality in the end-user's browser. > Recipe: > https://github.com/openbmc/openbmc/blob/master/meta-phosphor/recipes-phosphor/webui/webui-vue_git.bb > > Project source: https://github.com/openbmc/webui-vue/ > NPM packages are specified here: > https://github.com/openbmc/webui-vue/blob/master/package-lock.json > Package-lock docs: > https://docs.npmjs.com/cli/v9/configuring-npm/package-lock-json > > I want my SBOM to include the webui-vue application together with each > of the NPM packages it uses. How can I do that? > > Sincerely, > Joseph Reynolds > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177215): https://lists.openembedded.org/g/openembedded-core/message/177215 Mute This Topic: https://lists.openembedded.org/mt/96969479/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] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
patchreview.py will care about the space (like insane.bbclass does) if https://lists.openembedded.org/g/openembedded-core/message/177207 is merged On Wed, Feb 15, 2023 at 9:35 PM Khem Raj wrote: > On Wed, Feb 15, 2023 at 11:26 AM Khem Raj wrote: > > > > On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa > wrote: > > > > > > * I've noticed this, because patchreview.py reports Malformed > > > Upstream-Status in this one now, but the QA check in insane.bbclass > > > wasn't reporting it before > > > > > > * the reason why insane.bbclass doesn't report it is because: > > > SRC_URI:append:ptest = " > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" > > > doesn't work and probably never did as "ptest" is not an override > > > and patch-status-core checks only the .patch files which are really > > > in SRC_URI. > > > > > > * I've added it directly to SRC_URI and it also didn't apply: > > > http://errors.yoctoproject.org/Errors/Details/689955/ > > > as the "endif" at the end was removed in 1.10.0 version: > > > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db > > > > > > after updating the patch to apply I got expected patch-status-core > failure: > > > http://errors.yoctoproject.org/Errors/Details/689956/ > > > ERROR: QA Issue: Malformed Upstream-Status in patch > > > > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > > Please correct according to > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status > : > > > Upstream-Status: Inappropriate[oe specific] [patch-status-core] > > > > > > * so the mystery is solved, but what should be do with this never-used > > > patch, I think we should just delete it together with > > > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed > > > > > > * it was originally added by Changqing Li in meta-oe with: > > > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 > > > then imported to oe-core by Randy MacLeod with: > > > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 > > > > > > Signed-off-by: Martin Jansa > > > --- > > > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- > > > 1 file changed, 7 insertions(+), 15 deletions(-) > > > > > > diff --git > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > > index b1204e49eb..eb2658 100644 > > > --- > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > > +++ > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > > @@ -1,24 +1,23 @@ > > > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 > > > -From: Your Name > > > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 > > > +From: Changqing Li > > > Date: Mon, 28 Dec 2020 02:08:03 + > > > Subject: [PATCH] Don't let host enviroment to decide if a test is > build > > > > > > test ssh2.sh need sshd, for cross compile, we need it on target, so > > > don't use SSHD on host to decide weither to build a test > > > > > > -Upstream-Status: Inappropriate[oe specific] > > > +Upstream-Status: Inappropriate [oe specific] > > > > Since we are already using a special token '[' to separate reason from > > status, I always wondered if having this space before '[' is something > > that could be ignored. > > > > I see that scripts/contrib/patchreview.py does not care for space, > that answers my question. Maybe it would be > good to tabulate reason as well perhaps. > > > > > > > Signed-off-by: Changqing Li > > > - > > > --- > > > - tests/Makefile.am | 6 +- > > > - 1 file changed, 1 insertion(+), 5 deletions(-) > > > + tests/Makefile.am | 4 > > > + 1 file changed, 4 deletions(-) > > > > > > diff --git a/tests/Makefile.am b/tests/Makefile.am > > > -index dc0922f..6cbc35d 100644 > > > +index 27ddc2d..13de8ab 100644 > > > --- a/tests/Makefile.am > > > +++ b/tests/Makefile.am > > > -@@ -1,16 +1,12 @@ > > > +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz > > > AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include > -I$(top_builddir)/src > > > LDADD = ../src/libssh2.la > > > > > > @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644 > > > check_PROGRAMS = $(ctests) > > > > > > TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT) > > > -@@ -38,4 +34,4 @@ if OPENSSL > > > - # EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c > > > - # EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c > > > -
[OE-core] [langdale][PATCH] git: upgrade 2.37.4 -> 2.37.6
Upgrade git to latest 2.37.x release to address
security issues CVE-2022-23521 and CVE-2022-41903.
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/git/{git_2.37.4.bb => git_2.37.6.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/git/{git_2.37.4.bb => git_2.37.6.bb} (98%)
diff --git a/meta/recipes-devtools/git/git_2.37.4.bb
b/meta/recipes-devtools/git/git_2.37.6.bb
similarity index 98%
rename from meta/recipes-devtools/git/git_2.37.4.bb
rename to meta/recipes-devtools/git/git_2.37.6.bb
index 2205a50d16..638b08a0cf 100644
--- a/meta/recipes-devtools/git/git_2.37.4.bb
+++ b/meta/recipes-devtools/git/git_2.37.6.bb
@@ -165,4 +165,4 @@ EXTRA_OECONF += "ac_cv_snprintf_returns_bogus=no \
"
EXTRA_OEMAKE += "NO_GETTEXT=1"
-SRC_URI[tarball.sha256sum] =
"a638c9bf9e45e8d48592076266adaa9b7aa272a99ee2aee2e166a649a9ba8a03"
+SRC_URI[tarball.sha256sum] =
"626e4c338f72b170e2b3afb1cb2161f6fbe4fb1d0749154f1ebfb5f0a57ec25f"
--
2.33.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177213):
https://lists.openembedded.org/g/openembedded-core/message/177213
Mute This Topic: https://lists.openembedded.org/mt/96992538/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] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
On Wed, Feb 15, 2023 at 11:26 AM Khem Raj wrote: > > On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa wrote: > > > > * I've noticed this, because patchreview.py reports Malformed > > Upstream-Status in this one now, but the QA check in insane.bbclass > > wasn't reporting it before > > > > * the reason why insane.bbclass doesn't report it is because: > > SRC_URI:append:ptest = " > > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" > > doesn't work and probably never did as "ptest" is not an override > > and patch-status-core checks only the .patch files which are really > > in SRC_URI. > > > > * I've added it directly to SRC_URI and it also didn't apply: > > http://errors.yoctoproject.org/Errors/Details/689955/ > > as the "endif" at the end was removed in 1.10.0 version: > > > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db > > > > after updating the patch to apply I got expected patch-status-core > > failure: > > http://errors.yoctoproject.org/Errors/Details/689956/ > > ERROR: QA Issue: Malformed Upstream-Status in patch > > > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > Please correct according to > > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status > > : > > Upstream-Status: Inappropriate[oe specific] [patch-status-core] > > > > * so the mystery is solved, but what should be do with this never-used > > patch, I think we should just delete it together with > > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed > > > > * it was originally added by Changqing Li in meta-oe with: > > > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 > > then imported to oe-core by Randy MacLeod with: > > > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 > > > > Signed-off-by: Martin Jansa > > --- > > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- > > 1 file changed, 7 insertions(+), 15 deletions(-) > > > > diff --git > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > index b1204e49eb..eb2658 100644 > > --- > > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > +++ > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > @@ -1,24 +1,23 @@ > > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 > > -From: Your Name > > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 > > +From: Changqing Li > > Date: Mon, 28 Dec 2020 02:08:03 + > > Subject: [PATCH] Don't let host enviroment to decide if a test is build > > > > test ssh2.sh need sshd, for cross compile, we need it on target, so > > don't use SSHD on host to decide weither to build a test > > > > -Upstream-Status: Inappropriate[oe specific] > > +Upstream-Status: Inappropriate [oe specific] > > Since we are already using a special token '[' to separate reason from > status, I always wondered if having this space before '[' is something > that could be ignored. > I see that scripts/contrib/patchreview.py does not care for space, that answers my question. Maybe it would be good to tabulate reason as well perhaps. > > > > Signed-off-by: Changqing Li > > - > > --- > > - tests/Makefile.am | 6 +- > > - 1 file changed, 1 insertion(+), 5 deletions(-) > > + tests/Makefile.am | 4 > > + 1 file changed, 4 deletions(-) > > > > diff --git a/tests/Makefile.am b/tests/Makefile.am > > -index dc0922f..6cbc35d 100644 > > +index 27ddc2d..13de8ab 100644 > > --- a/tests/Makefile.am > > +++ b/tests/Makefile.am > > -@@ -1,16 +1,12 @@ > > +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz > > AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include > > -I$(top_builddir)/src > > LDADD = ../src/libssh2.la > > > > @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644 > > check_PROGRAMS = $(ctests) > > > > TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT) > > -@@ -38,4 +34,4 @@ if OPENSSL > > - # EXTRA_DIST += > > test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c > > - # EXTRA_DIST += > > test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c > > - EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_openssh_key.c > > --endif > > -\ No newline at end of file > > -+endif > > -- > > 2.39.2 > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177212):
Re: [OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
Please no. Much less readable without a space. Alex On Wed 15. Feb 2023 at 20.27, Khem Raj wrote: > On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa > wrote: > > > > * I've noticed this, because patchreview.py reports Malformed > > Upstream-Status in this one now, but the QA check in insane.bbclass > > wasn't reporting it before > > > > * the reason why insane.bbclass doesn't report it is because: > > SRC_URI:append:ptest = " > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" > > doesn't work and probably never did as "ptest" is not an override > > and patch-status-core checks only the .patch files which are really > > in SRC_URI. > > > > * I've added it directly to SRC_URI and it also didn't apply: > > http://errors.yoctoproject.org/Errors/Details/689955/ > > as the "endif" at the end was removed in 1.10.0 version: > > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db > > > > after updating the patch to apply I got expected patch-status-core > failure: > > http://errors.yoctoproject.org/Errors/Details/689956/ > > ERROR: QA Issue: Malformed Upstream-Status in patch > > > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > Please correct according to > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status > : > > Upstream-Status: Inappropriate[oe specific] [patch-status-core] > > > > * so the mystery is solved, but what should be do with this never-used > > patch, I think we should just delete it together with > > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed > > > > * it was originally added by Changqing Li in meta-oe with: > > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 > > then imported to oe-core by Randy MacLeod with: > > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 > > > > Signed-off-by: Martin Jansa > > --- > > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- > > 1 file changed, 7 insertions(+), 15 deletions(-) > > > > diff --git > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > index b1204e49eb..eb2658 100644 > > --- > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > +++ > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > @@ -1,24 +1,23 @@ > > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 > > -From: Your Name > > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 > > +From: Changqing Li > > Date: Mon, 28 Dec 2020 02:08:03 + > > Subject: [PATCH] Don't let host enviroment to decide if a test is build > > > > test ssh2.sh need sshd, for cross compile, we need it on target, so > > don't use SSHD on host to decide weither to build a test > > > > -Upstream-Status: Inappropriate[oe specific] > > +Upstream-Status: Inappropriate [oe specific] > > Since we are already using a special token '[' to separate reason from > status, I always wondered if having this space before '[' is something > that could be ignored. > > > > > Signed-off-by: Changqing Li > > - > > --- > > - tests/Makefile.am | 6 +- > > - 1 file changed, 1 insertion(+), 5 deletions(-) > > + tests/Makefile.am | 4 > > + 1 file changed, 4 deletions(-) > > > > diff --git a/tests/Makefile.am b/tests/Makefile.am > > -index dc0922f..6cbc35d 100644 > > +index 27ddc2d..13de8ab 100644 > > --- a/tests/Makefile.am > > +++ b/tests/Makefile.am > > -@@ -1,16 +1,12 @@ > > +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz > > AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include > -I$(top_builddir)/src > > LDADD = ../src/libssh2.la > > > > @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644 > > check_PROGRAMS = $(ctests) > > > > TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT) > > -@@ -38,4 +34,4 @@ if OPENSSL > > - # EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c > > - # EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c > > - EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_rsa_openssh_key.c > > --endif > > -\ No newline at end of file > > -+endif > > -- > > 2.39.2 > > > > > > > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177211): https://lists.openembedded.org/g/openembedded-core/message/177211 Mute This Topic: https://lists.openembedded.org/mt/96987532/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe:
[OE-core] [PATCH] lttng-modules: fix for kernel 6.2+
From: Bruce Ashfield
Backporting a patching from the 2.13.x stable branch of lttng
to fix the build against kernel 6.2+.
Signed-off-by: Bruce Ashfield
---
...ccessor-helpers-into-accessors.h-v6..patch | 45 +++
.../lttng/lttng-modules_2.13.8.bb | 1 +
2 files changed, 46 insertions(+)
create mode 100644
meta/recipes-kernel/lttng/lttng-modules/0001-fix-btrfs-move-accessor-helpers-into-accessors.h-v6..patch
diff --git
a/meta/recipes-kernel/lttng/lttng-modules/0001-fix-btrfs-move-accessor-helpers-into-accessors.h-v6..patch
b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-btrfs-move-accessor-helpers-into-accessors.h-v6..patch
new file mode 100644
index 00..26ae605b31
--- /dev/null
+++
b/meta/recipes-kernel/lttng/lttng-modules/0001-fix-btrfs-move-accessor-helpers-into-accessors.h-v6..patch
@@ -0,0 +1,45 @@
+From 69d3aa79a641f539cfd5c11b46b2dd9b4df9b0f0 Mon Sep 17 00:00:00 2001
+From: Michael Jeanson
+Date: Mon, 16 Jan 2023 15:01:51 -0500
+Subject: [PATCH] fix: btrfs: move accessor helpers into accessors.h (v6.2)
+
+See upstream commit :
+
+ commit 07e81dc94474eb62705c6f96d9ab1a5a797b8703
+ Author: Josef Bacik
+ Date: Wed Oct 19 10:51:00 2022 -0400
+
+btrfs: move accessor helpers into accessors.h
+
+This is a large patch, but because they're all macros it's impossible to
+split up. Simply copy all of the item accessors in ctree.h and paste
+them in accessors.h, and then update any files to include the header so
+everything compiles.
+
+Upstream-Status: Backport
+
+Change-Id: I1f0876dd8b7a8687f6802b60c3e3baabd017cc52
+Signed-off-by: Michael Jeanson
+Signed-off-by: Mathieu Desnoyers
+---
+ include/instrumentation/events/btrfs.h | 4
+ 1 file changed, 4 insertions(+)
+
+diff --git a/include/instrumentation/events/btrfs.h
b/include/instrumentation/events/btrfs.h
+index 785f16ac..01157107 100644
+--- a/include/instrumentation/events/btrfs.h
b/include/instrumentation/events/btrfs.h
+@@ -9,6 +9,10 @@
+ #include
+ #include
+
++#if (LTTNG_LINUX_VERSION_CODE >= LTTNG_KERNEL_VERSION(6,2,0))
++#include <../fs/btrfs/accessors.h>
++#endif
++
+ #ifndef _TRACE_BTRFS_DEF_
+ #define _TRACE_BTRFS_DEF_
+ struct btrfs_root;
+--
+2.34.1
+
diff --git a/meta/recipes-kernel/lttng/lttng-modules_2.13.8.bb
b/meta/recipes-kernel/lttng/lttng-modules_2.13.8.bb
index 3cfc1bc58e..c04796be16 100644
--- a/meta/recipes-kernel/lttng/lttng-modules_2.13.8.bb
+++ b/meta/recipes-kernel/lttng/lttng-modules_2.13.8.bb
@@ -13,6 +13,7 @@ SRC_URI =
"https://lttng.org/files/${BPN}/${BPN}-${PV}.tar.bz2 \
file://0009-Rename-genhd-wrapper-to-blkdev.patch \
file://fix-jbd2-use-the-correct-print-format-v5.10.163.patch \
file://fix-jbd2-upper-bound-for-v5.10.163.patch \
+
file://0001-fix-btrfs-move-accessor-helpers-into-accessors.h-v6..patch \
"
# Use :append here so that the patch is applied also when using devupstream
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177210):
https://lists.openembedded.org/g/openembedded-core/message/177210
Mute This Topic: https://lists.openembedded.org/mt/96991086/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] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
On Wed, Feb 15, 2023 at 9:18 AM Martin Jansa wrote: > > * I've noticed this, because patchreview.py reports Malformed > Upstream-Status in this one now, but the QA check in insane.bbclass > wasn't reporting it before > > * the reason why insane.bbclass doesn't report it is because: > SRC_URI:append:ptest = " > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" > doesn't work and probably never did as "ptest" is not an override > and patch-status-core checks only the .patch files which are really > in SRC_URI. > > * I've added it directly to SRC_URI and it also didn't apply: > http://errors.yoctoproject.org/Errors/Details/689955/ > as the "endif" at the end was removed in 1.10.0 version: > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db > > after updating the patch to apply I got expected patch-status-core failure: > http://errors.yoctoproject.org/Errors/Details/689956/ > ERROR: QA Issue: Malformed Upstream-Status in patch > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > Please correct according to > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status > : > Upstream-Status: Inappropriate[oe specific] [patch-status-core] > > * so the mystery is solved, but what should be do with this never-used > patch, I think we should just delete it together with > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed > > * it was originally added by Changqing Li in meta-oe with: > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 > then imported to oe-core by Randy MacLeod with: > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 > > Signed-off-by: Martin Jansa > --- > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- > 1 file changed, 7 insertions(+), 15 deletions(-) > > diff --git > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > index b1204e49eb..eb2658 100644 > --- > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > +++ > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > @@ -1,24 +1,23 @@ > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 > -From: Your Name > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 > +From: Changqing Li > Date: Mon, 28 Dec 2020 02:08:03 + > Subject: [PATCH] Don't let host enviroment to decide if a test is build > > test ssh2.sh need sshd, for cross compile, we need it on target, so > don't use SSHD on host to decide weither to build a test > > -Upstream-Status: Inappropriate[oe specific] > +Upstream-Status: Inappropriate [oe specific] Since we are already using a special token '[' to separate reason from status, I always wondered if having this space before '[' is something that could be ignored. > > Signed-off-by: Changqing Li > - > --- > - tests/Makefile.am | 6 +- > - 1 file changed, 1 insertion(+), 5 deletions(-) > + tests/Makefile.am | 4 > + 1 file changed, 4 deletions(-) > > diff --git a/tests/Makefile.am b/tests/Makefile.am > -index dc0922f..6cbc35d 100644 > +index 27ddc2d..13de8ab 100644 > --- a/tests/Makefile.am > +++ b/tests/Makefile.am > -@@ -1,16 +1,12 @@ > +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz > AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include > -I$(top_builddir)/src > LDADD = ../src/libssh2.la > > @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644 > check_PROGRAMS = $(ctests) > > TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT) > -@@ -38,4 +34,4 @@ if OPENSSL > - # EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c > - # EXTRA_DIST += > test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c > - EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_openssh_key.c > --endif > -\ No newline at end of file > -+endif > -- > 2.39.2 > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177209): https://lists.openembedded.org/g/openembedded-core/message/177209 Mute This Topic: https://lists.openembedded.org/mt/96987532/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] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
On Wed, 2023-02-15 at 18:18 +0100, Martin Jansa wrote: > * I've noticed this, because patchreview.py reports Malformed > Upstream-Status in this one now, but the QA check in insane.bbclass > wasn't reporting it before > > * the reason why insane.bbclass doesn't report it is because: > SRC_URI:append:ptest = " > file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" > doesn't work and probably never did as "ptest" is not an override > and patch-status-core checks only the .patch files which are really > in SRC_URI. > > * I've added it directly to SRC_URI and it also didn't apply: > http://errors.yoctoproject.org/Errors/Details/689955/ > as the "endif" at the end was removed in 1.10.0 version: > > https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db > > after updating the patch to apply I got expected patch-status-core failure: > http://errors.yoctoproject.org/Errors/Details/689956/ > ERROR: QA Issue: Malformed Upstream-Status in patch > > TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > Please correct according to > https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status > : > Upstream-Status: Inappropriate[oe specific] [patch-status-core] > > * so the mystery is solved, but what should be do with this never-used > patch, I think we should just delete it together with > SRC_URI:append:ptest, but please Changqing Li confirm it's not needed > > * it was originally added by Changqing Li in meta-oe with: > > https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 > then imported to oe-core by Randy MacLeod with: > > https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 > > Signed-off-by: Martin Jansa > --- > ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- > 1 file changed, 7 insertions(+), 15 deletions(-) > > diff --git > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > index b1204e49eb..eb2658 100644 > --- > a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > +++ > b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch > @@ -1,24 +1,23 @@ > -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 > -From: Your Name > +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 > +From: Changqing Li > Date: Mon, 28 Dec 2020 02:08:03 + > Subject: [PATCH] Don't let host enviroment to decide if a test is build > > test ssh2.sh need sshd, for cross compile, we need it on target, so > don't use SSHD on host to decide weither to build a test > > -Upstream-Status: Inappropriate[oe specific] > +Upstream-Status: Inappropriate [oe specific] > > Signed-off-by: Changqing Li The patch is to fix ssh2.sh as a test. The test was disabled here: https://git.yoctoproject.org/poky/commit/meta/recipes-support/libssh2?id=af067d427fc1000c2dcce84c5578ea26f9048208 referencing: https://github.com/libssh2/libssh2/issues/630 which is now fixed. The autobuilder doesn't currently run the test: https://autobuilder.yocto.io/pub/non-release/20230215-12/testresults/qemux86-64-ptest/libssh2.log I don't know if the test still needs the patch to fix it. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177208): https://lists.openembedded.org/g/openembedded-core/message/177208 Mute This Topic: https://lists.openembedded.org/mt/96987532/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [RFC][PATCH 3/3] patchreview: use check_upstream_status() from oe.qa
* the idea was to reuse the same function as I've noticed that the
QA check which was added to insane.bbclass in:
https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a
is in some cases more strcit than scripts/contrib/patchreview.py
To be honest I wasn't aware of scripts/contrib/patchreview.py
existence when I've asked about moving check_upstream_status()
to oe.qa in order to write standalone script just like
patchreview.py, now I don't feel strongly about sharing this
functionality (other than adjusting regexes in patchreview.py)
* it finds one "new" issue in oe-core:
Malformed Upstream-Status 'Malformed Upstream-Status in patch
meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch
Please correct according to
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
:
Upstream-Status: Inappropriate[oe specific]'
(meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch)
* but unlike the QA check patchreview.py will report this:
-Upstream-Status: Submitted [https://github.com/madler/zlib/pull/599]
+Upstream-Broken-Status: Submitted [https://github.com/madler/zlib/pull/599]
as a missing Upstream-Status instead of malformed as reported by QA check:
ERROR: zlib-native-1.2.13-r0 do_patch: QA Issue: Malformed Upstream-Status in
patch
/OE/build/oe-core/openembedded-core/meta/recipes-core/zlib/zlib/0001-configure-Pass-LDFLAGS-to-link-tests.patch
Please correct according to
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
:
Upstream-Broken-Status: Submitted [https://github.com/madler/zlib/pull/599]
[patch-status-core]
* RFC: let me know if you think it's worth re-working this to better
integrate (e.g. detecting Upstream-Broken-Status and not repeating
.patch path in patchreview.py output) or if I should just adjust
regexes in patchreview.py.
Signed-off-by: Martin Jansa
---
scripts/contrib/patchreview.py | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/scripts/contrib/patchreview.py b/scripts/contrib/patchreview.py
index b22cc07f0a..ce6b0f05c4 100755
--- a/scripts/contrib/patchreview.py
+++ b/scripts/contrib/patchreview.py
@@ -42,7 +42,9 @@ def blame_patch(patch):
"--", patch)).decode("utf-8").splitlines()
def patchreview(path, patches):
-import re, os.path
+import re, os.path, sys
+sys.path.append(os.path.join(sys.path[0], '../../meta/lib'))
+import oe.qa
# General pattern: start of line, optional whitespace, tag with optional
# hyphen or spaces, maybe a colon, some whitespace, then the value, all
case
@@ -72,12 +74,11 @@ def patchreview(path, patches):
else:
result.missing_sob = True
-
# Find the Upstream-Status tag
match = status_re.search(content)
if match:
-value = match.group(1)
-if value != "Upstream-Status:":
+value = oe.qa.check_upstream_status(fullpath)
+if value:
result.malformed_upstream_status = value
value = match.group(2).lower()
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177207):
https://lists.openembedded.org/g/openembedded-core/message/177207
Mute This Topic: https://lists.openembedded.org/mt/96987604/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [RFC][PATCH 2/3] insane.bbclass: move Upstream-Status logic to oe.qa
* to be used by standalone script scripts/contrib/patchreview.py
as well
Signed-off-by: Martin Jansa
---
meta/classes-global/insane.bbclass | 19 +++
meta/lib/oe/qa.py | 17 +
2 files changed, 20 insertions(+), 16 deletions(-)
diff --git a/meta/classes-global/insane.bbclass
b/meta/classes-global/insane.bbclass
index 720b75c395..c8e4219389 100644
--- a/meta/classes-global/insane.bbclass
+++ b/meta/classes-global/insane.bbclass
@@ -1358,22 +1358,9 @@ python do_qa_patch() {
if not allpatches:
continue
-kinda_status_re = re.compile(r"^.*upstream.*status.*$", re.IGNORECASE
| re.MULTILINE)
-strict_status_re = re.compile(r"^Upstream-Status:
(Pending|Submitted|Denied|Accepted|Inappropriate|Backport|Inactive-Upstream)(
.+)?$", re.MULTILINE)
-guidelines =
"https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status;
-
-with open(fullpath, encoding='utf-8', errors='ignore') as f:
-file_content = f.read()
-match_kinda = kinda_status_re.search(file_content)
-match_strict = strict_status_re.search(file_content)
-
-if not match_strict:
-if match_kinda:
-msg = "Malformed Upstream-Status in patch\n%s\nPlease
correct according to %s :\n%s" % (fullpath, guidelines, match_kinda.group(0))
-oe.qa.handle_error(patchtype, msg, d)
-else:
-msg = "Missing Upstream-Status in patch\n%s\nPlease add
according to %s ." % (fullpath, guidelines)
-oe.qa.handle_error(patchtype, msg, d)
+msg = oe.qa.check_upstream_status(fullpath)
+if msg:
+oe.qa.handle_error(patchtype, msg, d)
oe.qa.exit_if_errors(d)
}
diff --git a/meta/lib/oe/qa.py b/meta/lib/oe/qa.py
index b4cbc50045..de980638c4 100644
--- a/meta/lib/oe/qa.py
+++ b/meta/lib/oe/qa.py
@@ -213,6 +213,23 @@ def exit_with_message_if_errors(message, d):
def exit_if_errors(d):
exit_with_message_if_errors("Fatal QA errors were found, failing task.", d)
+def check_upstream_status(fullpath):
+import re
+kinda_status_re = re.compile(r"^.*upstream.*status.*$", re.IGNORECASE |
re.MULTILINE)
+strict_status_re = re.compile(r"^Upstream-Status:
(Pending|Submitted|Denied|Accepted|Inappropriate|Backport|Inactive-Upstream)(
.+)?$", re.MULTILINE)
+guidelines =
"https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status;
+
+with open(fullpath, encoding='utf-8', errors='ignore') as f:
+file_content = f.read()
+match_kinda = kinda_status_re.search(file_content)
+match_strict = strict_status_re.search(file_content)
+
+if not match_strict:
+if match_kinda:
+return "Malformed Upstream-Status in patch\n%s\nPlease correct
according to %s :\n%s" % (fullpath, guidelines, match_kinda.group(0))
+else:
+return "Missing Upstream-Status in patch\n%s\nPlease add
according to %s ." % (fullpath, guidelines)
+
if __name__ == "__main__":
import sys
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177206):
https://lists.openembedded.org/g/openembedded-core/message/177206
Mute This Topic: https://lists.openembedded.org/mt/96987600/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/3] insane.bbclass: use 4 spaces for indentation
* this block was using just 3
Signed-off-by: Martin Jansa
---
meta/classes-global/insane.bbclass | 50 +++---
1 file changed, 25 insertions(+), 25 deletions(-)
diff --git a/meta/classes-global/insane.bbclass
b/meta/classes-global/insane.bbclass
index e1295f8539..720b75c395 100644
--- a/meta/classes-global/insane.bbclass
+++ b/meta/classes-global/insane.bbclass
@@ -1349,31 +1349,31 @@ python do_qa_patch() {
coremeta_path = os.path.join(d.getVar('COREBASE'), 'meta', '')
for url in patch.src_patches(d):
- (_, _, fullpath, _, _, _) = bb.fetch.decodeurl(url)
-
- # skip patches not in oe-core
- patchtype = "patch-status-core"
- if not os.path.abspath(fullpath).startswith(coremeta_path):
- patchtype = "patch-status-noncore"
- if not allpatches:
- continue
-
- kinda_status_re = re.compile(r"^.*upstream.*status.*$", re.IGNORECASE |
re.MULTILINE)
- strict_status_re = re.compile(r"^Upstream-Status:
(Pending|Submitted|Denied|Accepted|Inappropriate|Backport|Inactive-Upstream)(
.+)?$", re.MULTILINE)
- guidelines =
"https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status;
-
- with open(fullpath, encoding='utf-8', errors='ignore') as f:
- file_content = f.read()
- match_kinda = kinda_status_re.search(file_content)
- match_strict = strict_status_re.search(file_content)
-
- if not match_strict:
- if match_kinda:
- msg = "Malformed Upstream-Status in patch\n%s\nPlease
correct according to %s :\n%s" % (fullpath, guidelines, match_kinda.group(0))
- oe.qa.handle_error(patchtype, msg, d)
- else:
- msg = "Missing Upstream-Status in patch\n%s\nPlease add
according to %s ." % (fullpath, guidelines)
- oe.qa.handle_error(patchtype, msg, d)
+(_, _, fullpath, _, _, _) = bb.fetch.decodeurl(url)
+
+# skip patches not in oe-core
+patchtype = "patch-status-core"
+if not os.path.abspath(fullpath).startswith(coremeta_path):
+patchtype = "patch-status-noncore"
+if not allpatches:
+continue
+
+kinda_status_re = re.compile(r"^.*upstream.*status.*$", re.IGNORECASE
| re.MULTILINE)
+strict_status_re = re.compile(r"^Upstream-Status:
(Pending|Submitted|Denied|Accepted|Inappropriate|Backport|Inactive-Upstream)(
.+)?$", re.MULTILINE)
+guidelines =
"https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status;
+
+with open(fullpath, encoding='utf-8', errors='ignore') as f:
+file_content = f.read()
+match_kinda = kinda_status_re.search(file_content)
+match_strict = strict_status_re.search(file_content)
+
+if not match_strict:
+if match_kinda:
+msg = "Malformed Upstream-Status in patch\n%s\nPlease
correct according to %s :\n%s" % (fullpath, guidelines, match_kinda.group(0))
+oe.qa.handle_error(patchtype, msg, d)
+else:
+msg = "Missing Upstream-Status in patch\n%s\nPlease add
according to %s ." % (fullpath, guidelines)
+oe.qa.handle_error(patchtype, msg, d)
oe.qa.exit_if_errors(d)
}
--
2.39.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177205):
https://lists.openembedded.org/g/openembedded-core/message/177205
Mute This Topic: https://lists.openembedded.org/mt/96987598/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [RFC][PATCH] libssh2: Update patch to apply and fix malformed Upstream-Status
* I've noticed this, because patchreview.py reports Malformed Upstream-Status in this one now, but the QA check in insane.bbclass wasn't reporting it before * the reason why insane.bbclass doesn't report it is because: SRC_URI:append:ptest = " file://0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch" doesn't work and probably never did as "ptest" is not an override and patch-status-core checks only the .patch files which are really in SRC_URI. * I've added it directly to SRC_URI and it also didn't apply: http://errors.yoctoproject.org/Errors/Details/689955/ as the "endif" at the end was removed in 1.10.0 version: https://github.com/libssh2/libssh2/commit/ecd6a74e44562797a1e92186ad4a402c5641720e#diff-32103f666ff2fb42b025a47ccf1b959bbcc6db89f217e5943b1de73c81a4f9db after updating the patch to apply I got expected patch-status-core failure: http://errors.yoctoproject.org/Errors/Details/689956/ ERROR: QA Issue: Malformed Upstream-Status in patch TOPDIR/openembedded-core/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch Please correct according to https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status : Upstream-Status: Inappropriate[oe specific] [patch-status-core] * so the mystery is solved, but what should be do with this never-used patch, I think we should just delete it together with SRC_URI:append:ptest, but please Changqing Li confirm it's not needed * it was originally added by Changqing Li in meta-oe with: https://git.openembedded.org/meta-openembedded/commit/?id=d7aa7173405c3b36235af736cd31dbe110708787 then imported to oe-core by Randy MacLeod with: https://git.openembedded.org/openembedded-core/commit/?id=57df134b1be56a688f41851e5ff014dd859c0bc3 Signed-off-by: Martin Jansa --- ...nviroment-to-decide-if-a-test-is-bui.patch | 22 ++- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch index b1204e49eb..eb2658 100644 --- a/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch +++ b/meta/recipes-support/libssh2/files/0001-Don-t-let-host-enviroment-to-decide-if-a-test-is-bui.patch @@ -1,24 +1,23 @@ -From f6abce5ba41a412a247250dcd80e387e53474466 Mon Sep 17 00:00:00 2001 -From: Your Name +From 7ffa1773be8d262bed0f5c8bdcb4dd8f906de095 Mon Sep 17 00:00:00 2001 +From: Changqing Li Date: Mon, 28 Dec 2020 02:08:03 + Subject: [PATCH] Don't let host enviroment to decide if a test is build test ssh2.sh need sshd, for cross compile, we need it on target, so don't use SSHD on host to decide weither to build a test -Upstream-Status: Inappropriate[oe specific] +Upstream-Status: Inappropriate [oe specific] Signed-off-by: Changqing Li - --- - tests/Makefile.am | 6 +- - 1 file changed, 1 insertion(+), 5 deletions(-) + tests/Makefile.am | 4 + 1 file changed, 4 deletions(-) diff --git a/tests/Makefile.am b/tests/Makefile.am -index dc0922f..6cbc35d 100644 +index 27ddc2d..13de8ab 100644 --- a/tests/Makefile.am +++ b/tests/Makefile.am -@@ -1,16 +1,12 @@ +@@ -3,16 +3,12 @@ SUBDIRS = ossfuzz AM_CPPFLAGS = -I$(top_srcdir)/src -I$(top_srcdir)/include -I$(top_builddir)/src LDADD = ../src/libssh2.la @@ -35,10 +34,3 @@ index dc0922f..6cbc35d 100644 check_PROGRAMS = $(ctests) TESTS_ENVIRONMENT = SSHD=$(SSHD) EXEEXT=$(EXEEXT) -@@ -38,4 +34,4 @@ if OPENSSL - # EXTRA_DIST += test_public_key_auth_succeeds_with_correct_encrypted_ed25519_key.c - # EXTRA_DIST += test_public_key_auth_succeeds_with_correct_ed25519_key_from_mem.c - EXTRA_DIST += test_public_key_auth_succeeds_with_correct_rsa_openssh_key.c --endif -\ No newline at end of file -+endif -- 2.39.2 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177204): https://lists.openembedded.org/g/openembedded-core/message/177204 Mute This Topic: https://lists.openembedded.org/mt/96987532/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
There was a parallel conversation on the irc meanwhile; we've concluded that Enrico will look into adding qemu based tests for barebox into oe-selftest like we already have for EFI bootloaders, and there will be a new patchset then. Alex On Wed, 15 Feb 2023 at 16:01, Enrico Jörns wrote: > > Am Mittwoch, dem 15.02.2023 um 15:11 +0100 schrieb Alexander Kanavin: > > On Wed, 15 Feb 2023 at 14:53, Otavio Salvador > > wrote: > > > I think the Barebox inside OE-Core allows a bigger integration and > > > reuse of existing tooling for signing and other classes currently well > > > integrated with U-Boot. For me, a critical point for decision is if > > > Pengutronix will commit to support it. > > > > You should be well aware there's a history of people contributing > > stuff to core and even assigning themselves as maintainers, then > > disappearing. > > If possible I would add my name with the above-mentioned Mailing list to the > maintainers file. > This ensures I am responsible but not the only one reading the mails. > > > And then it falls (largely) on me to keep things > > (barely) going. What happens if ptx withdraws its commitment? Can I > > then send a commit that removes barebox from core? Imagine the angry > > lynch mob that will show up after my head. > > I am fully ok with removing barebox again if we fail maintaining it properly. > > Should I sign this somewhere? ;) > > > Adding things to core is a decision that cannot be easily reversed, so > > I'd rather have barebox in meta-barebox for a while, with any needed > > fixing to classes and infra in core. > > It has been in meta-ptx since 2015 and in meta-barebox since 2016. I would > call that 'a while' :) > > > Best regards, Enrico > > -- > Pengutronix e.K. | Enrico Jörns| > Embedded Linux Consulting & Support| https://www.pengutronix.de/ | > Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | > 31137 Hildesheim, Germany | Fax: +49-5121-206917-9| > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177203): https://lists.openembedded.org/g/openembedded-core/message/177203 Mute This Topic: https://lists.openembedded.org/mt/96956667/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/2] kernel-module-split: make autoload and probeconf distribution specific
Hi Octavio, Otavio Salvador escreveu no dia quarta, 15/02/2023 à(s) 13:25: > Em qua., 15 de fev. de 2023 às 10:01, Jose Quaresma > escreveu: > > > > The modules-load.d [1] - Configure kernel modules to load at boot > > should install their configuration files in /usr/lib/modules-load.d. > > > > The modprobe.d [2] - Configuration directory for modprobe > > should install their configuration files in /lib/modprobe.d > > > > [1] https://www.freedesktop.org/software/systemd/man/modules-load.d.html > > [2] https://www.man7.org/linux/man-pages//man5/modprobe.d.5.html > > > > Signed-off-by: Jose Quaresma > > > Did you validate this using busybox only? Using sysv and busybox need > to be validated as well. > Please drop this patch series because it doesn work with busybox. Looks like busybox don't support other path than /etc: https://git.busybox.net/busybox/tree/modutils/modprobe.c?id=669c40ed8ebf480c95ce36135104e474e361a7e6#n658 So I need to implement this in another way, maybe relocating the files from /etc only when systemd is enabled. Thanks for raising the issue. Jose > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 > -- Best regards, José Quaresma -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177202): https://lists.openembedded.org/g/openembedded-core/message/177202 Mute This Topic: https://lists.openembedded.org/mt/96981851/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Am Mittwoch, dem 15.02.2023 um 15:11 +0100 schrieb Alexander Kanavin: > On Wed, 15 Feb 2023 at 14:53, Otavio Salvador > wrote: > > I think the Barebox inside OE-Core allows a bigger integration and > > reuse of existing tooling for signing and other classes currently well > > integrated with U-Boot. For me, a critical point for decision is if > > Pengutronix will commit to support it. > > You should be well aware there's a history of people contributing > stuff to core and even assigning themselves as maintainers, then > disappearing. If possible I would add my name with the above-mentioned Mailing list to the maintainers file. This ensures I am responsible but not the only one reading the mails. > And then it falls (largely) on me to keep things > (barely) going. What happens if ptx withdraws its commitment? Can I > then send a commit that removes barebox from core? Imagine the angry > lynch mob that will show up after my head. I am fully ok with removing barebox again if we fail maintaining it properly. Should I sign this somewhere? ;) > Adding things to core is a decision that cannot be easily reversed, so > I'd rather have barebox in meta-barebox for a while, with any needed > fixing to classes and infra in core. It has been in meta-ptx since 2015 and in meta-barebox since 2016. I would call that 'a while' :) Best regards, Enrico -- Pengutronix e.K. | Enrico Jörns| Embedded Linux Consulting & Support| https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9| -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177201): https://lists.openembedded.org/g/openembedded-core/message/177201 Mute This Topic: https://lists.openembedded.org/mt/96956667/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Em qua., 15 de fev. de 2023 às 11:11, Alexander Kanavin escreveu: > > On Wed, 15 Feb 2023 at 14:53, Otavio Salvador > wrote: > > I think the Barebox inside OE-Core allows a bigger integration and > > reuse of existing tooling for signing and other classes currently well > > integrated with U-Boot. For me, a critical point for decision is if > > Pengutronix will commit to support it. > > You should be well aware there's a history of people contributing > stuff to core and even assigning themselves as maintainers, then > disappearing. And then it falls (largely) on me to keep things > (barely) going. What happens if ptx withdraws its commitment? Can I > then send a commit that removes barebox from core? Imagine the angry > lynch mob that will show up after my head. Yes. If no one maintains, it should be removed. People will get mad but then we'll see more commitment in future. > Adding things to core is a decision that cannot be easily reversed, so > I'd rather have barebox in meta-barebox for a while, with any needed > fixing to classes and infra in core. Sure but adding things to the core should still be possible and it is a place to foster work sharing and contribution. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177200): https://lists.openembedded.org/g/openembedded-core/message/177200 Mute This Topic: https://lists.openembedded.org/mt/96956667/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 v3 2/2] runqemu: kill qemu if it hangs
qemu doesn't always behave well and can hang too.
kill it with force if it was still alive. Move clean up
commands into cleanup() function.
Signed-off-by: Mikko Rapeli
---
scripts/runqemu | 24 +++-
1 file changed, 15 insertions(+), 9 deletions(-)
v3: moved from qemurunner.py to runqemu SIGTERM and cleanup handling
v2: https://lists.openembedded.org/g/openembedded-core/message/176926
diff --git a/scripts/runqemu b/scripts/runqemu
index def11ea911..cedf4f62ad 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -211,7 +211,7 @@ class BaseConfig(object):
self.mac_slirp = "52:54:00:12:35:"
# pid of the actual qemu process
self.qemu_environ = os.environ.copy()
-self.qemupid = None
+self.qemuprocess = None
# avoid cleanup twice
self.cleaned = False
# Files to cleanup after run
@@ -1531,7 +1531,7 @@ class BaseConfig(object):
for descriptor in self.portlocks.values():
pass_fds.append(descriptor.fileno())
process = subprocess.Popen(cmds, stderr=subprocess.PIPE,
pass_fds=pass_fds, env=self.qemu_environ)
-self.qemupid = process.pid
+self.qemuprocess = process
retcode = process.wait()
if retcode:
if retcode == -signal.SIGTERM:
@@ -1554,6 +1554,15 @@ class BaseConfig(object):
signal.signal(signal.SIGTERM, signal.SIG_IGN)
logger.info("Cleaning up")
+
+if self.qemuprocess:
+try:
+# give it some time to shut down, ignore return values and
output
+self.qemuprocess.send_signal(signal.SIGTERM)
+self.qemuprocess.communicate(timeout=5)
+except subprocess.TimeoutExpired:
+self.qemuprocess.kill()
+
with open('/proc/uptime', 'r') as f:
uptime_seconds = f.readline().split()[0]
logger.info('Host uptime: %s\n' % uptime_seconds)
@@ -1581,6 +1590,9 @@ class BaseConfig(object):
else:
shutil.rmtree(ent)
+# Deliberately ignore the return code of 'tput smam'.
+subprocess.call(["tput", "smam"])
+
self.cleaned = True
def run_bitbake_env(self, mach=None):
@@ -1657,12 +1669,8 @@ def main():
subprocess.check_call([renice, str(os.getpid())])
def sigterm_handler(signum, frame):
-logger.info("SIGTERM received")
-if config.qemupid:
-os.kill(config.qemupid, signal.SIGTERM)
+logger.info("Received signal: %s" % (signum))
config.cleanup()
-# Deliberately ignore the return code of 'tput smam'.
-subprocess.call(["tput", "smam"])
signal.signal(signal.SIGTERM, sigterm_handler)
config.check_args()
@@ -1686,8 +1694,6 @@ def main():
finally:
config.cleanup_cmd()
config.cleanup()
-# Deliberately ignore the return code of 'tput smam'.
-subprocess.call(["tput", "smam"])
if __name__ == "__main__":
sys.exit(main())
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177199):
https://lists.openembedded.org/g/openembedded-core/message/177199
Mute This Topic: https://lists.openembedded.org/mt/96983837/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 v3 1/2] oeqa ssh.py: fix hangs in run()
When qemu machine hangs, the ssh commands done by tests
are not timing out. do_testimage() task has last logs like this:
DEBUG: time: 1673531086.3155053, endtime: 1673531686.315502
The test process is stuck for hours, or for ever if the
executing command or test case did not set a timeout correctly.
The default 300 second timeout is not working when target hangs.
Note that timeout is really a "inactive timeout" since data returned
by the process will reset the timeout.
Make the process stdout non-blocking so read() will always return
right away using os.set_blocking() available in python 3.5 and later.
Then change from python codec reader to plain read() and make
the ssh subprocess stdout non-blocking. Even with select()
making sure the file had input to be read, the codec reader was
trying to find more stuff and blocking for ever when process hangs.
While at it, add a small timeout to read data in larger chunks if
possible. This avoids reading data one or few characters at a time
and makes the debug logs more readable.
close() the stdout file in all cases after read loop is complete.
Then make sure to wait or kill the ssh subprocess in all cases.
Just reading the output stream and receiving EOF there does not mean
that the process exited, and wait() needs a timeout if the process
is hanging. In the end kill the process and return the return value
and captured output utf-8 encoded, just like before these changes.
This fixes ssh run() related deadlocks when a qemu target hangs
completely.
Signed-off-by: Mikko Rapeli
---
meta/lib/oeqa/core/target/ssh.py | 39
1 file changed, 30 insertions(+), 9 deletions(-)
v3: reading raw data in chunks and converting to utf-8 in the end
v2: removed all debug prints,
https://lists.openembedded.org/g/openembedded-core/message/176921
v1: https://lists.openembedded.org/g/openembedded-core/message/176192
diff --git a/meta/lib/oeqa/core/target/ssh.py b/meta/lib/oeqa/core/target/ssh.py
index 2597256c91..51079075b5 100644
--- a/meta/lib/oeqa/core/target/ssh.py
+++ b/meta/lib/oeqa/core/target/ssh.py
@@ -226,27 +226,33 @@ def SSHCall(command, logger, timeout=None, **opts):
def run():
nonlocal output
nonlocal process
+output_raw = b''
starttime = time.time()
process = subprocess.Popen(command, **options)
if timeout:
endtime = starttime + timeout
eof = False
+os.set_blocking(process.stdout.fileno(), False)
while time.time() < endtime and not eof:
-logger.debug('time: %s, endtime: %s' % (time.time(), endtime))
try:
+logger.debug('Waiting for process output: time: %s,
endtime: %s' % (time.time(), endtime))
if select.select([process.stdout], [], [], 5)[0] != []:
-reader = codecs.getreader('utf-8')(process.stdout,
'ignore')
-data = reader.read(1024, 4096)
+# wait a bit for more data, tries to avoid reading
single characters
+time.sleep(0.2)
+data = process.stdout.read()
if not data:
-process.stdout.close()
eof = True
else:
-output += data
-logger.debug('Partial data from SSH call:\n%s' %
data)
+output_raw += data
+# ignore errors to capture as much as possible
+logger.debug('Partial data from SSH call:\n%s' %
data.decode('utf-8', errors='ignore'))
endtime = time.time() + timeout
except InterruptedError:
+logger.debug('InterruptedError')
continue
+process.stdout.close()
+
# process hasn't returned yet
if not eof:
process.terminate()
@@ -254,6 +260,7 @@ def SSHCall(command, logger, timeout=None, **opts):
try:
process.kill()
except OSError:
+logger.debug('OSError when killing process')
pass
endtime = time.time() - starttime
lastline = ("\nProcess killed - no output for %d seconds.
Total"
@@ -262,8 +269,21 @@ def SSHCall(command, logger, timeout=None, **opts):
output += lastline
else:
-output = process.communicate()[0].decode('utf-8', errors='ignore')
-logger.debug('Data from SSH call:\n%s' % output.rstrip())
+output_raw = process.communicate()[0]
+
+output = output_raw.decode('utf-8', errors='ignore')
+logger.debug('Data from SSH call:\n%s' % output.rstrip())
+
+# timout or not, make sure process exits and is not hanging
+if
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
On Wed, 15 Feb 2023 at 14:53, Otavio Salvador wrote: > I think the Barebox inside OE-Core allows a bigger integration and > reuse of existing tooling for signing and other classes currently well > integrated with U-Boot. For me, a critical point for decision is if > Pengutronix will commit to support it. You should be well aware there's a history of people contributing stuff to core and even assigning themselves as maintainers, then disappearing. And then it falls (largely) on me to keep things (barely) going. What happens if ptx withdraws its commitment? Can I then send a commit that removes barebox from core? Imagine the angry lynch mob that will show up after my head. Adding things to core is a decision that cannot be easily reversed, so I'd rather have barebox in meta-barebox for a while, with any needed fixing to classes and infra in core. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177197): https://lists.openembedded.org/g/openembedded-core/message/177197 Mute This Topic: https://lists.openembedded.org/mt/96956667/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Am Mittwoch, dem 15.02.2023 um 10:53 -0300 schrieb Otavio Salvador: > Em qua., 15 de fev. de 2023 às 10:44, Alexander Kanavin > escreveu: > > On Wed, 15 Feb 2023 at 12:22, Otavio Salvador > > wrote: > > > > Fair enough, I'm open to the idea. It would be interesting/useful to > > > > see if anyone else in the community is in favour of this or not. I'm > > > > sure you appreciate why we need to ask the question and why we can't > > > > just add everything! :) > > > > > > > > The community usage does appear to be primarily phytec/ptx. > > > > > > I have used barebox in some projects in the past for multiple customers. > > > It is a solid and > > > commonly used bootloader. I consider U-Boot the industry standard, but > > > Barebox is also widely > > > used, and it makes sense to be part of OE-Core. > > > > I do not quite understand why barebox needs to be specifically in > > oe-core. There's a well maintained layer for it: > > https://github.com/menschel-d/meta-barebox > > so once all those meta-phytec recipes are phased out in favour of > > using that layer, there's no fragmentation. > > I think the Barebox inside OE-Core allows a bigger integration and > reuse of existing tooling for signing and other classes currently well > integrated with U-Boot. Yes, this is another valid point. We have already identified that many things in OE are a bit tailored to u-boot. Having another option (as one has for x86 with grub anyway) could, especially on ARM platforms, inspire to make things more generic and probably also create community synergy effects. What clearly would not be the intention is to tailor things in oe-core for barebox only. > For me, a critical point for decision is if > Pengutronix will commit to support it. Yes, I stated that this is clearly our intention. So support isn't only a one-man show at all ;) Thanks and best regards, Enrico -- Pengutronix e.K. | Enrico Jörns| Embedded Linux Consulting & Support| https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9| -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177196): https://lists.openembedded.org/g/openembedded-core/message/177196 Mute This Topic: https://lists.openembedded.org/mt/96956667/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core][kirkstone 00/27] Pull request (cover letter only)
The following changes since commit cb64ace13db85e143d99627c8803fbb13ba18617:
Fix missing leading whitespace with ':append' (2023-02-01 04:16:52 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/kirkstone-next
Alejandro Hernandez Samaniego (1):
testimage: Fix error message to reflect new syntax
Alexander Kanavin (3):
vulkan-samples: branch rename master -> main
gdk-pixbuf: do not use tools from gdk-pixbuf-native when building
tests
oeqa/qemurunner: do not use Popen.poll() when terminating runqemu with
a signal
Arnout Vandecappelle (1):
python3-pytest: depend on python3-tomli instead of python3-toml
Bruce Ashfield (2):
linux-yocto/5.15: update to v5.15.89
linux-yocto/5.15: update to v5.15.91
Changqing Li (1):
apt: fix do_package_qa failure
Chee Yang Lee (1):
git: upgrade to 2.35.6
Harald Seiler (1):
bootchart2: Fix usrmerge support
Khem Raj (2):
scons: Pass MAXLINELENGTH to scons invocation
scons.bbclass: Make MAXLINELENGTH overridable
Louis Rannou (1):
oeqa/selftest/locales: Add selftest for locale generation/presence
Martin Jansa (1):
meta: remove True option to getVar and getVarFlag calls (again)
Mikko Rapeli (1):
oeqa context.py: fix --target-ip comment to include ssh port number
Mingli Yu (1):
glslang: branch rename master -> main
Narpat Mali (1):
python3-certifi: fix for CVE-2022-23491
Pawel Zalewski (1):
classes/fs-uuid: Fix command output decoding issue
Richard Purdie (3):
kernel/linux-kernel-base: Fix kernel build artefact determinism issues
make-mod-scripts: Ensure kernel build output is deterministic
libc-locale: Fix on target locale generation
Ross Burton (4):
git: ignore CVE-2022-41953
buildtools-tarball: set pkg-config search path
sdkext/cases/devtool: pass a logger to HTTPService
httpserver: add error handler that write to the logger
Ulrich Ölmann (2):
recipe_sanity: fix old override syntax
lsof: fix old override syntax
meta/classes/fs-uuid.bbclass | 2 +-
meta/classes/image.bbclass| 2 +-
meta/classes/kernel.bbclass | 3 -
meta/classes/libc-package.bbclass | 1 +
meta/classes/license_image.bbclass| 2 +-
meta/classes/linux-kernel-base.bbclass| 4 +
meta/classes/recipe_sanity.bbclass| 2 +-
meta/classes/scons.bbclass| 8 +-
meta/classes/testimage.bbclass| 2 +-
meta/lib/oe/package_manager/deb/__init__.py | 8 +-
meta/lib/oeqa/runtime/context.py | 4 +-
meta/lib/oeqa/sdkext/cases/devtool.py | 2 +-
meta/lib/oeqa/selftest/cases/locales.py | 45
meta/lib/oeqa/utils/httpserver.py | 6 +
meta/lib/oeqa/utils/qemurunner.py | 11 +-
meta/recipes-core/meta/buildtools-tarball.bb | 3 +
meta/recipes-devtools/apt/apt_2.4.5.bb| 1 +
.../0001-bootchart2-support-usrmerge.patch| 37 ---
.../bootchart2/bootchart2_0.14.9.bb | 11 +-
.../git/{git_2.35.5.bb => git_2.35.6.bb} | 4 +-
meta/recipes-devtools/go/go_1.17.13.bb| 4 +-
.../python3-certifi/CVE-2022-23491.patch | 230 ++
.../python/python3-certifi_2021.10.8.bb | 2 +
.../python/python3-pytest_7.1.1.bb| 2 +-
meta/recipes-devtools/rust/rust-common.inc| 2 +-
meta/recipes-devtools/rust/rust.inc | 20 +-
meta/recipes-extended/lsof/lsof_4.94.0.bb | 2 +-
.../0001-Add-use_prebuilt_tools-option.patch | 173 -
...w-a-subset-of-tests-in-cross-compile.patch | 66 +
.../gdk-pixbuf/gdk-pixbuf_2.42.10.bb | 17 +-
.../glslang/glslang_1.3.204.1.bb | 2 +-
.../vulkan/vulkan-samples_git.bb | 2 +-
.../linux/linux-yocto-rt_5.15.bb | 6 +-
.../linux/linux-yocto-tiny_5.15.bb| 6 +-
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +-
.../make-mod-scripts/make-mod-scripts_1.0.bb | 2 +-
scripts/contrib/image-manifest| 2 +-
scripts/lib/devtool/menuconfig.py | 2 +-
38 files changed, 432 insertions(+), 292 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/locales.py
delete mode 100644
meta/recipes-devtools/bootchart2/bootchart2/0001-bootchart2-support-usrmerge.patch
rename meta/recipes-devtools/git/{git_2.35.5.bb => git_2.35.6.bb} (97%)
create mode 100644
meta/recipes-devtools/python/python3-certifi/CVE-2022-23491.patch
delete mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/0001-Add-use_prebuilt_tools-option.patch
create mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/0001-meson.build-allow-a-subset-of-tests-in-cross-compile.patch
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177195):
[OE-core][langdale 00/28] Pull request (cover letter only)
The following changes since commit ab39d244cb844c9d183296945a095c17fdfef29e:
Fix missing leading whitespace with ':append' (2023-01-31 13:15:53 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/langdale-next
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=stable/langdale-next
Alejandro Hernandez Samaniego (1):
testimage: Fix error message to reflect new syntax
Alexander Kanavin (3):
vulkan-samples: branch rename master -> main
gdk-pixbuf: do not use tools from gdk-pixbuf-native when building
tests
oeqa/qemurunner: do not use Popen.poll() when terminating runqemu with
a signal
Arnout Vandecappelle (1):
python3-pytest: depend on python3-tomli instead of python3-toml
Bruce Ashfield (2):
linux-yocto/5.15: update to v5.15.89
linux-yocto/5.15: update to v5.15.91
Changqing Li (1):
apt: fix do_package_qa failure
Chee Yang Lee (1):
git: upgrade to 2.37.5
Harald Seiler (1):
bootchart2: Fix usrmerge support
Khem Raj (2):
scons: Pass MAXLINELENGTH to scons invocation
scons.bbclass: Make MAXLINELENGTH overridable
Louis Rannou (1):
oeqa/selftest/locales: Add selftest for locale generation/presence
Martin Jansa (1):
meta: remove True option to getVar and getVarFlag calls (again)
Mikko Rapeli (1):
oeqa context.py: fix --target-ip comment to include ssh port number
Mingli Yu (1):
glslang: branch rename master -> main
Pawel Zalewski (1):
classes/fs-uuid: Fix command output decoding issue
Richard Purdie (4):
kernel/linux-kernel-base: Fix kernel build artefact determinism issues
make-mod-scripts: Ensure kernel build output is deterministic
perf: Enable debug/source packaging
libc-locale: Fix on target locale generation
Ross Burton (4):
git: ignore CVE-2022-41953
buildtools-tarball: set pkg-config search path
sdkext/cases/devtool: pass a logger to HTTPService
httpserver: add error handler that write to the logger
Tobias Hagelborn (1):
sstate.bbclass: Fetch non-existing local .sig files if needed
Ulrich Ölmann (2):
recipe_sanity: fix old override syntax
lsof: fix old override syntax
meta/classes-global/sstate.bbclass| 5 +-
meta/classes-recipe/fs-uuid.bbclass | 2 +-
meta/classes-recipe/image.bbclass | 2 +-
meta/classes-recipe/kernel.bbclass| 3 -
meta/classes-recipe/libc-package.bbclass | 1 +
meta/classes-recipe/license_image.bbclass | 2 +-
meta/classes-recipe/linux-kernel-base.bbclass | 4 +
.../classes-recipe/rust-target-config.bbclass | 2 +-
meta/classes-recipe/scons.bbclass | 8 +-
meta/classes-recipe/testimage.bbclass | 2 +-
meta/classes/recipe_sanity.bbclass| 2 +-
meta/lib/oe/package_manager/deb/__init__.py | 8 +-
meta/lib/oeqa/runtime/context.py | 4 +-
meta/lib/oeqa/sdkext/cases/devtool.py | 2 +-
meta/lib/oeqa/selftest/cases/locales.py | 45 +
meta/lib/oeqa/utils/httpserver.py | 6 +
meta/lib/oeqa/utils/qemurunner.py | 11 +-
meta/recipes-core/meta/buildtools-tarball.bb | 3 +
meta/recipes-devtools/apt/apt_2.4.5.bb| 1 +
.../0001-bootchart2-support-usrmerge.patch| 37
.../bootchart2/bootchart2_0.14.9.bb | 11 +-
.../git/{git_2.37.4.bb => git_2.37.5.bb} | 4 +-
meta/recipes-devtools/go/go_1.19.4.bb | 4 +-
.../python/python3-pytest_7.1.3.bb| 2 +-
meta/recipes-devtools/rust/rust.inc | 22 +--
meta/recipes-extended/lsof/lsof_4.95.0.bb | 2 +-
.../0001-Add-use_prebuilt_tools-option.patch | 173 --
...w-a-subset-of-tests-in-cross-compile.patch | 66 +++
.../gdk-pixbuf/gdk-pixbuf_2.42.10.bb | 17 +-
.../glslang/glslang_1.3.216.0.bb | 2 +-
.../vulkan/vulkan-samples_git.bb | 2 +-
.../linux/linux-yocto-rt_5.15.bb | 6 +-
.../linux/linux-yocto-tiny_5.15.bb| 6 +-
meta/recipes-kernel/linux/linux-yocto_5.15.bb | 26 +--
.../make-mod-scripts/make-mod-scripts_1.0.bb | 2 +-
meta/recipes-kernel/perf/perf.bb | 14 +-
scripts/contrib/image-manifest| 2 +-
scripts/lib/devtool/menuconfig.py | 2 +-
38 files changed, 216 insertions(+), 297 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/locales.py
delete mode 100644
meta/recipes-devtools/bootchart2/bootchart2/0001-bootchart2-support-usrmerge.patch
rename meta/recipes-devtools/git/{git_2.37.4.bb => git_2.37.5.bb} (97%)
delete mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/0001-Add-use_prebuilt_tools-option.patch
create mode 100644
meta/recipes-gnome/gdk-pixbuf/gdk-pixbuf/0001-meson.build-allow-a-subset-of-tests-in-cross-compile.patch
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177194):
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Em qua., 15 de fev. de 2023 às 10:44, Alexander Kanavin escreveu: > On Wed, 15 Feb 2023 at 12:22, Otavio Salvador > wrote: > >> Fair enough, I'm open to the idea. It would be interesting/useful to > >> see if anyone else in the community is in favour of this or not. I'm > >> sure you appreciate why we need to ask the question and why we can't > >> just add everything! :) > >> > >> The community usage does appear to be primarily phytec/ptx. > > > > I have used barebox in some projects in the past for multiple customers. It > > is a solid and commonly used bootloader. I consider U-Boot the industry > > standard, but Barebox is also widely used, and it makes sense to be part of > > OE-Core. > > I do not quite understand why barebox needs to be specifically in > oe-core. There's a well maintained layer for it: > https://github.com/menschel-d/meta-barebox > so once all those meta-phytec recipes are phased out in favour of > using that layer, there's no fragmentation. I think the Barebox inside OE-Core allows a bigger integration and reuse of existing tooling for signing and other classes currently well integrated with U-Boot. For me, a critical point for decision is if Pengutronix will commit to support it. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177193): https://lists.openembedded.org/g/openembedded-core/message/177193 Mute This Topic: https://lists.openembedded.org/mt/96956667/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Am Mittwoch, dem 15.02.2023 um 14:43 +0100 schrieb Alexander Kanavin: > On Wed, 15 Feb 2023 at 12:22, Otavio Salvador > wrote: > > > Fair enough, I'm open to the idea. It would be interesting/useful to > > > see if anyone else in the community is in favour of this or not. I'm > > > sure you appreciate why we need to ask the question and why we can't > > > just add everything! :) > > > > > > The community usage does appear to be primarily phytec/ptx. > > > > > > I have used barebox in some projects in the past for multiple customers. It > > is a solid and > > commonly used bootloader. I consider U-Boot the industry standard, but > > Barebox is also widely > > used, and it makes sense to be part of OE-Core. > > I do not quite understand why barebox needs to be specifically in > oe-core. There's a well maintained layer for it: > https://github.com/menschel-d/meta-barebox > so once all those meta-phytec recipes are phased out in favour of > using that layer, there's no fragmentation. > You forgot to mention https://github.com/pengutronix/meta-ptx/tree/master/recipes-bsp/barebox I did never say that fragmentation is my only motivation. Regards, Enrico -- Pengutronix e.K. | Enrico Jörns| Embedded Linux Consulting & Support| https://www.pengutronix.de/ | Steuerwalder Str. 21 | Phone: +49-5121-206917-180 | 31137 Hildesheim, Germany | Fax: +49-5121-206917-9| -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177192): https://lists.openembedded.org/g/openembedded-core/message/177192 Mute This Topic: https://lists.openembedded.org/mt/96956667/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
On Wed, 15 Feb 2023 at 12:22, Otavio Salvador wrote: >> Fair enough, I'm open to the idea. It would be interesting/useful to >> see if anyone else in the community is in favour of this or not. I'm >> sure you appreciate why we need to ask the question and why we can't >> just add everything! :) >> >> The community usage does appear to be primarily phytec/ptx. > > > I have used barebox in some projects in the past for multiple customers. It > is a solid and commonly used bootloader. I consider U-Boot the industry > standard, but Barebox is also widely used, and it makes sense to be part of > OE-Core. I do not quite understand why barebox needs to be specifically in oe-core. There's a well maintained layer for it: https://github.com/menschel-d/meta-barebox so once all those meta-phytec recipes are phased out in favour of using that layer, there's no fragmentation. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177191): https://lists.openembedded.org/g/openembedded-core/message/177191 Mute This Topic: https://lists.openembedded.org/mt/96956667/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: provide support for packing development and testing tools
On Wed, 15 Feb 2023 at 14:25, Dmitry Baryshkov wrote:
> +# dependencies for tools. libconfig is optional, it is a part of meta-oe so
> it needs special treatment
> +TOOLS_DEPS_FREEDRENO_LIBCONFIG = "
> ${@bb.utils.contains('BBFILE_COLLECTIONS', 'openembedded-layer', 'libconfig',
> '', d)} "
Oe-core cannot build things differently depending on whether other
layers are present.
On the other hand, it is fine to refer to dependencies from other
layers if the corresponding options are disabled by default. You
probably want to have the option for freedreno tools separate from the
option for freedreno driver.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177190):
https://lists.openembedded.org/g/openembedded-core/message/177190
Mute This Topic: https://lists.openembedded.org/mt/96982252/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/2] kernel-module-split: make autoload and probeconf distribution specific
Em qua., 15 de fev. de 2023 às 10:01, Jose Quaresma escreveu: > > The modules-load.d [1] - Configure kernel modules to load at boot > should install their configuration files in /usr/lib/modules-load.d. > > The modprobe.d [2] - Configuration directory for modprobe > should install their configuration files in /lib/modprobe.d > > [1] https://www.freedesktop.org/software/systemd/man/modules-load.d.html > [2] https://www.man7.org/linux/man-pages//man5/modprobe.d.5.html > > Signed-off-by: Jose Quaresma Did you validate this using busybox only? Using sysv and busybox need to be validated as well. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177189): https://lists.openembedded.org/g/openembedded-core/message/177189 Mute This Topic: https://lists.openembedded.org/mt/96981851/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: provide support for packing development and testing tools
Mesa contains several optional tools that can be useful for application
and driver developers. Add a packageconfig option to build a mesa-tools
package containing relevant programs.
Signed-off-by: Dmitry Baryshkov
---
meta/recipes-graphics/mesa/mesa.inc | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-graphics/mesa/mesa.inc
b/meta/recipes-graphics/mesa/mesa.inc
index 0a3dc1dd62a0..96e4a1959332 100644
--- a/meta/recipes-graphics/mesa/mesa.inc
+++ b/meta/recipes-graphics/mesa/mesa.inc
@@ -107,6 +107,20 @@ VULKAN_DRIVERS:append
="${@bb.utils.contains('PACKAGECONFIG', 'freedreno', ',fre
VULKAN_DRIVERS:append ="${@bb.utils.contains('PACKAGECONFIG', 'broadcom',
',broadcom', '', d)}"
PACKAGECONFIG[vulkan] =
"-Dvulkan-drivers=${@strip_comma('${VULKAN_DRIVERS}')},
-Dvulkan-drivers='',glslang-native vulkan-loader vulkan-headers"
+# mesa development and testing tools support, per driver
+TOOLS = ""
+TOOLS_DEPS = ""
+TOOLS:append = "${@bb.utils.contains('PACKAGECONFIG', 'etnaviv', ',etnaviv',
'', d)}"
+TOOLS:append = "${@bb.utils.contains('PACKAGECONFIG', 'freedreno',
',freedreno', '', d)}"
+TOOLS:append = "${@bb.utils.contains('PACKAGECONFIG', 'lima', ',lima', '', d)}"
+TOOLS:append = "${@bb.utils.contains('PACKAGECONFIG', 'panfrost', ',panfrost',
'', d)}"
+
+# dependencies for tools. libconfig is optional, it is a part of meta-oe so it
needs special treatment
+TOOLS_DEPS_FREEDRENO_LIBCONFIG = " ${@bb.utils.contains('BBFILE_COLLECTIONS',
'openembedded-layer', 'libconfig', '', d)} "
+TOOLS_DEPS:append = "${@bb.utils.contains('PACKAGECONFIG', 'freedreno', '
ncurses libxml2 ${TOOLS_DEPS_FREEDRENO_LIBCONFIG} ', '', d)}"
+
+PACKAGECONFIG[tools] = "-Dtools=${@strip_comma('${TOOLS}')}, -Dtools='',
${TOOLS_DEPS}"
+
PACKAGECONFIG[opengl] = "-Dopengl=true, -Dopengl=false"
PACKAGECONFIG[glvnd] = "-Dglvnd=true, -Dglvnd=false, libglvnd"
@@ -211,7 +225,7 @@ PACKAGES =+ "libegl-mesa libegl-mesa-dev \
libopencl-mesa libopencl-mesa-dev \
libxatracker libxatracker-dev \
mesa-megadriver mesa-vulkan-drivers \
- mesa-vdpau-drivers \
+ mesa-vdpau-drivers mesa-tools \
"
do_install:append () {
@@ -323,6 +337,9 @@ FILES:libosmesa-dev = "${libdir}/libOSMesa.*
${includedir}/GL/osmesa.h ${libdir}
FILES:libxatracker-dev = "${libdir}/libxatracker.so ${libdir}/libxatracker.la \
${includedir}/xa_tracker.h
${includedir}/xa_composite.h ${includedir}/xa_context.h \
${libdir}/pkgconfig/xatracker.pc"
+# catch all to get all the tools and data
+FILES:${PN}-tools = "${bindir} ${datadir}"
+ALLOW_EMPTY:${PN}-tools = "1"
# Fix upgrade path from mesa to mesa-megadriver
RREPLACES:mesa-megadriver = "mesa"
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177188):
https://lists.openembedded.org/g/openembedded-core/message/177188
Mute This Topic: https://lists.openembedded.org/mt/96982252/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] kernel: autoload and probeconf are handled by kernel-module-split
Signed-off-by: Jose Quaresma
---
meta/classes-recipe/kernel.bbclass | 2 --
1 file changed, 2 deletions(-)
diff --git a/meta/classes-recipe/kernel.bbclass
b/meta/classes-recipe/kernel.bbclass
index d327cd6888..5718600eee 100644
--- a/meta/classes-recipe/kernel.bbclass
+++ b/meta/classes-recipe/kernel.bbclass
@@ -478,8 +478,6 @@ kernel_do_install() {
install -m 0644 .config
${D}/${KERNEL_IMAGEDEST}/config-${KERNEL_VERSION}
install -m 0644 vmlinux
${D}/${KERNEL_IMAGEDEST}/vmlinux-${KERNEL_VERSION}
[ -e Module.symvers ] && install -m 0644 Module.symvers
${D}/${KERNEL_IMAGEDEST}/Module.symvers-${KERNEL_VERSION}
- install -d ${D}${sysconfdir}/modules-load.d
- install -d ${D}${sysconfdir}/modprobe.d
}
# Must be ran no earlier than after do_kernel_checkout or else Makefile won't
be in ${S}/Makefile
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177187):
https://lists.openembedded.org/g/openembedded-core/message/177187
Mute This Topic: https://lists.openembedded.org/mt/96981853/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] kernel-module-split: make autoload and probeconf distribution specific
The modules-load.d [1] - Configure kernel modules to load at boot
should install their configuration files in /usr/lib/modules-load.d.
The modprobe.d [2] - Configuration directory for modprobe
should install their configuration files in /lib/modprobe.d
[1] https://www.freedesktop.org/software/systemd/man/modules-load.d.html
[2] https://www.man7.org/linux/man-pages//man5/modprobe.d.5.html
Signed-off-by: Jose Quaresma
---
.../kernel-module-split.bbclass | 30 +--
1 file changed, 14 insertions(+), 16 deletions(-)
diff --git a/meta/classes-recipe/kernel-module-split.bbclass
b/meta/classes-recipe/kernel-module-split.bbclass
index 50882c31a7..b70650888a 100644
--- a/meta/classes-recipe/kernel-module-split.bbclass
+++ b/meta/classes-recipe/kernel-module-split.bbclass
@@ -31,7 +31,8 @@ fi
PACKAGE_WRITE_DEPS += "kmod-native depmodwrapper-cross"
do_install:append() {
- install -d ${D}${sysconfdir}/modules-load.d/
${D}${sysconfdir}/modprobe.d/
+ install -d ${D}${libdir}/modules-load.d
+ install -d ${D}${nonarch_base_libdir}/modprobe.d
}
KERNEL_SPLIT_MODULES ?= "1"
@@ -93,8 +94,9 @@ python split_kernel_module_packages () {
dvar = d.getVar('PKGD')
-# If autoloading is requested, output /etc/modules-load.d/.conf
and append
+# If autoloading is requested, output
${libdir}/modules-load.d/.conf and append
# appropriate modprobe commands to the postinst
+autoloadpath = '%s/modules-load.d/%s.conf' % (d.getVar('libdir'),
basename)
autoloadlist = (d.getVar("KERNEL_MODULE_AUTOLOAD") or "").split()
autoload = d.getVar('module_autoload_%s' % basename)
if autoload and autoload == basename:
@@ -102,8 +104,7 @@ python split_kernel_module_packages () {
if autoload and basename not in autoloadlist:
bb.warn("module_autoload_%s is defined but '%s' isn't included in
KERNEL_MODULE_AUTOLOAD, please add it there" % (basename, basename))
if basename in autoloadlist:
-name = '%s/etc/modules-load.d/%s.conf' % (dvar, basename)
-f = open(name, 'w')
+f = open("%s%s" % (dvar, autoloadpath), 'w')
if autoload:
for m in autoload.split():
f.write('%s\n' % m)
@@ -117,23 +118,19 @@ python split_kernel_module_packages () {
d.setVar('pkg_postinst:%s' % pkg, postinst)
# Write out any modconf fragment
+modconfpath = '%s/modprobe.d/%s.conf' %
(d.getVar('nonarch_base_libdir'), basename)
modconflist = (d.getVar("KERNEL_MODULE_PROBECONF") or "").split()
modconf = d.getVar('module_conf_%s' % basename)
if modconf and basename in modconflist:
-name = '%s/etc/modprobe.d/%s.conf' % (dvar, basename)
-f = open(name, 'w')
+f = open("%s%s" % (dvar, modconfpath), 'w')
f.write("%s\n" % modconf)
f.close()
elif modconf:
bb.error("Please ensure module %s is listed in
KERNEL_MODULE_PROBECONF since module_conf_%s is set" % (basename, basename))
-files = d.getVar('FILES:%s' % pkg)
-files = "%s /etc/modules-load.d/%s.conf /etc/modprobe.d/%s.conf" %
(files, basename, basename)
-d.setVar('FILES:%s' % pkg, files)
-
-conffiles = d.getVar('CONFFILES:%s' % pkg)
-conffiles = "%s /etc/modules-load.d/%s.conf /etc/modprobe.d/%s.conf" %
(conffiles, basename, basename)
-d.setVar('CONFFILES:%s' % pkg, conffiles)
+appendfiles = " %s %s" % (autoloadpath, modconfpath)
+d.appendVar('FILES:%s' % pkg, appendfiles)
+d.appendVar('CONFFILES:%s' % pkg, appendfiles)
if "description" in vals:
old_desc = d.getVar('DESCRIPTION:' + pkg) or ""
@@ -167,10 +164,11 @@ python split_kernel_module_packages () {
splitmods = d.getVar('KERNEL_SPLIT_MODULES')
postinst = d.getVar('pkg_postinst:modules')
postrm = d.getVar('pkg_postrm:modules')
+nonarch_base_libdir = d.getVar("nonarch_base_libdir")
+libdir = d.getVar("libdir")
if splitmods != '1':
-etcdir = d.getVar('sysconfdir')
-d.appendVar('FILES:' + metapkg, '%s/modules-load.d/ %s/modprobe.d/
%s/modules/' % (etcdir, etcdir, d.getVar("nonarch_base_libdir")))
+d.appendVar('FILES:' + metapkg, '%s/modules-load.d/ %s/modprobe.d/
%s/modules/' % (libdir, nonarch_base_libdir, nonarch_base_libdir))
d.appendVar('pkg_postinst:%s' % metapkg, postinst)
d.prependVar('pkg_postrm:%s' % metapkg, postrm);
return
@@ -189,7 +187,7 @@ python split_kernel_module_packages () {
# avoid warnings. removedirs only raises an OSError if an empty
# directory cannot be removed.
dvar = d.getVar('PKGD')
-for dir in ["%s/etc/modprobe.d" % (dvar), "%s/etc/modules-load.d" %
(dvar), "%s/etc" % (dvar)]:
+for dir in ["%s%s/modprobe.d" % (dvar, nonarch_base_libdir),
"%s%s/modules-load.d" % (dvar,
Re: [OE-core][PATCH 1/2] gobject-introspection: check for GI_DATA_ENABLED
On Wed, 15 Feb 2023 at 10:39, Petr Kubizňák - 2N wrote: > > The way I read gtk4 and graphene source code, what the recipe claims > > is not true: you can disable introspection in graphene, and it would > > still build and install graphene-gobject.pc which is what gtk4 is > > looking for. If the needed piece is not installed, then you need to > > get to the bottom of why, e.g. specific source code lines where that > > decision is made. > > That's not really true. If no patches are applied and g-i is disabled, > graphene fails in do_compile: > > [75/75] > /home/kubiznak/projects/poky2/build/tmp/work/core2-64-poky-linux/graphene/1.10.8-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper > src/Graphene-1.0.gir --output src/Graphene-1.0.typelib > --includedir=/usr/share/gir-1.0 > FAILED: src/Graphene-1.0.typelib > /home/kubiznak/projects/poky2/build/tmp/work/core2-64-poky-linux/graphene/1.10.8-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper > src/Graphene-1.0.gir --output src/Graphene-1.0.typelib > --includedir=/usr/share/gir-1.0 > Could not find GIR file 'GObject-2.0.gir'; check XDG_DATA_DIRS or use > --includedir > error parsing file src/Graphene-1.0.gir: Failed to parse included gir > GObject-2.0 I replicated this locally. graphene isn't being correctly configured when introspection is disabled globally, and the attached patch is correct. Can you resend it as a proper oe-core submission? I haven't seen webkit fail like that before, and it does not fail for me locally this way. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177185): https://lists.openembedded.org/g/openembedded-core/message/177185 Mute This Topic: https://lists.openembedded.org/mt/96048399/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [OE-core] [PATCH 1/2] barebox: add initial support
Hello Richard, Em ter., 14 de fev. de 2023 às 10:56, Richard Purdie < richard.pur...@linuxfoundation.org> escreveu: > Fair enough, I'm open to the idea. It would be interesting/useful to > see if anyone else in the community is in favour of this or not. I'm > sure you appreciate why we need to ask the question and why we can't > just add everything! :) > > The community usage does appear to be primarily phytec/ptx. > I have used barebox in some projects in the past for multiple customers. It is a solid and commonly used bootloader. I consider U-Boot the industry standard, but Barebox is also widely used, and it makes sense to be part of OE-Core. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177184): https://lists.openembedded.org/g/openembedded-core/message/177184 Mute This Topic: https://lists.openembedded.org/mt/96956667/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 v2 1/1] create-spdx-2.2: Add support for custom Annotations
V1 got merged, can you rebase ? :)
On 14/02/2023 09:21:56-0800, Saul Wold wrote:
> This change adds a new variable to track which recipe variables
> are added as SPDX Annotations.
>
> Usage: add SPDX_CUSTOM_ANNOTATION_VARS =
>
> The recipe spdx json will contain an annotation stanza that looks
> something like this:
>
> "annotations": [
> {
> "annotationDate": "2023-02-13T19:44:20Z",
> "annotationType": "OTHER",
> "annotator": "Tool: oe-spdx-creator - 1.0",
> "comment": "CUSTOM_VARIABLE=some value or string"
> },
>
> Signed-off-by: Saul Wold
> ---
> meta/classes/create-spdx-2.2.bbclass | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/create-spdx-2.2.bbclass
> b/meta/classes/create-spdx-2.2.bbclass
> index f0513af083b..bdc2e2c91e7 100644
> --- a/meta/classes/create-spdx-2.2.bbclass
> +++ b/meta/classes/create-spdx-2.2.bbclass
> @@ -30,6 +30,8 @@ SPDX_PRETTY ??= "0"
>
> SPDX_LICENSES ??= "${COREBASE}/meta/files/spdx-licenses.json"
>
> +SPDX_CUSTOM_ANNOTATION_VARS ??= ""
> +
> SPDX_ORG ??= "OpenEmbedded ()"
> SPDX_SUPPLIER ??= "Organization: ${SPDX_ORG}"
> SPDX_SUPPLIER[doc] = "The SPDX PackageSupplier field for SPDX packages
> created from \
> @@ -402,7 +404,6 @@ def collect_dep_sources(d, dep_recipes):
>
> return sources
>
> -
> python do_create_spdx() {
> from datetime import datetime, timezone
> import oe.sbom
> @@ -479,6 +480,11 @@ python do_create_spdx() {
> if description:
> recipe.description = description
>
> +if d.getVar("SPDX_CUSTOM_ANNOTATION_VARS"):
> +for var in d.getVar("SPDX_CUSTOM_ANNOTATION_VARS").split():
> +if d.getVar(var):
> +recipe.annotations.append(create_annotation(d, var + "=" +
> d.getVar(var)))
> +
> # Some CVEs may be patched during the build process without incrementing
> the version number,
> # so querying for CVEs based on the CPE id can lead to false positives.
> To account for this,
> # save the CVEs fixed by patches to source information field in the SPDX.
> --
> 2.25.1
>
>
>
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#177183):
https://lists.openembedded.org/g/openembedded-core/message/177183
Mute This Topic: https://lists.openembedded.org/mt/96964900/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/2] gobject-introspection: check for GI_DATA_ENABLED
Hi Alex, May I kindly ask you for your opinion? Thank you, Petr From: openembedded-core@lists.openembedded.org on behalf of Petr Kubizňák - 2N Sent: Wednesday, February 1, 2023 5:04 PM To: openembedded-core@lists.openembedded.org Subject: Re: [OE-core][PATCH 1/2] gobject-introspection: check for GI_DATA_ENABLED From: Alexander Kanavin Sent: Tuesday, January 17, 2023 5:50 PM To: Petr Kubizňák - 2N Cc: openembedded-core@lists.openembedded.org Subject: Re: [OE-core][PATCH 1/2] gobject-introspection: check for GI_DATA_ENABLED > The way I read gtk4 and graphene source code, what the recipe claims > is not true: you can disable introspection in graphene, and it would > still build and install graphene-gobject.pc which is what gtk4 is > looking for. If the needed piece is not installed, then you need to > get to the bottom of why, e.g. specific source code lines where that > decision is made. That's not really true. If no patches are applied and g-i is disabled, graphene fails in do_compile: [75/75] /home/kubiznak/projects/poky2/build/tmp/work/core2-64-poky-linux/graphene/1.10.8-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper src/Graphene-1.0.gir --output src/Graphene-1.0.typelib --includedir=/usr/share/gir-1.0 FAILED: src/Graphene-1.0.typelib /home/kubiznak/projects/poky2/build/tmp/work/core2-64-poky-linux/graphene/1.10.8-r0/recipe-sysroot/usr/bin/g-ir-compiler-wrapper src/Graphene-1.0.gir --output src/Graphene-1.0.typelib --includedir=/usr/share/gir-1.0 Could not find GIR file 'GObject-2.0.gir'; check XDG_DATA_DIRS or use --includedir error parsing file src/Graphene-1.0.gir: Failed to parse included gir GObject-2.0 If the attached patch is applied, graphene builds and yes, graphene-gobject-1.0.pc is then created, too. (Maybe this is the first patch to send individually?) In that case, gtk4 builds fine. Anyway, webkitgtk fails in do_compile, with a failure which I worry I'm not able to resolve (see the attached tail of the log, full log is ~50MiB). Petr -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177182): https://lists.openembedded.org/g/openembedded-core/message/177182 Mute This Topic: https://lists.openembedded.org/mt/96048399/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
