Thanks Martin and Mike for your explanations and tips. So, I've done a lot of testing today and it seems I simplified the example in my first email a bit too much. The example as-is works fine when

I wrote a similar thing a while back, to review the license checksums in a layer. It’s only in my ross/mut branch on poky-contrib right

"t-maiaxiao" <t-maiaxiao@...> writes: I've been working on meta-binaryaudit integration into CI in the Oniro Project [1]. We had to fork the project due to maintainer

<richard.purdie@...> wrote: Yet another generation script referencing itself .. they seem to like doing that. I don't get the warning, but I do have the file with the reference in it

Hello everyone, Microsoft is going to pick this up (the ABI compliance layer[0]) as an intern project again this summer, with a particular focus on improving code quality. I’ll be working on it for

Thanks, this test build showed two warnings. I have no idea why this only showed up now: beaglebone: WARNING: linux-yocto-5.15.52+gitAUTOINC+f122fe59e7_3ec00e9ee0-r0 do_package_qa: QA Issue: File

Thank you Nicolas for asking this question since I will probably run into this issue soon if not for this email thread. The answers so far have been very helpful but I just want to clarify a bit more

Quick answer: Don't build multiple distros in one build directory. You might get away with setting TMPDIR = "tmp-${DISTRO}" to give each its own. But I'd rather advice to set up two separate builds

Hi Nicolas, I stumbled over this issue as well. Think of it this way, the package gets built in one environment and then it's built. Now ask to build it in another environment -- but it's built

I'd suggest adding some "bogus" things to your machine-extra.conf, because I don't think the file will actually be used (or even parsed) anywhere. You can override SERIAL_CONSOLES in your DISTRO

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.15 to the latest korg -stable release that comprises the following commits: 545aecd22961 Linux 5.15.52 ea512d540a55

From: Bruce Ashfield <bruce.ashfield@...> Updating linux-yocto/5.10 to the latest korg -stable release that comprises the following commits: ea86c1430c83 Linux 5.10.128 2d10984d99ac

I started working on something like this as I'm currently not aware that this functionality already exists (someone correct me if I'm wrong). My goal was to create a PDF with a list of packets and

Current Dev Position: YP 4.1 M2 Next Deadline: 11th July 2022 YP 4.1 M2 Build Next Team Meetings: Bug Triage meeting Thursday July 14th 7:30 am PDT

Hi all, I'm currently using an additional layer and image to differentiate between a release and development build (enabling NFS, SSH, root login, etc.). To create a development build, I manually add

Thank you for you reply. I actually do want to replace SERIAL_CONSOLES because I am using the original for another purpose ( not a console).

there can be multiple entries in SERIAL_CONSOLES so you might try adding instead of replacing SERIAL_CONSOLES += "115200;ttymxc0" might work

Hi, I’m trying to customize the SERIAL_CONSOLESvariable. In another thread I read this can be done by adding amachine-extra.conf file too my custom layer. So I added “ SERIAL_CONSOLES

Although bitbake.conf sets the default SDKMACHINE to the build architecture, config.json resets that to i686. As oe-selftest assumes that the SDKs it builds are usable on the host machine, we should

Apologies for the test spam. Hopefully this doesn’t have a legal disclaimer attached. Ross