Re: [OE-core] [PATCH] runqemu: match .rootfs. in image names instead of -image-

2024-01-03 Thread Mikko Rapeli
Hi, On Thu, Jan 04, 2024 at 08:59:03AM +0200, Mikko Rapeli via lists.openembedded.org wrote: > Hi, > > On Wed, Jan 03, 2024 at 03:54:02PM +0100, Martin Jansa wrote: > > On Wed, Jan 3, 2024 at 11:16 AM Mikko Rapeli > > wrote: > > > > > Don't expect image file names to include "-image-" but > >

Re: [OE-core] [PATCH] runqemu: match .rootfs. in image names instead of -image-

2024-01-03 Thread Mikko Rapeli
Hi, On Wed, Jan 03, 2024 at 03:54:02PM +0100, Martin Jansa wrote: > On Wed, Jan 3, 2024 at 11:16 AM Mikko Rapeli > wrote: > > > Don't expect image file names to include "-image-" but > > expect them to have the ".rootfs." postfix which is the > > default. > > > > It's the current default, but

[OE-core] [PATCH] usbutils: Update to version 017

2024-01-03 Thread Fabio Estevam
From: Fabio Estevam Update to version 017 and add a patch to fix a buildpath error. Signed-off-by: Fabio Estevam --- ...0001-usbutils.pc.in-Fix-Cflags-entry.patch | 34 +++ .../{usbutils_015.bb => usbutils_017.bb} | 3 +- 2 files changed, 36 insertions(+), 1 deletion(-)

Patchtest results for [OE-core][dunfell][PATCH] go: Backport fix for CVE-2023-45287

2024-01-03 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/dunfell-go-Backport-fix-for-CVE-2023-45287.patch FAIL: test mbox format: Series has malformed diff lines. Create

[OE-core][dunfell][PATCH] go: Backport fix for CVE-2023-45287

2024-01-03 Thread Vijay Anusuri via lists.openembedded.org
From: Vijay Anusuri Upstream-Status: Backport [https://github.com/golang/go/commit/9baafabac9a84813a336f068862207d2bb06d255 & https://github.com/golang/go/commit/c9d5f60eaa4450ccf1ce878d55b4c6a12843f2f3 & https://github.com/golang/go/commit/8f676144ad7b7c91adb0c6e1ec89aaa6283c6807 &

[OE-core] [PATCH 2/2] quilt,cpio: Create ptest user when ptest is enabled in distro features

2024-01-03 Thread Khem Raj
Fixes warnings run.do_install_ptest_base.107960:175 exit 1 from 'chgrp -R ptest /mnt/b/yoe/master/build/tmp/work/core2-64-yoe-linux-musl/cpio/2.14/image/usr/lib/cpio/ptest/' Signed-off-by: Khem Raj --- meta/recipes-devtools/quilt/quilt.inc | 8

[OE-core] [PATCH 1/2] Revert "opkg-utils: upgrade 0.6.2 -> 0.6.3"

2024-01-03 Thread Khem Raj
This reverts commit a856192be5dd78c621478ed29871191c580686c4. It causes a regression in creating different GIDs in image and ipk as reported in [1] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15334 Signed-off-by: Khem Raj --- .../opkg-utils/{opkg-utils_0.6.3.bb =>

Re: [OE-core] [PATCH 0/7] kernel: consolidated pull request

2024-01-03 Thread Bruce Ashfield
On Wed, Jan 3, 2024 at 6:37 PM Bruce Ashfield via lists.openembedded.org wrote: > > On Wed, Jan 3, 2024 at 6:25 PM Richard Purdie > wrote: > > > > On Mon, 2024-01-01 at 23:31 -0500, bruce.ashfi...@gmail.com wrote: > > > From: Bruce Ashfield > > > > > > Richard, > > > > > > As promised, I waited

[OE-core] [PATCH] linux-yocto-rt/6.6: correct meta data branch

2024-01-03 Thread Bruce Ashfield
From: Bruce Ashfield The copied 6.5 -> 6.6 linux-yocto-rt recipe missed one branch update to 6.6. The scripts setting the SRCREVs of course are using the 6.6 branches, which leaves us with a fetch failure. Signed-off-by: Bruce Ashfield --- Richard, Here's the simple fix for the testing

Re: [OE-core] [PATCH 0/7] kernel: consolidated pull request

2024-01-03 Thread Bruce Ashfield
On Wed, Jan 3, 2024 at 6:25 PM Richard Purdie wrote: > > On Mon, 2024-01-01 at 23:31 -0500, bruce.ashfi...@gmail.com wrote: > > From: Bruce Ashfield > > > > Richard, > > > > As promised, I waited until the new year to send this update > > to introduce the 6.6 kernel and libc-headers. > > > >

Re: [OE-core] [PATCH 0/7] kernel: consolidated pull request

2024-01-03 Thread Richard Purdie
On Mon, 2024-01-01 at 23:31 -0500, bruce.ashfi...@gmail.com wrote: > From: Bruce Ashfield > > Richard, > > As promised, I waited until the new year to send this update > to introduce the 6.6 kernel and libc-headers. > > I'll be sending patches to the appropriate lists to remove > 6.5 shortly

Re: [OE-core] how to sneak a function into the *middle* of "prefuncs"?

2024-01-03 Thread Richard Purdie
On Wed, 2024-01-03 at 11:21 -0500, Robert P. J. Day wrote: > no, no, hear me out ... colleague has a vendor's YP build system and > needs to -- in the middle of a bunch of a task's [prefuncs] -- sneak > in a signing step. can't be at the beginning (what to be signed not > created yet), and can't

[OE-core] how to sneak a function into the *middle* of "prefuncs"?

2024-01-03 Thread Robert P. J. Day
no, no, hear me out ... colleague has a vendor's YP build system and needs to -- in the middle of a bunch of a task's [prefuncs] -- sneak in a signing step. can't be at the beginning (what to be signed not created yet), and can't be at the end cuz by then it's too late as the artifact has been

[OE-core] [PATCH] inetutils: Update to the 2.5 release

2024-01-03 Thread Tom Rini
The update from 2.4 to 2.5 was almost something AUH could take care of. However, we had backported two patches to address CVE-2023-40303 and that threw off AUH. These changes are confirmed to be in 2.5, so drop them and update to 2.5. Signed-off-by: Tom Rini ---

[OE-core] [PATCH 4/4] classes/recipes: Switch to use inherit_defer

2024-01-03 Thread Richard Purdie
Now that bitbake supports the use of inherit_defer, switch all conditional (variable based) inherits to use this instead. This leads to more a more deterministic user experience since there is no longer an immediate expansion and later changes to the variables in question (e.g. a bbappend) are

[OE-core] [PATCH 3/4] rootfs-postcommands: Try and improve ordering constraints

2024-01-03 Thread Richard Purdie
The current code is in race to see who can set things last. This isn't scalable or sustainable and problemtic in the face of inherit ordering changes. Move the ordering issue into the actual code execution, which isn't ideal but the best of several bad options and at least lets us drop the

[OE-core] [PATCH 1/4] allarch: Fix allarch corner case

2024-01-03 Thread Richard Purdie
Most of the allarch code is conditional and only set if the recipe remains marked as allarch. The qemu wrapper handling is not handled in the same way however and is unconditional. Move the code to some slightly uglier inline python to allow it to be conditional and match the way the rest of

[OE-core] [PATCH 2/4] rootfs: Fix MULTILIB_RE_ALLOW to be inherit order independent

2024-01-03 Thread Richard Purdie
This variable is only used by the ipk backend with multilibs. In order to make it work correctly regardless of inherit order, change the string to be space delimeted, set using += and add in the regex '|' sperator at the end of processing. Signed-off-by: Richard Purdie ---

Re: [OE-core] [PATCH] runqemu: match .rootfs. in image names instead of -image-

2024-01-03 Thread Martin Jansa
On Wed, Jan 3, 2024 at 11:16 AM Mikko Rapeli wrote: > Don't expect image file names to include "-image-" but > expect them to have the ".rootfs." postfix which is the > default. > It's the current default, but whole runqemu won't work when someone changes:

[OE-core] [PATCH] grub: fs/fat: Don't error when mtime is 0

2024-01-03 Thread Ming Liu
From: Ming Liu A issue was found when I run "runqemu genericx86-64 ovmf", grub failed to boot, it's a known issue has been fixed in grub upstream, backport the fix. Signed-off-by: Ming Liu --- ...1-fs-fat-Don-t-error-when-mtime-is-0.patch | 70 +++

[OE-core] [PATCH] tcp-wrappers: drop libnsl2 build dependency

2024-01-03 Thread Enrico Scholz via lists.openembedded.org
From: Enrico Scholz The only libnsl2 function which is used by tcp-wrappers is 'yp_get_default_domain()'. When USE_GETDOMAIN is set, this is implemented as a simple wrapper around getdomainname() so that libnsl2 is not used at all. We added a patch which does '#include ' to avoid implicit

[OE-core] [PATCH] glibc-y2038-tests: do not run tests using 32 bit time APIs

2024-01-03 Thread Alexander Kanavin
I'm not sure why this was included and enabled to begin with: the tests predictably mass-fail if system time is set to after y2038. Signed-off-by: Alexander Kanavin --- meta/recipes-core/glibc/glibc/run-ptest | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git

[OE-core] [PATCH v2] sanity.bbclass: Check for additional native perl modules.

2024-01-03 Thread Philip Balister
Since we use the build systems native perl, we need to check that all perl modules required for a build are installed. For a default Fedora 39 install, autoconf-native and libxcrypt both fail to build due to missing perl modules. After taking careful notes, this commits adds checks for

Re: [OE-core][dunfell][PATCH] tzdata: Upgrade to 2023d

2024-01-03 Thread Shubham Kulkarni via lists.openembedded.org
Thank you Steve! Thanks, Shubham Kulkarni On Tue, Jan 2, 2024 at 11:19 PM Steve Sakoman wrote: > On Mon, Jan 1, 2024 at 8:26 AM Shubham Kulkarni > wrote: > > > > Hi Steve, > > > > Thanks for your response. Will it be possible to merge this patch in > dunfell-nut till Jan 02, if there are no

Re: [OE-core] [PATCH] sanity.bbclass: CHeck for additional native perl modules.

2024-01-03 Thread Philip Balister
On 1/2/24 17:47, Richard Purdie wrote: On Tue, 2024-01-02 at 16:14 -0500, Philip Balister wrote: On 1/2/24 11:45, Richard Purdie wrote: On Tue, 2024-01-02 at 11:40 -0500, Philip Balister wrote: On 1/2/24 10:34, Richard Purdie wrote: On Tue, 2024-01-02 at 06:21 -0500, Philip Balister wrote:

[OE-core] [PATCH] runqemu: match .rootfs. in image names instead of -image-

2024-01-03 Thread Mikko Rapeli
Don't expect image file names to include "-image-" but expect them to have the ".rootfs." postfix which is the default. Enables running tests against image recipes which are not called "bla-image" but plain "bla". Currently they fail with do_testimage/runqemu error: runqemu - ERROR - Unknown

[OE-core] [PATCH] devtool: modify: fix exception

2024-01-03 Thread Jamin Lin via lists.openembedded.org
Root Cause: initial_revs is an empty dictionary and do not have "." key. Traceback (most recent call last): File "scripts/devtool", line 349, in ret = main() File "scripts/devtool", line 336, in main ret = args.func(args, config, basepath, workspace) File

Re: [OE-core][PATCH] debugedit: add UPSTREAM_CHECK settings

2024-01-03 Thread Chen Qi via lists.openembedded.org
On 1/3/24 16:28, Alexander Kanavin wrote: On Wed, 3 Jan 2024 at 08:45, Chen Qi via lists.openembedded.org wrote: On 1/3/24 15:21, Alexander Kanavin via lists.openembedded.org wrote: This works as expected. What made you think it’s broken and needs changing? The 404 ERROR that 'devtool

[oe-core][kirkstone][PATCH 1/1] dropbear: fix CVE-2023-48795

2024-01-03 Thread Meenali Gupta via lists.openembedded.org
From: Meenali Gupta A flaw was found in the SSH channel integrity. By manipulating sequence numbers during the handshake, an attacker can remove the initial messages on the secure channel without causing a MAC failure. For example, an attacker could disable the ping extension and thus disable

[OE-core] [PATCH] python3-lxml: upgrade 4.9.4 -> 45.0.0

2024-01-03 Thread wangmy
From: Wang Mingyu Changelog: == -LP#1976304: The "Element.addnext()" method previously inserted the new element before existing tail text. The tail text of both sibling elements now stays on the respective elements. -LP#1980767, GH#379: "TreeBuilder.close()" could fail with a

[OE-core] [PATCH] python3-attrs: upgrade 22.1.0 -> 23.2.0

2024-01-03 Thread wangmy
From: Wang Mingyu Changelog: === - The type annotation for 'attrs.resolve_types()' is now correct. - Type stubs now use 'typing.dataclass_transform' to decorate dataclass-like decorators, instead of the non-standard '__dataclass_transform__' special form, which is only supported by

Re: [OE-core][PATCH] debugedit: add UPSTREAM_CHECK settings

2024-01-03 Thread Alexander Kanavin
On Wed, 3 Jan 2024 at 08:45, Chen Qi via lists.openembedded.org wrote: > > On 1/3/24 15:21, Alexander Kanavin via lists.openembedded.org wrote: > > This works as expected. What made you think it’s broken and needs changing? > > The 404 ERROR that 'devtool check-ugprade-status' prints out to me >