On Mon, 2002-09-09 at 21:01, Brian J. Murrell wrote:
> One of the thing that the apt-get evangelists are always going on
> about is the ability to use apt-get to do complete O/S upgrades, live.
> Is there any way to upgrade a running 8.2 (or even a Cooker) system to
> 9.0(beta, rc1, rc2, final when it comes out) by playing with the
> urpmi.cfg file (or altering urpmi sources in another way)?
The first step is easy, add cooker (or the new release) to your urpmi
sources (and remove the old one).
Then you have a couple of ways to move forward:
1 - single step: urpmi --auto-select (this is similar to allowing
apt-get to do a full upgrade), cross your fingers and let it fly.
2 - my paranoid way (I use this even though I'm exclusively on
cooker on my home machine, and I used it to update my work
computer from 8.2 to cooker)
* urpmq --auto-select | sort > packagelist
* look through packagelist
* remove packages that you didn't know were on your system
and never use (then redo the urpmq)
* manually rpm certain lib stuff to make sure
the old versions are not removed to allow backwards
compatibility. For example, if glibc is changing from
2.2.4 to 2.2.5, I know that it will remove 2.2.4, so I
backup the 2.2.4 libs, install 2.2.5, then restore the
2.2.4 libs.
* backup /etc
* use urpmi to upgrade "manageable" chunks of the packages
(like libs, gnome, kde, gcc, etc.). I do something like:
-> urpmi $(egrep '^kde|arts|qt' packagelist)
-> urpmi $(egrep 'next group of stuff' packagelist)
-> ......
This allows me to better watch the messages from urpmi about
.rpmsave/.rpmnew stuff that I have to look over
* compare /etc to the saved one to make sure certain settings
didn't get lost and restore any lost settings (like my pet
peeve of rpm removing BACKSPACE=BackSpace from
/etc/sysconfig/keyboard)
* enjoy newly upgraded system.
* repeat as necessary/desired to keep up with cooker, or go to
another later release.
TTFN,
Lonnie Borntreger
