It keeps getting weirder and weirder, I ran -c cleansstate and rebuilt the sdk and I didn’t get an error. I then added something else into the sdk build and now I get the ‘dynamically renamed’

Hello list, I changed the license on the recipe below to ‘GPL-3.0-or-later’ and the problem went away. Can anyone explain what is going on? I don’t understand how the package name was being

It was just a personal opinion saying that I won't mind. If it's needed, then someone would hopefully fix the issues. Thanks, Anuj

On Wed, 20 Jul 2022 at 17:46, Alexander Kanavin via lists.yoctoproject.org <alex.kanavin=gmail.com@...> wrote: Which I just resent. Now we have confirmation from Intel that

There has been a persistent stream of graphical failures on x32, and there is doubt about whether x32 is at all used by anyone nowadays - let's reduce the scope of x32 QA, and perhaps later drop it

This series passed CI and is a fantastic improvement https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/597428786

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.18.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

Hi We are pleased to announce the second milestone release for Yocto Project 4.1 (yocto-4.1_M2) is now available for download. Download:

Signed-off-by: Armin Kuster <akuster808@...> --- meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm.bb | 1 + 1 file changed, 1 insertion(+) diff --git

Hello list, I'm getting the following error message: do_package_write_ipk: An allarch packagegroup shouldn't depend on packages which are dynamically renamed (zint to libzint2.11) The zint_2.11.0.bb

Oops, I forgot my s-o-b. Here it is: Signed-off-by: Jon Mason <jon.mason@...>

The fix for the gcc issue has been upstreamed and the workaround is no longer needed. --- ci/base.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/ci/base.yml b/ci/base.yml index

From: Peter Hoyes <Peter.Hoyes@...> When TESTIMAGE_AUTO is enabled, the do_testimage task is inserted after do_image_complete and before do_build so that the test suites automatically run as part

From: Peter Hoyes <Peter.Hoyes@...> Now that TESTIMAGE_AUTO is available for Zephyr builds, enable it in ci/testimage.yml and remove the redundant build_and_test base configuration. Remove

intel-x86-64 machine isn't happy It looks like it's not able to find stdint.h https://gitlab.com/jonmason00/meta-zephyr/-/jobs/2771910955

Current Dev Position: YP 4.1 M3 Next Deadline: 22nd August 2022 YP 4.1 M3 Build Next Team Meetings: Bug Triage meeting Thursday July 28th 7:30 am PDT

Actually it required two versions of this patch as we're still supporting v2.7. Bart

From: Bartosz Golaszewski <bartosz.golaszewski@...> This upgrades the 3.x series to using v3.1.0. Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...> --- - add a rebased

With this patch, I'm seeing: WARNING: interrupt-3.1.0+gitAUTOINC+2ddd73feaf_5f86244bad-r0 do_patch: Fuzz detected: Applying patch 0001-cmake-add-yocto-toolchain.patch patching file

A build flagged for QA (yocto-3.1.18.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.18.rc1 Build hash information: bitbake: