This is a discussion on RE: Upgrading - SpamAssassin ; Hello Hiram, It's not scary, you have to step up and own it - be prepared. The best way might be to replicate the situation/scenario in a Virtual environment, and attempt upgrading in there first, to see what might go ...
It's not scary, you have to step up and own it - be prepared. The best
way might be to replicate the situation/scenario in a Virtual
environment, and attempt upgrading in there first, to see what might go
wrong, and how you can avoid problems on your live server.
VMWare is great for this, for me. You might find some other
Virtualization software suits you, but it is much better to use that
than to "learn" Spamassassin on your live server(s).
Doing something on a live server that you haven't done before at all,
will get you labelled as a loose cannon.
> -----Original Message-----
> From: hiram [mailto:firstname.lastname@example.org]
> Sent: 14 April 2008 9:04 p.m.
> To: email@example.com
> Subject: RE: Upgrading
> Hi Mike,
> That sounds on the limit to scarry.
> I will rethink it before upgrading then.
> Thanks for the advice and the information!
> Best regards,
> Michael Hutchinson-3 wrote:
> >> -----Original Message-----
> > Sir,
> > You or someone else, has managed to break apt-get's info about S.A.
> > not going into fixing that, that is a Debian question.
> > You need to download the package manually with 'wget'.
> > You can "apt-get install wget" if you don't have it.
> > Use wget to get the package.
> > Example "wget http://somefileyouwant.deb"
> > After that use dpkg -i to install the package just as if you'd used
> > apt-get.
> > "dpkg -i somefileyouwant.deb"
> > That will install your Spamassassin package. Just remember you're
> > opening a can of worms by using anything later than S.A. version
> > on Debian Sarge. The newer versions are reported to run fine on
> > Etch.
> > I botched an upgrade from 3.1.4 -> 3.2.3 on Sarge a while ago, and
> > caused a MASSIVE headache with incorrect dependencies, wrong perl
> > modules being installed, and config being installed in new/different
> > locations, which ended up with an INSANE installation - more than
> > version existing in binaries or config on one singular computer. Not
> > good look.
> > It took a long time to fix. (well, it seemed like a very long time)
> > You'd be better off arranging some downtime. Copying out your
> > S.A config, and completely removing S.A altogether, including
> > hunting down every config file and binary. Then and only then would
> > consider installing the 3.2.4 package, and restoring the config.
> > HTH,
> > Mike
> View this message in context: http://www.nabble.com/Upgrading-
> Sent from the SpamAssassin - Users mailing list archive at Nabble.com.