Re: [OE-core][dunfell] qemu-system-native build failure

Ok great, I'll wait for this one to be included in dunfell then. Thanks. On Fri, 7 Apr 2023 at 07:26, Jeremy Puhlman wrote: > There is already a patch in dunfell-next to resolve the issue.. > > > https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/dunfell-nut&id=d17f4c741c66

Re: [OE-core][dunfell] qemu-system-native build failure

There is already a patch in dunfell-next to resolve the issue.. https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/dunfell-nut&id=d17f4c741c66268ce54ff89be2be9b0402c98df2 On 4/6/2023 10:16 PM, Frederic Martinsons wrote: Hello, I came across a build issue for qemu-system-na

[OE-core][dunfell] qemu-system-native build failure

Hello, I came across a build issue for qemu-system-native on dunfell branch when using spice PACKAGECONFIG. I found that the culprit is the CVE-2022-4144.patch introduced mid-march and that was merged in upstream end of november 2022: https://gitlab.com/qemu-project/qemu/-/commit/6dbbf055148c6f1b7

[OE-core] [PATCH] libnotify: remove dependency dbus

From: Kai Kang It ported to use GDBus in libnotify 0.7.0 [1]. So remove dbus from DEPENDS. And GDBus is provided by glib-2.0. [1]: https://gitlab.gnome.org/GNOME/libnotify/-/commit/f63e8ab Signed-off-by: Kai Kang --- meta/recipes-gnome/libnotify/libnotify_0.8.2.bb | 2 +- 1 file changed, 1 in

Re: [OE-core] [yocto] QA notification for completed autobuilder build (yocto-4.2.rc2)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.2.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4. TGL

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2.rc1)

Hi Richard, Noted. We will proceed to test the rc2 build. Best regards, Jing Hui > -Original Message- > From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Richard Purdie > Sent: Thursday, April 6, 2023 7:58 PM > To: qa-build-notificat...@lists.y

Re: [OE-core] [meta-oe][PATCHv5 1/8] glib-2.0: update 2.74.6 -> 2.76.1

Hello, On 06/04/2023 22:50:47+0200, mrksv...@googlemail.com wrote: > Hello Alexandre, > I have rebased the patchset two days ago after a patch for webkitgtk was > added to master-next. I guess it will still apply but will check that once I > come home tomorrow in the morning. > >

Re: [OE-core] [PATCH v2] migration-guides: update 4.2 migration and release notes

On 06.04.23 at 12:12, Richard Purdie wrote: The ptest images have changed structure in this release. The underlying core-image-ptest recipe now uses BBCLASSEXTEND to create a variant for each ptest enabled recipe in OE-Core. For example, this means that "core-image-ptest-bzip2", "core-image- pt

Re: [OE-core] [meta-oe][PATCHv5 1/8] glib-2.0: update 2.74.6 -> 2.76.1

Hello Markus, Do you mind rebasing that on top of master or ideally my own branch, abelloni/master-next? The series seemed to build fine but we had other conflicting patches that were taken for mickledore. Thanks! On 28/03/2023 12:31:37+0200, Markus Volk wrote: > From: Markus Volk > > --- >

[OE-core][langdale 25/26] runqemu: respect IMAGE_LINK_NAME

From: Martin Jansa * when searching for qemuboot.conf * don't assume that IMAGE_LINK_NAME is always - (with -.qemuboot.conf) * runqemu: use IMAGE_LINK_NAME set by testimage.bbclass or query with bitbake -e * testimage.bbclass was setting DEPLOY_DIR which I don't see used anywhere else, so I

[OE-core][langdale 26/26] report-error: catch Nothing PROVIDES error

From: Mingli Yu Make the report-error catch Nothing PROVIDES error and then we can check it directly via error report web. Signed-off-by: Mingli Yu Signed-off-by: Richard Purdie (cherry picked from commit a57d8f82b83554c821a83eacc02f9c73b263ff02) Signed-off-by: Steve Sakoman --- meta/classes

[OE-core][langdale 24/26] shadow: Fix can not print full login timeout message

From: Soumya When we do not enter password during login, it is expected to display message "Login timed out after 60 seconds". But it prints only first few bytes(like "Login t") when write is immediately followed by exit. Fix - Calling exit from new handler provides enough time to display full

[OE-core][langdale 22/26] selftest: runqemu: use better error message when asserts fail

From: Martin Jansa * It was showing whole log and that the runqemu command failed, but not where the log file is, nor why it thinks the runqemu failed [YOCTO #12937] Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie (cherry picked from commit ad4b72e6524114a3bdee10cab71f194ea143cd24

[OE-core][langdale 21/26] selftest: runqemu: better check for ROOTFS: in the log

From: Martin Jansa * it was searching for line like this: ROOTFS: [/OE/build/poky/build/build-st-2023-03-20-esdk-runqemu-patch1/runqemu.RunqemuTests.test_boot_machine_ext4/build-st/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20230320081121.rootfs.ext4] but with IMAGE_NAME_SUFF

[OE-core][langdale 23/26] oeqa/runtime: clean up deprecated backslash expansion

From: Ross Burton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie (cherry picked from commit 77085a05240c3f8226b9f2199c977f2555807789) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/runtime/cases/apt.py | 4 ++-- meta/lib/oeqa/runtime/cases/buildcpio.py | 7 +-- meta/lib/oe

[OE-core][langdale 20/26] oeqa/utils/qemurunner: replace hard-coded user 'root' in debug output

From: Enrico Jörns Since login user is configurable with boot_patterns['send_login_user'], unconditionally using 'root' in the debug message can be confusing. Also fix the debug message to say 'Logged in' instead of 'Logged'. Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry p

[OE-core][langdale 18/26] oeqa/utils/commands: fix usage of undefined EPIPE

From: Enrico Jörns Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry picked from commit 1cb17e37e275794e26debed2d171c2394d8bb945) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/utils/commands.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/lib/oeq

[OE-core][langdale 19/26] oeqa/utils/commands: remove unused imports

From: Enrico Jörns Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry picked from commit 0c00b5cdd57c3d9c47d4780d6627c74221911b72) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/utils/commands.py | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta/lib/oeqa/utils/commands

[OE-core][langdale 15/26] oeqa/targetcontrol: fix misspelled RuntimeError

From: Enrico Jörns Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry picked from commit 92ffc35052768c753a89b4839c70db87072437a2) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/targetcontrol.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/t

[OE-core][langdale 17/26] oeqa/targetcontrol: remove unused imports

From: Enrico Jörns Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry picked from commit 46b42edbf814d15be3a18283018ede2d4f817bc6) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/targetcontrol.py | 4 1 file changed, 4 deletions(-) diff --git a/meta/lib/oeqa/targetcontrol.

[OE-core][langdale 16/26] oeqa/targetcontrol: do not set dump_host_cmds redundantly

From: Enrico Jörns This is already set above, thus simply use the set value from there. Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry picked from commit 2f6571ffb23b1a0b5bd6a1212fc108e536f04539) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/targetcontrol.py | 2 +- 1 fil

[OE-core][langdale 14/26] oeqa/selftest/cases/runqemu: update imports

From: Enrico Jörns 'tempfile' and 'oeqa.utils.command.runCmd' are unused while 'os' is actually used. Signed-off-by: Enrico Jorns Signed-off-by: Richard Purdie (cherry picked from commit 50f766233e83528eebeca92877277374c7193530) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/selftest/cases/r

[OE-core][langdale 13/26] lib/oe/gpg_sign.py: Avoid race when creating .sig files in detach_sign

From: Tobias Hagelborn Move the signature file into place only after it is successfully signed. This to avoid race and corrupted .sig files in cases multiple onging builds write to a shared sstate-cache dir. Signed-off-by: Tobias Hagelborn Signed-off-by: Peter Kjellerstedt Signed-off-by: Richa

[OE-core][langdale 12/26] Revert "runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86"

From: Khem Raj This reverts commit 82e67b82ea8e12aa0b7b9db1d84fec0436dec71b. It was commited as part of https://bugzilla.yoctoproject.org/show_bug.cgi?id=12301 for kernels < 4.15, as of now oldest builder kernel we have is 4.15 on ubuntu 18.04 so we should not require this workaround. Moreover,

[OE-core][langdale 10/26] package.bbclass: check packages name conflict in do_package

From: Fawzi KHABER It is possible to rename packages with the macro PKG:${PN} and result in a package name conflict if the target name exists already. Add a fatal check to prevent this issue to go unnoticed. Fix [Yocto #12060] Reviewed-by: Yoann CONGAL Signed-off-by: Fawzi KHABER Signed-off-

[OE-core][langdale 11/26] oeqa/selftest/cases/package.py: adding unittest for package rename conflicts

From: Fawzi KHABER This Unittest tries to rename a package, using an already used name and fails on do_package. Reviewed-by: Yoann CONGAL Signed-off-by: Fawzi KHABER Signed-off-by: Richard Purdie (cherry picked from commit c3fe173d5196506d89aa464ba56aabcf581a60db) Signed-off-by: Steve Sakoman

[OE-core][langdale 09/26] run-postinsts: Set dependency for ldconfig to avoid boot issues

From: Arturo Buzarra If a package with a postsints script requires ldconfig, the package class adds a ldconfig postinst fragment to initialize it before. Systemd has its own ldconfig.service to initialize it and sometimes if both services are running at the same time in the first boot, the first

[OE-core][langdale 07/26] oeqa/selftest: OESelftestTestContext: convert relative to full path when newbuilddir is provided

From: Jose Quaresma Relative paths in BBLAYERS only works when the new build dir are on the same ascending directory node: . ├── build ├── build-st It works because they share the same ascending relative directory node. So use the full path when the argument newbuilddir is provided to make t

[OE-core][langdale 08/26] oeqa/selftest/reproducible: Split different packages from missing packages output

From: Jose Quaresma When we provide sstate_targets recipes they are reported as missing which is not quite correct because they are proveided to cut build/debugging time. Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni (cherry picked from commit fd70a564d6946fa460638dd04ce2daecf

[OE-core][langdale 05/26] filemap.py: enforce maximum of 4kb block size

From: Andrew Geissler The logic in this script validates that the length of data sections are evenly divisible by the block size. On most systems the block size is 4KB and all is good. Some systems though, such as ppc64le, have a block size larger then 4KB. For example on a POWER9 based ppc64le s

[OE-core][langdale 06/26] oeqs/selftest: OESelftestTestContext: replace the os.environ after subprocess.check_output

From: Jose Quaresma No function change but is needed to simplify the next patch. Signed-off-by: Jose Quaresma Signed-off-by: Alexandre Belloni (cherry picked from commit 193d8f0d6383f54c61f90d58eeb8f41580c2360a) Signed-off-by: Steve Sakoman --- meta/lib/oeqa/selftest/context.py | 10 +---

[OE-core][langdale 04/26] uninative: Upgrade to 3.9 to include glibc 2.37

From: Michael Halstead Update uninative to work with the new glibc 2.37. Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman --- meta/conf/distro/include/yocto-uninative.inc | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/

[OE-core][langdale 02/26] xdg-utils: Fix CVE number

From: Richard Purdie In the previous commit I somehow mixed up and used an incorrect CVE number. Use the correct one. Signed-off-by: Richard Purdie (cherry picked from commit b3e2729f686ff6e16e11590bcd701c057ae5f1e2) Signed-off-by: Steve Sakoman --- .../xdg-utils/{CVE-2020-27748.patch => CVE-

[OE-core][langdale 03/26] tzdata: upgrade to 2023c

From: Ross Burton Drop a backport patch as it is now integrated. Signed-off-by: Ross Burton Signed-off-by: Alexandre Belloni (cherry picked from commit 80d26d1da47dcd9213a7083d9493a7bce0897a57) Signed-off-by: Steve Sakoman --- meta/recipes-extended/timezone/timezone.inc | 6 +- .../timez

[OE-core][langdale 01/26] xdg-utils: Add a patch for CVE-2020-27748

From: Richard Purdie Take a patch submitted upstream for the issue while upstream decide what to do. We don't use thunderbird integration so this isn't an issue for us. Signed-off-by: Richard Purdie (cherry picked from commit b85b7714a44caa70beb2f115483ee52745aa1b97) Signed-off-by: Steve Sakoma

[OE-core][langdale 00/26] Patch review

Please review this set of patches for langdale and have comments back by end of day Monday. Passed a-full on autobuilder: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5152 The following changes since commit 6c9ca2f2de98c84d11beccbfde7c1e26cb25dfb6: scripts/lib/buildstats:

[OE-core][dunfell 0/7] Pull request (cover letter only)

The following changes since commit 1c7d555379c4b0962bccd018870989050d87675f: classes/package: Use gzip for extended package data (2023-03-27 16:29:20 -1000) are available in the Git repository at: https://git.openembedded.org/openembedded-core-contrib stable/dunfell-next http://cgit.open

[OE-core] [PATCH 2/2] cve-extra-exclusion: ignore disputed CVE-2023-23005

Signed-off-by: Yoann Congal Reviewed-by: Frank WOLFF --- meta/conf/distro/include/cve-extra-exclusions.inc | 10 ++ 1 file changed, 10 insertions(+) diff --git a/meta/conf/distro/include/cve-extra-exclusions.inc b/meta/conf/distro/include/cve-extra-exclusions.inc index 0b89598501..439d

[OE-core] [PATCH 1/2] cve-exclusions_6.1: ignore patched CVE-2022-38457 & CVE-2022-40133

Ignore CVE-2022-38457 & CVE-2022-40133 as they looks patched in our 6.1 branch. I've asked the NVD to add the commit as the patch for these CVEs, but in the meantime, other sources seem to agree that the commit fixes these CVEs (and I concur). Signed-off-by: Yoann Congal --- meta/recipes-kernel

[OE-core] [PATCHv2] cargo-update-recipe-crates.bbclass: Do not add name= to crate:// URIs

With the recent change to the crate fetcher, which automatically sets the name for each crate to be versioned, there is no longer a need to explicitly set the name= parameter for each URI. This also results in generated files that are compatible with the crate fetcher in Kirkstone and Langdale. Si

[OE-core] [PATCH] cargo-update-recipe-crates.bbclass: Do not add name= to crate:// URIs

With the recent change to the crate fetcher, which automatically sets the name to for each crate to be versioned, there is no longer a need to explicitly set the name= parameter for each URI. This also results in generated files that are compatible with the crate fetcher in Kirkstone and Langdale.

[OE-core] [PATCH 2/2] python3-bcrypt-crates.inc: regenerate with updated bbclass

* it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.sch...@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-bcrypt-crates.inc bitbake -c update

[OE-core] [PATCH 1/2] python3-cryptography-crates.inc: regenerate with updated bbclass

* it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.sch...@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-cryptography-crates.inc bitbake -c

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2.rc1)

Hi Jing Hui, Unfortunately there is an issue that has come up regarding the recent crate fetcher changes. This means we're going to need to move to an rc2 build so we should probably stop testing rc1. I'll hopefully have that ready soon. Sorry about the churn. Cheers, Richard On Thu, 2023-04-

Re: [OE-core] [PATCH] cve-extra-exclusions.inc: Exclude some issues not present in linux-yocto

On 4/6/23 10:36, Richard Purdie wrote: > On Thu, 2023-04-06 at 10:23 +0200, Yoann Congal wrote: >> >> For CVE-2022-38457 and CVE-2022-40133 > > This one appears to be fixed for 6.1 only with this change: > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=a309c7194e8

Re: [OE-core] [PATCH v2] migration-guides: update 4.2 migration and release notes

On Thu, 2023-04-06 at 11:12 +0200, Michael Opdenacker via lists.openembedded.org wrote: > From: Michael Opdenacker > > Signed-off-by: Michael Opdenacker > CC: Frederic Martinsons > CC: Marta Rybczynska > CC: Paul Eggleton > CC: Alex Kiernan > > --- > > Changes in V2: > - Add details about

[OE-core] [PATCH v2] migration-guides: update 4.2 migration and release notes

From: Michael Opdenacker Signed-off-by: Michael Opdenacker CC: Frederic Martinsons CC: Marta Rybczynska CC: Paul Eggleton CC: Alex Kiernan --- Changes in V2: - Add details about filling checksums using the 'cargo-update-recipe-crates' class, as suggested by Frederic Martinsons. --- .../

[OE-core] [PATCH] cve-extra-exclusions: ignore inapplicable linux-yocto CVEs

CVEs CVE-2023-0179, CVE-2023-1079 and CVE-2023-1513 are patched in our kernels but appear as active because the NVD database is not up to date. Signed-off-by: Yoann Congal Reviewed-by: Frank WOLFF --- .../distro/include/cve-extra-exclusions.inc | 25 +++ 1 file changed, 25 ins

Re: [OE-core] [RFC][PATCH] wic: use part_name when defined

Hi, On Wed, Mar 29, 2023 at 5:55 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Wed, 2023-03-22 at 16:54 +0100, dit.koz...@kynetics.com wrote: > > From: Dit Kozmaj > > > > So far part.label has been used to define GPT partition label even if > > part.part_name was defined. >

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.2.rc1)

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-4.2.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2. NUC 7 3. ADL 4. TGL

Re: [docs] [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes

Le jeu. 6 avr. 2023, 10:23, Michael Opdenacker < michael.opdenac...@bootlin.com> a écrit : > Hi Frederic > > On 05.04.23 at 21:04, Frederic Martinsons wrote: > > > > > > > > Any more Rust changes we should mention in the migration notes? > > > > > > Maybe mention a specific procedure to update

[OE-core] [PATCH 3/3] kickstart: Expand label and part-name doc

From: Dit Kozmaj Update --label and --part-name documentation to reflect the behaviour with GPT partition format. Signed-off-by: Dit Kozmaj --- documentation/ref-manual/kickstart.rst | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/documentation/ref-manual/kickstart.rst

[OE-core] [PATCH 2/3] selftest: wic: Add test for --part-name argument

From: Dit Kozmaj Add test for wic --part-name argument in .wks file. Test three different cases: - Set only the --part-name argument. - Set only the --label argument. In this case the GPT partition label is set to the value of --label for compatibility reasons. - Set both. In this case the code

[OE-core] [PATCH 1/3] wic: use part_name when defined

From: Dit Kozmaj So far part.label has been used to define GPT partition label even if part.part_name was defined. Fix the code to use part.part_name whenever available, as it makes sense to have a GPT partition label which is different from the contained filesystem label. Signed-off-by: Dit Koz

Re: [OE-core] [PATCH] cve-extra-exclusions.inc: Exclude some issues not present in linux-yocto

On Thu, 2023-04-06 at 10:23 +0200, Yoann Congal wrote: > > > > > > Should I write a patch including the missing CVEs from Geoffrey's patch > > > or that will clash with your work-in-progress? > > > > I haven't done anything yet with these so I'd happily take a patch! > > I'll send a patch later

Re: [OE-core] [PATCH] cve-extra-exclusions.inc: Exclude some issues not present in linux-yocto

Hi On 4/5/23 11:55, Richard Purdie wrote: > On Wed, 2023-04-05 at 11:51 +0200, Yoann Congal wrote: >> Hi Richard, >> >> On 4/5/23 00:26, Richard Purdie wrote: >>> .../... >>> Thanks, I tweaked those bits. I did a bit more research and the other >>> easier looking linux-yocto ones to mark up are li

Re: [docs] [OE-core] [PATCH] migration-guides: update 4.2 migration and release notes

Hi Frederic On 05.04.23 at 21:04, Frederic Martinsons wrote: Any more Rust changes we should mention in the migration notes? Maybe mention a specific procedure to update a cargo based recipe from scratch (i.e. a recipe that didn't use the cargo-update-recipe-crates inheritance): To b

Re: [OE-core] [PATCH] yocto-check-layer: scan additional layers for tested layer dependencies

On Wed, Apr 5, 2023 at 2:29 PM Marek Vasut wrote: > On 4/5/23 08:48, Nicolas Dechesne wrote: > > On Tue, Apr 4, 2023 at 11:36 PM Marek Vasut wrote: > > > >> In case a LAYERDEPENDS of a tested layer contains a dependency which is > >> present in additional layers, such dependency does not get pul