I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt.
Is the only solution to uninstall the base version and then install the rpmforge version?
According the the wiki "Packages from repositories with a lower priority will never be used to upgrade packages that were installed from a repository with a higher priority." If this true why the conflicts? please advise Thanks Dan
on 1-30-2009 1:13 PM Dan Carl spake the following:
I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt.
Is the only solution to uninstall the base version and then install the rpmforge version?
According the the wiki "Packages from repositories with a lower priority will never be used to upgrade packages that were installed from a repository with a higher priority." If this true why the conflicts? please advise Thanks Dan
Sometimes you will get conflicts if the new package doesn't have a corresponding base package but was built into the base's monolithic rpm. I don't think base has a separate package for that module, but has it as part of the base perl rpm.
If you really need the newer version you might have to --force it. Or you can see if the version in base perl is OK for your needs.
Hi,
On Fri, Jan 30, 2009 at 16:36, Scott Silva ssilva@sgvwater.com wrote:
If you really need the newer version you might have to --force it.
Bad advice. This is the exactly same reason why installing from CPAN is not recommended under CentOS.
RPM is designed to prevent you from installing something that could risk breaking your system. Whenever you use --force you are telling RPM to stop doing that. This is a bad idea.
And remember: If you break it, you get to keep the pieces.
HTH, Filipe
--- On Fri, 1/30/09, Dan Carl danc@bluestarshows.com wrote:
From: Dan Carl danc@bluestarshows.com Subject: [CentOS] Yum update conflicts perl-Math-BigInt To: "CentOS mailing list" centos@centos.org Date: Friday, January 30, 2009, 1:13 PM I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt.
Is the only solution to uninstall the base version and then install the rpmforge version?
Take a deep breath there... the base version is Perl itself - Math::BigInt is a core module in C5.
I would like to know why the developers of Clamd feel the need to use the latest perl-Math-BigInt? Try checking your /var/log/yum.log to see if this RPM was installed coincident with Clamd. Perhaps you can exclude it somehow.
On Fri, 30 Jan 2009, Mark Pryor wrote:
--- On Fri, 1/30/09, Dan Carl danc@bluestarshows.com wrote:
From: Dan Carl danc@bluestarshows.com Subject: [CentOS] Yum update conflicts perl-Math-BigInt To: "CentOS mailing list" centos@centos.org Date: Friday, January 30, 2009, 1:13 PM I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt.
Is the only solution to uninstall the base version and then install the rpmforge version?
Take a deep breath there... the base version is Perl itself - Math::BigInt is a core module in C5.
I would like to know why the developers of Clamd feel the need to use the latest perl-Math-BigInt? Try checking your /var/log/yum.log to see if this RPM was installed coincident with Clamd. Perhaps you can exclude it somehow.
ClamAV does not need perl-Math-BigInt. And FWIW, the latter has not been updated since 21 Apr 2008.
Dan Carl wrote on Fri, 30 Jan 2009 15:13:50 -0600:
I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt.
add check_obsoletes = 1 to the /etc/yum.d/priorities.comf
Kai
Kai Schaetzl wrote:
Dan Carl wrote on Fri, 30 Jan 2009 15:13:50 -0600:
I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt.
add check_obsoletes = 1 to the /etc/yum.d/priorities.comf
Kai
Sorry to take so long to follow up on this, been busy.
add check_obsoletes = 1 does nothing
Here's the errors I'm getting: Transaction Check Error: <snip> file /usr/share/man/man3/Math::BigInt.3pm.gz from install of perl-Math-BigInt-1.89-1.el5.rf conflicts with file from package perl-5.8.8-15.el5_2.1 file /usr/share/man/man3/Math::BigInt::Calc.3pm.gz from install of perl-Math-BigInt-1.89-1.el5.rf conflicts with file from package perl-5.8.8-15.el5_2.1 file /usr/share/man/man3/Math::BigInt::CalcEmu.3pm.gz from install of perl-Math-BigInt-1.89-1.el5.rf conflicts with file from package perl-5.8.8-15.el5_2.1 <snip>
#rpm -qa | grep perl-Math
perl-Math-BigInt-1.86-2 perl-Math-BigRat-0.19-2
This tells me rpmforge has a newer version, but isn't yum-priorities suppose to keep rpmforge from updating it? I've never needed rpmforge before, what am I doing wrong?
Dan Carl wrote on Wed, 04 Feb 2009 14:48:23 -0600:
add check_obsoletes = 1 does nothing
Not in this situation, as you didn't tell everything last time ;-)
file /usr/share/man/man3/Math::BigInt.3pm.gz from install of perl-Math-BigInt-1.89-1.el5.rf conflicts with file from package perl-5.8.8-15.el5_2.1
You got the same messages when you installed MailScanner. You should have woken up *then* ;-)
This tells me rpmforge has a newer version, but isn't yum-priorities suppose to keep rpmforge from updating it?
Correct. But there is no such file in CentOS. You installed the complete MailScanner package which installs lots of "not so good" perl packages which either are not necessary (including this one) or can be fetched from rpmforge. Remove that BigInt package and all shoulkd be well. And do not install the complete MailScanner package when you do your next upgrade, install only the mailscanner*.rpm.
Kai
Kai Schaetzl wrote:
Dan Carl wrote on Wed, 04 Feb 2009 14:48:23 -0600:
add check_obsoletes = 1 does nothing
Not in this situation, as you didn't tell everything last time ;-)
Sorry, I usually post too much info
Correct. But there is no such file in CentOS. You installed the complete MailScanner package which installs lots of "not so good" perl packages which either are not necessary (including this one) or can be fetched from rpmforge. Remove that BigInt package and all shoulkd be well. And do not install the complete MailScanner package when you do your next upgrade, install only the mailscanner*.rpm
If I remove the conflicting perl packages won't this break MailScanner? I doubt he would install them if they weren't needed.
If I uninstall the older perl package versions and install the newer ones from rpmforge will MailScanner still function properly?
I know there's MailScanner users on this list so I'll wait for a response here before posting to the MailScanner list.
Dan
Kai
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.
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.
There is another solution for you. You can use the repo by Hugo van der Kooiy who has taken a lot of effort to workaround these problems. You can either install his "mailscanner-wrapper" or his "mailscanner" package. mailscanner will only install the necessary additional packages. mailscanner-wrapper will install a few extra packages ("updates") that were built by Hugo in a way that they don't conflict with the built-in files. http://yum.vanderkooij.org/el5/
Kai
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
Dan Carl wrote on Thu, 05 Feb 2009 17:43:14 -0600:
Removed perl-Math-BigInt now Mailscanner won't start
because the forced modules probably overwrote the original built-in version, so that after removal nothing was left.
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. :-)
Should not be difficult. Shutdown all programs that are based on Perl and remove the MailScanner rpm and then Perl (and all Perl modules) with rpm. Then reinstall Perl with yum. Make a note of all modules you had installed for other programs, so you can reinstall them. (Just force-installing Perl over the existing setup may also cure it, but it's not really clean.) Then use Hugo's repo.
You may run into this problem again, when the system Perl gets updated which may happen with 5.3. There was already a Perl upgrade late last year.
Kai
-
Dan Carl -
Filipe Brandenburger -
Kai Schaetzl -
Mark Pryor -
Sahil Tandon -
Scott Silva