meta-virtualization.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: patrick.wicki@subset.ch
Cc: meta-virtualization@lists.yoctoproject.org,
	Patrick Wicki <patrick.wicki@siemens.com>
Subject: Re: [meta-virtualization][PATCH 2/2] podman: require catatonit
Date: Thu, 2 May 2024 17:58:19 +0000	[thread overview]
Message-ID: <ZjPUO/MGsicD6/+H@gmail.com> (raw)
In-Reply-To: <20240429172523.1635019-2-patrick.wicki@subset.ch>

In message: [meta-virtualization][PATCH 2/2] podman: require catatonit
on 29/04/2024 Patrick Wicki via lists.yoctoproject.org wrote:

> From: Patrick Wicki <patrick.wicki@siemens.com>
> 
> Alternatively, we could add it to RRECOMMENDS. But I would say, given
> its name, managing pods is part of podman's core functionality and that
> requires catatonit, which is currently only pulled in for the ptest:
> 
> root@qemux86-64:~# podman pod create
> Error: building local pause image: finding pause binary: exec: "catatonit": executable file not found in $PATH

We've never required this before since podman create isn't
a common use case for our target devices.

The change is fine with me, but I'll wait for it to be resent
along with v2 of patch 1/2 as the list dependency formatting
will be different.

Bruce

> 
> Signed-off-by: Patrick Wicki <patrick.wicki@siemens.com>
> ---
>  recipes-containers/podman/podman_git.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/recipes-containers/podman/podman_git.bb b/recipes-containers/podman/podman_git.bb
> index 41f090f0..7bdefba5 100644
> --- a/recipes-containers/podman/podman_git.bb
> +++ b/recipes-containers/podman/podman_git.bb
> @@ -150,6 +150,7 @@ VIRTUAL-RUNTIME_base-utils-nsenter ?= "util-linux-nsenter"
>  COMPATIBLE_HOST = "^(?!mips).*"
>  
>  RDEPENDS:${PN} += " \
> +	catatonit \
>  	conmon \
>  	iptables \
>  	libdevmapper \
> @@ -172,7 +173,6 @@ RDEPENDS:${PN}-ptest += " \
>  	bash \
>  	bats \
>  	buildah \
> -	catatonit \
>  	coreutils \
>  	file \
>  	gnupg \
> -- 
> 2.44.0
> 

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#8705): https://lists.yoctoproject.org/g/meta-virtualization/message/8705
> Mute This Topic: https://lists.yoctoproject.org/mt/105805580/1050810
> Group Owner: meta-virtualization+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub [bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 



  reply	other threads:[~2024-05-02 17:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 17:25 [meta-virtualization][PATCH 1/2] podman: remove skopeo rdepends patrick.wicki
2024-04-29 17:25 ` [meta-virtualization][PATCH 2/2] podman: require catatonit patrick.wicki
2024-05-02 17:58   ` Bruce Ashfield [this message]
2024-05-02 17:56 ` [meta-virtualization][PATCH 1/2] podman: remove skopeo rdepends Bruce Ashfield

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=ZjPUO/MGsicD6/+H@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    --cc=patrick.wicki@siemens.com \
    --cc=patrick.wicki@subset.ch \
    /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).