public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: kernel/selinux-testsuite: put back libbpf-devel CRB workaround
Date: Fri, 11 Sep 2026 13:17:51 GMT [thread overview]
Message-ID: <178913267178.1.14929218981883984017.tests-selinux-f2a19e494f1a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : f2a19e494f1a2af450ce173e3be74032732725c0
Author : Ondrej Mosnacek <omosnace@redhat.com>
Date : 2020-03-16T11:33:03+01:00
Stats : +8/-0 in 1 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/f2a19e494f1a2af450ce173e3be74032732725c0?branch=pr775-checkpolicy-revdeps
Log:
kernel/selinux-testsuite: put back libbpf-devel CRB workaround
It turns out that in CKI's kickstart the CRB repo is enabled by default,
but this is not true for the usual beaker install. Thus, try to install
libbpf-devel from the usual CRB repo names. Yes, it's an ugly
workaround, but there's currently no better way.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
---
diff --git a/kernel/selinux-testsuite/runtest.sh b/kernel/selinux-testsuite/runtest.sh
index 2bc3c82..5887303 100755
--- a/kernel/selinux-testsuite/runtest.sh
+++ b/kernel/selinux-testsuite/runtest.sh
@@ -185,6 +185,14 @@ rlJournalStart
which
"
rlRun "installDeps \$REQUIRES" 0 "Install requires"
+
+ # The CRB repo with libbpf-devel might not be enabled on RHEL
+ if rlIsRHEL '>=8'; then
+ for repo in "rhel-CRB" "beaker-CRB"; do
+ rpm -q libbpf-devel &>/dev/null && break
+ rlRun "dnf install --enablerepo $repo -y libbpf-devel" 0-255
+ done
+ fi
rlPhaseEnd
rlPhaseStartSetup
reply other threads:[~2026-09-11 13:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178913267178.1.14929218981883984017.tests-selinux-f2a19e494f1a@fedoraproject.org \
--to=omosnace@redhat.com \
--cc=git-commits@fedoraproject.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