Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionYaroslav Popovitch
2011-03-22 19:22:47 UTC
Description of problem:
Rpm allows to install rpm packages with the same name and version but with different architecture. 'Rpm -q', 'rpm -qa' shows only one installed package in the system.
Version-Release number of selected component (if applicable):
rpm-4.8.0-12.el6.i686
How reproducible:
100% reproducible
Steps to Reproduce:
1. Generate two packages with the same name and version but with different architecture.
For example:
auto-1.11.1-5.i386.rpm, auto-1.11.1-5.noarch.rpm
2. Install packages to the system with 'rpm -i'
rpm -i auto-1.11.1-5.i386.rpm
rpm -i auto-1.11.1-5.noarch.rpm
3.1 Run rpm -q command
rpm -q auto-1.11.1-5.i386
rpm -q auto-1.11.1-5.noarch
3.2 Run 'rpm -qa |grep auto' command
Actual results:
3.1
For 'rpm -q'
# rpm -q auto-1.11.1-5.i386
auto-1.11.1-5.i386
# rpm -q auto-1.11.1-5.noarch
package auto-1.11.1-5.noarch is not installed
3.2
# rpm -qa|grep auto
shown only auto-1.11.1-5.i386 package
Expected results:
3.1
# rpm -q auto-1.11.1-5.i386
auto-1.11.1-5.i386
# rpm -q auto-1.11.1-5.noarch
auto-1.11.1-5.noarch
3.2
shown packages:
auto-1.11.1-5.i386
auto-1.11.1-5.noarch
Comment 2RHEL Program Management
2011-04-04 02:08:50 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3RHEL Program Management
2011-10-07 16:04:42 UTC
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
I'm not able to reproduce with the given steps:
[root@localhost ~]# rpm -i archtest-1.0-1.i686.rpm
[root@localhost ~]# rpm -i archtest-1.0-1.noarch.rpm
package archtest-1.0-1.noarch is already installed
The message is a bit misleading but on i686, you can *not* install different archs of same package version in parallel. The closest thing I can come to reproducing this is when one tries to install both packages in the same transaction:
[root@localhost ~]# rpm -i archtest-1.0-1.i686.rpm archtest-1.0-1.noarch.rpm
[root@localhost ~]# rpm -q archtest
archtest-1.0-1.i686
[root@localhost ~]# rpm -qa|grep archtest
archtest-1.0-1.i686
[root@localhost ~]#
The behavior becomes more obvious with -v to explain what happens:
[root@localhost ~]# rpm -iv archtest-1.0-1.i686.rpm archtest-1.0-1.noarch.rpm
warning: package archtest = 1.0-1 was already added, skipping archtest = 1.0-1
Preparing packages for installation...
archtest-1.0-1
[root@localhost ~]#
Ie the second package of same NEVR (but different arch) is simply skipped: trying to install both does not make sense, but it can worked around so rpm doesn't make a lot of noise of it.
Description of problem: Rpm allows to install rpm packages with the same name and version but with different architecture. 'Rpm -q', 'rpm -qa' shows only one installed package in the system. Version-Release number of selected component (if applicable): rpm-4.8.0-12.el6.i686 How reproducible: 100% reproducible Steps to Reproduce: 1. Generate two packages with the same name and version but with different architecture. For example: auto-1.11.1-5.i386.rpm, auto-1.11.1-5.noarch.rpm 2. Install packages to the system with 'rpm -i' rpm -i auto-1.11.1-5.i386.rpm rpm -i auto-1.11.1-5.noarch.rpm 3.1 Run rpm -q command rpm -q auto-1.11.1-5.i386 rpm -q auto-1.11.1-5.noarch 3.2 Run 'rpm -qa |grep auto' command Actual results: 3.1 For 'rpm -q' # rpm -q auto-1.11.1-5.i386 auto-1.11.1-5.i386 # rpm -q auto-1.11.1-5.noarch package auto-1.11.1-5.noarch is not installed 3.2 # rpm -qa|grep auto shown only auto-1.11.1-5.i386 package Expected results: 3.1 # rpm -q auto-1.11.1-5.i386 auto-1.11.1-5.i386 # rpm -q auto-1.11.1-5.noarch auto-1.11.1-5.noarch 3.2 shown packages: auto-1.11.1-5.i386 auto-1.11.1-5.noarch