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

This was an "all green" build, so it can take its place in line for QA behind scarthgap. Steve On Wed, Apr 17, 2024 at 4:54 PM Pokybuild User via lists.yoctoproject.org wrote: > > > A build flagged for QA (yocto-3.1.33.rc1) was completed on the autobuilder > and is available at: > > >

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

A build flagged for QA (yocto-3.1.33.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.33.rc1 Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6816 Build hash information: bitbake:

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

On Wed, 2024-04-17 at 11:36 +, Ross Burton via lists.yoctoproject.org wrote: > On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org > wrote: > > For b), updating buildtools should resolve it, I thought I had done > > that but there were a lot of moving pieces so I must not have

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

On Wed, Apr 17, 2024 at 1:50 AM Richard Purdie via lists.yoctoproject.org wrote: > On Wed, 2024-04-17 at 08:37 +, Pokybuild User via > lists.yoctoproject.org wrote: > > > > A build flagged for QA (yocto-5.0.rc2) was completed on the > autobuilder and is available at: > > > > > >

Re: [linux-yocto] Overlapped upstream patch in yocto-kernel-cache

On Tue, Apr 16, 2024 at 2:38 PM Bruce Ashfield wrote: > > Without including the ktypes/preempt-rt/preempt-rt.scc, you won't actually > have the preempt-rt patches applied, as that's where the branches are > created and the features/rt is included (and that feature is the actual -rt > patches).

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

On Wed, Apr 17, 2024 at 11:36:27AM +, Ross Burton wrote: > On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org > wrote: > > For b), updating buildtools should resolve it, I thought I had done > > that but there were a lot of moving pieces so I must not have got the > >

Re: [linux-yocto] [PATCH yocto-kc v6.1/v6.6/master] full_nohz: remove RCU_FAST_NO_HZ gone from upstream

merged. Bruce In message: [PATCH yocto-kc v6.1/v6.6/master] full_nohz: remove RCU_FAST_NO_HZ gone from upstream on 16/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > In commit e2c73a6860bd ("rcu: Remove the RCU_FAST_NO_HZ Kconfig option") > the so named option was removed from the

Re: [linux-yocto] [PATCH yocto-kc v6.6/master] cgl: drop SELINUX_DISABLE option

merged. Bruce In message: [PATCH yocto-kc v6.6/master] cgl: drop SELINUX_DISABLE option on 16/04/2024 pa...@kernel.org wrote: > From: Paul Gortmaker > > It was removed from mainline in v6.4 in commit f22f9aaf6c3d ("selinux: > remove the runtime disable functionality"). > > Signed-off-by:

Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable GPIO_VF610 for nxp-imx9

merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx9: Enable GPIO_VF610 for nxp-imx9 on 16/04/2024 Xiaolei Wang wrote: > Enable GPIO_VF610 for nxp-imx9. > > Signed-off-by: Xiaolei Wang > --- > bsp/nxp-imx9/nxp-imx9.cfg | 1 + > 1 file changed, 1 insertion(+)

Re: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/3] phy: lynx-28g: truly power the lanes up or down

merged. Bruce In message: [linux-yocto][v6.1/standard/nxp-sdk-6.1/nxp-soc & v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH 1/3] phy: lynx-28g: truly power the lanes up or down on 16/04/2024 Xulin Sun wrote: > From: Vladimir Oltean > > commit f73df580c2379a90c9269dace6dc3084fdf85ccc

Re: [yocto] Issue with Installing openssh Package #systemd #yocto #kirkstone

Peter, So I did little clean up and fixed the error: "unknown option -- G.", so that is taken care. Now the only issue is getting this service "sshdgenkeys.service" enabled by default. Just to recap, I have "openssh-sshd" disable by default and "openssh-sshdgenkeys" enable:

Re: [yocto] Issue with Installing openssh Package #systemd #yocto #kirkstone

Peter, Ah ha! that jogged my memory... Even though openssh is in the IMAGE_INSTALL group I still need to add "openssh-sshdgenkeys" since I'm splitting the openssh package. After adding "openssh-sshdgenkeys" into my image recipe service was installed as expected but it is not getting enabled,

Re: [yocto] Issue with Installing openssh Package #systemd #yocto #kirkstone

From: yocto@lists.yoctoproject.org On Behalf Of Nitesh D via lists.yoctoproject.org Sent: Wednesday, April 17, 2024 14:21 To: Alexander Kanavin ; yocto@lists.yoctoproject.org Subject: Re: [yocto] Issue with Installing openssh Package #systemd #yocto #kirkstone > Alex, > > Thanks for your

Re: [yocto] Issue with Installing openssh Package #systemd #yocto #kirkstone

Alex, Thanks for your prompt response. Shouldn't "PACKAGES =+ "${PN}-sshdgenkeys"" take care of installing it on the image? Meaning my image recipe picks up everything from the packagegroup, which includes "openssh". Part of the package is getting installed. When I flash the image on my

Re: [yocto] Issue with Installing openssh Package #kirkstone #systemd #yocto

openssh recipe (or its appends) does not control what gets installed into the image, only how openssh gets split into packages. To see what gets installed you need to find the image recipe and modify that as appropriate. Alex On Wed, 17 Apr 2024 at 13:56, Nitesh D via lists.yoctoproject.org

[yocto] Issue with Installing openssh Package #kirkstone #systemd #yocto

Hello All, This is my first time posting in the Yocto forum, so please bear with me (I'm a rookie). One of my projects requires "openssh" to be installed in the image, but with all services disabled except for keeping sshdgenkeys.service running. I split it into two packages, but for some odd

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

On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org wrote: > For b), updating buildtools should resolve it, I thought I had done > that but there were a lot of moving pieces so I must not have got the > latest. > > I'm proposing we do but this into QA as I'd not block release on

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

On Wed, 2024-04-17 at 08:37 +, Pokybuild User via lists.yoctoproject.org wrote: > >     A build flagged for QA (yocto-5.0.rc2) was completed on the autobuilder > and is available at: > > >     https://autobuilder.yocto.io/pub/releases/yocto-5.0.rc2 > > >     Build URL: >

[yocto] QA notification for completed autobuilder build (yocto-5.0.rc2)

A build flagged for QA (yocto-5.0.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-5.0.rc2 Build URL: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6813 Build hash information: bitbake:

Re: [yocto] Implicit RPROVIDES somewhere ?

Hi Joel, On 4/16/24 19:09, Joel GUITTET via Lists.Yoctoproject.Org wrote: You don't often get email from jguittet.opensource=witekio@lists.yoctoproject.org. Learn why this is important Hello Quentin, Thanks for the quick reply on this