>> A more simple method that I use is:<br>>><br>>> # yum -y update (this will fail with the conflicts but download the<br>>> packages into the yum cache for the rpm --force command below)<br>>> # yum -y update --exclude=perl*<br>
>> # cd /var/cache/yum/rpmforge/packages<br>>> # rpm -Uhv --force perl*<br>>This could downgrade a perl module that is needed by mailscanner. You could<br>>have no problems, and you could have many.<br><br>
It will not downgrade with the "-U" option. The rpm command should only<br>upgrade existing modules using the latest version in that directory if you have<br>multiple versions of the same rpm package. The yum output proves this by<br>
skipping older versions. This is validated by running another "yum update"<br>and it shows everything is up to date.<br><br>If you think this "perl*" is not safe, then you could manually run the rpm --force<br>
on the latest version of the perl module that is conflicting. I used to do this but<br>found that rpm was smart enough, so I took the easy "perl* way. All of this<br>would still be much faster, easier, and less risky than reinstalling MailScanner<br>
every few months.<br><br>I will try to figure out how to post this to the wiki if others think this procedure<br>is useful (and safe). I have been following this procedure for over a year on<br>about a dozen MailScanner instances with no problems.<br>
<br>><br>>The SAFER method is the first method;<br>>rpm -e perl-IO perl-File-Temp perl-Math-BigInt perl-Math-BigRat perl-bignum<br>><br>>yum update perl<br>><br>>re-install the current (or your preferred) mailscanner version to get the perl<br>
>modules re-installed.<br>>> # reboot (if needed to get on a new kernel -- or just restart MailScanner)<br>>><br>>> You don't have to reinstall MailScanner everytime you get an updated<br>>> perl module conflict.<br>
>><br>-- <br>Dave Jones