Bug 126201 - rpm doesn't warn when files conflict in different architectures
rpm doesn't warn when files conflict in different architectures
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-06-17 09:05 EDT by David Juran
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-17 17:41:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Juran 2004-06-17 09:05:17 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.4.2)

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):

How reproducible:

Steps to Reproduce:
1. on a AMD64, make sure that the x86_64 version of e.g. setserial is
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 17:41:25 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.