Bug 477226

Summary:	xine-lib-devel multilib conflict
Product:	[Fedora] Fedora	Reporter:	Philippe Troin <phil>
Component:	xine-lib	Assignee:	Aurelien Bompard <gauret>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	gauret, kevin, phil, rdieter
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	1.1.16.2-3.fc10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-13 18:39:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Philippe Troin 2008-12-19 18:35:34 UTC

Description of problem:

yum install xine-lib-devel.i386 xine-lib-devel.x86_64

fails with:

Transaction Check Error:
  file /usr/bin/xine-config conflicts between attempted installs of xine-lib-devel-1.1.15-3.fc10.x86_64 and xine-lib-devel-1.1.15-3.fc10.i386


Version-Release number of selected component (if applicable):
xine-lib-devel-1.1.15-3.fc10

Comment 1 Kevin Kofler 2008-12-19 18:40:26 UTC

Valid complaint => triaging to ASSIGNED.

Comment 2 Fedora Update System 2009-02-24 20:55:10 UTC

xine-lib-1.1.16.2-3.fc10 has been pushed to the Fedora 10 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update xine-lib'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-2013

Comment 3 Fedora Update System 2009-03-13 18:37:33 UTC

xine-lib-1.1.16.2-3.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2009-03-13 18:39:33 UTC

xine-lib-1.1.16.2-3.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.