>Dave Jones a écrit :<br>>> >> A more simple method that I use is:<br>>> >><br>>> >> # yum -y update (this will fail with the conflicts but download the<br>>> >> packages into the yum cache for the rpm --force command below)<br>
>> >> # yum -y update --exclude=perl*<br>>> >> # cd /var/cache/yum/rpmforge/packages<br>>> >> # rpm -Uhv --force perl*<br>>> >This could downgrade a perl module that is needed by mailscanner. You<br>
>> could<br>>> >have no problems, and you could have many.<br>>><br>>> It will not downgrade with the "-U" option. The rpm command should only<br>>> upgrade existing modules using the latest version in that directory if<br>
>> you have<br>>> multiple versions of the same rpm package. The yum output proves this by<br>>> skipping older versions. This is validated by running another "yum<br>>> update"<br>>> and it shows everything is up to date.<br>
>><br>>> If you think this "perl*" is not safe, then you could manually run the<br>>> rpm --force<br>>> on the latest version of the perl module that is conflicting. I used<br>>> to do this but<br>
>> found that rpm was smart enough, so I took the easy "perl* way. All<br>>> of this<br>>> would still be much faster, easier, and less risky than reinstalling<br>>> MailScanner<br>>> every few months.<br>
>><br>>> I will try to figure out how to post this to the wiki if others think<br>>> this procedure<br>>> is useful (and safe). I have been following this procedure for over a<br>>> year on<br>
>> about a dozen MailScanner instances with no problems.<br>><br>>I tried this on a RHEL 5.2 server (same as CentOS 5.2) and it didn't<br>>work... MS refused to start... so reinstalling MS (or at just the RPMs<br>
>we removed in the first place) is the best way to go.<br>><br><br>Of course this will depend on how you originally installed the perl<br>modules in conflict. If you installed them via CPAN or from source RPMs,<br>
then the rpm --force _could_ downgrade packages from another source.<br>As long as you installed them originally from rpmforge, then forcing<br>the rpmforge packages is safe.<br><br>BTW, RHEL servers are going to get their perl modules from RHN and not<br>
from rpmforge. You need to use rpmforge very carefully with a RHEL<br>server using RHN and you really need to know what you are doing<br>with package management and repo priorities (rpmforge and others are<br>always lower than RHN) or you can end up with many conflicts.<br>
So the package management on RHEL will not be the same as<br>CentOS with respect to rpmforge and other repos that overlap<br>packages with the RHN.<br><br>I know the MailScanner RPM install needs to be generic enough for multiple<br>
RPM-based distros, but it would be nice if the installer could somehow<br>detect if a package is available from a repo and use that rather than having<br>to force a compile of perl modules from a source RPM. I think the source of<br>
all these conflicts comes from the MailScanner install.sh is forcing some perl<br>packages that exist in repos.<br><br>>Denis<br clear="all"><br>-- <br>Dave Jones