Re: Kernel 6.5 ttyS1 hang with qemu (was Re: [OE-core] Summary of the remaining 6.5 kernel serial issue (and 6.5 summary)

Hi, Thanks a lot Paul! Updating linux-serial that bisection shows 84a9582fd203 serial: core: Start managing serial controllers to enable runtime PM caused this regression in ttyS1 functionality with qemu. Lots of more details below. Cheers, -Mikko On Fri, Oct 13, 2023 at 11:15:35AM -0400,

Re: [OE-Core][PATCH v14 03/11] sstate.bbclass: override tar with tar-native

Dnia niedziela, 15 października 2023 20:26:49 CEST Richard Purdie pisze: > On Sun, 2023-10-15 at 16:57 +0200, Piotr Łobacz wrote: > > Due to the bugs > > https://eur04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsavanna > >

[OE-core] Recent failures on master depmodwrapper-cross

Running a number of builds recently, a small number of them failed. Note we ran about 20 builds and only 3 failed like this, the others completed. I'm wondering if maybe there is a race condition with the new code? Error: ERROR: depmodwrapper-cross-1.0-r0 do_patch: Error executing a python

Re: Kernel 6.5 ttyS1 hang with qemu (was Re: [OE-core] Summary of the remaining 6.5 kernel serial issue (and 6.5 summary)

On Sun, 2023-10-15 at 17:31 +0200, Greg Kroah-Hartman wrote: > On Sun, Oct 15, 2023 at 01:29:48PM +0100, Richard Purdie wrote: > > On Sat, 2023-10-14 at 12:13 +0100, Richard Purdie via > > lists.openembedded.org wrote: > > > On Sat, 2023-10-14 at 10:41 +0100, Richard Purdie wrote: > > > > Brief

[OE-core] [AUH] linux-firmware: upgrading to 20230919 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *linux-firmware* to *20230919* has Succeeded. Next steps: - apply the patch: git am 0001-linux-firmware-upgrade-20230804-20230919.patch - check the changes to upstream

[OE-core] [AUH] vte: upgrading to 0.74.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vte* to *0.74.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe vte failed. NOTE: Starting bitbake server... NOTE: Reconnecting to

[OE-core] [AUH] librsvg: upgrading to 2.57.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *librsvg* to *2.57.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-librsvg-upgrade-2.56.3-2.57.0.patch

[OE-core] [AUH] hwlatdetect: upgrading to 2.6 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *hwlatdetect* to *2.6* has Succeeded. Next steps: - apply the patch: git am 0001-hwlatdetect-upgrade-2.5-2.6.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] bmap-tools: upgrading to 3.7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *bmap-tools* to *3.7* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade bmap-tools -V 3.7 -S

[OE-core] [AUH] libical: upgrading to 3.0.17 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libical* to *3.0.17* has Succeeded. Next steps: - apply the patch: git am 0001-libical-upgrade-3.0.16-3.0.17.patch - check the changes to upstream patches and summarize

[OE-core] [AUH] libva: upgrading to 2.20.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libva* to *2.20.0* has Succeeded. Next steps: - apply the patch: git am 0001-libva-upgrade-2.19.0-2.20.0.patch - check the changes to upstream patches and summarize them in

[OE-core] [AUH] rt-tests: upgrading to 2.6 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rt-tests* to *2.6* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rt-tests failed. NOTE: Starting bitbake server... Loading

[OE-core] [AUH] virglrenderer: upgrading to 1.0.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *virglrenderer* to *1.0.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] cups: upgrading to 2.4.7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cups* to *2.4.7* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-cups-upgrade-2.4.6-2.4.7.patch - check

[OE-core] [AUH] shaderc: upgrading to 2023.7 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shaderc* to *2023.7* has Succeeded. Next steps: - apply the patch: git am 0001-shaderc-upgrade-2023.6-2023.7.patch - check the changes to upstream patches and summarize

[OE-core] [AUH] libva-initial: upgrading to 2.20.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.20.0* has Failed (devtool error). Detailed error information: The following devtool command failed: finish -f libva-initial

[OE-core] [AUH] libxkbcommon: upgrading to 1.6.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libxkbcommon* to *1.6.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] vulkan-samples: upgrading to 26eb94f79f9c2377cbaa28db2fbd7dd6efb55ffe FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *26eb94f79f9c2377cbaa28db2fbd7dd6efb55ffe* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] rust: upgrading to 1.73.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust* to *1.73.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust failed. NOTE: Starting bitbake server... NOTE: Reconnecting to

[OE-core] [AUH] man-db: upgrading to 2.12.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *man-db* to *2.12.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade man-db -V 2.12.0 NOTE: Starting bitbake server... NOTE:

[OE-core] [AUH] stress-ng: upgrading to 0.17.00 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *stress-ng* to *0.17.00* has Succeeded. Next steps: - apply the patch: git am 0001-stress-ng-upgrade-0.16.05-0.17.00.patch - check the changes to upstream patches and

[OE-core] [AUH] libxrandr: 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 *libxrandr* to *1.5.4* has Succeeded. Next steps: - apply the patch: git am 0001-libxrandr-upgrade-1.5.3-1.5.4.patch - check the changes to upstream patches and summarize

[OE-core] [AUH] waffle: upgrading to 1.8.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *waffle* to *1.8.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe waffle failed. NOTE: Starting bitbake server... NOTE: Reconnecting

[OE-core] [AUH] epiphany: upgrading to 45.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *epiphany* to *45.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-epiphany-upgrade-44.6-45.0.patch -

[OE-core] [AUH] rust-llvm: upgrading to 1.73.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust-llvm* to *1.73.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust-llvm failed. NOTE: Starting bitbake server... NOTE:

[OE-core] [AUH] libstd-rs: upgrading to 1.73.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libstd-rs* to *1.73.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libstd-rs failed. NOTE: Starting bitbake server... NOTE:

[OE-core] [AUH] lighttpd: upgrading to 1.4.72 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *lighttpd* to *1.4.72* has Succeeded. Next steps: - apply the patch: git am 0001-lighttpd-upgrade-1.4.71-1.4.72.patch - check the changes to upstream patches and summarize

[OE-core] [AUH] libnsl2: upgrading to 2.0.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libnsl2* to *2.0.1* has Succeeded. Next steps: - apply the patch: git am 0001-libnsl2-upgrade-2.0.0-2.0.1.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] cargo: upgrading to 1.73.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cargo* to *1.73.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe cargo failed. NOTE: Starting bitbake server... NOTE: Reconnecting

[OE-core] [AUH] shadow: upgrading to 4.14.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shadow* to *4.14.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe shadow failed. NOTE: Starting bitbake server... NOTE: Reconnecting

[OE-core] [AUH] iptables: upgrading to 1.8.10 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *iptables* to *1.8.10* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe iptables failed. NOTE: Starting bitbake server... NOTE:

[OE-core] [AUH] cronie: 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 *cronie* to *1.7.0* has Succeeded. Next steps: - apply the patch: git am 0001-cronie-upgrade-1.6.1-1.7.0.patch - check the changes to upstream patches and summarize them in

[OE-core] [AUH] python3-setuptools-scm: upgrading to 8.0.4 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-setuptools-scm* to *8.0.4* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-setuptools-scm -V 8.0.4 NOTE:

[OE-core] [AUH] mpg123: upgrading to 1.32.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mpg123* to *1.32.3* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-mpg123-upgrade-1.31.3-1.32.3.patch

[OE-core] [AUH] python3-subunit: upgrading to 1.4.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-subunit* to *1.4.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-subunit-upgrade-1.4.2-1.4.3.patch - check the changes to upstream patches and

[OE-core] [AUH] python3-sphinxcontrib-htmlhelp: upgrading to 2.0.4 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-sphinxcontrib-htmlhelp* to *2.0.4* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-sphinxcontrib-htmlhelp

[OE-core] [AUH] cairo: upgrading to 1.18.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cairo* to *1.18.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe cairo failed. NOTE: Starting bitbake server... NOTE: Reconnecting

[OE-core] [AUH] webkitgtk: upgrading to 2.42.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *webkitgtk* to *2.42.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe webkitgtk failed. NOTE: Starting bitbake server... Loading

[OE-core] [AUH] piglit: upgrading to 24207f5bed81f4e66594282900e2259c80aeb6a2 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *piglit* to *24207f5bed81f4e66594282900e2259c80aeb6a2* has Succeeded. Next steps: - apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch - check the changes

[OE-core] [AUH] go-helloworld: upgrading to 1d6d2400d4027025cb8edc86a139c9c581d672f7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-helloworld* to *1d6d2400d4027025cb8edc86a139c9c581d672f7* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade go-helloworld

[OE-core] [AUH] python3: upgrading to 3.12.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3* to *3.12.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3 -V 3.12.0 NOTE: Starting bitbake server...

[OE-core] [AUH] kmscube: upgrading to 96d63eb59e34c647cda1cbb489265f8c536ae055 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *kmscube* to *96d63eb59e34c647cda1cbb489265f8c536ae055* has Succeeded. Next steps: - apply the patch: git am 0001-kmscube-upgrade-to-latest-revision.patch - check the

[OE-core] [AUH] python3-git: upgrading to 3.1.37 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-git* to *3.1.37* has Succeeded. Next steps: - apply the patch: git am 0001-python3-git-upgrade-3.1.36-3.1.37.patch - check the changes to upstream patches and

[OE-core] [AUH] rpm: upgrading to 4.19.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rpm* to *4.19.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rpm failed. NOTE: Starting bitbake server... NOTE: Reconnecting to

[OE-core] [AUH] python3-sphinxcontrib-applehelp: upgrading to 1.0.7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-sphinxcontrib-applehelp* to *1.0.7* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-sphinxcontrib-applehelp

[OE-core] [AUH] python3-sphinxcontrib-devhelp: upgrading to 1.0.5 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-sphinxcontrib-devhelp* to *1.0.5* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-sphinxcontrib-devhelp -V

[OE-core] [AUH] gsettings-desktop-schemas: upgrading to 45.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gsettings-desktop-schemas* to *45.0* has Succeeded. Next steps: - apply the patch: git am 0001-gsettings-desktop-schemas-upgrade-44.0-45.0.patch - check the changes to

[OE-core] [AUH] python3-sphinxcontrib-serializinghtml: upgrading to 1.1.9 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-sphinxcontrib-serializinghtml* to *1.1.9* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade

[OE-core] [AUH] repo: upgrading to 2.37 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *repo* to *2.37* has Succeeded. Next steps: - apply the patch: git am 0001-repo-upgrade-2.36.1-2.37.patch - check the changes to upstream patches and summarize them in the

[OE-core] [AUH] python3-wcwidth: upgrading to 0.2.8 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-wcwidth* to *0.2.8* has Succeeded. Next steps: - apply the patch: git am 0001-python3-wcwidth-upgrade-0.2.6-0.2.8.patch - check the changes to upstream patches and

[OE-core] [AUH] python3-dtschema: upgrading to 2023.9 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-dtschema* to *2023.9* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] python3-iso8601: 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 *python3-iso8601* to *2.1.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-iso8601-upgrade-2.0.0-2.1.0.patch - check the changes to upstream patches and

[OE-core] [AUH] qemu: upgrading to 8.1.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *qemu* to *8.1.1* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-qemu-upgrade-8.1.0-8.1.1.patch - check

[OE-core] [AUH] python3-ruamel-yaml: upgrading to 0.17.35 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-ruamel-yaml* to *0.17.35* has Succeeded. Next steps: - apply the patch: git am 0001-python3-ruamel-yaml-upgrade-0.17.32-0.17.35.patch - check the changes to

[OE-core] [AUH] python3-cffi: upgrading to 1.16.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-cffi* to *1.16.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-cffi-upgrade-1.15.1-1.16.0.patch - check the changes to upstream patches and

[OE-core] [AUH] python3-jsonschema: upgrading to 4.19.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-jsonschema* to *4.19.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-jsonschema-upgrade-4.17.3-4.19.1.patch - check the changes to upstream

[OE-core] [AUH] python3-beartype: upgrading to 0.16.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-beartype* to *0.16.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-beartype-upgrade-0.15.0-0.16.3.patch - check the changes to upstream patches

[OE-core] [AUH] python3-sphinxcontrib-qthelp: upgrading to 1.0.6 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-sphinxcontrib-qthelp* to *1.0.6* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-sphinxcontrib-qthelp -V

[OE-core] [AUH] python3-packaging: upgrading to 23.2 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-packaging* to *23.2* has Succeeded. Next steps: - apply the patch: git am 0001-python3-packaging-upgrade-23.1-23.2.patch - check the changes to upstream patches and

[OE-core] [AUH] libtest-warnings-perl: upgrading to 0.032 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libtest-warnings-perl* to *0.032* has Succeeded. Next steps: - apply the patch: git am 0001-libtest-warnings-perl-upgrade-0.031-0.032.patch - check the changes to upstream

[OE-core] [AUH] python3-babel: upgrading to 2.13.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-babel* to *2.13.0* has Succeeded. Next steps: - apply the patch: git am 0001-python3-babel-upgrade-2.12.1-2.13.0.patch - check the changes to upstream patches and

[OE-core] [AUH] python3-cython: upgrading to 3.0.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-cython* to *3.0.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-cython-upgrade-0.29.36-3.0.3.patch - check the changes to upstream patches and

[OE-core] [AUH] go: upgrading to 1.21.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go* to *1.21.3* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go failed. NOTE: Starting bitbake server... Loading cache...done.

[OE-core] [AUH] btrfs-tools: upgrading to 6.5.2 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.5.2* has Succeeded. Next steps: - apply the patch: git am 0001-btrfs-tools-upgrade-6.5.1-6.5.2.patch - check the changes to upstream patches and

[OE-core] [AUH] python3-markdown: upgrading to 3.5 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-markdown* to *3.5* has Succeeded. Next steps: - apply the patch: git am 0001-python3-markdown-upgrade-3.4.4-3.5.patch - check the changes to upstream patches and

[OE-core] [AUH] gnu-config: upgrading to 28ea239c53a2d5d8800c472bc2452eaa16e37af2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gnu-config* to *28ea239c53a2d5d8800c472bc2452eaa16e37af2* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade gnu-config -S

[OE-core] [AUH] mmc-utils: upgrading to b5ca140312d279ad2f22068fd72a6230eea13436 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mmc-utils* to *b5ca140312d279ad2f22068fd72a6230eea13436* has Succeeded. Next steps: - apply the patch: git am 0001-mmc-utils-upgrade-to-latest-revision.patch - check the

[OE-core] [AUH] desktop-file-utils: upgrading to 0.27 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *desktop-file-utils* to *0.27* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] python3-hypothesis: upgrading to 6.87.4 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-hypothesis* to *6.87.4* has Succeeded. Next steps: - apply the patch: git am 0001-python3-hypothesis-upgrade-6.86.2-6.87.4.patch - check the changes to upstream

[OE-core] [AUH] libcomps: upgrading to 0.1.20 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libcomps* to *0.1.20* has Succeeded. Next steps: - apply the patch: git am 0001-libcomps-upgrade-0.1.19-0.1.20.patch - check the changes to upstream patches and summarize

[OE-core] [AUH] go-runtime: upgrading to 1.21.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-runtime* to *1.21.3* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go-runtime failed. NOTE: Starting bitbake server... Loading

[OE-core] [AUH] cmake: upgrading to 3.27.7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cmake* to *3.27.7* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-cmake-upgrade-3.27.5-3.27.7.patch -

[OE-core] [AUH] erofs-utils: upgrading to 1.7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *erofs-utils* to *1.7* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-erofs-utils-upgrade-1.6-1.7.patch

[OE-core] [AUH] gettext: upgrading to 0.22.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gettext* to *0.22.3* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-gettext-upgrade-0.22-0.22.3.patch

[OE-core] [AUH] libubootenv: upgrading to 0.3.5 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libubootenv* to *0.3.5* has Succeeded. Next steps: - apply the patch: git am 0001-libubootenv-upgrade-0.3.4-0.3.5.patch - check the changes to upstream patches and

[OE-core] [AUH] ell: upgrading to 0.59 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ell* to *0.59* has Succeeded. Next steps: - apply the patch: git am 0001-ell-upgrade-0.58-0.59.patch - check the changes to upstream patches and summarize them in the commit

[OE-core] [AUH] glib-networking: upgrading to 2.78.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *glib-networking* to *2.78.0* has Succeeded. Next steps: - apply the patch: git am 0001-glib-networking-upgrade-2.76.1-2.78.0.patch - check the changes to upstream patches

[OE-core] [AUH] dhcpcd: upgrading to 10.0.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dhcpcd* to *10.0.3* has Succeeded. Next steps: - apply the patch: git am 0001-dhcpcd-upgrade-10.0.2-10.0.3.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] bluez5: upgrading to 5.70 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *bluez5* to *5.70* has Succeeded. Next steps: - apply the patch: git am 0001-bluez5-upgrade-5.69-5.70.patch - check the changes to upstream patches and summarize them in the

[OE-core] [AUH] systemd-boot: upgrading to 254.5 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *systemd-boot* to *254.5* has Succeeded. Next steps: - apply the patch: git am 0001-systemd-boot-upgrade-254.4-254.5.patch - check the changes to upstream patches and

Re: [OE-Core][PATCH v14 03/11] sstate.bbclass: override tar with tar-native

On Sun, 2023-10-15 at 16:57 +0200, Piotr Łobacz wrote: > Due to the bugs https://savannah.gnu.org/bugs/?61934 and > https://savannah.gnu.org/bugs/?59184, which are fixed in > tar version 1.35, we need to force yocto to use it instead > of the one provided by the host machine. > >

[OE-core][dunfell][PATCH] glib-2.0: Fix multiple vulnerabilities

From: Siddharth Doshi CVE's Fixed: CVE-2023-29499: glib: GVariant offset table entry size is not checked in is_normal() CVE-2023-32611: glib: g_variant_byteswap() can take a long time with some non-normal inputs CVE-2023-32636: glib: Timeout in fuzz_variant_text CVE-2023-32643: glib:

[OE-core] [PATCH] python3-urllib3: Update to 2.0.6

Only changes in this release [1] fixes CVE-2023-43804 [2] on top of 2.0.5 [1] https://github.com/urllib3/urllib3/commit/644124ecd0b6e417c527191f866daa05a5a2056d [2] https://github.com/advisories/GHSA-v845-jxx5-vc9f Signed-off-by: Khem Raj --- .../{python3-urllib3_2.0.5.bb =>

[OE-Core][PATCH v14 06/11] package.bbclass: add support for ACLs and xattr

Extend `tar` command, with additional parameters, depending on choosen package class and target distro features, in order to support ACLs and xattr. Currently only `package_ipk` supports fully ACLs and xattr. Signed-off-by: Piotr Łobacz --- meta/classes-global/package.bbclass | 9 +++-- 1

[OE-Core][PATCH v14 05/11] package_ipk.bbclass: add support for ACLs and xattr

Extend OPKGBUILDCMD variable, with additional parameters, depending on target distro features, in order to support ACLs and xattr. With fix pushed to the opkg-devel: https://groups.google.com/g/opkg-devel/c/dYNHrLjDwg8 opkg-build is able to create tar archives with ACLs and xattr. Signed-off-by:

[OE-Core][PATCH v14 11/11] opkg: set locale from system environment variables

A C program inherits its locale environment variables when it starts up. This happens automatically. However, these variables do not automatically control the locale used by the library functions, because ISO C says that all programs start by default in the standard ‘C’ locale. Fixes warnings:

[OE-Core][PATCH v14 10/11] opkg: add options to enable support for acl and xattr

The libarchive library, which is being used by opkg, supports ACLs and xattr already. More informations can be read at this link: https://github.com/libarchive/libarchive/pull/691 Signed-off-by: Piotr Łobacz --- ...-to-enable-support-for-acl-and-xattr.patch | 70 +++

[OE-Core][PATCH v14 07/11] sstate.bbclass: add support for ACLs and xattr

Extend `tar` command, with additional parameters, depending on choosen package class and target distro features, in order to support ACLs and xattr. Additionaly set archive posix format, in order to preserve milliseconds in timestamps for reproducibility tests. Currently only `package_ipk`

[OE-Core][PATCH v14 08/11] sstatesig.py: fix hash calculation for timestamp

Passing timestamp as an integer was losing precision, which led to problems with badly recreated sstate cache. Passing it as floating point number fixes the issue. Signed-off-by: Piotr Łobacz --- meta/lib/oe/sstatesig.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-Core][PATCH v14 09/11] opkg-utils: add acl and xattr support

Add support for tar archives created with --acls and/or --xattrs options, PAX header format. GNU tar and libarchive already supports ACLs and extended attributes. We can now add this support as well to opkg-build script in order to use fsetattr or setcap inside do_install command and end up with

[OE-Core][PATCH v14 04/11] path.py: add support for ACLs and all additional attributes

Extend `tar` command inside copytree() and copyhardlinktree() functions, with additional parameters, in order to support ACLs and xattr. The posix format doesn't need to be set in here, as GNU tar switches to it whenewer is uses --acls and/or --xattrs parameters. Additionaly change preservation

[OE-Core][PATCH v14 02/11] image_types.bbclass: override tar with tar-native

Due to the bugs https://savannah.gnu.org/bugs/?61934 and https://savannah.gnu.org/bugs/?59184, which are fixed in tar version 1.35, we need to force yocto to use it instead of the one provided by the host machine. IMAGE_CMD_TAR will use the tar provided by tar recipe, which is already in proper

[OE-Core][PATCH v14 03/11] sstate.bbclass: override tar with tar-native

Due to the bugs https://savannah.gnu.org/bugs/?61934 and https://savannah.gnu.org/bugs/?59184, which are fixed in tar version 1.35, we need to force yocto to use it instead of the one provided by the host machine. sstate_create_package and sstate_unpack_package functions, will use the tar

[OE-Core][PATCH v14 01/11] package.bbclass: override tar with tar-native

Due to the bugs https://savannah.gnu.org/bugs/?61934 and https://savannah.gnu.org/bugs/?59184, which are fixed in tar version 1.35, we need to force yocto to use it instead of the one provided by the host machine. perform_packagecopy function and opkg-build script, will use the tar provided by

[OE-core] OE-core CVE metrics for mickledore on Sun 15 Oct 2023 04:00:01 AM HST

Branch: mickledore New this week: 19 CVEs CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 * CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 * CVE-2023-39189 (CVSS3: 6.0

[OE-core] OE-core CVE metrics for kirkstone on Sun 15 Oct 2023 03:00:01 AM HST

Branch: kirkstone New this week: 14 CVEs CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 * CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 * CVE-2023-3576 (CVSS3: 5.5

Re: Kernel 6.5 ttyS1 hang with qemu (was Re: [OE-core] Summary of the remaining 6.5 kernel serial issue (and 6.5 summary)

On Sat, 2023-10-14 at 12:13 +0100, Richard Purdie via lists.openembedded.org wrote: > On Sat, 2023-10-14 at 10:41 +0100, Richard Purdie wrote: > > Brief summary: > > > > We're seeing an issue on x86_64 with 6.5.X where data appears to be > > left in the transmission buffer and not sent to the

[OE-core] OE-core CVE metrics for dunfell on Sun 15 Oct 2023 02:00:01 AM HST

Branch: dunfell New this week: 13 CVEs CVE-2023-28198 (CVSS3: 8.8 HIGH): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-28198 * CVE-2023-32370 (CVSS3: 5.3 MEDIUM): webkitgtk https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-32370 * CVE-2023-3576 (CVSS3: 5.5 MEDIUM):

[OE-core] OE-core CVE metrics for master on Sun 15 Oct 2023 01:00:02 AM HST

Branch: master New this week: 7 CVEs CVE-2023-39189 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39189 * CVE-2023-39192 (CVSS3: 6.0 MEDIUM): linux-yocto https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-39192 * CVE-2023-39193 (CVSS3: 6.0

[OE-core] [PATCH] linux-yocto-6.5: Add serial port suspend/boot workaround

The 6.5 kernel has some issues with serial ports not always starting up in early boot correctly after upstream PM changes. Add a hack to cause data not to get lost in the xmit buffer. This has caused breakage on the autobuilder. [Patch being sent for wider attention and not for merging as Bruce

  1   2   >