On Thu, Jul 11, 2024 at 10:54 AM František Šumšal <frantisek@xxxxxxxxx> wrote:
Hey!
I'm updating one of my packages due to a couple of CVEs, and when I got to the EPEL 8 branch I can't seem to do a scratch build (via `fedpkg scratch-build`). All attempts (even the ones rebuilding an existing SRPM) fail when mock tries to install dnf:
Start(bootstrap): installing dnf tooling
ERROR: Command failed:
# /usr/bin/dnf-3 --installroot /var/lib/mock/epel8-build-52195576-6245162-bootstrap/root/ --setopt=install_weak_deps=0 --disableplugin=local --disableplugin=spacewalk --disableplugin=versionlock install python3-dnf dnf-plugins-core --setopt=tsflags=nocontexts
Unable to detect release version (use '--releasever' to specify release version)
No matches found for the following disable plugin patterns: local, spacewalk, versionlock
Last metadata expiration check: 0:00:06 ago on Thu Jul 11 17:45:35 2024.
Error:
Problem 1: conflicting requests
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.0.9.2-5.el8.noarch from build
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.2.17-6.el8.noarch from build
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.2.17-7.el8_2.noarch from build
...
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.7.0-19.el8.noarch from build
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.7.0-20.el8.noarch from build
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.7.0-4.el8.noarch from build
- nothing provides /usr/libexec/platform-python needed by python3-dnf-4.7.0-8.el8.noarch from build
(try to add '--skip-broken' to skip uninstallable packages or '--setopt=optional_metadata_types=filelists' to load additional filelists metadata)
Full log: https://kojipkgs.fedoraproject.org//work/tasks/6447/120336447/mock_output.log (taken from https://koji.fedoraproject.org/koji/taskinfo?taskID=120336447)
Am I doing something wrong?
It's not just you, I started seeing the same thing last night.
I was hoping it was just some weird networking bug, and I wasn't in a rush, so I let it be until today. But no luck.
Essentially the same thing you have, so I'm not going to repeat it.
My best guess is it's a modularity / grobisplitter issue. But I'm not in a position to see things.
I think this deserves a releng ticket.
Troy
-- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
