From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: joerg.sommer@navimatix.de
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH v2] packagegroup-container: require ipv6 for podman
Date: Mon, 16 Oct 2023 14:22:52 -0400 [thread overview]
Message-ID: <CADkTA4OUUU_U9-yC8W5zq8t4E5ceit=Fy1pSGnVVj2VvU6YjGA@mail.gmail.com> (raw)
In-Reply-To: <9ca767079c48373a2d3117217376b0ab5b2a3143.1697111572.git.joerg.sommer@navimatix.de>
This is staged on master-next.
I also had to do: git commit --amend --author="Jörg Sommer
<joerg.sommer@navimatix.de>" --no-edit
Otherwise the Author of the commit was incorrectly set and the yocto
git hooks were preventing my push
I'm not sure how the patch was sent, but it is worth looking into.
Bruce
On Thu, Oct 12, 2023 at 7:53 AM Jörg Sommer via lists.yoctoproject.org
<joerg.sommer=navimatix.de@lists.yoctoproject.org> wrote:
>
> The recipe *podman* requires the distro feature *ipv6*. Using a distro
> without it causes the build of *packagegroup-container* fails, even if
> *packagegroup-podman* is not used:
>
> ERROR: Nothing RPROVIDES 'podman' (but /build/../work/layers-3rdparty/meta-virtualization/recipes-core/packagegroups/packagegroup-container.bb RDEPENDS on or otherwise requires it)
> podman was skipped: missing required distro feature 'ipv6' (not in DISTRO_FEATURES)
> NOTE: Runtime target 'podman' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['podman']
> NOTE: Runtime target 'packagegroup-docker' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['packagegroup-docker', 'podman']
>
> Signed-off-by: Jörg Sommer <joerg.sommer@navimatix.de>
> ---
> recipes-core/packagegroups/packagegroup-container.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/recipes-core/packagegroups/packagegroup-container.bb b/recipes-core/packagegroups/packagegroup-container.bb
> index 8d418e9..8309a08 100644
> --- a/recipes-core/packagegroups/packagegroup-container.bb
> +++ b/recipes-core/packagegroups/packagegroup-container.bb
> @@ -9,7 +9,7 @@ PACKAGES = "\
> packagegroup-lxc \
> packagegroup-docker \
> packagegroup-oci \
> - ${@bb.utils.contains('DISTRO_FEATURES', 'seccomp', \
> + ${@bb.utils.contains('DISTRO_FEATURES', 'seccomp ipv6', \
> 'packagegroup-podman', '', d)} \
> packagegroup-containerd \
> "
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8351): https://lists.yoctoproject.org/g/meta-virtualization/message/8351
> Mute This Topic: https://lists.yoctoproject.org/mt/101916200/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
prev parent reply other threads:[~2023-10-16 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 11:52 [meta-virtualization][PATCH v2] packagegroup-container: require ipv6 for podman Jörg Sommer
2023-10-16 18:22 ` Bruce Ashfield [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='CADkTA4OUUU_U9-yC8W5zq8t4E5ceit=Fy1pSGnVVj2VvU6YjGA@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=joerg.sommer@navimatix.de \
--cc=meta-virtualization@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).