Re: [OE-core] [PATCH 0/6] keep reducing regression reports noise

Hello Tim, On 3/1/23 07:24, Tim Orling wrote: > On Tue, Feb 28, 2023 at 10:10 AM Alexis Lothoré via lists.openembedded.org > > > wrote: > > From: Alexis Lothoré > > >

[OE-core][dunfell][PATCH] gcc: Fix inconsistent noexcept specifier for valarray in libstdc++

From: Virendra Thakur Backport of gcc upstream commit 2b2d97fc545635a0f6aa9c9ee3b017394bc494bf to gcc release 9.5.0. This fix is available to all release-branches except releases/gcc-9 because upstream do not support gcc-9 now. Signed-off-by: Virendra Thakur ---

Re: [OE-core] Yocto reproducibilty issue :: rust-llvm binary differences

You should not copy things between sysroot and ${D}. There is post-processing between those steps, so do it only between sysroots please. Alex On Wed, 1 Mar 2023 at 07:28, Sundeep KOKKONDA wrote: > > Hello, > > > > I tried to copy the libLTO.so to ${D}. But this shows ERROR: >

Re: [OE-core] Yocto reproducibilty issue :: rust-llvm binary differences

Hello, I tried to copy the libLTO.so to ${D}. But this shows ERROR: rust-llvm-1.67.0-r0 do_package_qa: QA Issue: -dev package rust-llvm-dev contains non-symlink .so '/usr/lib/llvm-rust/lib/libLTO.so' [dev-elf] and I had a look into symlink where it points... The libLTO.so files RPATH in ${D} &

Re: [OE-core] [PATCH 0/6] keep reducing regression reports noise

On Tue, Feb 28, 2023 at 10:10 AM Alexis Lothoré via lists.openembedded.org wrote: > From: Alexis Lothoré > > Hello, > here is another batch of fixes to reduce noise in regression reports. > Fixes are > directly linked to main noise sources seen in 4.2_M3 regression report > ([1]). > - fix some

[OE-core] [PATCH] kernel: Add kernel specific OBJDUMP

This helps in switching toolchains cleanly for kernel build between gcc and clang Currently, some kernels allow building with clang but not all the distro might use clang as default system compiler but kernel may demand gcc which is provided via KERNEL_* variables, however kernel does use OBJCOPY

[OE-core] [patch][dunfell] tiff: fix multiple CVEs

From: Chee Yang Lee import patches from debian http://security.debian.org/debian-security/pool/updates/main/t/tiff/tiff_4.1.0+git191117-2~deb10u7.debian.tar.xz fix multiple CVEs: CVE-2022-3570 CVE-2022-3597 CVE-2022-3598 CVE-2022-3599 CVE-2022-3626 CVE-2022-3627 CVE-2022-3970 CVE-2022-48281

[OE-core] [kirkstone][PATCH] less: backport the fix for CVE-2022-46663

Upstream-Status: Backport from https://github.com/gwsw/less/commit/a78e1351113cef564d790a730d657a321624d79c Signed-off-by: Hitendra Prajapati --- .../less/less/CVE-2022-46663.patch| 31 +++ meta/recipes-extended/less/less_600.bb| 1 + 2 files changed, 32

Re: [OE-core] [dunfell 1/4] cve-extra-exclusions.inc: Use CVE_CHECK_WHITELIST

Hi Ranjitsinh, Any specific reason to ignore the QEMU: CVE-2021-20255  CVE ?? Regards, Hitendra -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#177863): https://lists.openembedded.org/g/openembedded-core/message/177863 Mute This Topic:

Re: [OE-core] [meta-java] icedtea7-native build fails on kirkstone and in master

Hi all, I met this error after I had changed my build environment from Ubuntu22.04 to Ubuntu 24.04. And this patch does work. But why hasn't this patch not been merged yet? Best regards Lei > -Original Message- > From: openembedded-core@lists.openembedded.org > On Behalf Of Bartosz >

[OE-core] [pseudo][PATCH 1/1] pseudo_util.c: Open file with O_CLOEXEC to avoid fd leak

From: Pavel Modilaynen Use close-on-exec (O_CLOEXEC) flag when open log file to make sure its file descriptor is not leaked to parent process on fork/exec. Fixes [YOCTO #13311] Signed-off-by: Mingli Yu Signed-off-by: Yoann Congal --- pseudo_util.c | 2 +- 1 file changed, 1 insertion(+), 1

[OE-core] [pseudo][PATCH 0/1] pseudo_util.c: Open file with O_CLOEXEC to avoid fd leak

Hi, The following patch is the work done by Pavel Modilaynen in 04-2019 on [YOCTO #13311]. Then, Mingli Yu tried to get it merged in 01-2020 without success. I just added a ref to [YOCTO #13311] in the commit message. Best regards, Yoann Pavel Modilaynen (1): pseudo_util.c: Open file with

Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

On 28/02/2023 17:50:05+, Richard Purdie wrote: > On Tue, 2023-02-28 at 08:43 -0800, Khem Raj wrote: > > On Tue, Feb 28, 2023 at 8:18 AM Alexandre Belloni > > wrote: > > > > > > Hello Khem, > > > > > > As discussed I gave it a go again and got this: > > > > > > >

Re: [OE-core] [PATCH] enchant2: upgrade 2.3.3 -> 2.3.4

Hello, This failed on the autobuilders: https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2471/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/6734/steps/11/logs/errors On 28/02/2023 17:49:16+0800, wangmy wrote: > From: Wang Mingyu > >

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

Thank you for the explanation and the work done. Could you contact me off list so that we confirm what and where was send? 14 days is longer than I've ever had as a response time from NVD. Kind regards Marta On Tue, 28 Feb 2023, 10:05 Geoffrey GIRY, wrote: > Hello Marta, Richard, > > We sent

Re: [OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

> -Original Message- > From: Richard Purdie > Sent: Tuesday, February 28, 2023 4:04 AM > To: michael.opdenac...@bootlin.com; Tom Hochstein > ; OE-core c...@lists.openembedded.org> > Cc: YP docs mailing list > Subject: Re: [OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: >

[OE-core] [PATCH 1/6] scripts/resulttool: call fixup_ptest_names in regression_common

From: Alexis Lothoré ptests names not only need to be fixed for regression based on git testresults but also for testsresults provided "manually" Move ptests naming fixup in regression_common to share the fixup between both regression use cases Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH 3/6] oeqa/selftest/resulttool: fix fake data

From: Alexis Lothoré resulttool searches for "status" field, not "STATUS", in results. This fix is more to avoid confusion than fixing anything, since the updated tests are about regression.can_be_compared, which does not check for "status" Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH 3/6] oeqa/selftest/resulttool: fix fake data used for testing

From: Alexis Lothoré resulttool searches for "status" field, not "STATUS", in results. This fix is more to avoid confusion than fixing anything, since the updated tests are about regression.can_be_compared, which does not check for "status" Signed-off-by: Alexis Lothoré ---

[OE-core] [PATCH 6/6] scripts/resulttool: do not count newly passing tests as regressions

From: Alexis Lothoré resulttool regression module simply compare a base test status to a target test result status. This approach raises many false positives since all XXX -> PASS transitions (XXX being any status different from PASS) are flagged as regression. - Do not list XXX -> PASS

[OE-core] [PATCH 2/6] oeqa/selftest/resulttool: fix ptest tests

From: Alexis Lothoré There are multiple issues with the tests for the ptest fixup mechanism introduced in c45d58f003e8d8b323169ca9d479dc49c43a9974: - the feature does not impact regression.can_be_compared but directly the comparison step in regression.regression_common - the "status" field was

[OE-core] [PATCH 4/6] scripts/resulttool: fix ptests results containing a non reproducible path

From: Alexis Lothoré Some ptests results may be wrongly sampled, resulting in some part of the error being propagated in test name. For example: "ptestresult.binutils-ld.in testcase

[OE-core] [PATCH 5/6] oeqa/selftest/resulttool: add test for error propagation in test name filtering

From: Alexis Lothoré Signed-off-by: Alexis Lothoré --- .../oeqa/selftest/cases/resulttooltests.py| 24 +++ 1 file changed, 24 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/resulttooltests.py b/meta/lib/oeqa/selftest/cases/resulttooltests.py index

[OE-core] [PATCH 0/6] keep reducing regression reports noise

From: Alexis Lothoré Hello, here is another batch of fixes to reduce noise in regression reports. Fixes are directly linked to main noise sources seen in 4.2_M3 regression report ([1]). - fix some existing selftests for resulttool - add more filters for ptests incorrectly logging failures. The

[OE-core] [PATCH 2/6] oeqa/selftest/resulttool: fix ptest filtering tests

From: Alexis Lothoré There are multiple issues with the tests for the ptest fixup mechanism introduced in c45d58f003e8d8b323169ca9d479dc49c43a9974: - the feature does not impact regression.can_be_compared but directly the comparison step in regression.regression_common - the "status" field was

Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

On Tue, 2023-02-28 at 08:43 -0800, Khem Raj wrote: > On Tue, Feb 28, 2023 at 8:18 AM Alexandre Belloni > wrote: > > > > Hello Khem, > > > > As discussed I gave it a go again and got this: > > > > > /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: > > > linux-tdep.o: in

Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

On Tue, Feb 28, 2023 at 8:18 AM Alexandre Belloni wrote: > > Hello Khem, > > As discussed I gave it a go again and got this: > > | /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: > linux-tdep.o: in function `linux_corefile_thread(thread_info*, > linux_corefile_thread_data*)':

Re: [OE-core] [PATCH] binutils: Enable --enable-new-dtags

Hello Khem, As discussed I gave it a go again and got this: | /home/pokybuild/yocto-worker/qemuarm/build/build/tmp/hosttools/ld: linux-tdep.o: in function `linux_corefile_thread(thread_info*, linux_corefile_thread_data*)': | linux-tdep.c:(.text+0x13ac): undefined reference to

Re: [OE-core] PEP 517 and PEP 621 support on Dunfell?

On 28 Feb 2023, at 15:00, Ernst Sjöstrand via lists.openembedded.org wrote: > more and more Python projects are removing their setup.py and setup.cfg and > switching to pyproject.toml. That unfortunately means you can't install those > packages on Yocto Dunfell. > > Would it be reasonable to

[OE-core] Yocto Project Status 28 February 2023 (WW09)

Current Dev Position: YP 4.2 M4 Next Deadline: 3rd April 2023 YP 4.2 M4 Build Next Team Meetings: * Bug Triage meeting Thursday March 2nd 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *

Re: [oe-core][PATCH 1/1] wic: Add support for F2FS in WIC rootfs plugin

Hello, this failed on the autobuilders: ERROR: Nothing PROVIDES 'f2fs-tools-native' (but /home/pokybuild/yocto-worker/beaglebone/build/meta/recipes-sato/images/core-image-sato.bb, /home/pokybuild/yocto-worker/beaglebone/build/meta/recipes-sato/images/core-image-sato-sdk.bb,

Re: [OE-core] [PATCH] meta/lib/oeqa/selftest/cases/wic: Add tests for configuring kernel image install into boot partition.

Hello, This caused: AssertionError: Command 'wic cp /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-1632991/wic-tmp/tmpy7vqghuf-202302281124-sda.direct:1 /tmp/tmp9xlwzw5t' returned non-zero exit status 1: ERROR: Can't find executable 'mcopy' so bitbake("mtools-native") was not

[oe-core][PATCH 1/1] wic: Add support for F2FS in WIC rootfs plugin

Building F2FS rootfs is supported in Yocto/OpenEmbedded - see image_types.bbclass, but not in WIC. This adds it as a nice convenience feature. F2FS needs a minimum size of ~500M to operate correctly due to an overprovision functionality. Signed-off-by: Anna-Lena Marx ---

[oe-core][PATCH 0/1] wic: Add support for F2FS in WIC rootfs plugin

Hi there, Yocto/OpenEmbedded supports generating F2FS rootfs in general for years but WIC does not, yet. The patch adds support to do so in the "rootfs" WIC plugin. Generating the F2FS rootfs follows mostly the way it is implemented in meta/classes-recipe/image_types.bbclass. Thereby, F2FS

[OE-core] PEP 517 and PEP 621 support on Dunfell?

Hi, more and more Python projects are removing their setup.py and setup.cfg and switching to pyproject.toml. That unfortunately means you can't install those packages on Yocto Dunfell. Would it be reasonable to backport support for this to Dunfell? I see that the changes done for this support

Re: [OE-core] [PATCH] make: update from 4.4 to 4.4.1

Hello, This causes: WARNING: make-4.4.1-r0 do_package_qa: QA Issue: File /usr/bin/make in package make contains reference to TMPDIR [buildpaths] On 27/02/2023 17:36:19-0800, Randy MacLeod wrote: > Drop the backported sigpipe.patch > > NEWS: > Version 4.4.1 (26 Feb 2023) > > This release is

[oe-core][PATCH] libsdl2: add missing libdecor RDEPEND

libdecor is dlopen'ed ... add it as RDEPEND to make it work on runtime Signed-off-by: Markus Volk --- meta/recipes-graphics/libsdl2/libsdl2_2.26.3.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.26.3.bb

Re: [OE-core] multiconfig: Build breaks parsing recipes for other config layer

Mikko and Joshua, Thanks for the guidance. I tried using BBMASK and that wasn't working for me. After a little digging I figured out that the BSP for this new board is based on an old enough version of gatesgarth that it doesn't have the patch for BBMASK multiconfig support. I've been

Re: [OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

On Tue, Feb 28, 2023 at 10:52 AM Michael Opdenacker via lists.openembedded.org wrote: > Greetings, > > Thank you all for your replies and comments! > > On 24.02.23 at 00:24, Tom Hochstein wrote: > > I agree. The problem I have with these variable names is that it's > ambiguous whether the

Re: [OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

On Tue, 2023-02-28 at 10:52 +0100, Michael Opdenacker via lists.openembedded.org wrote: > Greetings, > > Thank you all for your replies and comments! > > On 24.02.23 at 00:24, Tom Hochstein wrote: > > I agree. The problem I have with these variable names is that it's > > ambiguous whether the

Re: [OE-core] [DISTRO|MACHINE]_FEATURES_BACKFILL_CONSIDERED: confusing variable names?

Greetings, Thank you all for your replies and comments! On 24.02.23 at 00:24, Tom Hochstein wrote: I agree. The problem I have with these variable names is that it's ambiguous whether the features will be included or excluded from the backfill. All you can tell from the names is that the

[OE-core] [PATCH] python3-zipp: upgrade 3.14.0 -> 3.15.0

From: Wang Mingyu Changelog: == gh-102209: "test_implied_dirs_performance" now tests measures the time complexity experimentally. Signed-off-by: Wang Mingyu --- .../python/{python3-zipp_3.14.0.bb => python3-zipp_3.15.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[OE-core] [PATCH] libnotify: upgrade 0.8.1 -> 0.8.2

From: Wang Mingyu Changelog: === * Set new summary for library * docs: port to gi-docgen * docs: Fix URL to Desktop Notification Spec * meson: replace deprecated meson.source_root() calls * meson: bump minimum meson version to 0.58 * Introspection docs fixes Signed-off-by: Wang Mingyu

[OE-core] [PATCH] python3-more-itertools: upgrade 9.0.0 -> 9.1.0

From: Wang Mingyu Changelog: === Fix trailing space Fix malformed table Signed-off-by: Wang Mingyu --- ...-more-itertools_9.0.0.bb => python3-more-itertools_9.1.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename

[OE-core] [PATCH] enchant2: upgrade 2.3.3 -> 2.3.4

From: Wang Mingyu Changelog: === - Document the personal wordlist format. - Improve the man pages in various ways, and make online versions, now linked from the web site. - Fix some potential crashes (double-free and NULL dereferences). - Update the build system to use autoconf 2.71.

[OE-core] [PATCH] diffoscope: upgrade 235 -> 236

From: Wang Mingyu Signed-off-by: Wang Mingyu --- .../diffoscope/{diffoscope_235.bb => diffoscope_236.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-support/diffoscope/{diffoscope_235.bb => diffoscope_236.bb} (92%) diff --git

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

Hello Marta, Richard, We sent to NVD an update for one CVE (CVE-2020-27784) 14 days ago, we are still waiting for an answer. This is the first time we ever do this, so we did send only the first as a test. When the change is accepted, we will send updates requests for each already patched CVE.