Description of problem: python3.11-rpm-4.14.3-26.1.el8 in EPEL no longer matches the latest rpm-libs-4.14.3-28.el8_9.x86_64 in RHEL 8, so users cannot install the latest RHEL 8 with python3.11-rpm. Version-Release number of selected component (if applicable): EPEL 8 has python3.11-rpm-4.14.3-26.1.el8 RHEL 8 has rpm-libs-4.14.3-28.el8_9 How reproducible: always Steps to Reproduce: 1. podman run -it --rm --pull=always ubi8 2. yum -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm 3. yum install python3.11-rpm Actual results: Error: Problem: conflicting requests - nothing provides (rpm-libs(x86-64) >= 4.14.3-26 with rpm-libs(x86-64) < 4.14.3-27) needed by python3.11-rpm-4.14.3-26.1.el8.x86_64 from epel (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) Expected results: Yum installs python3.11-rpm successfully
Thanks for the report. I wanted to start with EPEL 8 Next but I got side tracked by modularity infrastructure issues (see https://pagure.io/releng/issue/11947). I guess I'll fixup EPEL 8 first.
The brp-python-script change is no-op for our package, so the only difference between c8s and RHEL 8.9 seems to be in the release number. I'll cherry-pick the c8s commits and lower the release number.
https://src.fedoraproject.org/rpms/python3-rpm/pull-request/12 Are you able to test?
Yes, this works great with my application's test suite.
FEDORA-EPEL-2024-c0d82c247e (python3-rpm-4.14.3-28.1.el8) has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c0d82c247e
FEDORA-EPEL-2024-c0d82c247e has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-c0d82c247e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2024-c0d82c247e (python3-rpm-4.14.3-28.1.el8) has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.