The command is: yocto-check-layer-wrapper ../meta-virtualization --dependency ../meta-openembedded/meta-oe ../meta-openembedded/meta-networking ../meta-openembedded/meta-python

<alexandre.belloni@...> wrote: Aha. These recipes need the defaults that are supplied when the virtualization distro feature is specified. What is the exact command the nightly check is

I missed this one: ERROR: Nothing RPROVIDES '${VIRTUAL-RUNTIME_container_runtime}' (but

Hi Bruce, check-layer-nightly is failing for meta-virt: ERROR: Nothing RPROVIDES '${VIRTUAL-RUNTIME_container_networking}' (but

This should be fixed by https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/28513 and no longer be an issue. Best regards, Jan-Simon ------ Jan-Simon Möller AGL Release Manager The Linux

Hello, We still see this failure on kirkstone: https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1205/steps/11/logs/stdio -- Alexandre Belloni, co-owner and COO, Bootlin Embedded

I noticed Alexandre's build on fedora36-ty-3 was hanging in oe-selftest: https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/4815 Looking at the bitbake-cookerdaemon.log, we

There's a new DEPENDS on grpc added to agl-shell-activator in

Thanks for the report. Short term workaround: PACKAGECONFIG[grpc-proxy] = "-Dgrpc-proxy=true,-Dgrpc-proxy=false" We'll upload a fix shortly. Best, JS Am Donnerstag, 16. Februar 2023, 10:36:28

Hello, meta-agl failed check-layer-nightly with: ERROR: Nothing PROVIDES 'grpc' (but

Hi Alexandre, then we have to drop meta-agl from YP langdale autobuilds. The value for both sides is YP master branch + meta-agl's next branch. There we can detect and fix issues regularly. Plus the

Hello, meta-agl failed check-layer-nightly with: ERROR: No recipes in default available for:

Hi Alexandre, Sorry to hear that that, but we did not intent to be troublemakers ;) for sure. This is a learning curve I suppose on both sides as we do uprev's on different timelines while we track

Hello, Well, I think this goes against the principle of least astonishment and is quite convoluted. I don't feel this is normal that the only three commits after introducing langdale on the

Hi Alexandre, hmm, I think there's some confusion. Let me try to clarify: For https://autobuilder.yoctoproject.org/typhoon/#/builders/121/builds/1049 -> Build Properties branch (yocto) ->

As Scott points out, meta-agl uses "next" branch to track upstream master development, i.e. langdale and later. As meta-agl "master" branch is kept compatible with the latest LTS, namely

Okay, Jan-Simon is more awake than I am, and points out that our next branch is where it should be. We do have a commit that adds langdale to LAYERSERIES_COMPAT for all the layers in meta-agl, so

Our next branch seems to have been rebased/pushed to an old version last night, Jan-Simon and I will try to figure out what happened. I can push the previous state that I have, but I want to make

Hello, meta-agl is still failing check-layer-nightly on langdale builds because of meta-pipewire: ERROR: Layer meta-pipewire is not compatible with the core layer which only supports these series:

Hello, python3-colorama has been upgraded once again and we now have a check-layer-nightly failure. AssertionError: Adding layer meta-virtualization changed signatures. 23 signatures changed,