[CentOS] Yum update conflicts perl-Math-BigInt

[Dan Carl]

Kai Schaetzl wrote:
> Dan Carl wrote on Thu, 05 Feb 2009 11:27:30 -0600:
>
>   
>> If I remove the conflicting perl packages won't this break MailScanner?
>>     
>
> No. It might break your Perl, though, if it overwrote anything from Perl. 
> In that case you want to reinstall Perl.
>   
Removed perl-Math-BigInt
now Mailscanner won't start
Glad this server isn't in production yet.

I did see in the install.log for MailScanner that it did do a force 
install of BigInt, BigRat and bignum
I remedied (not fxed) the problem by rerunning the the install.sh script 
and excluding bignum BigInt and BigRat from the rpmforge.repo.
>> I doubt he would install them if they weren't needed.
>>     
>
> Believe me. I've been using MailScanner since long on many systems and 
> also on CentOS since I changed to CentOS in 2004 or so.
>
>   
>> If I uninstall the older perl package versions and install the newer 
>> ones from rpmforge will MailScanner still function properly?
>>     
>
> I'm not exactly sure what you mean. The point is: Perl in CentOS has quite 
> a few "packages" that come with MailScanner already built-in. There is 
> *no* need to replace them with what comes with MailScanner. These should 
> remain as is.
> In other words: you only need to add those packages which are really 
> missing (from rpmforge). All the "packages" that are built-in should not 
> be "upgraded" at all. This are the following packages:
> perl-bignum
> perl-File-Spec
> perl-File-Temp
> perl-Getopt-Long
> perl-IO
> perl-Math-BigRat
> perl-Test-Harness
> perl-Test-Simple
>
> which means you do:
> yum install perl-Convert-BinHex perl-Convert-TNEF perl-Convert-BinHex 
> perl-Convert-TNEF perl-DBD-SQLite perl-Filesys-Df perl-IO-stringy perl-
> MIME-tools perl-Net-CIDR perl-OLE-Storage_Lite perl-Pod-Escapes perl-Pod-
> Simple perl-Test-Pod perl-Time-HiRes
>
> with rpmforge enabled and then install mailscanner*.rpm (and not use 
> install.sh!). That's all.
>
>
>   
It was too late, I already installed via the install.sh script.
(I've always done it this way without any problems)

I suppose now I can either...
Cross my fingers and hope I won't run into any perl problems,
try reinstalling perl which doesn't sound easy or wait for
5.3 to come out cause its going to fix everything. :-)

Thanks for the help, next time I try installing it your way,
or maybe by then it will be as easy as yum install MailScanner.

Dan