From: Stefano Brivio <sbrivio@redhat.com>
To: Max Chernoff <git@maxchernoff.ca>
Cc: passt-dev@passt.top, Danish Prakash <danish.prakash@suse.com>,
Vit Mojzis <vmojzis@redhat.com>
Subject: Re: [PATCH] fedora: Fix build on Fedora 43, selinux_requires_min not available on Copr builders
Date: Tue, 9 Dec 2025 01:33:31 +0100 [thread overview]
Message-ID: <20251209013331.60ca85dc@elisabeth> (raw)
In-Reply-To: <4672d56268328b395e3e85d971d276528b7f5c84.camel@maxchernoff.ca>
On Mon, 08 Dec 2025 04:30:52 -0700
Max Chernoff <git@maxchernoff.ca> wrote:
> Hi Stefano,
>
> On Mon, 2025-12-08 at 11:55 +0100, Stefano Brivio wrote:
> > This (not a permanent link, sorry!) worked:
> >
> > https://download.copr.fedorainfracloud.org/results/sbrivio/passt/fedora-rawhide-x86_64/09885681-passt/builder-live.log.gz
> >
> > and this didn't:
> >
> > https://download.copr.fedorainfracloud.org/results/sbrivio/passt/fedora-43-x86_64/09885681-passt/builder-live.log.gz
>
> %selinux_requires_min is defined in
>
> /usr/lib/rpm/macros.d/macros.selinux-policy
>
> which is provided by the "selinux-policy" package, which is installed in
> the
>
> Start: installing minimal buildroot with dnf5
>
> section of the rawhide builder, but not the F43 one. The "Installing
> group/module packages" are identical in both builders, but it looks like
> one of the dependencies changed in rawhide to automatically pull in
> "selinux-policy":
>
> https://src.fedoraproject.org/rpms/rust-add-determinism/c/e2ef3ed3?branch=rawhide
Hah, thanks for the explanation! I saw that selinux-policy wasn't
installed in one case but it didn't even occur to me to trace it down
like you did.
--
Stefano
prev parent reply other threads:[~2025-12-09 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 10:34 Stefano Brivio
2025-12-08 10:43 ` Max Chernoff
2025-12-08 10:55 ` Stefano Brivio
2025-12-08 11:30 ` Max Chernoff
2025-12-09 0:33 ` Stefano Brivio [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=20251209013331.60ca85dc@elisabeth \
--to=sbrivio@redhat.com \
--cc=danish.prakash@suse.com \
--cc=git@maxchernoff.ca \
--cc=passt-dev@passt.top \
--cc=vmojzis@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).