Description of problem: DEBUG util.py:443: Error: DEBUG util.py:443: Problem: package sane-backends-devel-1.2.1-1.fc37.ppc64le requires sane-backends = 1.2.1-1.fc37, but none of the providers can be installed DEBUG util.py:443: - package sane-backends-1.2.1-1.fc37.ppc64le requires systemd-udev >= 196, but none of the providers can be installed DEBUG util.py:443: - conflicting requests DEBUG util.py:443: - nothing provides systemd-boot-unsigned(ppc-64) = 251.13-5.fc37 needed by systemd-udev-251.13-5.fc37.ppc64le DEBUG util.py:445: (try to add '--skip-broken' to skip uninstallable packages) DEBUG util.py:596: Child return code was: 1 Version-Release number of selected component (if applicable): sane-backends-devel-1.2.1-1.fc37.ppc64le How reproducible: 100% Steps to Reproduce: 1. fedpkg build libreoffice Actual results: as above Expected results: worked earlier in fedora 37 cycle Additional info: presumably some part of the recent systemd conditionals is at play commit ff5d912bcadeec7b87cea423aef796779fd3e8e9 Author: Zdenek Dohnal <zdohnal> Date: Wed Mar 1 15:21:14 2023 +0100 hyphen is not allowed in RPM, use underscore commit 1ff59ebe6618fdde66ea2d1b3711fc94cb3c1bad Author: Zdenek Dohnal <zdohnal> Date: Mon Feb 27 09:12:50 2023 +0100 flatpak doesn't want systemd only in runtime commit 0ad9add3c7f570cc30ce4f35eb47c9f92f703541 Author: Zdenek Dohnal <zdohnal> Date: Thu Feb 23 16:23:37 2023 +0100 add bcond for systemd - used in flatpak
Hi Caolan, thank you for reporting the issue! Those commits actually aren't in the latest F37 build, they are only committed because module build needs them (sane-backends will be part of simple-scan flatpak, which uses modules and containers). Actually it is an error in systemd, which started to require systemd-boot-unsigned on all archs, but the package is built only on archs which have GNU EFI. Created PR: https://src.fedoraproject.org/rpms/systemd/pull-request/103
Looks like systemd people don't check pagure - the same fix was applied in dist-git yesterday after I had opened the PR. So closing this one as dupe of newer bug. *** This bug has been marked as a duplicate of bug 2177691 ***