Description of problem: In Fedora 34+, python3-devel requires pyproject-rpm-macros. Individual python packages do not need to BuildRequire it explicitly. In CentOS Stream 9, python3-devel does not require pyproject-rpm-macros. As a result, it is not easy to rebuild Fedora python packages on RHEL 9 if they use the new pyproject RPM macros. This hinders the adoption of these modern macros. Version-Release number of selected component (if applicable): python3-devel-3.9.6-6.el9 How reproducible: always Steps to Reproduce: 1. Run dnf repoquery --requires python3-devel on Fedora 34+ 2. Run dnf repoquery --requires python3-devel on CentOS 9 3. Compare the presence or absence of pyproject-rpm-macros Actual results: CentOS 9's python3-devel does not require pyproject-rpm-macros, so every Python packager for el9 must add "BuildRequires: pyproject-rpm-macros" to each individual package. This leads to a divergence between Fedora, more friction with EPEL 9. Developers must re-add code they've already cleaned up across spec files over multiple Fedora releases. Expected results: CentOS 9's python3-devel package requires pyproject-rpm-macros just as in Fedora. Additional info:
Here's an example package where I have to add "BuildRequires: pyproject-rpm-macros". I expect to encounter this more often as more Fedora packages clean up. https://src.fedoraproject.org/fork/ktdreyer/rpms/python-websocket-client/commits/rhbz2001034
Looks like this was a one-line change in Fedora: https://src.fedoraproject.org/rpms/python3.10/c/d2d07f0ea7f6f7a1ccc34ab90abe22598ee382db
Indeed, that would be useful. One problem I see is that pyproject-rpm-macros is in the CRB repository while both python3-devel and rpm-build are in AppStream. Hence requiring it might move pyproject-rpm-macros to AppStream which might not be desired. Can we make this happen somehow, or is that a blocker?
About EPEL: Once epel-rpm-macros is available for EPEL 9 Next, we can add the requirement there (i.e. add Requires: pyproject-rpm-macros if python3-devel).
Removing devel_ack which should have not been given before the repo thing is answered.
(In reply to Miro Hrončok from comment #3) > Indeed, that would be useful. One problem I see is that pyproject-rpm-macros > is in the CRB repository while both python3-devel and rpm-build are in > AppStream. Hence requiring it might move pyproject-rpm-macros to AppStream > which might not be desired. > > Can we make this happen somehow, or is that a blocker? Since python3-devel needs to *runtime* require pyproject-rpm-macros, adding that dependency to python3-devel in AppStream would indeed pull pyproject-rpm-macros into the same repository. Packages from BaseOS/AppStream can't runtime-require packages outside of these two repos. That way the packages are installable without having to enable any other repository. And we do not consider pyproject-rpm-macros a suitable candidate for AppStream, because we would be forced to guarantee backwards compatibility for the next 10/15 years. Since the macros are rather new in Fedora, they're expected to evolve and change, often in backwards incompatible ways. So by including pyproject-rpm-macros in AppStream, we would be forced to keep the old version of the macros, and over time we would introduce much greater inconsistency between Fedora and RHEL then just adding one more buildrequires. > About EPEL: Once epel-rpm-macros is available for EPEL 9 Next, we can add the requirement there (i.e. add Requires: pyproject-rpm-macros if python3-devel). I like that idea.
Reassigning this bug to EPEL since it cannot be solved on the RHEL side. There is no EPEL 9 yet, so I've set it to EPEL 8 temporarily.
I will be working on the initial epel-rpm-macros fpr epel9-next this week. I'll be sure to get this in.
Troy, if you do, please add: Requires: pyproject-rpm-macros if python3-rpm-macros That'll ensure pyproject-rpm-macros are only pulled in when python3-rpm-macros is required, which is pulled in by another conditional requirement in python3-devel (required only if rpm-build). Or import the package without this and we'll send a PR later.
I've added it to the spec file https://src.fedoraproject.org/rpms/epel-rpm-macros/blob/epel9-next/f/epel-rpm-macros.spec Still working on the package, but it should be in the first release. Taking this ticket, and I'll close it when we manage to get epel-rpm-macros built.
FEDORA-EPEL-NEXT-2021-341875060f has been submitted as an update to Fedora EPEL 9 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-341875060f
FEDORA-EPEL-NEXT-2021-341875060f has been pushed to the Fedora EPEL 9 Next testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2021-341875060f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-NEXT-2021-341875060f has been pushed to the Fedora EPEL 9 Next stable repository. If problem still persists, please make note of it in this bug report.