Bug 72695 - Installer needs to update up2date before running up2date
Summary: Installer needs to update up2date before running up2date
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: unspecified
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Adrian Likins
QA Contact: Fanny Augustin
Depends On:
TreeView+ depends on / blocked
Reported: 2002-08-26 18:30 UTC by Matt Jamison
Modified: 2007-07-31 19:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2002-08-26 19:04:07 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Josef Komenda 2002-08-26 18:30:41 UTC
Description of Problem: when running the installer, it will optionally run
up2date. Currently, up2date incorrectly identifies the processor that sat-inst
is using - running 'up2date up2date' before launching the full gui installer
would fix this. 

Version-Release number of selected component (if applicable): bug 63780

Comment 1 Adrian Likins 2002-08-26 18:33:17 UTC
incorrectly identifies the processor?


Comment 2 Josef Komenda 2002-08-26 19:00:40 UTC
Yup - the stock 7.2 up2date seemed to think that sat-inst.webdev-colo was an
athlon. upgrading up2date made it see the light - it's i686. Todd had to do this
with the new proxy installer as well. 

Comment 3 Josef Komenda 2002-08-26 19:03:59 UTC
Ah - this is Misa's bug: 

Update of /mnt/devel/CVS/rhn/backend/server
In directory devserv.devel.redhat.com:/tmp/cvs-serv7970

Modified Files:
Log Message:
The pristine 7.2 up2date had a bug where it was not selecting the right
arch if an incompatible one was presented before a compatible one. Reordering
them on the server side fixes this. My bad, shouldn't have put the desc there.

The old query had: order by generation
In the new query, rank is ascending the way it's supposed to be (i386 has only
noarch and i386 to be compatible with, while i686 has all of them)

Comment 4 Josef Komenda 2002-08-26 20:37:40 UTC
Fixed, closing.

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