<Sana.Kazi=kpit.com@...> wrote: This fails on the autobuilder meta-mingw test with: ../../curl-7.69.1/lib/fopen.c: In function 'Curl_fopen': ../../curl-7.69.1/lib/fopen.c:83:8:

Ack - I will be working on this over this weekend and will let you know. Christopher

Yes, for all of those things it's irrelevant. It's at the end of the file. File is written via python's json module which decides where it goes. 'git-remote' is not a mandatory property in the json,

As long as the order is truly irrelevant because different implementations (and even different versions of Python!) will result in a different processing order. Missing the version? Although I see

Okay, the reworked version of the layer tooling is now out as well. I've addressed most of the feedback, and placed the things still TBD in FIXME notes in the commits. Alex

This script can be used directly from poky, or can be copied directly into a layer or any other repository - it is self-suffucient and requires only python3 and git on the host where it will run. It

This addresses a long standing gap in the core offering: there is no tooling to capture the currently configured layers with their revisions, or restore the layers from a configuration file (without

From: Joshua Watt <JPEWhacker@...> Defines a common schema for layer setup that can be consumed by tools to know how to fetch and assemble layers for end users. Also includes an example of the

We're trying to keep CVE check tooling in sync across master and the LTS branches as much as possible. So you should submit this approach first to master, and then versions for kirkstone and

On Thu, Jul 7, 2022 at 12:00 PM Steve Sakoman via lists.openembedded.org <steve=sakoman.com@...> wrote: Actually I'm seeing a similar issue on kirkstone now :-( I'm testing a

Thanks. I built qemuppc locally and got a different failure, I'd really like to know why I saw that and the autobuilder did not. The failure was: WARNING:

<richard.purdie@...> wrote: I'll take this one. My fix was only for arch/arm, but I'll expand it to cover ppc32. Hopefully Christopher can chime in here. If not, I'll have a

<richard.purdie@...> wrote: I tried explicitly building all the recipes in there, the list is even longer and there's two which don't build at all (msmtp - can't find the source,

There is some piece we're still not understanding. I had a look at my local build (master so gcc 12.1) and I see HAVE_S_ISREG is set correctly, I don't see any "file is empty" message. Are you able

Use conditional override for CVE_CHECK_WHITELIST variable to whitelist CVEs for specific recipe. After including cve-extra-exclusions.inc all CVEs from file are getting shown in whitelist list for

From: Joshua Watt <JPEWhacker@...> Moving the function will allow other classes to capture which CVEs have been patched, in particular SBoM generation. Also add a function to capture the CPE

Hi All, We've made good progress and I appreciate the help from people. I ran a fresh build on the autobuilder and I forced it to rerun the QA checks for all recipes. The tricky bit about warnings is

This is the only one that the autobuilder saw at least. Ross

Fix below listed CVEs for curl: 1.CVE-2022-32206 Link: http://archive.ubuntu.com/ubuntu/pool/main/c/curl/curl_7.81.0-1ubuntu1.3.debian.tar.xz 2.CVE-2022-32207 Linkh:

From: Mingli Yu <mingli.yu@...> After the below commit introduced, the shebang size of native scripts is also checked, so rework the patch to fix the gap. 377fe11bc0 insane.bbclass: Make