On Sun, Jan 11, 2009 at 08:39:35AM -0500, Derick Centeno wrote:
> Hi John:
>
> I'm pleased to discover of your success and that your approach appears
> to be working for you. I recall coming across a dated, but
> still useful, explanation discussing upgrading across versions.
> Unfortunately I had not recalled exactly where the reference was
> located.
On the question of a 'yum upgrade' I have found it works okay, but you
need to check for non-upgraded rpm's (due to the version problem
mentioned earlier in the thread). For example, after upgrading from
ydl6 to ydl6.1 I did
rpm -qa --last > rpmlist.txt
Looking through the file thus created I scrolled down to a point where
I found:
chkconfig-1.3.30.1-2 Sat 10 Jan 2009 21:45:45 EST
libxml2-2.6.26-2.1.2.6 Sat 10 Jan 2009 21:45:43 EST
popt-1.10.2-48.ydl6.1 Sat 10 Jan 2009 21:45:41 EST
libX11-1.0.3-9 Sat 10 Jan 2009 21:44:57 EST
bash-3.2-21 Sat 10 Jan 2009 21:44:51 EST
lm_sensors-devel-2.10.0-3.1.ydl.1 Sun 07 Dec 2008 10:39:13 EST
gnokii-0.6.14-2.fc6 Sun 30 Nov 2008 14:02:15 EST
lzo-2.02-2 Sat 29 Nov 2008 19:34:00 EST
acpid-1.0.4-5.ydl.1 Sat 29 Nov 2008 19:11:08 EST
setools-devel-3.0-3 Sat 29 Nov 2008 19:00:07 EST
setools-3.0-3 Sat 29 Nov 2008 19:00:03 EST
This shows where the change from new rpm's (10 Jan 2009) to 'old'
rpm's. I then manually forced the install of the new versions of
these 'old' rpm's. This gives a consistent new version. Finally I
run a script which uses find to search for all 'rpmold' 'rpmnew' and
similar files so I can check and fix files where necessary changes
have occurred.
I hope this is of some use to others in making sure their systems are
consistent.
--
Stephen Harker [email protected]
PEMS
u...@adfa
_______________________________________________
yellowdog-general mailing list
[email protected]
http://lists.fixstars.com/mailman/listinfo/yellowdog-general
HINT: to Google archives, try '<keywords> site:terrasoftsolutions.com'
