up2date conflict

vu pham vu at sivell.com
Thu Sep 18 08:18:33 PDT 2008


Collins Richey wrote:
> On Tue, Sep 9, 2008 at 7:44 AM, vu pham <vu at sivell.com> wrote:
>> When I run up2date -u on my server RHEL4, I got the following error, even
>> with --force and the up2date configuration has "Force To Install", too.
>>
>> [[root at jetco ~]# up2date -u --force
>>
>> Fetching Obsoletes list for channel: rhel-i386-es-4...
>>
>> Name                                    Version        Rel
>> ----------------------------------------------------------
>> perl                                    5.8.5          36.el4_6.3  i386
>>
>>
>> Testing package set / solving RPM inter-dependencies...
>> ########################################
>> RPM package conflict error.  The message was:
>> Test install failed because of package conflicts:
>> package perl-5.8.5-36.el4_6.3 is already installed
>>
> 
> I don't really know the answer. We haven't seen this problem with our
> rhel4 systems, but then we don't use up2dte for anything but fetching
> packages to our local yum repository.
> 
> My first inclination when situations like this arise is to wait a few
> days and try again. Many (if not all) distros don't really seem to
> test that packages are actually installable before releasing them to
> the repos. Dependency conflicts are usually resolved quickly as soon
> as someone reports them. Also, there is always the possibility that
> your mirror for updates was not completely synced when you tried
> up2dte.
> 

Collin, I waited for 3 days but still experienced the same problem then 
I opened the ticket with Redhat. After several tries, the latest advice 
is to use rpm to remove that package and update again.

So I built a similar system to that one ( that one is a production one 
so I do not try there ). It turns out it is MailScanner installs the 
Perl package that causes that conflicts.

Vu



More information about the Linux-users mailing list