RE: Packages Upgrades from 7.1 --> 7.2 (Itanium) - FOLLOW UP

Anyone at RedHat read this board?
Any recommendation on the problem detailed below?

-----Original Message-----
From: [email protected] [mailto:[email protected]]On
Behalf Of Donny Cooper
Sent: Wednesday, March 13, 2002 11:47 AM
To: [email protected]
Subject: RE: Packages Upgrades from 7.1 --> 7.2 (Itanium) - FOLLOW UP



In addition to choosing "Upgrade Existing System" (as in the last email), I have also tried the option to select
individual packages to be upgraded.  All of the packages installed are selected by default (including those in question,
such as glibc), but still DO NOT get upgraded to the 7.2 Distribution Level (according to the RPM Database).

It appears that the packages (docs, etc...) are actually upgraded to the appropriate level, but the RPM Database info is
not.  Is there some problem with the RPM Database being updated?  This doesn't appear to be a problem on an IA32 7.1 -->
7.2 upgrade.

Here's an example of the conflicting info:
------------------------------------------

# rpm -qa | grep gcc-2.96
gcc-2.96-85

# gcc -v
Reading specs from /usr/lib/gcc-lib/ia64-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-101)

------------------------------------------
: As you can see, the RPM Database reports 2.96-85, but the actual package is 2.96-101 (which is the level shipped with
7.2).

Any insight is appreciated.

Donny

-----Original Message-----
From: [email protected] [mailto:[email protected]]On
Behalf Of Donny Cooper
Sent: Tuesday, March 12, 2002 5:25 PM
To: [email protected]
Subject: Packages Upgrades from 7.1 --> 7.2 (Itanium)



What system components are "candidate" when you "Upgrade Existing System"?

I have upgraded a 7.1 system to 7.2, but noticed that certain packages do not get upgraded to the level distributed with
7.2 (important ones, like glibc).  Is this an Itanium thing or is there some rule on package selection when you use the
upgrade option?

Some of these components are very important, since these systems are used for porting applications, but I prefer not to
do a clean install every time we move to the next release.

If this is just the way it is, what is a safe package and package dependency list to install post upgrade, to make the
machine look just like a clean install, or at least so I know that we are porting safely to that release?

(some details are below)

Thanks,
-----------------------------------
Donny Cooper
NEC Systems, Inc.
Advanced Technical Computing Center
[email protected]
-----------------------------------



Here is some package info from a
system that was upgraded to 7.2 from 7.1:
=========================================
(upgrade_install) # cat /etc/redhat-release
Red Hat Linux release 7.2 (Enigma)

(upgrade_install) # rpm -qa | grep redhat-release
redhat-release-7.1-1

(upgrade_install) # rpm -qa | grep glibc
glibc-common-2.2.3-10
glibc-devel-2.2.3-10
glibc-profile-2.2.3-10
glibc-2.2.3-10


Here is some package info from a
system that was installed cleanly with 7.2:
===========================================
(clean_install) # cat /etc/redhat-release
Red Hat Linux release 7.2 (Enigma)

(clean_install) # rpm -qa | grep redhat-release
redhat-release-7.2-4

(clean_install) # rpm -qa | grep glibc
glibc-devel-2.2.4-19.3
glibc-2.2.4-19.3
glibc-common-2.2.4-19.3




_______________________________________________
ia64-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/ia64-list



_______________________________________________
ia64-list mailing list
[email protected]
https://listman.redhat.com/mailman/listinfo/ia64-list