[ATrpms-users] FC7 Dependency Resolution problem.

[Jason Sullivan]

On 10/30/07, Axel Thimm <Axel.Thimm at atrpms.net> wrote:
> Hi,
>
> On Tue, Oct 30, 2007 at 08:47:08PM -0400, Jason Sullivan wrote:
> > I've installed the "skip-broken" plugin, but I'm still having
> > problems updating to the latest kernel.  First I tried it without
> > skip-broken....
> >
> > [root at localhost ~]# yum update
> > Loading "skip-broken" plugin
> > Setting up Update Process
> > Resolving Dependencies
> > --> Running transaction check
> > ---> Package kernel.i686 0:2.6.23.1-10.fc7 set to be updated
>                                              ^^^^^^^^^^^^^^^^^
>
> I read this as yum trying to uninstall 2.6.22.9-91.fc7 otherwise it
> should say set to be installed. Isn't 2.6.22.9-91.fc7 your running
> kernel? If so then this could break havoc on your system and you need
> to investigate why yum is trying to do that.

Yep, that is my running kernel, and the only kernel I have on the system.

> skip-broken saved your system from nuking the running (?)
> kernel. Maybe you have some test kernels installed? I thinnk the following is the cause:
>
>        installonly_limit
>               Number of packages listed in installonlypkgs to  keep  installed
>               at the same time. Setting to 0 disables this feature. Default is
>               '2'.
>
> Set this to a higher number or to 0 and try again. If that succeeds
> please file a bug against yum at bugzilla.redhat.com to indicate need
> for adjustment of the default value of this parameter. Seems to bit
> quite a lot of people lately.

I've set it to 0 and to 4 with no change in behavior (it was unset
before).  What's strange is when I simply try and install the kernel,
I get the following...

[root at localhost ~]# yum install kernel
Loading "skip-broken" plugin
Setting up Install Process
Parsing package install arguments
Resolving Dependencies
--> Running transaction check
---> Package kernel.i686 0:2.6.21-1.3194.fc7 set to be updated
---> Package kernel.i686 0:2.6.23.1-10.fc7 set to be updated

..and then the same complaints about dependencies.  I've deleted
2.6.21-1.3194, rebuilt the rpm database, and done a yum clean all, and
for some reason yum thinks the package is still there.  I'll head over
to bugzilla and file something, because this is just weird.

-- 
Jason Sullivan
jason0x21 at gmail.com