Bug 313011 - Conflicts between fontconfig-devel.x86_64 and fontconfig-devel.i386
Summary: Conflicts between fontconfig-devel.x86_64 and fontconfig-devel.i386
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: 7
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 336731 341151 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-09-30 12:20 UTC by André Johansen
Modified: 2008-02-22 22:01 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-26 00:55:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description André Johansen 2007-09-30 12:20:29 UTC 
+++ This bug was initially created as a clone of Bug #312991 +++

Description of problem:
On Fedora 7/x86-64, installing fontconfig-devel.x86_64 and 
fontconfig-devel.i386 
(for compiling 32 bit applications) causes conflicts.


Version-Release number of selected component (if applicable):
2.4.2-3.fc7

How reproducible:
Every time.

Steps to Reproduce:
1. Install Fedora 7/x86-64
2. Have fontconfig-devel.x86_64 installed
3. yum install fontconfig-devel.i386
  
Actual results:
Transaction Check Error:
  file /usr/share/doc/fontconfig-devel-2.4.2/fontconfig-devel.txt from install 
of fontconfig-devel-2.4.2-3.fc7 conflicts with file from package 
fontconfig-devel-2.4.2-3.fc7


Expected results:
The package should install to accommodate 64 and 32 bit development.

Additional info:
Comment 1 Behdad Esfahbod 2007-10-26 00:39:07 UTC 
*** Bug 341151 has been marked as a duplicate of this bug. ***
Comment 2 Behdad Esfahbod 2007-10-26 01:10:30 UTC 
*** Bug 336731 has been marked as a duplicate of this bug. ***
Comment 3 Behdad Esfahbod 2007-10-26 01:15:20 UTC 
*** Bug 251289 has been marked as a duplicate of this bug. ***
Comment 4 Benjamin Smedberg 2008-02-22 22:01:26 UTC 
verified fixed with fontconfig/fontconfig-devel 2.5.0-2.fc9
Note You need to log in before you can comment on or make changes to this bug.