Description of problem: systemd-boot from EPEL 9 does not install on CentOS Stream 9 due to a file conflict. Version-Release number of selected component (if applicable): systemd-boot-250.3-1.el9 systemd-252-8.el9 How reproducible: always Steps to Reproduce: 1. dnf install systemd-boot Actual results: Error: Transaction test error: file /usr/share/man/man7/systemd-stub.7.gz conflicts between attempted installs of systemd-boot-250.3-1.el9.x86_64 and systemd-252-8.el9.x86_64 Expected results: successful installation Additional info: This also affects RHEL 9.2 (not yet released).
This is caused by bug #2140646 and my request with bug #2157663 made things maybe even more worse…
Honestly, I'm not really sure how to fix this: RHEL 9.2 ships the systemd-boot executables as part of systemd-udev, as well as systemd-boot-unsigned (with the stub files) in CRB. Latter RPM provides systemd-boot, but does not obsolete it.
From my understanding, 'dnf swap systemd-boot systemd-boot-unsigned' and 'dnf install systemd-udev' does hopefully do the trick for existing installations.
I've had a sort of recurrence of this while upgrading a Rocky 9.1 system to 9.3. I have not tried to reproduce this on RHEL yet. ``` Error: Transaction test error: file /usr/bin/coredumpctl from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/sysctl.d/50-default.conf from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system-generators/systemd-integritysetup-generator from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system-generators/systemd-veritysetup-generator from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system/initrd-parse-etc.service from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system/initrd-switch-root.service from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system/proc-sys-fs-binfmt_misc.automount from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system/proc-sys-fs-binfmt_misc.mount from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system/systemd-binfmt.service from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/system/systemd-sysctl.service from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/systemd-binfmt from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/systemd-coredump from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/systemd-integritysetup from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/systemd-sysctl from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/lib/systemd/systemd-veritysetup from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/bash-completion/completions/coredumpctl from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man1/coredumpctl.1.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man5/binfmt.d.5.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man5/coredump.conf.5.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man5/crypttab.5.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man5/integritytab.5.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man5/sysctl.d.5.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-binfmt.service.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-coredump.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-integritysetup-generator.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-integritysetup@.service.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-sysctl.service.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-veritysetup-generator.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 file /usr/share/man/man8/systemd-veritysetup@.service.8.gz from install of systemd-udev-252-18.el9.x86_64 conflicts with file from package systemd-250-12.el9_1.3.x86_64 ``` The only way I was able to convince my system to upgrade was by using `dnf shell` to swap and upgrade in a single transaction: ``` dnf shell --setopt=protected_packages= --noautoremove --refresh > swap systemd-250-12.el9_1.3 systemd-252-18.el9 > upgrade > run ``` I'm mostly commenting here to remind me to look into this more, though I don't know there's really ever going to be a solution to the craziness which happened with systemd here.