seth vidal <mailto:firstname.lastname@example.org> wrote:
On Thu, 2004-09-30 at 01:32 -0500, Mike Loiterman wrote:
> Michal Jaegermann <mailto:email@example.com> wrote:
>> On Thu, Sep 30, 2004 at 12:45:43AM -0400, seth vidal wrote:
>>> On Wed, 2004-09-29 at 23:45 -0500, Mike Loiterman wrote:
>>>> I'm doing yum update, but its only doing one package at a
>>>> time...any idea why?
>>>> I've done a yum clean all and I'm using version 2.1.4
>>> What do you mean one package at a time?
>> It seems to me that something went haywire with a dependency
>> resolution and not really in yum but somewhere in rpm libraries.
>> An attempt to use directly 'rpm -Fvh ...' with a bunch of packages
>> from the current updates ends up with:
>> error: Failed dependencies:
>> linc >= 0.1.6 is needed by (installed) pyorbit-2.0.0-3.1
>> linc = 1.0.3 is needed by (installed) linc-devel-1.0.3-6
>> while 'rpm -q linc' responds with 'linc-1.0.3-6' and
>> 'rpm -q linc-devel' with 'linc-devel-1.0.3-6'. This appears to
>> trip yum.
>> It seems that the real culprit is ORBit2, though, but why it
>> triggers this problem is far from clear to me. Still, when other
>> packages are updated then ORBit2, and ORBit2-devel, can be updated
>> as well but only then.
>> This is probably a bugzilla material but against what?
> So I guess we should wait it out? But how can we upgrade when yum
> is trashed?
try upgrading yum to yum 2.1.4 and see if it makes any difference at
all. In this case I doubt it will. Also try rebooting your system to
see if there some sort of peculiar lock in the rpmdb causing this
Upgrading to 2.1.4 was what caused the problem. I rebooted, but I'm getting
PGP Key: 0xD1B9D18E
GPG Key: 0x661D0518