Bug 126201

Summary: rpm doesn't warn when files conflict in different architectures
Product: Red Hat Enterprise Linux 3 Reporter: David Juran <djuran>
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: msw
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-06-17 21:41:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description David Juran 2004-06-17 13:05:17 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.4.2)
Gecko/20040301

Description of problem:
When updating an installed package with a package from a different
architecture, rpm does not issue an warning when files are conflicting
between the old and the new package

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

How reproducible:
Always

Steps to Reproduce:
1. on a AMD64, make sure that the x86_64 version of e.g. setserial is
installed
2. rpm -Uvh setserial-2.17-12.i386.rpm
     note that no warnings are issued
3. rpm -V setserial-2.17-12.x86_64
..5....T d /usr/share/man/man8/setserial.8.gz
4.  rpm -V setserial-2.17-12.i386
S.5....T   /bin/setserial
    

Additional info:

Comment 1 Jeff Johnson 2004-06-17 21:41:25 UTC
Yup. Warning on arch conflict is not possible when several arches may
be installed on same machine.

What is done instead is prefer the elf64 file in order to
resolve the conflict.