Re: [OE-core] Issues with kernel.bbclass default "S" value

Hello Bruce, On Fri, 19 May 2023 09:24:21 +0200 "Luca Ceresoli via lists.openembedded.org" wrote: > Hello, > > I have been facing some troubles while writing a very simple recipe > inheriting kernel.bbclass to build a mainline kernel. > > The error message is: > > ... do_populate_lic: QA

[OE-core] Yocto Project Status 23 May 2023 (WW21)

Current Dev Position: YP 4.3 M1 Next Deadline: 5th June 2023 YP 4.3 M1 build date Next Team Meetings: * Bug Triage meeting Thursday May 25th 7:30 am PDT (

[OE-core] [PATCH] attr: Package attr, getfattr, and setfattr into attr-tools

Signed-off-by: Stefan Berger --- meta/recipes-support/attr/attr.inc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-support/attr/attr.inc b/meta/recipes-support/attr/attr.inc index 8ba865a74a..2d2ff0912e 100644 --- a/meta/recipes-support/attr/attr.inc +++

[OE-core] [PATCH] attr: Package attr, getfattr, and setfattr into attr-tools

Signed-off-by: Stefan Berger --- meta/recipes-support/attr/attr.inc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/meta/recipes-support/attr/attr.inc b/meta/recipes-support/attr/attr.inc index 8ba865a74a..2d2ff0912e 100644 --- a/meta/recipes-support/attr/attr.inc +++

[OE-core] [PATCH] lib/terminal.py: Add urxvt terminal

This fixes failure [1] of menuconfig task in rxvt-unicode terminal in case if xterm/Konsole/Gnome is not installed. Tested with rxvt-unicode-256color [1] WARNING: Terminal screen is supported but did not start ERROR: No valid terminal found, unable to open devshell. Tried the following commands:

Re: [OE-core][PATCH v3 1/3] cve-check: add option to add additional patched CVEs

Hello Richard, Could you please take a look on the latest revision a make a decision there? There are still bunch of unclear statements. So please make a final design and we will try to implement it. Thank you, Andrej On Mon, 2023-05-22 at 10:57 +0300, Mikko Rapeli wrote: > Hi, > > On Fri, May

Re: [OE-core] [PATCH 5/8] Remove usage of /var/volatile/tmp

As much as I like the concept of this patch, it needs a good review. Can you remove it from this series so the rest isn’t dependent on it? Thanks, Ross > On 22 May 2023, at 18:25, Alexander Kanavin via lists.openembedded.org > wrote: > > From: Markus Volk > > Glib-2.0 uses ptest to ensure

Re: [OE-core][RFC] tests artifacts retriever

I think having to write a custom artifacts.conf for each ptest is not a good direction, as it's both too much work, and requires good understanding what is important in the output and what isn't :) When a ptest fails, it would be enough to simply make a tarball of /usr/lib/component/ptest/ with

Re: [OE-core] [PATCH 5/8] Remove usage of /var/volatile/tmp

Nothing depends on this patch and it can be dropped for testing or merging. I pulled it in because otherwise glib update to 2.76 would start failing its ptest, but I see that glib update landed in master but this patch did not. Not sure how that happened, are ptests passing as of current master?

[OE-core] [PATCH] rpm: drop unused 0001-Rip-out-partial-support-for-unused-MD2-and-RIPEMD160.patch

* it was removed from SRC_URI in oe-core commit: commit 67257ca87c6fa8e6050a20ecea50daf834c7e869 Author: Alexander Kanavin Date: Sat Apr 25 19:28:00 2020 +0200 Subject: rpm: upgrade to 4.15.1 and it's unused since then Signed-off-by: Martin Jansa ---

Re: [OE-core] [PATCH 5/8] Remove usage of /var/volatile/tmp

On 23 May 2023, at 11:16, Ross Burton via lists.openembedded.org wrote: > > On 23 May 2023, at 10:04, Alexander Kanavin wrote: >> >> Nothing depends on this patch and it can be dropped for testing or >> merging. I pulled it in because otherwise glib update to 2.76 would >> start failing its

Re: [OE-core] [PATCH 5/8] Remove usage of /var/volatile/tmp

On 23 May 2023, at 10:04, Alexander Kanavin wrote: > > Nothing depends on this patch and it can be dropped for testing or > merging. I pulled it in because otherwise glib update to 2.76 would > start failing its ptest, but I see that glib update landed in master > but this patch did not. Not

Re: [OE-core][PATCH v4 1/3] cve-check: add option to add additional patched CVEs

Hello Richard and Andrej, Recently, I have observed the OpenEmbedded team is going beyond "patched" status for CVE. This change is required and helps to capture additional status. We can identify and define the reason for a whitelisted or CVE that are not "patched". Customers can get this

[OE-core] [PATCH v2] psmisc: Set ALTERNATIVE for pstree to resolve conflict with busybox

From: Frieder Schrempf If pstree in busybox is enabled there is a conflict with pstree from psmisc resulting in: do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget:${PN} ().

Re: [OE-core] [PATCH] rootfs-postcommands: Set vardeps for write_image_test_data

Hello, This causes the following failures: https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/2223/steps/14/logs/stdio 2023-05-23 09:43:18,091 - oe-selftest - INFO - sstatetests.SStateHashSameSigs.test_sstate_nativelsbstring_same_hash (subunit.RemotedTestCase) 2023-05-23

Re: [OE-core][RFC] tests artifacts retriever

On 23/05/2023 17:37:25+0200, Alexis Lothoré wrote: > Hello Alexander, thanks for the feedback > > On 5/23/23 11:50, Alexander Kanavin wrote: > > I think having to write a custom artifacts.conf for each ptest is not > > a good direction, as it's both too much work, and requires good > >

Re: [OE-core] [PATCH] attr: Package attr, getfattr, and setfattr into attr-tools

What’s the rationale for this? attr: /etc/xattr.conf /usr/bin/attr /usr/bin/getfattr /usr/bin/setfattr.attr libattr: /usr/lib/libattr.so.1 /usr/lib/libattr.so.1.1.2501 The library is already split out so what does this gain? Also, the idiom for

Re: [OE-core] [PATCH] rootfs-postcommands: Set vardeps for write_image_test_data

On 17 May 2023, at 17:29, Peter Hoyes via lists.openembedded.org wrote: > The testdata.json file generated as part of the rootfs postprocess > commands contains almost all Bitbake variables and is used by OEQA test > cases to inspect the build environment. However it is only regenerated > when

[OE-core] [PATCH] psmisc: Set ALTERNATIVE for pstree to resolve conflict with busybox

From: Frieder Schrempf If pstree in busybox is enabled there is a conflict with pstree from psmisc resulting in: do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget:${PN} ().

[OE-core] [PATCH] go: Upgrade 1.20.1 -> 1.20.4

- Remove already upstreamed patches - Brings a list of changes [1] [2] [3] [1] https://github.com/golang/go/issues?q=milestone%3AGo1.20.2+label%3ACherryPickApproved [2] https://github.com/golang/go/issues?q=milestone%3AGo1.20.3+label%3ACherryPickApproved [3]

Re: [OE-core][PATCH] b4: add recipe

Why? Alex On Tue, 23 May 2023 at 17:41, Trevor Gamblin wrote: > > Signed-off-by: Trevor Gamblin > --- > meta/conf/distro/include/maintainers.inc | 1 + > .../distro/include/ptest-packagelists.inc | 1 + > meta/recipes-devtools/b4/b4_0.12.2.bb | 35 +++ >

Re: [OE-core] [PATCH] psmisc: Set ALTERNATIVE for pstree to resolve conflict with busybox

> On 23 May 2023, at 16:36, Frieder Schrempf via lists.openembedded.org > wrote: > diff --git a/vscode-bitbake-build/executeBitBakeCmd.sh > b/vscode-bitbake-build/executeBitBakeCmd.sh > new file mode 100755 > index 00..d7a4c5a5aa > --- /dev/null > +++

Re: [OE-core][PATCH] b4: add recipe

On Tue, May 23, 2023 at 9:18 AM Alexander Kanavin wrote: > > Why? I guess implement a new patch test using it. > > Alex > > On Tue, 23 May 2023 at 17:41, Trevor Gamblin wrote: > > > > Signed-off-by: Trevor Gamblin > > --- > > meta/conf/distro/include/maintainers.inc | 1 + > >

Re: [OE-core][RFC] tests artifacts retriever

Hello Alexander, thanks for the feedback On 5/23/23 11:50, Alexander Kanavin wrote: > I think having to write a custom artifacts.conf for each ptest is not > a good direction, as it's both too much work, and requires good > understanding what is important in the output and what isn't :) When a >

[OE-core][PATCH v2] b4: add recipe

b4 is a tool for handling email-based patch workflows. It is being added to help modernize the patchtest tooling, but due to the state of meta-patchtest and the possibility that others may find it useful, add it to oe-core instead of that layer. Signed-off-by: Trevor Gamblin ---

[OE-core][PATCH] b4: add recipe

Signed-off-by: Trevor Gamblin --- meta/conf/distro/include/maintainers.inc | 1 + .../distro/include/ptest-packagelists.inc | 1 + meta/recipes-devtools/b4/b4_0.12.2.bb | 35 +++ ...skip-tests-requiring-git-filter-repo.patch | 30

Re: [OE-core][PATCH] b4: add recipe

On 2023-05-23 12:30, Khem Raj wrote: On Tue, May 23, 2023 at 9:18 AM Alexander Kanavin wrote: Why? I guess implement a new patch test using it. I'll send a v2 with details included. It's a useful tool for handling patch management and may be able to replace some/all of the legacy

Re: [OE-core] [PATCH] psmisc: Set ALTERNATIVE for pstree to resolve conflict with busybox

On 23.05.23 18:44, Ross Burton wrote: > > >> On 23 May 2023, at 16:36, Frieder Schrempf via lists.openembedded.org >> wrote: >> diff --git a/vscode-bitbake-build/executeBitBakeCmd.sh >> b/vscode-bitbake-build/executeBitBakeCmd.sh >> new file mode 100755 >> index 00..d7a4c5a5aa >> ---

Re: [OE-core] [PATCH] attr: Package attr, getfattr, and setfattr into attr-tools

On 5/23/23 12:46, Ross Burton wrote: What’s the rationale for this? attr: /etc/xattr.conf /usr/bin/attr /usr/bin/getfattr /usr/bin/setfattr.attr libattr: /usr/lib/libattr.so.1 /usr/lib/libattr.so.1.1.2501 The library is already split out so

[OE-core] [PATCH] llvm,mesa: Drop MESA_LLVM_RELEASE

This was needed to use provide different llvm from meta-clang or other layers, seems unused since meta-clang has stopped providing a versioned llvm Signed-off-by: Khem Raj --- meta/recipes-devtools/llvm/llvm_git.bb | 2 -- meta/recipes-graphics/mesa/mesa.inc| 5 + 2 files changed, 1

[OE-core] [mickledore][PATCH] go: update 1.20.1 -> 1.20.4

Update go to latest 1.20.x release. Removed patches contained in new version: - 0010-cmd-compile-re-compile-instantiated-generic-methods-.patch - CVE-2023-24532.patch - CVE-2023-24537.patch go.git$ git log --oneline go1.20.1..go1.20.4 324c3ace2d (tag: go1.20.4) [release-branch.go1.20]

[OE-core] [kirkstone][PATCH] go: fix CVE-2023-24540

Backport from go-1.19: html/template: handle all JS whitespace characters Signed-off-by: Sakib Sajal --- meta/recipes-devtools/go/go-1.17.13.inc | 1 + .../go/go-1.19/CVE-2023-24540.patch | 93 +++ 2 files changed, 94 insertions(+) create mode 100644