Attempting to build a package for epel10 results in this error in root.log
DEBUG util.py:558: Executing command: ['/usr/bin/dnf-3', '--installroot', '/var/lib/mock/epel10.0-build-53432824-6395462-bootstrap/root/', '--setopt=install_weak_deps=0', '--setopt=optional_metadata_types=filelists', '--disableplugin=local', '--disableplugin=spacewalk', '--disableplugin=versionlock', 'install', 'python3-dnf', 'dnf-plugins-core', '--setopt=tsflags=nocontexts'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/var/lib/mock/epel10.0-build-53432824-6395462-bootstrap/root/installation-homedir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'LC_MESSAGES': 'C.UTF-8'} and shell False DEBUG util.py:461: Unable to detect release version (use '--releasever' to specify release version) DEBUG util.py:461: No matches found for the following disable plugin patterns: local, spacewalk, versionlock DEBUG util.py:463: No match for argument: python3-dnf DEBUG util.py:463: No match for argument: dnf-plugins-core DEBUG util.py:461: Error: Unable to find a match: python3-dnf dnf-plugins-core DEBUG util.py:610: Child return code was: 1
Examples: https://koji.fedoraproject.org/koji/taskinfo?taskID=122927745 (perl-Module-Build-Tiny) https://koji.fedoraproject.org/koji/taskinfo?taskID=122927745 (perl-String-CRC32)
It seems that CentOS Stream builds (e.g. python3-dnf) disappeared from epel10.0-build Brew repository. Did somebody forget to add a side repo with CentOS Stream packages?
The CentOS Stream 10 repodata for the 2024-09-03 compose appears to be largely devoid of content. The primary.xml file only includes the shim package.
Reported here: https://pagure.io/centos-infra/issue/1489 Not sure it's the right place though.
Metadata Update from @kevin: - Issue assigned to kevin
This should be fixed now.
A new centos 10 stream compose was made, I synced it down and regenerated the koji buildroot.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)