Dag Wieers wrote:
There is not a bug in yum (well, not in this case ... I'm sure yum has some bugs) ... the problem is that the repositories that you have chosen have conflicting packages, or you are not pointed to the proper CentOS repos.
This is a bug in Yum. Yum only considers the latest version of amavisd-new and that one has unresolved dependencies.
I have a problem here. I try so hard not to replace core packages, but amavisd-new needs a newer perl module that is a core package.
Either people complain that I replace core packages, or they complain that I do not have amavisd-new 3.4 and if I provide both, Yum would complain anyway because it is stupid.
The problem is that you have to replace *perl* to meet the dependency on Digest::MD5 amavisd-new is having. Because of the shitty @INC ordering in RHEL (*and* perl itself) you cannot even push a new Digest::MD5 to vendor_perl/ or site_perl/ as that is not going to be picked up:
| @INC: | /usr/lib/perl5/5.8.0/i386-linux-thread-multi | /usr/lib/perl5/5.8.0 | /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi | /usr/lib/perl5/site_perl/5.8.0 | /usr/lib/perl5/site_perl | /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi | /usr/lib/perl5/vendor_perl/5.8.0 | /usr/lib/perl5/vendor_perl
There's a bugzilla entry concerning that (which I cannot find anymore at the moment), but it didn't look like RH wanted to change that.
So I don't think that this is a yum bug, this is a bug in RedHat's perl packaging, as you are not able to override modules which are included with the core perl package. And that hasn't change up to FC5.
Ralph