Bug 679507 - Cannot install both i686 and x86_64
Summary: Cannot install both i686 and x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 678982
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Benjamin Kosnik
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-22 18:45 UTC by Joel Kirchmeyer
Modified: 2013-08-09 05:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-02-23 19:00:16 UTC
Type: ---

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

Description Joel Kirchmeyer 2011-02-22 18:45:47 UTC 
Description of problem:
Cannot install both i686 and x86_64

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Transaction Check Error:
  file /usr/share/gcc-4.6.0/python/libjava/aotcompile.pyc from install of libstdc++-4.6.0-0.8.fc15.i686 conflicts with file from package libstdc++-4.6.0-0.8.fc15.x86_64
  file /usr/share/gcc-4.6.0/python/libjava/aotcompile.pyo from install of libstdc++-4.6.0-0.8.fc15.i686 conflicts with file from package libstdc++-4.6.0-0.8.fc15.x86_64
  file /usr/share/gcc-4.6.0/python/libjava/classfile.pyc from install of libstdc++-4.6.0-0.8.fc15.i686 conflicts with file from package libstdc++-4.6.0-0.8.fc15.x86_64
  file /usr/share/gcc-4.6.0/python/libjava/classfile.pyo from install of libstdc++-4.6.0-0.8.fc15.i686 conflicts with file from package libstdc++-4.6.0-0.8.fc15.x86_64


Expected results:


Additional info:
Comment 1 Joel Kirchmeyer 2011-02-23 14:42:35 UTC 
I saw mention of
gcc-4.6.0-0.9.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/gcc-4.6.0-0.9.fc15

but it's not fixed in that build.
Comment 2 Jakub Jelinek 2011-02-23 19:00:16 UTC 

*** This bug has been marked as a duplicate of bug 678982 ***
Note You need to log in before you can comment on or make changes to this bug.