[yocto][langdale] dropbear recipe fails to parse without pam in DISTRO_FEATURES

Good day everyone. We are in the process of upgrading to langdale, and I ran across a small problem when building dropbear. The order of external assets in SRC_URI seems to cause an issue when PAM is not available in DISTRO_FEATURES. ERROR: /home//yocto/poky-next/build-cyber-v/../meta/recipes

[yocto] meta-selinux: ERROR: nothing provides coreutils needed by packagegroup-core-selinux

Hi, I was trying to integrate meta-selinux layer with thud branch on our existing yocto build. I followed all the steps which are mentioned in README and SElinux-FAQ but I am facing an error in do_rootfs step. The error is shown below: ERROR: custom-base-image-1.0-r0 do_rootfs: Unable to install

[yocto] [autobuilder][PATCH 1/2] scripts/send-qa-email : clone older history to allow comparing against older releases

In order to generate relevant regression reports, we need to use resulttool against taggued releases, which can be way older than the last five previous commits Signed-off-by: Alexis Lothoré --- scripts/send-qa-email | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts

[yocto] [autobuilder][PATCH 0/2] generate regression reports against proper releases

This work has been initiated while discussing issue #14065 (https://bugzilla.yoctoproject.org/show_bug.cgi?id=14065) The topic initially covers ptest reports between releases, but after discussions with R. Purdie (https://lists.yoctoproject.org/g/automated-testing/message/1211), a general regressi

[yocto] [autobuilder][PATCH 2/2] scripts/send-qa-email: Generate regression reports against most relevant release

Instead of only generating regressions reports against HEAD of relevant branch, compute most relevant tag (ie : release) against which we can check for regressions. General rules introduced are the following : - milestone release is checked against previous milestone if possible, otherwise agai

Re: [yocto] meta-selinux: ERROR: nothing provides coreutils needed by packagegroup-core-selinux

On Fri, Jan 13, 2023 at 6:32 AM Kamal Kishor wrote: > > Hi, > I was trying to integrate meta-selinux layer with thud branch on our existing > yocto build. I followed all the steps which are mentioned in README and > SElinux-FAQ but I am facing an error in do_rootfs step. > The error is shown bel

Re: [yocto][langdale] dropbear recipe fails to parse without pam in DISTRO_FEATURES

On Fri, Jan 13, 2023 at 6:26 AM Claude Bing wrote: > > Good day everyone. > > We are in the process of upgrading to langdale, and I ran across a small > problem when building dropbear. The order of external assets in SRC_URI > seems to cause an issue when PAM is not available in DISTRO_FEATURES. >

Re: [yocto] [autobuilder][PATCH 1/2] scripts/send-qa-email : clone older history to allow comparing against older releases

On Fri, 2023-01-13 at 16:06 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > In order to generate relevant regression reports, we need to use resulttool > against taggued releases, which can be way older than the last five previous > commits > > Signed-off-by: Alexis Lothoré > --- > scr

Re: [yocto][langdale] dropbear recipe fails to parse without pam in DISTRO_FEATURES

Forgive the text wrapping, but modifying PAM_SRC_URI still yields the same results. I don't want to take up too much of your time since we have a workaround, but I figured you would want some feedback. SRC_URI = "http://matt.ucc.asn.au/dropbear/releases/dropbear-${PV}.tar.bz2 \ file://

Re: [yocto] [autobuilder][PATCH 0/2] generate regression reports against proper releases

On Fri, 2023-01-13 at 16:06 +0100, Alexis Lothoré via lists.yoctoproject.org wrote: > This work has been initiated while discussing issue #14065 > (https://bugzilla.yoctoproject.org/show_bug.cgi?id=14065) > The topic initially covers ptest reports between releases, but after > discussions > with R

Re: [yocto] [autobuilder][PATCH 1/2] scripts/send-qa-email : clone older history to allow comparing against older releases

On Fri, 2023-01-13 at 17:46 +, Richard Purdie via lists.yoctoproject.org wrote: > On Fri, 2023-01-13 at 16:06 +0100, Alexis Lothoré via > lists.yoctoproject.org wrote: > > In order to generate relevant regression reports, we need to use resulttool > > against taggued releases, which can be way

Re: [yocto] gn native do compile fails

On 2023-01-13 02:43, jovanbosic95 via lists.yoctoproject.org wrote: This is my gn-native_106.0.5.249.119.bb: Aside from: 1. the version number in the file name, and 2. the DEPENDS of libcxx-native added to list your file is the same as in meta-chromium/recipes-browser/chromium/gn-native_1

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

A build flagged for QA (yocto-3.1.22.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.22.rc1 Build hash information: bitbake: e3db9c2e9eded3c5cb6040714a6054b44f6b3880 meta-agl: ae982d798a979ee5690bee00ca90a2855bab4802 meta-ar

[yocto] How to properly modify/patch source of a Cargo Crate dependency

When creating recipes for Rust projects, all of the required crates are included in SRC_URI. I need to patch the source of several crates. I've tried creating individual recipes, but that does not really help. I've managed to get a hacky fix to work, however it involves having recipes copy sour