[OE-core] [nanbield][patch 1/2] xwayland: upgrade 23.2.2 -> 23.2.3

From: Wang Mingyu upgrade include fix for CVE-2023-6377 CVE-2023-6478 (Cherry-pick from OE-Core rev: bf0bb7b94ed4930145af5f1fb3836157daceb6bb) Signed-off-by: Wang Mingyu Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie Signed-off-by: Lee Chee Yang ---

[OE-core] [nanbield][patch 2/2] curl: Fix CVE-2023-46219

From: Lee Chee Yang Upstream docs for CVE-2023-46219: https://curl.se/docs/CVE-2023-46219.html Signed-off-by: Lee Chee Yang --- .../curl/curl/CVE-2023-46219.patch| 131 ++ meta/recipes-support/curl/curl_8.4.0.bb | 1 + 2 files changed, 132 insertions(+)

Re: [OE-core] [PATCH 2/2] python: update 3.11.5 -> 3.12.1

I got failures on the AB: https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/8302/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/8477/steps/25/logs/stdio On 12/01/2024 13:41:41+0100, Alexander Kanavin wrote: > Drop distutils and smtpd modules

Re: [OE-core] [PATCH] uboot-sign: support to load optee-os and TFA images

Hello Jamin! On Mon, 2024-01-15 at 15:54 +0800, Jamin Lin via lists.openembedded.org wrote: > Currently, u-boot FIT image only support to load u-boot image. > To support optee-os and trusted-firmware-a, update ITS file generation > scripts, so users are able to use u-boot FIT image to load >

[OE-core] [PATCH] newlib: Upgrade 4.3.0 -> 4.4.0

- COPYING.LICENSE: Added Apache-2.0-with-LLVM-exception from newlibs commit 96ec8f868e1a0f5a75badfe4627a41f12cce742d applicable to newlib/libc/machine/aarch64. - Also switch libgloss to use PV from newlib.inc instead to align with the newlib recipe behavior. Signed-off-by: Alejandro Enedino

Re: [OE-core] [dunfell][PATCH] systemd: fix CVE-2023-7008

Hi Steve, Yes, it is for kirkstone branch. Sorry for my mistake. Regards, Hitendra On 14/01/24 7:41 am, Steve Sakoman wrote: On Thu, Jan 11, 2024 at 6:12 PM Hitendra Prajapati via lists.openembedded.org wrote: Upstream-Status: Backport

[OE-core] [kirkstone][PATCH] systemd: fix CVE-2023-7008

Upstream-Status: Backport from https://github.com/systemd/systemd/commit/3b4cc1437b51fcc0b08da8cc3f5d1175eed25eb1 Signed-off-by: Hitendra Prajapati --- .../systemd/systemd/CVE-2023-7008.patch | 40 +++ meta/recipes-core/systemd/systemd_250.5.bb| 1 + 2 files changed,

Re: [OE-core] [PATCH] weston: Update to 13.0.0

On Mon, Jan 15, 2024 at 7:25 PM Fabio Estevam wrote: > > From: Fabio Estevam > > Update to Weston 13.0.0. > > Remove the following options that were no longer exist in 13.0.0: > launcher-libseat and launcher-libseat. I think one of them should be launcher-logind > > Add seatd as a required

[OE-core] [PATCH] weston: Update to 13.0.0

From: Fabio Estevam Update to Weston 13.0.0. Remove the following options that were no longer exist in 13.0.0: launcher-libseat and launcher-libseat. Add seatd as a required dependency for kms. Signed-off-by: Fabio Estevam --- .../wayland/{weston_12.0.2.bb => weston_13.0.0.bb} | 9

[OE-core] [PATCH] libxrandr: upgrade 1.5.3 -> 1.5.4

From: Jiang Kai Changelog: = -Remove "All rights reserved" from Oracle copyright notices -configure: Use LT_INIT from libtool 2 instead of deprecated AC_PROG_LIBTOOL -XRRGetMonitors(): free correct pointer in error path Signed-off-by: Jiang Kai Signed-off-by: Wang Mingyu ---

[OE-core] [PATCH] libsecret: upgrade 0.21.1 -> 0.21.2

From: Jiang Kai Changelog: * Support GnuTLS as an alternative crypto backend * Fix LeakSanitizer issues * secret-tool: Verify that the parsed stdin password is vaild UTF-8 * Fix markup syntax for SecretSchema * Public secret_attributes_validate method * Updated translations

[OE-core] [PATCH] enchant2: upgrade 2.6.4 -> 2.6.5

From: Jiang Kai Changelog: -permits error messages from spelling providers not to be valid UTF-8. -The --with-hunspell-dir configure option is removed (along with all the other ---with-PROVIDER-dir options, which did nothing). -Doxygen API documentation is now included in the

[OE-core][dunfell][PATCH] qemu: Backport fix for CVE-2023-2861

From: Vijay Anusuri Updated 0012-fix-libcap-header-issue-on-some-distro.patch to resolve patch fuzz caused by the CVE-2023-2861 patch Upstream-Status: Backport [https://gitlab.com/qemu-project/qemu/-/commit/a5804fcf7b22fc7d1f9ec794dd284c7d504bd16b &

[OE-core] [PATCH] debianutils: upgrade 5.15 -> 5.16

From: Jiang Kai Changelog: Upload to unstable per request of Chris Hofstaedtler. Signed-off-by: Jiang Kai Signed-off-by: Wang Mingyu --- .../debianutils/{debianutils_5.15.bb => debianutils_5.16.bb}| 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

[OE-core] [PATCH] btrfs-tools: upgrade 6.5.3 -> 6.6.3

From: Jiang Kai 0001-Add-a-possibility-to-specify-where-python-modules-ar.patch refreshed for 6.6.3 Changelog: == * subvol create: accept multiple arguments * subvol delete: print the subvolume id in the output * subvol sync: check if the filesystems is still writeable so it does not

Re: [OE-core] [PATCH] Revert "cve-check: Modify judgment processing using "=" in version comparison"

Hi, Ross, What do you think about the following? Regards, Shinji -Original Message- From: Matsunaga, Shinji/松永 慎司 Sent: Thursday, December 28, 2023 10:59 AM To: 'ross.bur...@arm.com' Cc: openembedded-core@lists.openembedded.org Subject: RE: [PATCH] Revert "cve-check: Modify judgment

[OE-core] "ptest-pkgs" image feature misses ptest package dependencies due to COMPLEMENTARY_GLOB ignoring all RRECOMMENDS

When I try to build a core-image-minimal image with ptest for openssl installed using the following conf/local.conf modifications, the openssl-ptest is installed but with missing runtime dependencies. DISTRO_FEATURES:append = " ptest" EXTRA_IMAGE_FEATURES += " ptest-pkgs"

[OE-core] [PATCH v2] libtest-warnings-perl: upgrade 0.031 -> 0.032

From: Wang Mingyu License-Update: basic artistic license changed to perl artistic license. Signed-off-by: Wang Mingyu --- ...ings-perl_0.031.bb => libtest-warnings-perl_0.032.bb} | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) rename

[OE-core] [PATCH v2] python3-subunit: upgrade 1.4.2 -> 1.4.4

From: Wang Mingyu License-Update: change License file to COPYING. add BSD-3-Clause to LICENSE Changelog: === * Removed use of deprecated "utc" and "utcfromtimestamp" methods of "datetime.datetime". * Fix an issue with date parsing exception handling * Add support for Python 3.12

Re: [OE-core] [PATCH] rng-tools: move to meta-oe

On Mon, 15 Jan 2024, Randy MacLeod via lists.openembedded.org wrote: > On 2024-01-15 11:58 a.m., Alexandre Belloni via lists.openembedded.org wrote: > > This is breaking meta-agl-core until this gets into meta-oe: > > > >

Re: [OE-core] [PATCH v3] glib-networking: Fix ptest failures with openssl backend

On Mon, Jan 15, 2024 at 11:38 AM Khem Raj wrote: > > On Mon, Jan 15, 2024 at 9:06 AM Ross Burton wrote: > > > > > > > > > On 15 Jan 2024, at 16:53, Khem Raj wrote: > > > Where does it say it does not support? On the contrary there are patches > > > in this area sent recently > > > >

Re: [OE-core] [PATCH] rng-tools: move to meta-oe

On Mon, Jan 15, 2024 at 12:20 PM Randy MacLeod via lists.openembedded.org wrote: > > On 2024-01-15 11:58 a.m., Alexandre Belloni via lists.openembedded.org wrote: > > This is breaking meta-agl-core until this gets into meta-oe: > >

[OE-core] [PATCHv3] rust: Re-write RPATHs in the copies llvm-config

Ensure that it can still access the native-sysroot for dependencies, use ORIGIN to indicate this relative its install location, this also helps in this not getting into the output of llvm-config which could otherwise provide incorrect library paths target rust recipe builds ( cross compile )

Re: [OE-core] [PATCH] rust: Use llvm-config from native llvm-rust on rust target builds

On Mon, Jan 15, 2024 at 9:49 AM Richard Purdie wrote: > > On Mon, 2024-01-15 at 08:56 -0800, Khem Raj wrote: > > Hi > > > > On Mon, Jan 15, 2024 at 5:19 AM Richard Purdie > > wrote: > > > On Sat, 2024-01-13 at 21:58 -0800, Khem Raj wrote: > > > > target rust recipe builds ( cross compile ) calls

[OE-core] [PATCHv2] rust: Re-write RPATHs in the copies llvm-config

Ensure that it can still access the native-sysroot for dependencies, use ORIGIN to indicate this relative its install location, this also helps in this not getting into the output of llvm-config which could otherwise provide incorrect library paths target rust recipe builds ( cross compile )

Re: [OE-core] [PATCH] rng-tools: move to meta-oe

On 2024-01-15 11:58 a.m., Alexandre Belloni via lists.openembedded.org wrote: This is breaking meta-agl-core until this gets into meta-oe: https://autobuilder.yoctoproject.org/typhoon/#/builders/120/builds/3849/steps/14/logs/stdio Thanks Alexandre. Stephane, Jan-Simon, Is rng-tools

Re: [OE-core] [PATCH v3] glib-networking: Fix ptest failures with openssl backend

On Mon, Jan 15, 2024 at 9:06 AM Ross Burton wrote: > > > > > On 15 Jan 2024, at 16:53, Khem Raj wrote: > > Where does it say it does not support? On the contrary there are patches in > > this area sent recently > >

Re: [OE-core] [PATCH] rust: Use llvm-config from native llvm-rust on rust target builds

On Mon, 2024-01-15 at 08:56 -0800, Khem Raj wrote: > Hi > > On Mon, Jan 15, 2024 at 5:19 AM Richard Purdie > wrote: > > On Sat, 2024-01-13 at 21:58 -0800, Khem Raj wrote: > > > target rust recipe builds ( cross compile ) calls llvm-config > > > from > > > target sysroot which works ok as long as

[OE-core] [AUH] iso-codes: upgrading to 4.16.0 SUCCEEDED

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

[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] puzzles: upgrading to 7a93ae5d3c90cb5d1d8d775a8cd9d30bc745f658 SUCCEEDED

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

[OE-core] [AUH] mpg123: upgrading to 1.32.4 SUCCEEDED

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

[OE-core] [AUH] pulseaudio: upgrading to 17.0 FAILED

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

[OE-core] [AUH] virglrenderer: upgrading to 1.0.1 SUCCEEDED

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

[OE-core] [AUH] debianutils: upgrading to 5.16 SUCCEEDED

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

[OE-core] [AUH] lttng-modules: upgrading to 2.13.11 FAILED

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

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

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *d9a6b1069f8008e83a74ae6c08fc7b0235aa2830* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe vulkan-samples failed.

[OE-core] [AUH] weston: upgrading to 13.0.0 FAILED

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

[OE-core] [AUH] lttng-ust: upgrading to 2.13.7 FAILED

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

[OE-core] [AUH] lsof: upgrading to 4.99.3 FAILED

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

[OE-core] [AUH] piglit: upgrading to f3f1b3f960611a88cb1a037114ba4724f1bf330e SUCCEEDED

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

[OE-core] [AUH] xserver-xorg: upgrading to 21.1.10 SUCCEEDED

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

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

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

[OE-core] [AUH] python3-pycryptodomex: upgrading to 3.20.0 SUCCEEDED

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

[OE-core] [AUH] cpio: upgrading to 2.15 SUCCEEDED

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

[OE-core] [AUH] libsecret: upgrading to 0.21.2 SUCCEEDED

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

[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-sphinxcontrib-applehelp: upgrading to 1.0.8 SUCCEEDED

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.8* has Succeeded. Next steps: - apply the patch: git am 0001-python3-sphinxcontrib-applehelp-upgrade-1.0.7-1.0.8.patch - check the

[OE-core] [AUH] rust-llvm: upgrading to 1.75.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.75.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust-llvm failed. NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] kexec-tools: upgrading to 2.0.28 SUCCEEDED

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

[OE-core] [AUH] python3-sphinxcontrib-devhelp: upgrading to 1.0.6 SUCCEEDED

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.6* has Succeeded. Next steps: - apply the patch: git am 0001-python3-sphinxcontrib-devhelp-upgrade-1.0.5-1.0.6.patch - check the

[OE-core] [AUH] icu: upgrading to 74-2 FAILED

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

[OE-core] [AUH] gtk+3: upgrading to 3.24.39 FAILED

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

[OE-core] [AUH] libtraceevent: upgrading to 1.8.2 FAILED

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

[OE-core] [AUH] attr: upgrading to 2.5.2 FAILED

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

[OE-core] [AUH] ruby: upgrading to 3.3.0 FAILED

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

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

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

[OE-core] [AUH] texinfo: upgrading to 7.1 FAILED

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

[OE-core] [AUH] stress-ng: upgrading to 0.17.04 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.04* has Succeeded. Next steps: - apply the patch: git am 0001-stress-ng-upgrade-0.17.03-0.17.04.patch - check the changes to upstream patches and

[OE-core] [AUH] shaderc: upgrading to 2023.8 FAILED

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

[OE-core] [AUH] python3-sphinxcontrib-qthelp: upgrading to 1.0.7 SUCCEEDED

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.7* has Succeeded. Next steps: - apply the patch: git am 0001-python3-sphinxcontrib-qthelp-upgrade-1.0.6-1.0.7.patch - check the

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

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

[OE-core] [AUH] linux-firmware: upgrading to 20231211 FAILED

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

[OE-core] [AUH] libstd-rs: upgrading to 1.75.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.75.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libstd-rs failed. NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] xz: upgrading to 5.4.5 SUCCEEDED

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

[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: Reconnecting to bitbake server... Loading

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

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

[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-markdown: upgrading to 3.5.2 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.2* has Succeeded. Next steps: - apply the patch: git am 0001-python3-markdown-upgrade-3.5-3.5.2.patch - check the changes to upstream patches and

[OE-core] [AUH] python3-sphinxcontrib-htmlhelp: upgrading to 2.0.5 SUCCEEDED

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.5* has Succeeded. Next steps: - apply the patch: git am 0001-python3-sphinxcontrib-htmlhelp-upgrade-2.0.4-2.0.5.patch - check the

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

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

[OE-core] [AUH] valgrind: upgrading to 3.22.0 FAILED

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

[OE-core] [AUH] cronie: upgrading to 1.7.1 SUCCEEDED

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

[OE-core] [AUH] python3-trove-classifiers: upgrading to 2024.1.8 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-trove-classifiers* to *2024.1.8* has Succeeded. Next steps: - apply the patch: git am 0001-python3-trove-classifiers-upgrade-2023.11.29-2024.1..patch - check the

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

[OE-core] [AUH] python3-numpy: upgrading to 1.26.3 SUCCEEDED

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

[OE-core] [AUH] python3-pycryptodome: upgrading to 3.20.0 SUCCEEDED

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

[OE-core] [AUH] python3-lxml: upgrading to 5.1.0 FAILED

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

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

[OE-core] [AUH] python3-sphinxcontrib-serializinghtml: upgrading to 1.1.10 SUCCEEDED

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.10* has Succeeded. Next steps: - apply the patch: git am 0001-python3-sphinxcontrib-serializinghtml-upgrade-1.1.9-.patch -

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

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

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

[OE-core] [AUH] libxml-parser-perl: upgrading to 2.47 FAILED

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

[OE-core] [AUH] gnu-config: upgrading to 948ae97ca5703224bd3eada06b7a69f40dd15a02 FAILED

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

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

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

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

[OE-core] [AUH] python3-alabaster: upgrading to 0.7.16 FAILED

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

[OE-core] [AUH] ovmf: upgrading to edk2-stable202311 FAILED

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

[OE-core] [AUH] dpkg: upgrading to 1.22.2 FAILED

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

[OE-core] [AUH] go-runtime: upgrading to 1.21.6 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.6* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go-runtime failed. NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] update-rc.d: upgrading to b8f950105010270a768aa12245d6abf166346015 SUCCEEDED

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

[OE-core] [AUH] ofono: upgrading to 2.3 SUCCEEDED

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

[OE-core] [AUH] systemd: upgrading to 255.2 FAILED

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

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

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go* to *1.21.6* has Failed(other errors). Detailed error information: 'MACHINE=qemux86-64 bitbake go' failed NOTE: Reconnecting to bitbake server... Loading cache...done. Loaded

[OE-core] [AUH] systemd-boot: upgrading to 255.2 FAILED

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

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

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

[OE-core] [AUH] librepo: upgrading to 1.17.0 FAILED

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

[OE-core] [AUH] libxml2: upgrading to 2.12.3 SUCCEEDED

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

[OE-core] [AUH] autoconf: upgrading to 2.72e FAILED

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

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

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

  1   2   >