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
Created attachment 1898374 [details] build.log
Created attachment 1898375 [details] root.log
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?
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.
FEDORA-EPEL-2022-342849b603 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-342849b603
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.
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.