Description of problem: Initially suggested here by Orion Poplawski: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/WVX2I3JW56VPUXZZU36QC7XXSCAAT5GM/ > That's a reasonable suggestion. I would suggest you file an RFE request again > python-rpm-macros in EPEL to have the %python_provide macro produce a > Provides: python3-%{name} for the "active" python3 version. With the move from python34 to python36 (and incidentally a decision to stop using python2 altogether even though packages are still present on el7) I ran into failing builds. It got overtaken by events but now that my builds are failing I would rather make sure we won't run into this again down the line when Python 3.6 goes EOL. Actual results: "BuildRequires: python3-foo" doesn't work. Expected results: "BuildRequires: python3-foo" drags the latest python3x-foo in the build root.
python-rpm-macros-3-24.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dad4eed6b7
python-rpm-macros-3-24.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.