Bug 126201 - rpm doesn't warn when files conflict in different architectures
Summary: rpm doesn't warn when files conflict in different architectures
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: rpm
Version: 3.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-17 13:05 UTC by David Juran
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-06-17 21:41:25 UTC


Attachments (Terms of Use)

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.


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