Yum update...only one at a time?

[Mike Loiterman]

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

------------------------------
Mike Loiterman
grantADLER
Tel: [phone]
Fax: [phone]
Email: [e-mail]
PGP Key: 0xD1B9D18E
GPG Key: 0x661D0518

[seth vidal]

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?

Can you describe the behavior more clearly?

-sv

[Mike Loiterman]

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?
>
> Can you describe the behavior more clearly?
>
> -sv

I issue the command:  yum update

This should update all currently installed packages (download headers,
download packages and install).  However, it will only download the header
for one package and then yum exists.  If I run yum update again, it gets the
next header and then exits.

------------------------------
Mike Loiterman
grantADLER
Tel: [phone]
Fax: [phone]
Email: [e-mail]
PGP Key: 0xD1B9D18E
GPG Key: 0x661D0518

[seth vidal]

On Thu, 2004-09-30 at 00:00 -0500, Mike Loiterman wrote:
> 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?
> >
> > Can you describe the behavior more clearly?
> >
> > -sv
>
> I issue the command:  yum update
>
> This should update all currently installed packages (download headers,
> download packages and install).  However, it will only download the header
> for one package and then yum exists.  If I run yum update again, it gets the
> next header and then exits.

Does it exit at the prompt, suddenly or is it a normal exit?

The last time I saw this it had to do with memory problems on a system.
Could you run memtest on your system and see if there are any problems?

Thanks
-sv

Kernel Panic - 2.6.8-1.590

[Paul Watkins]

I get a kernel panic when booting with the new kernel 2.6.8-1.590 -- 
happens when trying to load ext3 and switch to new root.

In fact the no version of the kernel above 2.6.8-1.541 works for me.

Any suggestions?  I have the latest downloads from Rawhide.

Thanks,

Paul

[Michal Jaegermann]

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?

Michal

[seth vidal]

On Thu, 2004-09-30 at 00:19 -0600, Michal Jaegermann 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?

'distribution' is the component to file against - and I think this is an
obsolete tag.

-sv

[Mike Loiterman]

Michal Jaegermann  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?
>
> Michal

So I guess we should wait it out?  But how can we upgrade when yum is
trashed?

------------------------------
Mike Loiterman
grantADLER
Tel: [phone]
Fax: [phone]
Email: [e-mail]
PGP Key: 0xD1B9D18E
GPG Key: 0x661D0518

[seth vidal]

On Thu, 2004-09-30 at 01:32 -0500, Mike Loiterman wrote:
> Michal Jaegermann  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?
> >
> > Michal
>
> 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 pain.

-sv

[Mike Loiterman]

seth vidal  wrote:
> On Thu, 2004-09-30 at 01:32 -0500, Mike Loiterman wrote:
> > Michal Jaegermann  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?
> > >
> > > Michal
> >
> > 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
> pain.

Upgrading to 2.1.4 was what caused the problem.  I rebooted, but I'm getting
the same.

------------------------------
Mike Loiterman
grantADLER
Tel: [phone]
Fax: [phone]
Email: [e-mail]
PGP Key: 0xD1B9D18E
GPG Key: 0x661D0518

[Michal Jaegermann]

> try upgrading yum to yum 2.1.4 and see if it makes any difference at
> all.

I tried that both with yum 2.1.3 and also after an update to 2.1.4.
Result were the same and also runing yum with '-d2' and '-d3' did
not bring anything which would make me wiser.

Only after I guessed that ORBit2 packages may have something to
do with the problem, and exluding those in the first phase, allowed
me to proceed.

Michal

[RaXeT]

Michal Jaegermann wrote:
> > try upgrading yum to yum 2.1.4 and see if it makes any difference at
> > all.
>
> I tried that both with yum 2.1.3 and also after an update to 2.1.4.
> Result were the same and also runing yum with '-d2' and '-d3' did
> not bring anything which would make me wiser.
>
> Only after I guessed that ORBit2 packages may have something to
> do with the problem, and exluding those in the first phase, allowed
> me to proceed.

Same here. Did an yum --exclude=ORBit2 --exclude=ORBit2-devel update

Worked great!

RaXeT

[seth vidal]

> > Only after I guessed that ORBit2 packages may have something to
> > do with the problem, and exluding those in the first phase, allowed
> > me to proceed.
>
> Same here. Did an yum --exclude=ORBit2 --exclude=ORBit2-devel update
>
> Worked great!

So in both your cases yum would only update one package then exit unless
you added the above exclude?

-sv

[Jon Savage]

> So in both your cases yum would only update one package then exit unless
> you added the above exclude?
>
> -sv

I was seeing the same thing with yum 2.14-1. It was not really
installing *anything* just getting one header at a time and exiting.
[root@sw-lt01 ~]# yum --exclude=udev update
Setting up Update Process
Setting up Repo:  development
repomd.xml                100% |=========================| 1.1 kB    00:00
Reading repository metadata in from local files
developmen: ################################################## 3441/3441
Excluding Packages in global exclude list
Finished
Resolving Dependencies
httpd-suexec-2.0.52-2.i38 100% |=========================|  18 kB    00:00
[root@sw-lt01 ~]#

when excluding the ORBit2* stuff yum worked as expected.