Hi, just FYI, I was looking at one of last build failures in my world builds and yq is failing again for aarch64. Looks like the issue is in go itself: https://github.com/golang/go/issues/58826 and sh

From: Chen Qi <Qi.Chen@...> When multilib is enabled we can see the following package QA error. QA Issue: Files/directories were installed but not shipped in any package: /usr/lib/firewalld/

I agree, but now when 99.9% of Upstream-Status have the right formatting and there is a QA check to keep or improve the percentage, it might be a step back to loosen the regexp. I've noticed because I

For my next presenter's gift, I want a regex that doesn't nitpick us on capitals and dashes ;) Funny that I'm not seeing this, I haven't inhibited the check completely yet. But my jest / complaint not

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- .../k3s/k3s/0001-Finding-host-local-in-usr-libexec.patch | 2 +- .../0001-hack-lib-golang.sh-use-CC-from-environment.patch | 2 +- ...1-Should-fi

* fails to build with byacc-native 20230219 from: https://git.openembedded.org/meta-openembedded/commit/?id=3462709d651f44f3d067b3ce0bcfba876be9ff1d * https://invisible-island.net/byacc/CHANGES.html#i

* this isn't complete fix as there are still issues from new boost as in: https://github.com/boostorg/phoenix/issues/111 http://errors.yoctoproject.org/Errors/Details/702743/ TOPDIR/tmp-glibc/work/cor

* this isn't complete fix as there are still issues from new boost as in: https://github.com/boostorg/phoenix/issues/111 http://errors.yoctoproject.org/Errors/Details/702743/ TOPDIR/tmp-glibc/work/cor

Signed-off-by: Martin Jansa <Martin.Jansa@...> --- ...-build-with-newer-linux-libc-headers.patch | 50 +++++++++++++++++++ recipes-containers/lxcfs/lxcfs_4.0.7.bb | 1 + 2 files changed, 51 insert

As a preparation for switching to using the cargo-update-recipe-crates bbclass to update the crate URIs, move the existing crate URIs to the netavark-crates.inc file that it expects. Signed-off-by: Pe

The previous version of the recipe was generated by cargo-bitbake, which expects that future updates to the recipe will also be done by cargo-bitbake and therefore formats it to accomodate this. Since

The previous version of the recipe was generated by cargo-bitbake, which expects that future updates to the recipe will also be done by cargo-bitbake and therefore formats it to accomodate this. Since

Use the cargo-update-recipe-crates bbclass to update the crate URIs including adding checksums for them, as they are now required by the crate fetcher. Signed-off-by: Peter Kjellerstedt <peter.kjeller

Use the cargo-update-recipe-crates bbclass to update the crate URIs including adding checksums for them, as they are now required by the crate fetcher. Signed-off-by: Peter Kjellerstedt <peter.kjeller

As a preparation for switching to using the cargo-update-recipe-crates bbclass to update the crate URIs, move the existing crate URIs to the aardvark-dns-crates.inc file that it expects. Signed-off-by

<peter.kjellerstedt@...> wrote: Agreed. I just meant to say that the commit message could say something along the lines of: "Rather than generating the crates via cargo-bitbake, we switch to the

<peter.kjellerstedt@...> wrote: I'm not following the rust and crates discussions too closely, but I am always a supporter of the revision control history in the source. As the one who ends up fi

Same comment as the other. This should stay as a git fetch, versus a crate. Bruce <peter.kjellerstedt@...> wrote: