From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <tim.orling@konsulko.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 1/5] vcontainer-bbmask.inc: add python3-pexpect,-ptyprocess
Date: Thu, 30 Jul 2026 07:25:42 +0200 [thread overview]
Message-ID: <DKBNMP986EDB.QTHUA2SN0EI0@bootlin.com> (raw)
In-Reply-To: <20260729213430.218008-2-tim.orling@konsulko.com>
On Wed Jul 29, 2026 at 11:34 PM CEST, Tim Orling via lists.openembedded.org wrote:
> From: Tim Orling <tim.orling@konsulko.com>
>
> For container-yocto-builder, the container is the "host" and so
> we need the "Build Host Packages" equivalent in [1]. When
> we are building with mc:container-aarch64,-x86-64 multiconfig
> and the vcontainer distro, we need python3-pexpect and its
> dependency python3-ptyprocess to fulfill
> packagegroup-yocto-builder-extras. Otherwise we see a build-time
> error like:
>
> ERROR: Nothing RPROVIDES 'python3-pexpect' (but mc:container-aarch64:
> .../meta-virtualization/recipes-core/packagegroups/packagegroup-yocto-builder.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'python3-pexpect' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['python3-pexpect']
> ERROR: Required build target 'packagegroup-yocto-builder' has no buildable providers.
> Missing or unbuildable dependency chain was: ['packagegroup-yocto-builder', 'python3-pexpect']
>
> Remove the layer-wide meta-python BBMASK and allow these
> specific recipes.
>
> Once meta-python is allowed, there was an error for
> meta-oe/dynamic-layers/meta-python which we do not need for the
> above recipes. It can be enabled in the future when needed.
>
> [1] https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#build-host-packages
> Signed-off-by: Tim Orling <tim.orling@konsulko.com>
> ---
> conf/distro/include/vcontainer-bbmask.inc | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/conf/distro/include/vcontainer-bbmask.inc b/conf/distro/include/vcontainer-bbmask.inc
> index 0c9b8b02..572ebc4a 100644
> --- a/conf/distro/include/vcontainer-bbmask.inc
> +++ b/conf/distro/include/vcontainer-bbmask.inc
> @@ -94,6 +94,9 @@ BBMASK += "meta-openstack/recipes-dbs/postgresql/"
> BBMASK += "meta-oe/dynamic-layers/networking-layer/recipes-core/"
> BBMASK += "meta-openstack/recipes-extended/libvirt/"
> BBMASK += "meta-webserver/recipes-(?!httpd/nginx)"
> +# To satisfy RDEPENDS for packagegroup-yocto-builder-extras in mc:container-*
> +BBMASK += "meta-python/recipes-devtools/python/python3-(?!pexpect|ptyprocess)"
> +BBMASK += "meta-oe/dynamic-layers/meta-python/recipes-core/packagegroups/"
>
> # ---------------------------------------------------------------------------
> # Entire layers with 0 recipes in the container image dependency graph.
> @@ -101,7 +104,7 @@ BBMASK += "meta-webserver/recipes-(?!httpd/nginx)"
> # does not warn about zero files matching BBFILE_PATTERN.
> # ---------------------------------------------------------------------------
> BBMASK += "meta-filesystems/"
> -BBMASK += "meta-python/"
> +
> # Warning suppression for these fully-masked layers is in meta-virt-host.conf
> # (BBFILE_PATTERN_IGNORE_EMPTY) because BitBake checks the base datastore,
> # not per-multiconfig datastores.
Hi Tim,
I believe this is a patch for meta-virtualization, right? And I believe
it's the same for the other patch?
[PATCH v2 5/5] docs: add container-yocto-builder.md
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-07-30 5:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260727000247.1623785-3-tim.orling@konsulko.com>
2026-07-29 21:34 ` [PATCH v2 1/5] vcontainer-bbmask.inc: add python3-pexpect,-ptyprocess tim.orling
2026-07-30 5:25 ` Mathieu Dubois-Briand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DKBNMP986EDB.QTHUA2SN0EI0@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tim.orling@konsulko.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox