Re: [yocto] [yocto-autobuilder-helper][PATCH] config.json: add a workaround for the "autobuilderlog.json" error

2023-10-18 Thread Jose Quaresma
Hi Yoann, I have found the same for BBLAYERS that was fixed [1] expanding any relative path that could exist. Maybe it would be better to also expand BB_LOGCONFIG when the newbuilddir argument is present. [1] https://git.yoctoproject.org/poky/commit/id=f5f465ff5777eb99941db3dda84e65d4699d97f7

[yocto] [yocto-autobuilder-helper][PATCH] config.json: add a workaround for the "autobuilderlog.json" error

2023-10-18 Thread Yoann Congal
For the reproducible-meta-oe builder, workaround the bug #15241 [1], by passing BB_LOGCONFIG through "readlink -f" to avoid relative reference to the main build dir. Also, switch from BBPATH to BUILDDIR to reference the main build dir. [1]: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15241

Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3.rc1)

2023-10-18 Thread Richard Purdie
On Wed, 2023-10-18 at 15:32 +, Ross Burton wrote: > On 18 Oct 2023, at 07:29, Richard Purdie via lists.yoctoproject.org > wrote: > > > > On Wed, 2023-10-18 at 06:16 +, Pokybuild User wrote: > > >A build flagged for QA (yocto-4.3.rc1) was completed on the > > > autobuilder and is

Re: [yocto] CDN for sstate.yoctoproject.org

2023-10-18 Thread Richard Purdie
On Wed, 2023-10-18 at 14:02 +0200, Alexander Kanavin wrote: > On Wed, 18 Oct 2023 at 08:45, Richard Purdie > wrote: > > I'm torn on the targets to test as sato-sdk is a large image and world > > is a lot of work. I'd be tempted to test sato, weston and full-cmdline? > > World is a good test I

Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-4.3.rc1)

2023-10-18 Thread Ross Burton
On 18 Oct 2023, at 07:29, Richard Purdie via lists.yoctoproject.org wrote: > > On Wed, 2023-10-18 at 06:16 +, Pokybuild User wrote: >>A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder >> and is available at: >> >> >>

Re: [yocto] [yocto-autobuilder-helper][PATCH v2] meta-oe-mirror: Use a 2 step job to fetch and verify meta-openembedded mirror.

2023-10-18 Thread David Pierret
Hi, This patch is v2 for this one : https://lists.yoctoproject.org/g/yocto/message/61306 Regards David On Wed, Oct 18, 2023 at 3:46 PM David Pierret via lists.yoctoproject.org wrote: > > Inspired from trigger-build and trigger-build-post-trigger > The branch must be selected on build

[yocto] [yocto-autobuilder-helper][PATCH v2] meta-oe-mirror: Use a 2 step job to fetch and verify meta-openembedded mirror.

2023-10-18 Thread David Pierret
Inspired from trigger-build and trigger-build-post-trigger The branch must be selected on build configuration. Signed-off-by: David Pierret Reviewed-by: Yoann Congal --- config.json | 30 ++ 1 file changed, 30 insertions(+) diff --git a/config.json b/config.json

Re: [yocto] [yocto-security] SRTool usage for CVE management at YP

2023-10-18 Thread Steve Sakoman
On Tue, Oct 17, 2023 at 7:43 PM Marta Rybczynska wrote: > > Hello all, > There' a discussion pending on the usage of SRTool and CVE management > for the Yocto project in general. It is related to the need of having > a list of CVEs the project is affected by, those fixed and those that > we know

Re: [yocto] CDN for sstate.yoctoproject.org

2023-10-18 Thread Alexander Kanavin
On Wed, 18 Oct 2023 at 08:45, Richard Purdie wrote: > I'm torn on the targets to test as sato-sdk is a large image and world > is a lot of work. I'd be tempted to test sato, weston and full-cmdline? > World is a good test I guess and if from sstate, shouldn't have that > much of an issue. It does

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Enrico Jörns
Am Mittwoch, dem 18.10.2023 um 12:50 +0200 schrieb Alexander Kanavin: > On Wed, 18 Oct 2023 at 12:37, Alexander Kanavin via > lists.yoctoproject.org > wrote: > > > > On Wed, 18 Oct 2023 at 12:24, Enrico Jörns wrote: > > > In how is this different to the default packagegroup handling in oe-core

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Alexander Kanavin
On Wed, 18 Oct 2023 at 12:37, Alexander Kanavin via lists.yoctoproject.org wrote: > > On Wed, 18 Oct 2023 at 12:24, Enrico Jörns wrote: > > In how is this different to the default packagegroup handling in oe-core > > where package 'force > > themself' into images based on specific

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Alexander Kanavin
On Wed, 18 Oct 2023 at 12:24, Enrico Jörns wrote: > In how is this different to the default packagegroup handling in oe-core > where package 'force > themself' into images based on specific DISTRO_FEATURE or MACHINE_FEATURE > settings? > > Thus this is a mechanism that is explicitly designed to

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Enrico Jörns
Hi Alex, Am Mittwoch, dem 18.10.2023 um 12:09 +0200 schrieb Alexander Kanavin: > On Wed, 18 Oct 2023 at 11:57, Enrico Jörns wrote: > > it's not really that it's 'forced' into all image. The .bbappend just says: > > > > > require ${@bb.utils.contains('DISTRO_FEATURES', 'rauc', > > >

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Alexander Kanavin
On Wed, 18 Oct 2023 at 11:57, Enrico Jörns wrote: > it's not really that it's 'forced' into all image. The .bbappend just says: > > > require ${@bb.utils.contains('DISTRO_FEATURES', 'rauc', '${BPN}_rauc.inc', > > '', d)} > The assumption was that if you have 'rauc' in you DISTRO_FEATURES, you

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Enrico Jörns
Hi, Am Mittwoch, dem 18.10.2023 um 11:08 +0200 schrieb Alexander Kanavin: > Ugh, that's a really ugly hack in meta-rauc. They shouldn't force > themselves into all images that way. You should file a ticket. it's not really that it's 'forced' into all image. The .bbappend just says: > require

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Alexander Kanavin
Ugh, that's a really ugly hack in meta-rauc. They shouldn't force themselves into all images that way. You should file a ticket. I would suggest either dropping rauc from DISTRO_FEATURES globally (that may have unwanted side effects though and you should check what else that affects), or using

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Ivan Stojanovic
We have 2 images, adios-image-standard and adios-image-recovery. In adios-image-standard, I want to have rauc. In adios-image-recovery due to lack of space, I want to remove it. It is a part of it since it is in DISTRO_FEATURES. In meta-rauc layer, they add rauc to pacakgegroup-base:

Re: [yocto] Remove packagegroup from image recipes

2023-10-18 Thread Alexander Kanavin
I suppose you need to make an image recipe where the unneeded packagegroup is not listed? Can you show the existing recipes? Alex On Wed, 18 Oct 2023 at 10:38, Ivan Stojanovic wrote: > > Hi, > > I am trying to remove a package group (pacakgegroup-core-rauc) from a custom > image but it fails

[yocto] Remove packagegroup from image recipes

2023-10-18 Thread Ivan Stojanovic
Hi, I am trying to remove a package group (pacakgegroup-core-rauc) from a custom image but it fails with error: "package packagegroup-base requires packagegroup-base-rauc, but none of the providers can be installed". We use Rauc for our "standard" image, but I want to remove it from the

Re: [yocto] CDN for sstate.yoctoproject.org

2023-10-18 Thread Richard Purdie
On Tue, 2023-10-17 at 17:33 +0200, Alexander Kanavin wrote: > Thanks for working on this! I finally got to playing with CDN mirror a > bit, and it seems to basically work ok, so next I'm going to write AB > tests that check that it remains useful. Specifically: > > 1. What should the test be? >

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

2023-10-18 Thread Richard Purdie
On Wed, 2023-10-18 at 06:16 +, Pokybuild User wrote: > A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1 > > > Build URL: >

[yocto] QA notification for completed autobuilder build (yocto-4.3.rc1)

2023-10-18 Thread Pokybuild User
A build flagged for QA (yocto-4.3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.3.rc1 Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6062 Build hash information: bitbake:

[linux-yocto] [PATCH] usb: hcd-pci: remove the action of faking interrupt request

2023-10-18 Thread Meng Li via lists.yoctoproject.org
With below command steps, PCIe-USB drvier also hangs even if commit c548795abe0d("USB: add check to detect host controller hardware removal") exists in latest kernel. - hot-unplug the PCIe-USB card - echo 1 > /sys/bus/pci/devices//remove The code hangs in function xhci_urb_dequeue() because it is

[linux-yocto]: [kernel/kernel-rt v6.1]: usb: hcd-pci: remove the action of faking interrupt request

2023-10-18 Thread Meng Li via lists.yoctoproject.org
From: Limeng Hi Bruce, This patch is used to remove the action of faking interrupt request. Could you please help merge this patch into linux-ycoto kernel firstly? I will send it to mainline upstream in later. Branch are v6.1/standard/nxp-sdk-6.1/nxp-soc and