Re: [OE-core] [PATCH] vulkan-validation-layers: add new recipe v1.3.243.0

Added Github issue to Vulkan-ValidationLayers here https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/5964 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#182346): https://lists.openembedded.org/g/openembedded-core/message/182346 Mute

[OE-core] [PATCH] vulkan-validation-layers: add new recipe v1.3.243.0

Recipe added with a fix to error: '../recipe-sysroot/usr/lib', needed by 'layers/libVkLayer_khronos_validation.so', missing and no known rule to make it Taking a look into ${B}/build.ninja LINK_LIBRARIES = \ layers/libVkLayer_utils.a /recipe-sysroot/usr/lib64/libSPIRV-Tools-opt.so

[OE-core] [PATCH] cmake: upgrade to v3.26.4

Signed-off-by: Sudip Mukherjee --- .../cmake/{cmake-native_3.26.3.bb => cmake-native_3.26.4.bb}| 0 meta/recipes-devtools/cmake/cmake.inc | 2 +- .../recipes-devtools/cmake/{cmake_3.26.3.bb => cmake_3.26.4.bb} | 0 3 files changed, 1 insertion(+), 1 deletion(-)

[OE-core] [PATCH] libssh2: Upgrade to v1.11.0

Changes: Update license checksum: change in copyright year. Remove patch fixed by upstream. Disable rpath, hardcoded rpath failed curl-native build. Adjust ptests. Signed-off-by: Sudip Mukherjee --- .../libssh2/libssh2/fix-ssh2-test.patch | 23 ---

[OE-core] [PATCH] dpkg: upgrade to v1.21.22

Signed-off-by: Sudip Mukherjee --- meta/recipes-devtools/dpkg/{dpkg_1.21.21.bb => dpkg_1.21.22.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-devtools/dpkg/{dpkg_1.21.21.bb => dpkg_1.21.22.bb} (95%) diff --git a/meta/recipes-devtools/dpkg/dpkg_1.21.21.bb

Re: [OE-core][PATCH v3 1/3] cve-check: add option to add additional patched CVEs

On Fri, 2023-06-02 at 23:10 +0200, adrian.freiho...@gmail.com wrote: > I like the VEX proposal from Sanjay. > > - It is a standard that can be supported by many tools and requested by > customers. One use case I see is where a vendor sells a product with an > SBOM. The customer can then match the

Re: [OE-core][PATCH v3 1/3] cve-check: add option to add additional patched CVEs

Hi I like the VEX proposal from Sanjay. - It is a standard that can be supported by many tools and requested by customers. One use case I see is where a vendor sells a product with an SBOM. The customer can then match the open vulnerabilities to the current state of the NIST database using a

Re: [OE-core] [PATCH 3/3] binutils: package static libs from gprofng

On Tue, May 02, 2023 at 07:44:06AM -0700, Khem Raj wrote: > From: Martin Jansa > > * fixes: > ERROR: binutils-2.40-r0 do_package: QA Issue: binutils: Files/directories > were installed but not shipped in any package: > /usr/lib/gprofng/libgp-collectorAPI.a > Please set FILES such that

[OE-core][PATCH] python3-poetry-core: upgrade 1.5.2 -> 1.6.1

Changelog: https://github.com/python-poetry/poetry-core/blob/main/CHANGELOG.md Notably, the project replaced its use of tomlkit with tomli, so the LICENSEs and associated checksums had to be changed. Signed-off-by: Trevor Gamblin --- ...hon3-poetry-core_1.5.2.bb =>

Re: [OE-core] [PATCH 1/3] python3-pyproject-metadata: New recipe

Hello, the series causes the following warnings: stdio: WARNING: python3-pyproject-metadata-native-0.7.1-r0 do_fetch: QA Issue: Recipe python3-pyproject-metadata in /home/pokybuild/yocto-worker/musl-qemux86/build/meta/recipes-devtools/python/python3-pyproject-metadata_0.7.1.bb does not

[OE-core] [PATCH] oeqa/selftest/wic: Fix host contamination issue

If wic.Wic2.test_gpt_partition_name is run on a system without sfdisk, the test will currently fail. As done in another test, it needs to use sfdisk from the wic-tools sysroot. This patch fixes that host contamination issue. Signed-off-by: Richard Purdie --- meta/lib/oeqa/selftest/cases/wic.py

[OE-core][PATCH] python3-webcolors: upgrade 1.12 -> 1.13

Replaced the inherit of setuptools3 with python_setuptools_build_meta to make the new version build. Changelog (see https://webcolors.readthedocs.io/en/latest/changelog.html): - Supported Python versions are now 3.7, 3.8, 3.9, 3.10, and 3.11 - The codebase was significantly reorganized and

[OE-Core][PATCH] rust: Upgrade 1.69.0 -> 1.70.0

Drop 0035-cmake-Enable-64bit-off_t-on-32bit-glibc-systems.patch as this is merged upstream in rust-llvm. https://blog.rust-lang.org/2023/06/01/Rust-1.70.0.html Signed-off-by: Alex Kiernan --- meta/conf/distro/include/tcmode-default.inc | 2 +- .../rust/{cargo_1.69.0.bb => cargo_1.70.0.bb}

[OE-core][PATCH v2] util-linux: upgrade 2.38.1 -> 2.39

util-linux's ChangeLog file simply points to the git log, and there are numerous changes between 2.38.1 and 2.39: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log There is a notable license change - README.licensing adds the BSD-2-Clause variant between these versions, but

[OE-core][PATCH] util-linux: upgrade 2.38.1 -> 2.39

util-linux's ChangeLog file simply points to the git log, and there are numerous changes between 2.38.1 and 2.39: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log There is a notable license change - README.licensing adds the BSD-2-Clause variant between these versions, but

Re: [OE-Core][RFC][PATCH 1/3] oeqa/target/ssh: update options for SCP

On Fri, 2023-06-02 at 15:41 +0200, Alexis Lothoré wrote: > On 6/2/23 14:02, Richard Purdie wrote: > > On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via > > lists.openembedded.org wrote: > > > Add two options for SCP: > > > - by default scp expects sftp server to be available on target, which

Re: [OE-Core][RFC][PATCH 1/3] oeqa/target/ssh: update options for SCP

On 6/2/23 14:02, Richard Purdie wrote: > On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via > lists.openembedded.org wrote: >> Add two options for SCP: >> - by default scp expects sftp server to be available on target, which is >> not always true (e.g: core-image-minimal image). Pass -O to

[OE-core] [PATCH 10/11] oeqa/selftest/sstatetests: Add easier debug option

In order to debug these selftest failures you end up having to comment out the file cleanup. Make this an option at the top of the file to make it a bit easier, I've had to do this too many times now. Signed-off-by: Richard Purdie --- meta/lib/oeqa/selftest/cases/sstatetests.py | 7 +++ 1

[OE-core] [PATCH 11/11] classes/create-spdx-2.2: Make license errors fatal

From: Joshua Watt Otherwise the task is still put into sstate, which means the error can effectively be hidden by ignoring it. Signed-off-by: Joshua Watt --- meta/classes/create-spdx-2.2.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 07/11] layer.conf: Add missing dependency exclusion

Add a dependency which should have been in this list but wasn't, found when debugging create-spdx hash issues. Signed-off-by: Richard Purdie --- meta/conf/layer.conf | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/conf/layer.conf b/meta/conf/layer.conf index 948ded667e8..2cc7ed84155

[OE-core] [PATCH 08/11] sstatesig: Drop SPDX special casing

Other changes in create-spdx code mean we shouldn't need to do this now. We need the various exclusions to allow the task hashes to behave correctly for the SPDX tasks too. Signed-off-by: Richard Purdie --- meta/lib/oe/sstatesig.py | 9 - 1 file changed, 9 deletions(-) diff --git

[OE-core] [PATCH 09/11] selftest/incompatible_lic: Ensure create_sdpx isn't used with the tests

The SPDX class doens't get on well with non-standard licenses. Disable it for the purposes of this test to avoid errors. Add a new helper function to the core test code to allow this to be done easily. Signed-off-by: Richard Purdie --- meta/lib/oeqa/selftest/case.py | 7

[OE-core] [PATCH 06/11] create-spdx-2.2: Add missing variable exclusions

Some variables cause issues with taskhashes and are accounted for in the output in other ways, or don't affect it. Exclude these to improve the taskhashes with create-spdx and allow the sstate selftests to work better. Signed-off-by: Richard Purdie --- meta/classes/create-spdx-2.2.bbclass | 9

[OE-core] [PATCH 04/11] classes/create-spdx-2.2: Fix runtime dependency calculations

From: Joshua Watt Fixes the runtime dependency calculations to also only follow direct dependencies of the current task instead of all transient dependencies in a similar way as the build time dependencies. Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie ---

[OE-core] [PATCH 05/11] create-spdx-2-2: Fix packagedata usage to work with SDK packages

There are two seperate PKGDATA_DIR directories, one for the target and one for the SDK. Rather than fail when a package can't be found, try the SDK first. We use a datastore copy to keep the code simple, rather than havng to parameterise all the packagedata functions. Signed-off-by: Richard

[OE-core] [PATCH 02/11] classes/create-spdx-2.2: Respect PKG for providers

From: Joshua Watt If a package renames itself using PKG, the new name should be respected as a name that the recipe provides. Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie --- meta/classes/create-spdx-2.2.bbclass | 4 1 file changed, 4 insertions(+) diff --git

[OE-core] [PATCH 01/11] classes/create-spdx-2.2: Use hashfn from BB_TASKDEPDATA instead of MACHINE

From: Joshua Watt Enabling the SPDX class and running two builds, one with SDKMACHINE=i686 and then again with SDKMACHINE=x86_64 would lead to errors since the output was stored per MACHINE and the overlapping files would cause manifest errors. The hashfn data from bitbake has SSTATE_PKGARCH

[OE-core] [PATCH 03/11] classes/create-spdx-2.2: Fix build time dependency calculations

From: Joshua Watt Build time dependencies were not being correctly calculated for SPDX documents because while a task can `deptask` itself (as do_create_spdx did), those dependencies do not appear in BB_TASKDEPDATA (to avoid circular dependencies). To fix this, an intermediate task called

Re: [OE-core] [PATCH v3] qemu: Split the qemu package

On Fri, 2023-06-02 at 09:08 -0400, Bruce Ashfield wrote: > On Thu, Jun 1, 2023 at 10:37 PM Yu, Mingli > wrote: > > > > From: Mingli Yu > > > > Currently all files as below packaged into one package such as > > qemu-7.2.0-*.rpm. After the qemu package installed on the target, > > it will take

Re: [OE-core] [PATCH v3] qemu: Split the qemu package

On Thu, Jun 1, 2023 at 10:37 PM Yu, Mingli wrote: > > From: Mingli Yu > > Currently all files as below packaged into one package such as > qemu-7.2.0-*.rpm. After the qemu package installed on the target, > it will take up about 464M which includes not only the one matches > the arch of the

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Hi, These changes are an improvement, but based on my experience in product test automation, instead of collecting logs after testing is completed, it is better to capture logs from the target device while tests are being executed. Serial console, systemd journal etc logs can be captured as

[OE-core][PATCH] sqlite3: upgrade 3.41.2 -> 3.42.0

Signed-off-by: Trevor Gamblin --- .../sqlite/{sqlite3_3.41.2.bb => sqlite3_3.42.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/sqlite/{sqlite3_3.41.2.bb => sqlite3_3.42.0.bb} (86%) diff --git a/meta/recipes-support/sqlite/sqlite3_3.41.2.bb

Re: [OE-Core][RFC][PATCH 2/3] testimage: shut down DUT later

Hello Richard, On 6/2/23 13:55, Richard Purdie wrote: > On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via > lists.openembedded.org wrote: >> Move target stop (for Qemu targets: qemu image stop) later in testimage >> main function, especially _after_ having access to general test results, to >>

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

On Fri, 2 Jun 2023 at 14:14, Alexis Lothoré wrote: > I wondered about this possibility while adding this variable, and at this > time I > thought it would encode to much "CI logic" in testimage class. But since you > raise the suggestion, I can update to pass directly the file list, which could

Re: [OE-core] [PATCH] mtd-utils: export headers and libraries for MTD and UBI

Hi Richard, On 02.06.23 14:02, Richard Purdie wrote: On Fri, 2023-06-02 at 13:24 +0200, Stefano Babic wrote: Mtd-utils has internal libraries (libmtd and libubi) that simplify the usage and access, and they can be used by applications to access MTD devices without reinventing the code. Does

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Hello Alexander, Mikko, On 6/2/23 13:52, Mikko Rapeli wrote: > Hi, > > On Fri, Jun 02, 2023 at 01:46:03PM +0200, Alexander Kanavin wrote: >> On Fri, 2 Jun 2023 at 11:50, Alexis Lothoré via lists.openembedded.org >> wrote: >>> +# When any test fails, if path to an artifacts configuration

Re: [OE-core] [PATCH] mtd-utils: export headers and libraries for MTD and UBI

On Fri, 2023-06-02 at 13:24 +0200, Stefano Babic wrote: > Mtd-utils has internal libraries (libmtd and libubi) that simplify the > usage and access, and they can be used by applications to access MTD > devices without reinventing the code. Does upstream plan to turn these into a shared library if

Re: [OE-Core][RFC][PATCH 1/3] oeqa/target/ssh: update options for SCP

On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via lists.openembedded.org wrote: > Add two options for SCP: > - by default scp expects sftp server to be available on target, which is > not always true (e.g: core-image-minimal image). Pass -O to force SCP to > fallback to legacy SCP protocol

Re: [OE-Core][RFC][PATCH 2/3] testimage: shut down DUT later

On Fri, 2023-06-02 at 11:50 +0200, Alexis Lothoré via lists.openembedded.org wrote: > Move target stop (for Qemu targets: qemu image stop) later in testimage > main function, especially _after_ having access to general test results, to > allow executing some other actions (like retrieving some

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Hi, On Fri, Jun 02, 2023 at 01:46:03PM +0200, Alexander Kanavin wrote: > On Fri, 2 Jun 2023 at 11:50, Alexis Lothoré via lists.openembedded.org > wrote: > > +# When any test fails, if path to an artifacts configuration (listing > > +# files/directories to retrieve on target) has been provided,

Re: [OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

On Fri, 2 Jun 2023 at 11:50, Alexis Lothoré via lists.openembedded.org wrote: > +# When any test fails, if path to an artifacts configuration (listing > +# files/directories to retrieve on target) has been provided, all listed > +# elements will be downloaded from target before shutting it down >

Re: [OE-core] [PATCH v14] Rust Oe-Selftest implementation

Hi Richard, Thanks for the confirmation. Regards, Yash From: Richard Purdie Sent: 02 June 2023 17:02 To: Shinde, Yash; Kokkonda, Sundeep;

Re: [OE-core] [PATCH v14] Rust Oe-Selftest implementation

Hi Yash, On Fri, 2023-06-02 at 07:25 +, Shinde, Yash wrote: > > As discussed in the meeting, I am sharing the steps followed and host > configurations used for the testing- >   > Steps followed for testing- >   > 1. Clone a fresh poky from $ git clone git://git.yoctoproject.org/poky > 2.

[OE-core] [PATCH] libubootenv: upgrade 0.3.3 -> 0.3.4

Signed-off-by: Stefano Babic --- .../u-boot/{libubootenv_0.3.3.bb => libubootenv_0.3.4.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-bsp/u-boot/{libubootenv_0.3.3.bb => libubootenv_0.3.4.bb} (93%) diff --git a/meta/recipes-bsp/u-boot/libubootenv_0.3.3.bb

[OE-core] [PATCH] mtd-utils: export headers and libraries for MTD and UBI

Mtd-utils has internal libraries (libmtd and libubi) that simplify the usage and access, and they can be used by applications to access MTD devices without reinventing the code. Signed-off-by: Stefano Babic --- meta/recipes-devtools/mtd/mtd-utils_git.bb | 8 1 file changed, 8

[OE-Core][RFC][PATCH 3/3] testimage: implement test artifacts retriever for failing tests

Add a basic artifacts retrievers in testimage class which: - triggers when at least one runtime test fails - reads a list of files to retrieve from ARTIFACTS_LIST_PATH - retrieve those files over scp thanks to existing ssh class - store those files in an "artifacts" directory in "tmp/log/oeqa/"

[OE-Core][RFC][PATCH 2/3] testimage: shut down DUT later

Move target stop (for Qemu targets: qemu image stop) later in testimage main function, especially _after_ having access to general test results, to allow executing some other actions (like retrieving some files) on DUT depending on test results (e.g. : retrieve some log files) Signed-off-by:

[OE-Core][RFC][PATCH 0/3] add failed test artifacts retriever

This series is a proposal to bring in an "artifact retriever" to ease debugging when some runtime tests fails. This is a follow-up to corresponding RFC ([1]), which in turn is a proposal to address general debugging issues like [2] In the proposed form the retriever is pretty simple/dumb: it

[OE-Core][RFC][PATCH 1/3] oeqa/target/ssh: update options for SCP

Add two options for SCP: - by default scp expects sftp server to be available on target, which is not always true (e.g: core-image-minimal image). Pass -O to force SCP to fallback to legacy SCP protocol - by default scp expects files. Passing -r option allows to copy directories too

[OE-core] [mickledore][PATCH v2 2/2] go: Use -no-pie to build target cgo

From: Khem Raj Fixes go: ELF binary /usr/lib/go/pkg/tool/linux_arm64/pprof has relocations in .text go: ELF binary /usr/lib/go/bin/go has relocations in .text [textrel] Signed-off-by: Khem Raj Signed-off-by: Richard Purdie (cherry picked from commit a27d39aebd5966b57c20518381cb06ba8373)

[OE-core] [mickledore][PATCH v2 1/2] go: Upgrade 1.20.1 -> 1.20.4

From: Khem Raj - Remove already upstreamed patches - Brings a list of changes [1] [2] [3] [1] https://github.com/golang/go/issues?q=milestone%3AGo1.20.2+label%3ACherryPickApproved [2] https://github.com/golang/go/issues?q=milestone%3AGo1.20.3+label%3ACherryPickApproved [3]

Re: [OE-core] [AUH] alsa-utils: upgrading to 1.2.9 FAILED

On 02.06.23 at 10:10, Auto Upgrade Helper wrote: Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *alsa-utils* to *1.2.9* has Failed(do_compile). This has already been addressed by a patch that hasn't been merged yet. See

Re: [OE-core] [meta-oe][PATCH V1] xz: add ptest support

Thanks for clarification, please do the pull request as well. Patches over email mean that any discussion about them with upstream is visible only to you, and we can't see who says what and what is the outcome. Alex On Fri, 2 Jun 2023 at 10:18, duep.f...@fujitsu.com wrote: > > I read the

[OE-core] [AUH] serf: upgrading to 1.3.10 SUCCEEDED

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

Re: [OE-core] [meta-oe][PATCH V1] xz: add ptest support

I read the 'README' in https://github.com/tukaani-project/xz It is recommended to submit the patch via email to 'x...@tukaani.org'. Later I will try submitting a Pull request in ' https://github.com/tukaani-project/xz ' duep -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this

[OE-core] [AUH] libproxy: upgrading to 0.5.1 FAILED

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

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

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

[OE-core] [AUH] libxslt: upgrading to 1.1.38 SUCCEEDED

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

[OE-core] [AUH] libcap: upgrading to 2.69 SUCCEEDED

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

[OE-core] [AUH] libssh2: upgrading to 1.11.0 FAILED

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

[OE-core] [AUH] apr: upgrading to 1.7.4 SUCCEEDED

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

[OE-core] [AUH] icu: upgrading to 73-1 FAILED

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

[OE-core] [AUH] gnupg: upgrading to 2.4.2 SUCCEEDED

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

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

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

[OE-core] [AUH] vulkan-headers: upgrading to 1.3.250.0 SUCCEEDED

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

[OE-core] [AUH] libxpm: upgrading to 3.5.16 SUCCEEDED

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

[OE-core] [AUH] systemtap: upgrading to 4.9 FAILED

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

[OE-core] [AUH] xdpyinfo: upgrading to 1.3.4 SUCCEEDED

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

[OE-core] [AUH] dos2unix: upgrading to 7.5.0 SUCCEEDED

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

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

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

[OE-core] [AUH] gstreamer1.0-python: upgrading to 1.22.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-python* to *1.22.3* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-python-upgrade-1.22.2-1.22.3.patch - check the changes to upstream

[OE-core] [AUH] squashfs-tools: upgrading to 4.6.1 SUCCEEDED

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

[OE-core] [AUH] vulkan-tools: upgrading to 1.3.250.0 FAILED

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

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

[OE-core] [AUH] xf86-input-mouse: upgrading to 1.9.5 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *xf86-input-mouse* to *1.9.5* has Succeeded. Next steps: - apply the patch: git am 0001-xf86-input-mouse-upgrade-1.9.4-1.9.5.patch - check the changes to upstream patches

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

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

[OE-core] [AUH] vulkan-loader: upgrading to 1.3.250.0 FAILED

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

[OE-core] [AUH] sysklogd: upgrading to 2.5.0 SUCCEEDED

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

[OE-core] [AUH] glslang: upgrading to 1.3.250.0 SUCCEEDED

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

[OE-core] [AUH] rpcsvc-proto: upgrading to 1.4.4 FAILED

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

[OE-core] [AUH] kmscube: upgrading to cf4ec7f35521eb54d72ce0c92ce65b2249171cbd SUCCEEDED

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

[OE-core] [AUH] gawk: upgrading to 5.2.2 SUCCEEDED

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

[OE-core] [AUH] parted: upgrading to 3.6 SUCCEEDED

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

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

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *6028893f409d0105ab1e394dd4c90eb73f2c4e7d* has Failed(other errors). Detailed error information: 'MACHINE=qemux86 bitbake vulkan-samples' failed WARNING: Host

[OE-core] [AUH] libpam: upgrading to 1.5.3 FAILED

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

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

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

[OE-core] [AUH] wget: upgrading to 1.21.4 SUCCEEDED

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

[OE-core] [AUH] python3-webcolors: upgrading to 1.13 FAILED

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

[OE-core] [AUH] alsa-utils: upgrading to 1.2.9 FAILED

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

[OE-core] [AUH] ethtool: upgrading to 6.3 SUCCEEDED

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

[OE-core] [AUH] gstreamer1.0-rtsp-server: upgrading to 1.22.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-rtsp-server* to *1.22.3* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-rtsp-server-upgrade-1.22.2-1.22.3.patch - check the changes to

[OE-core] [AUH] gstreamer1.0-plugins-ugly: upgrading to 1.22.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-plugins-ugly* to *1.22.3* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-plugins-ugly-upgrade-1.22.2-1.22.3.patch - check the changes

[OE-core] [AUH] python3-psutil: upgrading to 5.9.5 SUCCEEDED

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

[OE-core] [AUH] diffutils: upgrading to 3.10 FAILED

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

[OE-core] [AUH] systemtap-uprobes: upgrading to 4.9 FAILED

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

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

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

[OE-core] [AUH] gstreamer1.0-libav: upgrading to 1.22.3 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gstreamer1.0-libav* to *1.22.3* has Succeeded. Next steps: - apply the patch: git am 0001-gstreamer1.0-libav-upgrade-1.22.2-1.22.3.patch - check the changes to upstream

[OE-core] [AUH] python3-pytest-subtests: upgrading to 0.11.0 FAILED

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

[OE-core] [AUH] python3-ruamel-yaml: upgrading to 0.17.31 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.31* has Succeeded. Next steps: - apply the patch: git am 0001-python3-ruamel-yaml-upgrade-0.17.21-0.17.31.patch - check the changes to

[OE-core] [AUH] wireless-regdb: upgrading to 2023.05.03 SUCCEEDED

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

  1   2   >