public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ivan Kruglov <mail@ikruglov.com>
To: git-commits@fedoraproject.org
Subject: [rpms/systemd] rawhide: spec: enable sbin_compat only for >= f43
Date: Fri, 04 Sep 2026 13:37:57 GMT	[thread overview]
Message-ID: <178852907704.1.3115607285357343765.rpms-systemd-ce778758540b@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/systemd
            Branch : rawhide
            Commit : ce778758540bd52702fd35e243cdbb7acc1cc4f8
            Author : Ivan Kruglov <mail@ikruglov.com>
            Date   : 2026-09-04T15:36:45+02:00
            Stats  : +4/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/systemd/c/ce778758540bd52702fd35e243cdbb7acc1cc4f8?branch=rawhide

            Log:
            spec: enable sbin_compat only for >= f43

Only Fedora >= 43 ships a filesystem package with those file triggers
and the matching virtual provide; on el9 (filesystem-3.16) and el10
(filesystem-3.18) it does not exist, so enabling this there produces
packages that are simply uninstallable (and that would ship no
/usr/sbin/init at all).

[skip changelog]

---
diff --git a/systemd.spec b/systemd.spec
index 356810f..ce47dd6 100644
--- a/systemd.spec
+++ b/systemd.spec
@@ -23,7 +23,10 @@
 # create /usr/sbin symlinks instead of shipping them in the package. This
 # avoids file conflicts when installing on merged-sbin systems and eliminates
 # bootstrap ordering issues with the bin/sbin merge.
-%bcond sbin_compat 1
+#
+# So far only Fedora >= 43 ships a filesystem package with those file
+# triggers and the required matching virtual provides.
+%bcond sbin_compat %[0%{?fedora} >= 43]
 
 # riscv64 has LTO disabled globally
 %bcond lto       %["%_arch" != "riscv64"]

                 reply	other threads:[~2026-09-04 13:37 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=178852907704.1.3115607285357343765.rpms-systemd-ce778758540b@fedoraproject.org \
    --to=mail@ikruglov.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