Bug 2097122

Summary: copr-backend fails to build with the latest setuptools version
Product: [Fedora] Fedora Reporter: Charalampos Stratakis <cstratak>
Component: copr-backendAssignee: Copr Team <copr-team>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: clime7, copr-team, jkadlcik, msuchy, praiskup, turecek.dominik
Target Milestone: ---   
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: 2022-06-15 08:10:13 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: 2064842    

Description Charalampos Stratakis 2022-06-14 21:52:45 UTC
copr-backend fails to build with the latest setuptools version.

This report is automated and not very verbose, but we'll try to get back here with details.

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/cstratak/setuptools-62.4.0-final/fedora-rawhide-x86_64/04533400-copr-backend/

For all our attempts to build copr-backend with the latest setuptools, see:
https://copr.fedorainfracloud.org/coprs/cstratak/setuptools-62.4.0-final/package/copr-backend/

Testing and rebuild of packages is happening in copr. You can follow these instructions to test locally in mock if your package builds with latest setuptools version:
https://copr.fedorainfracloud.org/coprs/cstratak/setuptools-62.4.0-final/

Let us know here if you have any questions.

Comment 1 Pavel Raiskup 2022-06-15 08:10:13 UTC
Thank you for the report!

This was probably some temporary problem, some of the test cases are a bit
racy.  I tried to reproduce locally with the testing mock config, and
the build passed.

We'll do a new upstream release next week, so this issue (if present)
would be handled anyway very soon.