Bug 1164816

Summary: RFE: determine dependencies and build in order
Product: [Community] Copr Reporter: Brian J. Murrell <brian>
Component: backendAssignee: Copr Team <copr-team>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: fedora, fedora, Frodox, jkadlcik, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-04-03 18:28:59 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: 858570    
Bug Blocks:    

Description Brian J. Murrell 2014-11-17 15:19:32 UTC 
Description of problem:
If I submit a new build with multiple SRPMs where there is a build dependency between two (or some) of them, Copr should build these in the correct order.

Version-Release number of selected component (if applicable):
Whatever is currently on https://copr.fedoraproject.org

How reproducible:
100%

Steps to Reproduce:
1. Create two SRPMs, foo and bar where foo takes longer to build than bar (to prevent racing from hiding the bug) and where bar has a BuildRequires on [the version of] the foo package.
2. Submit them both to Copr in a single build
3.

Actual results:
foo and bar will be built at the same time and bar will fail to build

Expected results:
foo should complete it's build before bar is started because bar depends on something in foo

Additional info:
An existing example of this is building evolution and evolution-ews.  The latter will typically fail because it depends on the same version of the former.
Comment 1 Jakub Kadlčík 2023-04-03 18:28:59 UTC 
The bugs related to Copr build system are now migrated to the
default Copr team tracker:
https://github.com/fedora-copr/copr/issues/2638