+++ This bug was initially created as a clone of Bug #644778 +++
Description of problem:
There is a file conflict between many packages (i386 and x86_64) in the optional repository for the Workstation variant, x86_64 arch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Do yum localinstall *.rpm inside the optional repository
Multiple file conflicts, transaction aborted.
WIll post the entire log in the next comment.
--- Additional comment from atodorov on 2010-10-20 12:05:41 EEST ---
Running Transaction Test
Transaction Check Error:
file /usr/share/doc/wordnet-3.0/html/Makefile conflicts between attempted installs of wordnet-3.0-13.el6.x86_64 and wordnet-3.0-13.el6.i686
file /usr/share/doc/wordnet-3.0/pdf/Makefile conflicts between attempted installs of wordnet-3.0-13.el6.x86_64 and wordnet-3.0-13.el6.i686
file /usr/share/doc/wordnet-3.0/ps/Makefile conflicts between attempted installs of wordnet-3.0-13.el6.x86_64 and wordnet-3.0-13.el6.i686
--- Additional comment from atodorov on 2010-10-20 14:02:24 EEST ---
For the conflicting documentation files see bug #449731 (RHEL4) - it requested that rpm ignores file conflicts under /usr/share/doc to work around several multilib conflicts on ia64.
Created attachment 463476 [details]
Remove unneeded and conflicting Makefiles* from documentation directory.
This issue was proposed for RHEL 6.1 FasTrack but did not get resolved in time.
It has been moved to RHEL 6.2 FasTrack.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Installing both wordnet packages compiled for 32-bit and 64-bit
system on the same host.
The later packages could not been installed because of
Auxiliary files in conflict have been removed from the packages.
wordnet package is now multi-architecture safe.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.