This is a tracking bug for Change: Automatic Provides for Python RPM Packages
For more details, see: https://fedoraproject.org//wiki/Changes/Automatic_Provides_for_Python_RPM_Packages
Upon building Python packages containing packaging metadata, RPM will automatically detect the standardized name of the software (i.e. dist name, name on PyPI) in the canonical format and create a virtual Provides tag with the value pythonX.Ydist(CANONICAL_NAME), where X.Y is the used Python version.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
On 2016-July-26, we have reached Fedora 25 Change Checkpoint: Completion deadline (testable).
At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.
Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.
Incomplete and non testable Changes will be reported to FESCo on 2016-July-29 meeting.
New macros are ready to be deployed and a draft for Fedora Packaging Guidelines for Python is fully prepared as well.
We are waiting for a new version of the rpm package to drop into rawhide repos (which it hasn't since Friday 12th). After it does, a targeted rebuild of rawhide packages will be done. At that point macros will be deployed and guidelines can be modified. And that will mean this Fedora Change is complete.
As before new macros and Guidelines draft are ready to be deployed.
However, the guidelines draft should be unveiled only after all Python packages have the new Provides tags generated.
We've been debugging some small issues with the RPM Provides generator that was backported from upstream to Fedora. Right now, all issues seem to be finally fixed.
We had planned to do a new targeted rebuild of all Python packages so the proper Provides tags would be generated and the macros can start to be used ASAP. However, we have decided that we are getting close to the Fedora 26 mass rebuild, and thus a targeted rebuild won't be necessary.
Everything is ready. We are waiting for Fedora 26 mass rebuild, after which the change to the guidelines should be unveiled.
On 2016-Sep-27 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 25 release. At this point all the Changes not at least in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.
The code is in, but supporting macros and the Guidelines change is still being discussed .
This can be done after F25 is released with no ill effects.
Formally, the Change wasn't all implemented in time, so we can invoke the contingency plan: "Do not update the Fedora Packaging Guidelines".
Postponing this Change as suggested in Comment #6 and approced by FESCo in https://fedorahosted.org/fesco/ticket/1630#comment:3
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
This was done in Fedora 26.
BTW the change page https://fedoraproject.org/wiki/Changes/Automatic_Provides_for_Python_RPM_Packages is categorised as ChangePageIncomplete and thus not listed in https://fedoraproject.org/wiki/Releases/25/ChangeSet or https://fedoraproject.org/wiki/Releases/26/ChangeSet