Can't install CentOS 5.2 update?

Scott Silva ssilva at
Fri Jun 27 19:45:49 IST 2008

> Of course this will depend on how you originally installed the perl
> modules in conflict.  If you installed them via CPAN or from source RPMs,
> then the rpm --force _could_ downgrade packages from another source.
> As long as you installed them originally from rpmforge, then forcing
> the rpmforge packages is safe.
> BTW, RHEL servers are going to get their perl modules from RHN and not
> from rpmforge.  You need to use rpmforge very carefully with a RHEL
> server using RHN and you really need to know what you are doing
> with package management and repo priorities (rpmforge and others are
> always lower than RHN) or you can end up with many conflicts.
> So the package management on RHEL will not be the same as
> CentOS with respect to rpmforge and other repos that overlap
> packages with the RHN.
> I know the MailScanner RPM install needs to be generic enough for multiple
> RPM-based distros, but it would be nice if the installer could somehow
> detect if a package is available from a repo and use that rather than having
> to force a compile of perl modules from a source RPM.  I think the source of
> all these conflicts comes from the MailScanner is forcing 
> some perl
> packages that exist in repos.

I think that Hugo V. was experimenting with setting up a repo for mailscanner 
with a dummy package that had all the requires, but I haven't heard any more 
about it.
It worked pretty well until rpmforge released an incompatible perl module.

MailScanner is like deodorant...
You hope everybody uses it, and
you notice quickly if they don't!!!!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
Url :

More information about the MailScanner mailing list