Can't install CentOS 5.2 update?
Scott Silva
ssilva at sgvwater.com
Fri Jun 27 00:55:09 IST 2008
on 6-26-2008 6:43 AM Dave Jones spake the following:
> >> A more simple method that I use is:
> >>
> >> # yum -y update (this will fail with the conflicts but download the
> >> packages into the yum cache for the rpm --force command below)
> >> # yum -y update --exclude=perl*
> >> # cd /var/cache/yum/rpmforge/packages
> >> # rpm -Uhv --force perl*
> >This could downgrade a perl module that is needed by mailscanner. You
> could
> >have no problems, and you could have many.
>
> It will not downgrade with the "-U" option. The rpm command should only
> upgrade existing modules using the latest version in that directory if
> you have
> multiple versions of the same rpm package. The yum output proves this by
> skipping older versions. This is validated by running another "yum update"
> and it shows everything is up to date.
>
> If you think this "perl*" is not safe, then you could manually run the
> rpm --force
> on the latest version of the perl module that is conflicting. I used to
> do this but
> found that rpm was smart enough, so I took the easy "perl* way. All of this
> would still be much faster, easier, and less risky than reinstalling
> MailScanner
> every few months.
>
But so much changes in MailScanner every few months that it is usually worth
it for either features or fixes. Julian can really churn out the code.
--
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 : http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080626/7c385f7b/signature.bin
More information about the MailScanner
mailing list