Bug 21214 - architecture "aliases" are not used
Summary: architecture "aliases" are not used
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: up2date
Version: 7.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact: Aaron Brown
: 21237 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2000-11-22 01:06 UTC by Arenas Belon, Carlo Marcelo
Modified: 2007-04-18 16:29 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2000-12-23 07:32:19 UTC

Attachments (Terms of Use)

Description Arenas Belon, Carlo Marcelo 2000-11-22 01:06:44 UTC
even if running RedHat 7.0 on a i686 architecture, the RHN Update Agent
would only use the i386 versions of the packages

there is a :


entry on /etc/sysconfig/rhn/systemid

but the glibc-2.2-5.i386.rpm would be installed instead of the
glibc-2.2-5.i686.rpm that is best suited for this "architecture"

to be fair, i am not sure if this is a bug on the up2date scripts or in the
way the up2date "metadata" is build from the available updates

hope i could be of more help

Comment 1 Preston Brown 2000-11-28 16:54:19 UTC
Cristian:  are you sure you are doing architecture scoring right?

Comment 2 Preston Brown 2000-11-28 19:52:05 UTC
*** Bug 21237 has been marked as a duplicate of this bug. ***

Comment 3 Preston Brown 2000-11-28 20:05:25 UTC
*** Bug 21237 has been marked as a duplicate of this bug. ***

Comment 4 Arenas Belon, Carlo Marcelo 2000-12-19 01:48:03 UTC
FWIW latest glibc (2.2-9) errata is not "correctly" updated with the up2date

the "correct" rpm can be installed using :

  rpm -Uvh --force glibc-2.2-9-${ARCH}.rpm (where ARCH={i586,i686}

as a workaround

Comment 5 Arenas Belon, Carlo Marcelo 2000-12-23 07:32:16 UTC
no more workaround AFAIK, latest up2date update (2.1.7-1) selected the right
glibc architecture (i686) on a i686 system

Comment 6 Arenas Belon, Carlo Marcelo 2000-12-23 07:36:19 UTC
even if not on the "Bug IDs fixed" on :


this is already fixed

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