Bug 773738 - multilib conflict
Summary: multilib conflict
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libxcb
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-12 18:25 UTC by Jan Kratochvil
Modified: 2012-01-14 20:02 UTC (History)
5 users (show)

Fixed In Version: libxcb-1.8-2.fc17
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-14 20:02:08 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jan Kratochvil 2012-01-12 18:25:42 UTC 
Description of problem:
Update Rawhide.

Version-Release number of selected component (if applicable):
libxcb-1.8-1.fc17

How reproducible:
Always.

Steps to Reproduce:
yum install libxcb.{x86_64,i686}
later:
yum update

Actual results:
  file /usr/share/doc/libxcb-1.8/manual/xv_8h_source.html conflicts between attempted installs of libxcb-1.8-1.fc17.i686 and libxcb-1.8-1.fc17.x86_64
  file /usr/share/doc/libxcb-1.8/manual/xvmc_8h_source.html conflicts between attempted installs of libxcb-1.8-1.fc17.i686 and libxcb-1.8-1.fc17.x86_64
...

Expected results:
Updated package.

Additional info:
Maybe just create libxcb-doc.noarch?
Comment 1 Zdenek Kabelac 2012-01-13 10:11:30 UTC 
Well in fact,  libxcb.i686 wants to be upgrades/installed even on my x86_64 system.

# LANG=C yum upgrade libxcb.x86_64
Loaded plugins: auto-update-debuginfo, changelog, merge-conf, priorities, refresh-updatesd
Setting up Upgrade Process
Resolving Dependencies
--> Running transaction check
---> Package libxcb.x86_64 0:1.7-3.fc16 will be updated
---> Package libxcb.x86_64 0:1.8-1.fc17 will be an update
--> Finished Dependency Resolution
Error: Protected multilib versions: libxcb-1.8-1.fc17.x86_64 != libxcb-1.7-3.fc16.i686
Comment 2 Andreas Bierfert 2012-01-14 09:34:28 UTC 
http://koji.fedoraproject.org/koji/buildinfo?buildID=285047 fixes the issue for me. Thanks.
Note You need to log in before you can comment on or make changes to this bug.