Günter Palm wrote:
Hi All,
I know, others have asked the very same question here on the
list already: What is the best procedure for upgrading the
toaster?
And yes, I DID read the answer(s): just install those (software/options)
that have features you want/need.
Well, maybe thats basically it, but I can't believe that it's THAT easy.
Aren't there special things to consider when you upgrade a runnning system?
I don't mean such simple things like not to create already existing
users/groups or symlinks anew, but those which aren't so obvious - at least
not for everybody.
It's that easy IF you remember that upgrading vpopmail requires
upgrading/recompiling things that use vpopmail.so (courier and qmail
with the chkuser patch come to mind). Also, always read the UPGRADE
document for the program you are upgrading.
To make clear what I'm talking about (from my point of view) here some
of my updating experiences:
Example 1: I did an update from SpamAssassin 3.1.7 to 3.2.0 via CPAN.
Since this version requires module Net::DNS I had to install that first.
But what about the optional modules like Mail::Domainkeys or
Mail::DKIM? Are any of these required for the current toaster?
Nice to have Mail::DKIM but not needed for SA or the toaster.
Example 2: After making ClamAV i did a simscanmk -g to update the cdb
and got an error that libclamav.so.2 couldn't be found.
Since I didn't know if this error was related to (old) simscan I updated
simscan as well, but got the same error. A reboot fixed that.
Maybe I should have removed /usr/local/lib/*clam* before compiling/making
ClamAV and I wouldn't have to reboot the system?
The latest clamav requires you to manually run ldconfig after
installing. ldconfig also runs at boot time.
Example 3: Making ClamAV from source doesn't overwrite the existing
usr/local/etc/clamd.conf. In my case this led to clamd producing
errors in the log:
ERROR: Can't open/parse the config file /usr/local/etc/clamd.conf
ERROR: Parse error at line 39: Option LogClean requires boolean argument.
Copying the new clamd.conf manually fixed the problem (Option changed
from "LogClean" to "LogClean yes")
No, reading the UPGRADE document in the clamav source tree would have
alerted you to this before hand. There were major changes to .conf
files between 0.88 and 0.90.
Always read the UPGRADE document if it exists.
The conclusion is that updating by following the toaster like with a fresh
install just doesn't do it.
Correct. I guess someone with a wack of free time could write an
UPGRADE document for the toaster but most of us already do read it for
the individual packages we are upgrading.
Regards,
Rick
