Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The non-modular component python-rpm-generators contains machinery that automatically generates Provides and Requires tags for all Python RPM packages (Python 3.6 and Python 2.7).
However, the Provides and Requires tags that need to be generated for new Python 3.8 packages in the python38 module are different.
Thus we need to set the non-modular component python-rpm-generators to ignore Python 3.8 packages. This should be a non-invasive change with respect to other RHEL8 packages.
TlDr: python38 (sub)packages and packages build with python38 cannot provide 'python3dist(*)'.
Such packages can and should contain provide 'python38dist(*)
Reason being it is added only for the _main_ python of the distro.
Acceptance criteria:
- All packages of python38 module provide 'python38dist(*)'
- No package of python38 module provide 'python3dist(*)'
- Package build using python38 module provide 'python38dist(*)'
- Package build using python38 module does not provide 'python3dist(*)'
- Python36 is not affected so still holds that
- Package build using platform-python does provide 'python3dist(*)'
(In reply to Lukáš Zachar from comment #1)
> TlDr: python38 (sub)packages and packages build with python38 cannot provide
> 'python3dist(*)'.
> Such packages can and should contain provide 'python38dist(*)
Just a small correction, it's `python3.8dist(*)`.
> Reason being it is added only for the _main_ python of the distro.
>
> Acceptance criteria:
> - All packages of python38 module provide 'python38dist(*)'
I would say *most* packages. There are a few packages that don't have EGG/DIST-INFO and thus don't generate the Provides, which is acceptable. However, most packages should have it.
> - No package of python38 module provide 'python3dist(*)'
> - Package build using python38 module provide 'python38dist(*)'
> - Package build using python38 module does not provide 'python3dist(*)'
> - Python36 is not affected so still holds that
> - Package build using platform-python does provide 'python3dist(*)'
+1!