Bug 2104963

Summary:	python38 module from 20220702.n.0 compose is broken
Product:	Red Hat Enterprise Linux 8	Reporter:	Maxwell G <maxwell>
Component:	distribution	Assignee:	Johnny Hughes <jhughes>
Status:	CLOSED MIGRATED	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bstinson, carl, jwboyer, python-maint
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-14 13:18:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Maxwell G 2022-07-07 15:10:42 UTC

Description of problem:
The 20220702.n.0 CentOS Stream 8 compose has a broken python38 module that is missing essential packages such as python38-setuptools. This makes it impossible to build python38 packages for EPEL 8 Next, amongst other problems.

Version-Release number of selected component (if applicable):
python38:3.8:8070020220624145122:bd194b04

Comment 1 Maxwell G 2022-07-09 01:24:20 UTC

python38:3.8:8070020220705185202:bd194b04 from the 20220706.n.0 compose (which seems to have been published today) has python38-setuptools again. I think this can be closed, but I would check to make sure no other packages are missing before doing so.

Comment 2 RHEL Program Management 2023-09-14 13:17:18 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 3 RHEL Program Management 2023-09-14 13:18:12 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.