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

2024-01-23 Thread Jing Hui Tham
Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.31.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. MinnowBoard Turbot - 32bit

Re: [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.

2024-01-23 Thread Richard Purdie
On Tue, 2024-01-23 at 05:16 -0800, Shinde, Yash via lists.openembedded.org wrote: > From: Yash Shinde > > Fixes: Exception: no cargo executable found at > > `${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo` > > Fix the cargo binary path error on

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

2024-01-23 Thread Jing Hui Tham
Hi All, QA for yocto-5.0_M2.rc1 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new issue found. Thanks, Jing Hui >

Re: [OE-core] [PATCH v2] binutils: Add patch to fix CVE-2023-25584

2024-01-23 Thread Alexandre Belloni via lists.openembedded.org
Hello, This doesn't apply on master, please specify which branch this is for. On 22/01/2024 14:29:56+0530, Ashishx88 wrote: > Upstream-Status: Backport > [https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=77c225bdeb410cf60da804879ad41622f5f1aa44] > > CVE: CVE-2023-25584 > Signed-off-by:

[OE-core] [PATCH] perl: Fix perl-module-* being ignored via COMPLEMENTARY_GLOB

2024-01-23 Thread Lyu, William via lists.openembedded.org
From: William Lyu When perl-modules is added via COMPLEMENTARY_GLOB, all perl-module-* packages recommended by perl-modules are ignored due to the defined behavior of COMPLEMENTARY_GLOB. This patch changes the relationship between perl-modules and all of its perl-module-* from RRECOMMENDS to

[OE-core] Strange NFS file issue affecting sstate test

2024-01-23 Thread Richard Purdie
In this commit we removed some checks on the basis we wanted to better understand them: https://git.yoctoproject.org/poky/commit/?id=4675bbb757a4755e80914afb6840a640f292fc08 We ran into the file not found issue in this build:

[OE-core] [PATCH] python3-subunit: Add missing module dependency

2024-01-23 Thread Richard Purdie
In version 1.4.3: * Subunit now has a dependency on an external iso8601 module rather than shipping its own. so add the missing dependency. Signed-off-by: Richard Purdie --- meta/recipes-devtools/python/python3-subunit_1.4.4.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.

2024-01-23 Thread Richard Purdie
On Tue, 2024-01-23 at 20:07 +, Richard Purdie via lists.openembedded.org wrote: > On Tue, 2024-01-23 at 05:16 -0800, Shinde, Yash via > lists.openembedded.org wrote: > > From: Yash Shinde > > > > Fixes: Exception: no cargo executable found at > > > >

Re: [OE-core] [PATCH] xz: Add ptest support

2024-01-23 Thread Chi Xu
There are two types of cases in xz pkg: executables and POSIX shell scripts. I only integrated executables in V1 patch. There are two script cases "test_compress.sh" and "test_scripts.sh", create_compress_files is a test tool which will be called by "test_compress.sh". I will install both types

[OE-core][dunfell][PATCH] pam: Fix for CVE-2024-22365

2024-01-23 Thread Vijay Anusuri via lists.openembedded.org
From: Vijay Anusuri Upstream-Status: Backport from https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb Signed-off-by: Vijay Anusuri --- .../pam/libpam/CVE-2024-22365.patch | 59 +++ meta/recipes-extended/pam/libpam_1.3.1.bb |

Re: [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
On 24-01-2024 01:37, Richard Purdie wrote: CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. On Tue, 2024-01-23 at 05:16 -0800, Shinde, Yash via lists.openembedded.org wrote:

Re: [OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
On 24-01-2024 02:47, Richard Purdie wrote: CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. On Tue, 2024-01-23 at 20:07 +, Richard Purdie via lists.openembedded.org wrote:

[OE-core] [PATCH 4/4] grub2: upgrade 2.06 -> 2.12

2024-01-23 Thread Anuj Mittal
Drop patches that have been upstreamed. Refresh others. This version dropped extra_deps.lst from the tarball [1] and that leads to build failures. Restore it in do_configure for now. [1] https://git.savannah.gnu.org/cgit/grub.git/commit/?id=b835601c7639ed1890f2d3db91900a8506011a8e

[OE-core] [PATCH 1/4] bluez5: upgrade 5.71 -> 5.72

2024-01-23 Thread Anuj Mittal
Signed-off-by: Anuj Mittal --- .../bluez5/bluez5/0001-test-gatt-Fix-hung-issue.patch | 6 +++--- ...sts-add-a-target-for-building-tests-without-runnin.patch | 4 ++-- .../0004-src-shared-util.c-include-linux-limits.h.patch | 4 ++-- .../bluez5/{bluez5_5.71.bb => bluez5_5.72.bb}

[OE-core] [PATCH 3/4] libpsl: upgrade 0.21.2 -> 0.21.5

2024-01-23 Thread Anuj Mittal
License-Update: Copyright dates changed Signed-off-by: Anuj Mittal --- .../libpsl/{libpsl_0.21.2.bb => libpsl_0.21.5.bb} | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) rename meta/recipes-support/libpsl/{libpsl_0.21.2.bb => libpsl_0.21.5.bb} (79%) diff --git

[OE-core] [PATCH 2/4] cronie: upgrade 1.7.0 -> 1.7.1

2024-01-23 Thread Anuj Mittal
Signed-off-by: Anuj Mittal --- .../cronie/cronie/crond_pam_config.patch | 10 ++ .../cronie/{cronie_1.7.0.bb => cronie_1.7.1.bb}| 2 +- 2 files changed, 11 insertions(+), 1 deletion(-) rename meta/recipes-extended/cronie/{cronie_1.7.0.bb => cronie_1.7.1.bb} (97%)

[OE-core] [PATCH] mdadm: Disable ptests

2024-01-23 Thread Pavel Zhukov
As agreed upon in the bug triage meeting, disable mdadm ptest for the time being Related: [Yocto #15181] [Yocto #15159] [Yocto #15308] [Yocto #15309] Signed-off-by: Pavel Zhukov --- meta/conf/distro/include/ptest-packagelists.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [OE-core] [PATCH] xz: Add ptest support

2024-01-23 Thread Alexander Kanavin
On Tue, 23 Jan 2024 at 09:21, Chi Xu wrote: > +tests=`find . -type f -executable | sed 's/\.\///g'` > + > +for i in ${tests}; do > +if [ $i == "create_compress_files" ]; then > +./$i > +if [ $? -eq 0 ]; then > +echo "PASS: $i" > +else > +echo

[OE-core] [PATCH] xz: Add ptest support

2024-01-23 Thread Chi Xu
72 test cases in all and all test cases PASS. Test results on qemux86-64: root@qemux86-64:~# ptest-runner xz START: ptest-runner 2024-01-23T07:37 BEGIN: /usr/lib/xz/ptest === test_block_header.c === PASS: test_lzma_block_header_size PASS: test_lzma_block_header_encode PASS:

[OE-core] Patchtest results for [PATCH 1/4] bluez5: upgrade 5.71 -> 5.72

2024-01-23 Thread Patchtest
Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/1-4-bluez5-upgrade-5.71---5.72.patch FAIL: test commit message presence: Please include a commit message on your

[OE-core] Patchtest results for [PATCH 2/4] cronie: upgrade 1.7.0 -> 1.7.1

2024-01-23 Thread Patchtest
Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/2-4-cronie-upgrade-1.7.0---1.7.1.patch FAIL: test commit message presence: Please include a commit message on your

Re: [OE-core] [PATCH] shadow: replace static linking with dynamic libraries in a custom location and bundled with shadow

2024-01-23 Thread Alexander Kanavin
On Tue, 23 Jan 2024 at 02:13, Dmitry Baryshkov wrote: > > On Fri, 19 Jan 2024 at 14:43, Alexander Kanavin > wrote: > > > > Despite our efforts to make static linking work, there have > > been new reports of bizarre build failures: > >

Re: [OE-core] [PATCH] mdadm: Disable ptests

2024-01-23 Thread Alexander Kanavin
I think it needs to be removed from PTESTS_SLOW at the same time? Alex On Tue, 23 Jan 2024 at 10:06, Pavel Zhukov wrote: > > As agreed upon in the bug triage meeting, disable mdadm ptest for the time > being > > Related: [Yocto #15181] [Yocto #15159] [Yocto #15308] [Yocto #15309] > >

[OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: Exception: no cargo executable found at `${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo` Fix the cargo binary path error on oe-selftest and path set to rust-snapshot dir. Patch sent to upstream-

[OE-core] [PATCH v3 3/7] rust: Enable RUSTC_BOOTSTRAP to use nightly features during rust oe-selftest.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: error: the option `Z` is only accepted on the nightly compiler When rust.channel is set to either beta or stable, we can't use nightly features on bootstrap without RUSTC_BOOTSTRAP. Set RUSTC_BOOTSTRAP=1 to use nightly features on stable or beta.

[OE-core] [PATCH v3 4/7] rust: Fix assertion failure error on oe-selftest

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: thread 'main' panicked at 'assertion failed: `(left == right)` left: `x86_64-unknown-linux-gnu`, right: `x86_64-poky-linux-gnu`: Cannot obtain compiler for non-native build triple at stage 0', compile.rs:1474:13 Add correct target value for

[OE-core] [PATCH v3 2/7] rust: detect user-specified custom targets in compiletest

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: thread 'main' panicked at 'failed to gather the target spec for '-unknown-linux-gnu', synthetic_targets.rs:66:9 Detect and fetch custom target configurations when rustc is bootstrapped in rust oe-selftest. Signed-off-by: Yash Shinde ---

[OE-core] [PATCH v3 5/7] rust: Add new tests in the exclude list for rust oe-selftest

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Add newly failing tests cases in the exclude list for rust oe-selftest. Signed-off-by: Yash Shinde --- meta/lib/oeqa/selftest/cases/rust.py | 37 +++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git

[OE-core] [PATCH v3 6/7] rust: Remove the test cases whose parent dir is also present in the exclude list

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde To avoid overlap and redundancy of rust tests, remove the test cases whose parent dir is already excluded. Tests which are failing from below dirs are removed as these dirs are already present in exclude list tests/run-make tests/rustdoc

[OE-core] [PATCH v3 7/7] rust: Enable rust oe-selftest.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde * Enable rust oe-selftest and sort the overall added test cases. * Include the dependent patches for rust oe-selftest in meta/recipes-devtools/rust/rust-source.inc * Disable rust oe-selftest for mips32 target (Rust upstream has classified it into tier 3 target, for which

Re: [OE-core] [PATCH V2] tcmode-default.inc: use ?= to set PREFERRED_VERSION_llvm/llvm-native/nativesdk-llvm

2024-01-23 Thread Martin Jansa
-1 This doesn't fix the issue, just makes the work around in other layers a bit easier to implement. But those other layers will still need to update whenever llvm recipe version is updated in oe-core which is annoying and unnecessary. I have to do the same with LLVM_PREFERRED_VERSION as it was

Re: [OE-core] [PATCH] perl: Fix perl-module-* being ignored via COMPLEMENTARY_GLOB

2024-01-23 Thread Alexander Kanavin
On Tue, 23 Jan 2024 at 00:51, Lyu, William via lists.openembedded.org wrote: > > Do you have some examples of these packages which don't exist? > > > > I'd like to understand why they don't exist and perhaps not have them > > listed in PACKAGES in the first place. Creating a load of empty/useless

Re: [OE-core] [PATCH] shadow: replace static linking with dynamic libraries in a custom location and bundled with shadow

2024-01-23 Thread Dmitry Baryshkov
On Tue, 23 Jan 2024 at 11:13, Alexander Kanavin wrote: > > On Tue, 23 Jan 2024 at 02:13, Dmitry Baryshkov wrote: > > > > On Fri, 19 Jan 2024 at 14:43, Alexander Kanavin > > wrote: > > > > > > Despite our efforts to make static linking work, there have > > > been new reports of bizarre build

Re: [OE-core] [PATCH] binutils : CVE-2023-25584

2024-01-23 Thread Richard Purdie
On Mon, 2024-01-22 at 21:52 -0800, Khem Raj wrote: > On Mon, Jan 22, 2024 at 9:15 PM Ashishx88 > wrote: > > > > Hi Khem Raj , > > > > Thanks for the input . > > Do i need to submit v3 with the space fixed ? > > Just trying to get idea w.r.t process > > yes please. I think you also need to

[OE-core] [PATCH v3 0/3] devtool: modify: add support for multiple source

2024-01-23 Thread Julien Stephan
Hello all, As we discussed in #15162, I tried to implement a devtool unpack tracer. I did manage to get a list of files unpacked after do_unpack and manually copy them into WORKDIR but: - unpack tracer just tells us the url and the unpack dir, but does not directly give the unpacked files. Of

[OE-core] [PATCH v3 1/3] externalsrc: fix task dependency for do_populate_lic

2024-01-23 Thread Julien Stephan
do_populate_lic dependencies are defined inside license.bbclass such as: addtask populate_lic after do_patch before do_build but externalsrc deletes the do_patch task, so the only dependency left for do_populate_lic is "before do_build" On a devtool context, when doing devtool modify, sources

[OE-core] [PATCH v3 2/3] devtool: modify: add support for multiple source in SRC_URI

2024-01-23 Thread Julien Stephan
[YOCTO #15162] when doing devtool modify, sources are extracted into a devtool temporary workdir. The main source is moved inside build/workspace/sources/${BPN}/ and local files are moved inside build/workspace/sources/${BPN}/oe-local-files. Secondary sources are currently not handled and are

[OE-core] [PATCH v3 3/3] oeqa/selftest/devtool: add test for recipes with multiple sources in SRC_URI

2024-01-23 Thread Julien Stephan
add a non regression test for devtool modify/build on recipe having several sources in SRC_URI Signed-off-by: Julien Stephan --- meta/lib/oeqa/selftest/cases/devtool.py | 26 + 1 file changed, 26 insertions(+) diff --git a/meta/lib/oeqa/selftest/cases/devtool.py

[OE-core] [PATCH] pulseaudio: Update to 17.0

2024-01-23 Thread Fabio Estevam
From: Fabio Estevam Update to pulseaudio 17.0 version. Since pulseaudio commit e96d278bfc51 ("daemon/meson.build: Install dbus policy in /usr, not /etc"), ${datadir} needs to be passed in FILES, otherwise the following QA error is seen: ERROR: pulseaudio-17.0-r0 do_package: QA Issue:

Re: [OE-core] [PATCH v5 2/3] mesa: add support for RustiCL under PACKAGECONFIG "opencl"

2024-01-23 Thread Antoine Coutant
On 30/12/2023 22:02, Richard Purdie wrote: On Sat, 2023-12-30 at 21:14 +0200, Dmitry Baryshkov wrote: From: Zoltán Böszörményi Mesa now has two OpenCL implementations: Clover (older one) and RustiCL (newer one). Extend the "opencl" package config to include both implementations into the

Re: [OE-core] [PATCH v5 3/3] mesa: fix building of RustiCL + nouveau

2024-01-23 Thread Antoine Coutant
On 30/12/2023 20:14, Dmitry Baryshkov wrote: Incorporate a patch by Karol Herbst, fixing nouveau / libgalliumvl dependency. Signed-off-by: Dmitry Baryshkov --- meta/recipes-graphics/mesa/files/26680.patch | 236 +++ meta/recipes-graphics/mesa/mesa.inc | 1 + 2

[OE-core] [PATCH v3 6/7] rust: Remove the test cases whose parent dir is also present in the exclude list

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde To avoid overlap and redundancy of rust tests, remove the test cases whose parent dir is already excluded. Tests which are failing from below dirs are removed as these dirs are already present in exclude list tests/run-make tests/rustdoc

[OE-core] [PATCH v3 7/7] rust: Enable rust oe-selftest.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde * Enable rust oe-selftest. * Include the dependent patches for rust oe-selftest in meta/recipes-devtools/rust/rust-source.inc * Disable rust oe-selftest for mips32 target (Rust upstream has classified it into tier 3 target, for which the Rust project does not build or

[OE-core] [PATCH v3 3/7] rust: Enable RUSTC_BOOTSTRAP to use nightly features during rust oe-selftest.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: error: the option `Z` is only accepted on the nightly compiler When rust.channel is set to either beta or stable, we can't use nightly features on bootstrap without RUSTC_BOOTSTRAP. Set RUSTC_BOOTSTRAP=1 to use nightly features on stable or beta.

[OE-core] [PATCH v3 4/7] rust: Fix assertion failure error on oe-selftest

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: thread 'main' panicked at 'assertion failed: `(left == right)` left: `x86_64-unknown-linux-gnu`, right: `x86_64-poky-linux-gnu`: Cannot obtain compiler for non-native build triple at stage 0', compile.rs:1474:13 Add correct target value for

[OE-core] [PATCH v3 5/7] rust: Add new tests in the exclude list for rust oe-selftest

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Add newly failing tests cases in the exclude list for rust oe-selftest. Signed-off-by: Yash Shinde --- meta/lib/oeqa/selftest/cases/rust.py | 37 +++- 1 file changed, 36 insertions(+), 1 deletion(-) diff --git

[OE-core] [PATCH v3 2/7] rust: detect user-specified custom targets in compiletest

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: thread 'main' panicked at 'failed to gather the target spec for '-unknown-linux-gnu', synthetic_targets.rs:66:9 Detect and fetch custom target configurations when rustc is bootstrapped in rust oe-selftest. Signed-off-by: Yash Shinde ---

[OE-core] [PATCH v3 1/7] rust: Fetch cargo from rust-snapshot dir.

2024-01-23 Thread Shinde, Yash via lists.openembedded.org
From: Yash Shinde Fixes: Exception: no cargo executable found at `${B}/rustc-1.74.1-src/build/x86_64-unknown-linux-gnu/stage0/bin/cargo` Fix the cargo binary path error on oe-selftest and path set to rust-snapshot dir. Patch sent to upstream-

[OE-core] [PATCH v2] mdadm: Disable ptests

2024-01-23 Thread Pavel Zhukov
As agreed upon in the bug triage meeting, disable mdadm ptest for the time being Related: [Yocto #15181] [Yocto #15159] [Yocto #15308] [Yocto #15309] Signed-off-by: Pavel Zhukov --- meta/conf/distro/include/ptest-packagelists.inc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

Re: [OE-core] [PATCH] perl: Fix perl-module-* being ignored via COMPLEMENTARY_GLOB

2024-01-23 Thread Richard Purdie
On Tue, 2024-01-23 at 10:35 +0100, Alexander Kanavin wrote: > On Tue, 23 Jan 2024 at 00:51, Lyu, William via lists.openembedded.org > wrote: > > > Do you have some examples of these packages which don't exist? > > > > > > I'd like to understand why they don't exist and perhaps not have them > >

[OE-core] Yocto Project Status 23 January 2024 (WW04)

2024-01-23 Thread Stephen Jolley
Current Dev Position: YP 5.0 M3 Next Deadline: 19th February 2024 YP 5.0 M3 build Next Team Meetings: - Bug Triage meeting Thursday January 25th at 7:30 am PST ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) - Weekly Project Engineering Sync Tuesday January

[OE-core][PATCH v2] python3-yamllint: Add recipe

2024-01-23 Thread Ryan Eatmon via lists.openembedded.org
Add recipe for yamllint. There is an upcoming change in u-boot where the binman tool is now configured to call yamllint to verify the configs during compile time. There was a previous patch a year ago from Trevor Woerner that never made it into oe-core. This patch is a reworking of his patch

Re: [OE-core] [PATCH] binutils : CVE-2023-25584

2024-01-23 Thread Ashishx88
Hi KhemRaj / Richard , Thanks for input . Will check the  kirkstone branch Thanks , Ashish -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#194245): https://lists.openembedded.org/g/openembedded-core/message/194245 Mute This Topic:

Re: [OE-core] oe-selftest -v -K -r reproducible.ReproducibleTests.test_reproducible_builds always succeeds, even when pkg is non-reproducible

2024-01-23 Thread Alexander Kanavin
Host tools can influence reproducibility of target items too, so I would not want to use the same set in both builds. Checking for reproducibility is simply something that needs a powerful machine. Alex On Tue, 23 Jan 2024 at 19:52, Joakim Tjernlund wrote: > > On Mon, 2024-01-22 at 21:39 +0100,

Re: [OE-core] oe-selftest -v -K -r reproducible.ReproducibleTests.test_reproducible_builds always succeeds, even when pkg is non-reproducible

2024-01-23 Thread Joakim Tjernlund via lists.openembedded.org
On Tue, 2024-01-23 at 20:02 +0100, Alexander Kanavin wrote: > Host tools can influence reproducibility of target items too, so I > would not want to use the same set in both builds. Checking for > reproducibility is simply something that needs a powerful machine. We would like to start gently,

Re: [OE-core] oe-selftest -v -K -r reproducible.ReproducibleTests.test_reproducible_builds always succeeds, even when pkg is non-reproducible

2024-01-23 Thread Alexander Kanavin
On Tue, 23 Jan 2024 at 20:11, Joakim Tjernlund wrote: > > On Tue, 2024-01-23 at 20:02 +0100, Alexander Kanavin wrote: > > Host tools can influence reproducibility of target items too, so I > > would not want to use the same set in both builds. Checking for > > reproducibility is simply something

Re: [OE-core] oe-selftest -v -K -r reproducible.ReproducibleTests.test_reproducible_builds always succeeds, even when pkg is non-reproducible

2024-01-23 Thread Joakim Tjernlund via lists.openembedded.org
On Mon, 2024-01-22 at 21:39 +0100, Alexander Kanavin wrote: > On Mon, 22 Jan 2024 at 17:49, Joakim Tjernlund > wrote: > > > > On Mon, 2024-01-22 at 17:19 +0100, Alexander Kanavin wrote: > > > On Mon, 22 Jan 2024 at 16:59, Joakim Tjernlund > > > wrote: > > > > Maybe but what about the missing