Re: Safe to upgrade Perl in Sarge?

[chouck@binghamton.edu]

Roel;

I have done this AND recovered using this method.

Once you id all the pieces that change...(it is early and I was up late,
I forget how off the top of my head how to get all the 'objects' that change ..... that said
Simply make a script and mv the executables, files & libs
(watch the ln -s softlinks on the libs) to the name and rev
	EG: mv perl perl5.6.7

Now you have all the old ones to fall back to.
I did not include the path for the mv to make the example easier to 'see'.
I would include paths so the script could be run from a common location.
Makes it easier to create a recovery script.


Given that it is a set of 'objects' I might also do one or two more things.
1. Add a common PREFIX- to each file
	EG: mv perl RECOVER-perl5.6.7
2. After the rename cp all the 'objects' to a common location
	EG: cp RECOVER-perl5.6.7 /usr/local/RECOVER-perl_secupdate
	Note I did a cp to leave it in the same location

I use one file as an example this would need to be done to all the files in the security set.

I have 30 machines to do that to, I did a complete apt-get update; apt-get upgrade to 3o
machines Monday morning only to have the Perl sec-update come out minutes after!!!
I did it to 4 other machines I use and have had no problem this week.
I do NOT use spamassassin BUT I do use PERL for my web cgi.
No problems.



> Hi,
>
> There's a security upgrade for perl in sarge, but I'm not sure if it's
> safe to install it:
>
> $ apt-listbugs list perl
> Reading package fields... Done
> Reading package status... Done
> Retrieving bug reports... Done
> grave bugs of perl (5.8.4-8 -> ) <open>
>   #231082 - spamassassin: spamc hangs since most recent perl package
> updates for stable
>   #283320 - perl FTBFS on mipsel/lasat, but not on mipsel/cobalt
> Summary:
>   perl(2 bugs)
>
>
> We're using spamassassin via exiscan-acl. I don't know if that uses
> spamc, or has the same problem. I'd like to upgrade perl to the new
> version of course, but not if that breaks our spam filter.
>
> Is it safe to upgrade? Alternatively, what's the best way to go back to
> the previous version of perl if I update it and find out that the new
> version breaks our spamfilter?
>
>