SCIENTIFIC-LINUX-USERS Archives

November 2007

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Daniel Pfenniger <[log in to unmask]>
Reply To:
Date:
Wed, 28 Nov 2007 12:35:44 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
$ rpm -Fvh [some subset of the available rpms]

is useful, you just upgrade and replace the already installed ones.
But  as said in a previous post, you don't want to upgrade and
replace the kernels, so you could proceed by first adding with rpm -i 
the new kernel and dependent packages.  Then you can upgrade and
replace by group of packages.

Important package families to upgrade first are *glibc*rpm and rpm*rpm.
$ rpm -Fvh *glib*rpm
would attempt to upgrade and replace the glibc family of packages.
If anything is missing it will complain, so one can at the next attempt
complete the previous command until the group of package is consistent.

$ rpm -Fvh [a-j]*rpm [l-z]*rpm
replace all the packages beginning with a small character except k.

The lib*rpm is a group of packages that it is good to try to upgrade
before the others.

When all the packages are upgraded, you can check that
$ rpm -Fvh *rpm
does nothing.

	Dan

ATOM RSS1 RSS2