Bug 50115 - Packages with same name, different arch indistinguishable
Summary: Packages with same name, different arch indistinguishable
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnorpm
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Alexander Larsson
QA Contact: David Lawrence
: 52389 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-26 22:50 UTC by James Turner
Modified: 2007-04-18 16:35 UTC (History)
0 users

Clone Of:
Last Closed: 2001-08-02 15:34:29 UTC

Attachments (Terms of Use)

Description James Turner 2001-07-26 22:50:19 UTC
Description of Problem:
(usability grumbles)

Where there are several packages with the same name but different
architecture, they are indistinguishable from each other in the "Install"
window. Also, for installed packages, it doesn't seem possible to
tell which arch version of the package was installed. (possibly RPM
limitations rather than GnoRPM?)

How Reproducible:
Every time

Steps to Reproduce:
1. Insert and mount Red Hat 7.1 installation disc 1 (for example)
2. Fire up GnoRPM
3. Click Install
4. Observe duplicate entries for "gzip", "kernel", "glibc", etc.
5. Note that it is not possible to tell which arch version was installed
   by querying the installed version of one of the above 3 packages.

Entries for "kernel" might appear as

Would look better as
kernel-2.4.2-2 (i386)
kernel-2.4.2-2 (i586)
kernel-2.4.2-2 (i686)

Comment 1 Alexander Larsson 2001-07-27 14:43:46 UTC
Ah, that does indeed make it slightly hard to use.

Comment 2 Alexander Larsson 2001-08-02 15:34:24 UTC
In order to get the developers and maintainers of GnoRPM to look at this bug I
have moved it to the GnoRPM category in the Gnome bug tracker. It can be found
at http://bugzilla.gnome.org/show_bug.cgi?id=58445, where you can add yourself
to the cc-field if you want to recieve information about changes to the bug tatus.

Comment 3 Alexander Larsson 2001-08-23 15:02:34 UTC
*** Bug 52389 has been marked as a duplicate of this bug. ***

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