Bug 887549

Summary: libjpeg-turbo-devel and libjpeg-turbo-compat-devel Provides: clash
Product: [Fedora] Fedora Reporter: Ralf Corsepius <rc040203>
Component: libjpeg-turboAssignee: Adam Tkac <atkac>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: rawhideCC: atkac, ovasik
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: 2012-12-17 10:35:43 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 Ralf Corsepius 2012-12-16 08:47:01 UTC 
Description of problem:

The provides provided by libjpeg-turbo-devel and libjpeg-turbo-compat-devel
in rawhide conflict:

# rpm -q --provides -p libjpeg-turbo-devel-1.2.1-5.fc19.x86_64.rpm
libjpeg-devel = 6b-47.fc19
libjpeg-devel(x86-64) = 6b-47.fc19
libjpeg-turbo-devel = 1.2.1-5.fc19
libjpeg-turbo-devel(x86-64) = 1.2.1-5.fc19
# rpm -q --provides -p libjpeg-turbo-compat-devel-1.2.1-5.fc19.x86_64.rpm
libjpeg-devel = 6b-47.fc19
libjpeg-devel(x86-64) = 6b-47.fc19
libjpeg-turbo-compat-devel = 1.2.1-5.fc19
libjpeg-turbo-compat-devel(x86-64) = 1.2.1-5.fc19

Note: Both provide libjpeg-devel and libjpeg-devel(x86-64)

This breaks building packages, which BR: libjpeg-devel, 
because having one of each packages installed satisfies "BR: libjpeg-devel".

=> Non deterministic build results and non-deterministic build breakdowns (I am facing such breakdowns).


Version-Release number of selected component (if applicable):
1.2.1-5.fc19

Expected results:
Only one of these packages to provide libjpeg-devel.
Comment 1 Ralf Corsepius 2012-12-16 17:05:37 UTC 
Increasing priority, this shape this package is in is unusable.
Comment 2 Adam Tkac 2012-12-17 10:35:43 UTC 

*** This bug has been marked as a duplicate of bug 887013 ***