[OE-core] [PATCH V3] tar: add ptest support

2023-09-14 Thread qi...@fujitsu.com
From: Qiu Tingting Add a ptest for tar. - It is taking around 3m to execute with kvm, so added it to PTEST_SLOW. - It contains 244 cases. - It needs more fs space for test than normal. - Below is parts of the run log: START: ptest-runner 2023-09-14T08:02 BEGIN: /usr/lib/tar/ptest

[OE-core] [PATCH 2/2] libsoup: Only specify --cross-file when building for target

2023-09-14 Thread Peter Kjellerstedt
The soup.cross file is only created when building for target so only tell meson to read it when it exists. This allows libsoup-native to be built again. Signed-off-by: Peter Kjellerstedt --- meta/recipes-support/libsoup/libsoup_3.4.2.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[OE-core] [PATCH 1/2] libsoup-2.4: Only specify --cross-file when building for target

2023-09-14 Thread Peter Kjellerstedt
The soup.cross file is only created when building for target so only tell meson to read it when it exists. This allows libsoup-2.4-native to be built again. Signed-off-by: Peter Kjellerstedt --- meta/recipes-support/libsoup/libsoup-2.4_2.74.3.bb | 2 +- 1 file changed, 1 insertion(+), 1

Re: [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-09-14 Thread Richard Purdie
On Thu, 2023-09-14 at 20:51 +0200, Alexander Kanavin wrote: > On Thu, 14 Sept 2023 at 14:56, Richard Purdie > wrote: > > For the task signatures, we need to think about some questions. If I > > make a change locally, can I query how much will rebuild and how much > > will be reused? There is

Re: [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-09-14 Thread Alexander Kanavin
On Thu, 14 Sept 2023 at 14:56, Richard Purdie wrote: > For the task signatures, we need to think about some questions. If I > make a change locally, can I query how much will rebuild and how much > will be reused? There is bitbake --dry-run but perhaps it is time for a > an option (or dedicated

Re: [OE-core] [PATCH 2/2] update_mandb: deb fails due to missing man cache

2023-09-14 Thread Khem Raj
On Thu, Sep 14, 2023 at 7:39 AM Eilís 'pidge' Ní Fhlannagáin wrote: > > This only occurs in debian package builds when populating the sdk > and is a work around that seems to work. Eventually we should look > at why this is failing (I have ideas, it's somewhere in >

[OE-core][kirkstone][PATCH 1/1] go: Fix CVE-2023-39319

2023-09-14 Thread Soumya via lists.openembedded.org
From: Soumya Sambu The html/template package does not apply the proper rules for handling occurrences of " contexts. This may cause the template parser to improperly consider script contexts to be terminated early, causing actions to be improperly escaped. This could be leveraged to perform an

[OE-core] [PATCH 2/2] update_mandb: deb fails due to missing man cache

2023-09-14 Thread Eilís 'pidge' Ní Fhlannagáin
This only occurs in debian package builds when populating the sdk and is a work around that seems to work. Eventually we should look at why this is failing (I have ideas, it's somewhere in lib/oe/package_management/deb/sdk.py), but for now, do this so we can fix the core issue with

[OE-core] [PATCH 0/2] Ensure sdk.py knows about nativesdk-intercepts

2023-09-14 Thread Eilís 'pidge' Ní Fhlannagáin
This patch series ensures that do_populate_sdk knows about nativesdk-intercepts. It also ensures that debian builds work with update_mandb. Eilís 'pidge' Ní Fhlannagáin (2): lib/oe/package_managegment: Add nativesdk-intercept PATH update_mandb: deb fails due to missing man cache

[OE-core] [PATCH 1/2] lib/oe/package_managegment: Add nativesdk-intercept PATH

2023-09-14 Thread Eilís 'pidge' Ní Fhlannagáin
[YOCTO #15023] This patch adds (and removes after function execution) the nativesdk-intercept/chown|chgrp PATH before target_pm.run_intercepts calls during populate_sdk builds. This has been tested with cleanall builds and testsdk and fails on deb due to an issue where

Re: [OE-core] [PATCH v4 2/5] bitbake: cooker: add a new function to retrieve task signatures

2023-09-14 Thread Richard Purdie
Hi, Sorry, I meant to reply to this and somehow it got lost with everything else going on. On Tue, 2023-08-22 at 11:27 +0200, Julien Stephan wrote: > Le ven. 11 août 2023 à 17:16, Richard Purdie > a écrit : > > > > On Wed, 2023-08-02 at 16:44 +0200, Julien Stephan wrote: > > > On Wed, Aug 02,

Re: [OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-09-14 Thread Richard Purdie
On Thu, 2023-09-14 at 13:52 +0200, Alexander Kanavin wrote: > On Tue, 12 Sept 2023 at 16:44, Stephen Jolley wrote: > > Alexander Kanavin will be working on the core workflow topic > > I am now ready to start doing this, but before I do, I'd like to > decompose the subject into manageable tasks

Re: [OE-core] [PATCH] removing PN from BB_HASH_CODEPARSER_VALS

2023-09-14 Thread Richard Purdie
On Thu, 2023-09-14 at 12:50 +0200, Matthias Schoepfer via lists.openembedded.org wrote: > When using icecc.bbclass for builds, the build will break > due to the fact, that during parsing stage, PN is set to > no-pn, which leads to the issue that the ICECC_RECIPE_DISABLE > recipes (appended or

Re: [OE-core] [PATCH][mickledore] gcc: Fix -fstack-protector issue on aarch64

2023-09-14 Thread Ross Burton
On 14 Sep 2023, at 10:07, Martin Jansa via lists.openembedded.org wrote: > > FYI: one of LGE proprietary components triggers ICE with this applied, I'll > try to find minimal reproducer later, this is just for other people who might > hit the same: That’s… upsetting. I’ve forwarded this to

Re: [OE-core] [PATCH][mickledore] gcc: Fix -fstack-protector issue on aarch64

2023-09-14 Thread Martin Jansa
On Thu, Sep 14, 2023 at 11:07 AM Martin Jansa wrote: > FYI: one of LGE proprietary components triggers ICE with this applied, > I'll try to find minimal reproducer later, this is just for other people > who might hit the same: > > error: unrecognizable insn: > 2923 | } > | ^ > (insn 416

[OE-core] Core workflow: sstate for all, bblock/bbunlock, tools for why is sstate not being reused?

2023-09-14 Thread Alexander Kanavin
On Tue, 12 Sept 2023 at 16:44, Stephen Jolley wrote: > Alexander Kanavin will be working on the core workflow topic I am now ready to start doing this, but before I do, I'd like to decompose the subject into manageable tasks with a bit of help from RP and the community:

[OE-core] [PATCH 2/3] meta/lib/bblayers/buildconf.py: add support for configuration descriptions

2023-09-14 Thread Alexander Kanavin
Signed-off-by: Alexander Kanavin --- meta/lib/bblayers/buildconf.py | 10 -- meta/lib/oeqa/selftest/cases/bblayers.py | 2 +- 2 files changed, 9 insertions(+), 3 deletions(-) diff --git a/meta/lib/bblayers/buildconf.py b/meta/lib/bblayers/buildconf.py index

[OE-core] [PATCH 3/3] scripts/oe-setup-builddir: add support for configuration descriptions

2023-09-14 Thread Alexander Kanavin
They are handled exactly same as conf-notes.txt. Signed-off-by: Alexander Kanavin --- scripts/oe-setup-builddir | 10 ++ 1 file changed, 10 insertions(+) diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir index 678aeac4be5..1b5dc55743e 100755 ---

[OE-core] [PATCH 1/3] meta/conf/templates/default/conf-description.txt: add a template description

2023-09-14 Thread Alexander Kanavin
Existing conf-notes.txt is not adequate in situations where the user needs to select a config template from several, or get an overview of them and is interested only in a brief explanation of what the template is for, but not extended multi-paragraph instructions for how to use it. Such

[OE-core] [PATCH] removing PN from BB_HASH_CODEPARSER_VALS

2023-09-14 Thread Matthias Schoepfer via lists.openembedded.org
When using icecc.bbclass for builds, the build will break due to the fact, that during parsing stage, PN is set to no-pn, which leads to the issue that the ICECC_RECIPE_DISABLE recipes (appended or within icecc.bbclass) are no longer parsed / ignored correctly. This will lead to an error.

[OE-core] [PATCH 1/3] openssh: capture logs in run-ptest

2023-09-14 Thread Mikko Rapeli
Drop patch to improve logging since upstream rejected it but capture failure logs in run-ptests with similar code as what upstream uses when running the tests via https://github.com/openssh/openssh-portable/blob/master/.github/run_test.sh#L23 Signed-off-by: Mikko Rapeli ---

[OE-core] [PATCH 2/3] testimage.bbclass: remove QEMU_USE_SLIRP variable

2023-09-14 Thread Mikko Rapeli
QEMU_USE_SLIRP is replaced by TEST_RUNQEMUPARAMS with "slirp" and possibly other arguments to runqemu script. Signed-off-by: Mikko Rapeli --- meta/classes-recipe/testimage.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes-recipe/testimage.bbclass

[OE-core] [PATCH 3/3] oeqa/selftest/context.py: check git command return values

2023-09-14 Thread Mikko Rapeli
Don't ignore return values from the git command lines. If something goes wrong, fail the test right away. Signed-off-by: Mikko Rapeli --- meta/lib/oeqa/selftest/context.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/selftest/context.py

[oe-core][kirkstone][PATCH 1/1] vim: Upgrade 9.0.1664 -> 9.0.1894

2023-09-14 Thread Polampalli, Archana via lists.openembedded.org
From: Richard Purdie This includes multiple CVE fixes. The license change is due to changes in maintainership, the license itself is unchanged. (From OE-Core rev: 91e66b93a0c0928f0c2cfe78e22898a6c9800f34) Signed-off-by: Richard Purdie Signed-off-by: Archana Polampalli ---

[oe-core][kirkstone][PATCH V2 1/1] vim: upgrade 9.0.1592 -> 9.0.1664

2023-09-14 Thread Polampalli, Archana via lists.openembedded.org
Fixes: https://nvd.nist.gov/vuln/detail/CVE-2023-3896 8154e642a (tag: v9.0.1664) patch 9.0.1664: divide by zero when scrolling with 'smoothscroll' set (From OE-Core rev: 4a1ab744142c9229f03a359b45e5e89a1fbae0d3) Signed-off-by: Archana Polampalli Signed-off-by: Richard Purdie Signed-off-by:

[oe-core][kirkstone][PATCH 1/1] vim: update obsolete comment

2023-09-14 Thread Polampalli, Archana via lists.openembedded.org
From: Etienne Cordonnier vim 8.3 has been out for a long time, so this comment is obsolete. However we still need UPSTREAM_VERSION_UNKNOWN, since we ignore the last digit of the upstream version number. Test result: $ devtool check-upgrade-status vim ... INFO: vim

[oe-core][mickledore][PATCH 1/1] vim: Upgrade 9.0.1664 -> 9.0.1894

2023-09-14 Thread Polampalli, Archana via lists.openembedded.org
From: Richard Purdie This includes multiple CVE fixes. The license change is due to changes in maintainership, the license itself is unchanged. (From OE-Core rev: 91e66b93a0c0928f0c2cfe78e22898a6c9800f34) Signed-off-by: Richard Purdie Signed-off-by: Archana Polampalli ---