Hello Alex, it occurred again: NOTE: recipe gawk-5.1.1-r0: task do_patch: Succeeded NOTE: Running task 1673 of 4524

A build flagged for QA (yocto-3.4.3.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.4.3.rc2 Build hash information: bitbake:

I picked up a list of warnings in sequence from the build which had a mix from meta-selinux and meta-security. You can correct the message. The changes in this commit are only for meta-security layer

The commit message seems to not match the changes. The selinux changes don't apply to this layer.  I suspect a cut&paste issue. Did you want to do a v2 or do you want me to correct the message? I

Many of these recipes do not reside in meta-selinux. WARNING: ecryptfs-utils-111-r0 do_package_qa: QA Issue: Recipe LICENSE includes obsolete licenses GPL-2.0 [obsolete-license] \ WARNING:

WARNING: setools-4.4.0-r0 do_package_qa: QA Issue: Recipe LICENSE includes obsolete licenses GPLv2 LGPLv2.1 [obsolete-license] \ WARNING: policycoreutils-3.3-r0 do_package_qa: QA Issue: Recipe LICENSE

WARNING: checkpolicy-3.3-r0 do_package_qa: QA Issue: Recipe LICENSE includes obsolete licenses GPLv2+ [obsolete-license] \ WARNING: setools-4.4.0-r0 do_package_qa: QA Issue: Recipe LICENSE includes

WARNING: selinux-sandbox-3.3-r0 do_package_qa: QA Issue: Recipe LICENSE includes obsolete licenses GPLv2+ [obsolete-license] \ WARNING: selinux-gui-3.3-r0 do_package_qa: QA Issue: Recipe LICENSE

Hi there, Is there any update, by when this will get merge? Thanks, Ranjitsinh

Did we get that solved on master or not? I can't remember if there were remaining issues or not? Cheers, Richard

Hello, We are pleased to announce the Yocto Project 3.1.15 (dunfell-23.0.15) Release is now available for download.

Alex is very much correct, you should not see corruption. But I think more detail is in order. If your distro repository is a "garden variety" set of image recipes and recipe overrides that pull

Hello Alexandre, No, I was wrong. This also replaces all device trees. Only the overlays are then additionally present. I understand that it is bad practice. However, I would still like to

Hello Alexandre, Thank you, that works. OK. Best regards, Matthias

Hi, Did you try RPI_KERNEL_DEVICETREE:append? Whatt is happening here is that KERNEL_DEVICETREE is set like that in rpi-base.inc: KERNEL_DEVICETREE ??= " \ ${RPI_KERNEL_DEVICETREE} \

Hello, I am trying to add a device tree in a yocto based on the meta-raspberrypi layer. Adding the device tree via a patch in a bbapend of the kernel recipe is no problem. But all attempts to

Current Dev Position: YP 3.5 M4 Next Deadline: 4th April. 2022 YP 3.5 M4 build Next Team Meetings: Bug Triage meeting Thursday Mar. 24th 7:30 am PDT

No and no. Alex

Is the sstate cache sensitive to different releases and or the ordering of the bblayers? We are upgrading our Yocto-based distro from dunfell to hardknott. So for a while we will be building our

Hi, I came to know about the package feed feature, through which we can update the application in the target image by using apt-get commands. I just read about it on following