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.

Description of problem:

See https://git.centos.org/rpms/python3x-pip/pull-request/1

This should allow %pyproject_wheel to work in EL8

From the looks of it, the request is for python38-pip and python39-pip (if it doesn't already contain this).

Thank you for the PR, Orion, we'll take a look at it.

Is there a reason the latest version hasn't been built in c8s and isn't showing up on https://koji.mbox.centos.org/koji/packageinfo?packageID=3129 ? Is this intentional or is there (yet another...) RHEL nightly compose > CentOS Stream 8 sync issue?

I guess I'm re-asking Maxwell's question - why isn't this in CS8 yet?

The fix has been implemented in python3x-pip version 19.3.1-6 and the build in errata is python3x-pip-19.3.1-6.module+el8.7.0+15823+8950cfa7. I see the same built in C8S as python3x-pip-19.3.1-6.module_el8.7.0+1184+30eba247 (https://koji.mbox.centos.org/koji/buildinfo?buildID=22354) and also in the lastest compose https://composes.centos.org/latest-CentOS-Stream-8/compose/AppStream/x86_64/os/Packages/ . Also, when I try to install python38-pip in a fresh C8S container, dnf gives me python38-pip-19.3.1-6.module_el8.7.0+1184+30eba247 .

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: python38:3.8 and python38-devel:3.8 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:7581