Bug 2109363

Summary: python38-itsdangerous-epel FTBFS in EPEL 8
Product: [Fedora] Fedora EPEL Reporter: Maxwell G <maxwell>
Component: python38-itsdangerous-epelAssignee: Orion Poplawski <orion>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel8CC: maxwell, orion, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python38-itsdangerous-epel-2.1.1-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-13 03:13:54 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:
Bug Depends On:    
Bug Blocks: 1914423, 1946686    
Attachments:
Description Flags
build.log
none
root.log none

Description Maxwell G 2022-07-21 04:22:11 UTC
Description of problem:
python38-itsdangerous-epel fails to build from source in EPEL 8.

Version-Release number of selected component (if applicable):
python38-itsdangerous-epel-2.0.1-2.el8.src.rpm

Comment 1 Maxwell G 2022-07-21 04:22:47 UTC
Created attachment 1898374 [details]
build.log

Comment 2 Maxwell G 2022-07-21 04:23:29 UTC
Created attachment 1898375 [details]
root.log

Comment 3 Troy Dawson 2022-07-22 13:49:17 UTC
I'm confused about this.
You are rebuilding this package:  "Rebuild to fix bug in epel-rpm-macros' Python dependency generator"
And yet when you are done with the rebuild, nothing will have changed.
This package already has the same dependencies that the Fedora version of it does, except it depends on "python(abi) = 3.8" instead of 3.11.

Why is it being rebuilt?
And with a failure, why is it getting put on two separate trackers?

My big concern isn't just with python38-itsdangerous-epel, it's with all the other python packages.

Are you planning on rebuilding all the python38 packages in epel?
Will they also be getting thse FTBFS bugs?
Was there an announcement about this that I missed?

Comment 4 Troy Dawson 2022-07-22 14:09:16 UTC
I am terribly sorry.  I should have searched harder before writting the above.
An email was sent out, with a reason given.
My apologies.
Carry on.

Comment 5 Fedora Update System 2022-11-05 02:22:26 UTC
FEDORA-EPEL-2022-342849b603 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-342849b603

Comment 6 Fedora Update System 2022-11-05 17:42:22 UTC
FEDORA-EPEL-2022-342849b603 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-342849b603

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-11-13 03:13:54 UTC
FEDORA-EPEL-2022-342849b603 has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.