Bug 887549 - libjpeg-turbo-devel and libjpeg-turbo-compat-devel Provides: clash
Summary: libjpeg-turbo-devel and libjpeg-turbo-compat-devel Provides: clash
Keywords:
Status: CLOSED DUPLICATE of bug 887013
Alias: None
Product: Fedora
Classification: Fedora
Component: libjpeg-turbo
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-16 08:47 UTC by Ralf Corsepius
Modified: 2013-04-30 23:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-17 10:35:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.