Subject: | |
From: | |
Reply To: | |
Date: | Fri, 27 Aug 2010 12:02:22 +0100 |
Content-Type: | TEXT/PLAIN |
Parts/Attachments: |
|
|
On Thu, 26 Aug 2010, Markus Neteler wrote:
> Hi,
>
> I have updated from the previous to the current 5.x SL version following
> this procedure
<snip>
> [root@fep modules]# rpm -e
> kernel-module-fuse-2.6.18-92.1.6.el5-2.6.3-1.sl5.x86_64
> error: Failed dependencies:
> kernel-module-fuse >= 5:2.6.3-1.SL is needed by (installed)
> fuse-2.6.3-1.SL.x86_64
>
> [root@fep modules]# rpm -qa | grep fuse
> libconfuse-devel-2.5-4.x86_64
> fuse-libs-2.6.3-1.SL.x86_64
> libconfuse-2.5-4.x86_64
> fuse-2.6.3-1.SL.x86_64
> fuse-smb-0.8.7-1.SL.x86_64
> fuse-sshfs-2.2-1.SL.x86_64
> kernel-module-fuse-2.6.18-92.1.6.el5-2.6.3-1.sl5.x86_64
>
> But the current fuse version is 2.7.4-8.el5.
>
> While I fixed this manually, I wonder how many other outdated packages
> might be there. Is there a possibility to check that?
I *thought* that the fuse stuff was a change from sl53 to sl54 (which was
when TUV decided to include fuse so sl dropped the added packages) but I
may be misremembering when that change happened.
We are (still) in the process of upgrading our machines from sl53 to sl55,
and to assure ourselves that were were not having packages left with the
wrong versions we did a number of iterations of:
clean install of sl53 (our kickstart configs)
upgrade the sl53 to sl55
clean install of sl55 (our kickstart configs)
(and later) take some existing real machines running sl53 and
upgrade them to sl55
and then compared the list of packages we got, and tweaked until the
results were identical.
Apart from changes to which packages get pulled in by default the only
packages we had to perform hacks for were:
fuse (and fusekmods)
pcre/pcre-devel
and the pcre ones were things we had missed from a much earlier update
(long since fixed in the repos but we still had some machines with
pcre-6.6-2.el5.7 installed from before the names got fixed).
Of course I can't state that there are _no_ other issues since we don't
install *all* packages but you could always do a new install (e.g. into a
VM) and compare the package list...
We have been rather cautious about the upgrade, so far just 50 machines
upgraded to sl55, but the rest are due to be done automatically next
wednesday morning, so I'm quite confident that our procedure is safe!
--
/--------------------------------------------------------------------\
| "Computers are different from telephones. Computers do not ring." |
| -- A. Tanenbaum, "Computer Networks", p. 32 |
---------------------------------------------------------------------|
| Jon Peatfield, _Computer_ Officer, DAMTP, University of Cambridge |
| Mail: [log in to unmask] Web: http://www.damtp.cam.ac.uk/ |
\--------------------------------------------------------------------/
|
|
|