From: Max Chernoff <git@maxchernoff.ca>
To: Danish Prakash <contact@danishpraka.sh>, passt-dev@passt.top
Cc: sbrivio@redhat.com, pholzing@redhat.com
Subject: Re: [PATCH] spec: use %selinux_requires macro, drop overlapping dependencies
Date: Thu, 13 Nov 2025 02:47:42 -0700 [thread overview]
Message-ID: <8b1f10d9a674474e6d042b27cdee8d230bd15c0c.camel@maxchernoff.ca> (raw)
In-Reply-To: <20251113072256.4034068-1-contact@danishpraka.sh>
Hi Danish,
On Thu, 2025-11-13 at 12:52 +0530, Danish Prakash wrote:
> Also, drop unused preun policycoreutils requires.
>
> Signed-off-by: Danish Prakash <contact@danishpraka.sh>
> ---
> contrib/fedora/passt.spec | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/contrib/fedora/passt.spec b/contrib/fedora/passt.spec
> index d1bcf4a74338..cab2bb4c409b 100644
> --- a/contrib/fedora/passt.spec
> +++ b/contrib/fedora/passt.spec
> @@ -34,19 +34,15 @@ for network namespaces: traffic is forwarded using a tap interface inside the
> namespace, without the need to create further interfaces on the host, hence not
> requiring any capabilities or privileges.
>
> -%package selinux
> -BuildArch: noarch
> -Summary: SELinux support for passt and pasta
> -Requires: selinux-policy-%{selinuxtype}
> -Requires: container-selinux
> -Requires(post): selinux-policy-%{selinuxtype}
> +%package selinux
> +BuildArch: noarch
> +Summary: SELinux support for passt and pasta
> +%selinux_requires
I think that we want "%selinux_requires_min" instead, since
"%selinux_requires" also pulls in "policycoreutils-python-utils" (and
hence all of Python).
(I'm not very familiar with spec files, but since the RPM macro
"%selinux_requires" is provided by the "selinux-policy" package, do we
also need to add a Requires/BuildRequires for that?)
> +Requires: container-selinux
> +Requires: selinux-policy-%{selinuxtype}
I think that "selinux-policy-%{selinuxtype}" is included via
"%selinux_requires" above.
> Requires(post): container-selinux
> -Requires(post): policycoreutils
> -Requires(post): libselinux-utils
> -Requires(preun): policycoreutils
> -BuildRequires: selinux-policy-devel
> -BuildRequires: pkgconfig(systemd)
> -Recommends: selinux-policy-%{selinuxtype} >= %{selinux_policy_version}
> +Requires(post): selinux-policy-%{selinuxtype}
> +Recommends: selinux-policy-%{selinuxtype} >= %{selinux_policy_version}
>
> %description selinux
> This package adds SELinux enforcement to passt(1), pasta(1), passt-repair(1).
Everything else looks good to me.
Thanks,
-- Max
next prev parent reply other threads:[~2025-11-13 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 7:22 Danish Prakash
2025-11-13 9:47 ` Max Chernoff [this message]
2025-11-13 11:10 ` Stefano Brivio
2025-11-13 12:04 ` Vit Mojzis
2025-11-21 12:33 ` Danish Prakash
2025-11-21 12:47 ` [PATCH v2] spec: use %selinux_requires_min " Danish Prakash
2025-11-23 7:37 ` Max Chernoff
2025-11-27 22:33 ` Stefano Brivio
2025-12-08 10:37 ` Stefano Brivio
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=8b1f10d9a674474e6d042b27cdee8d230bd15c0c.camel@maxchernoff.ca \
--to=git@maxchernoff.ca \
--cc=contact@danishpraka.sh \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).