[ATrpms-users] FC7 Dependency Resolution problem.

[Axel Thimm]

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.

> --> Processing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 for package:
> madwifi-kmdl-2.6.22.9-91.fc7
> --> Processing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 for package:
> fuse-kmdl-2.6.22.9-91.fc7
> --> Processing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 for package:
> madwifi-hal-kmdl-2.6.22.9-91.fc7
> --> Finished Dependency Resolution
> Error: Missing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 is needed by
> package madwifi-kmdl-2.6.22.9-91.fc7
> Error: Missing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 is needed by
> package fuse-kmdl-2.6.22.9-91.fc7
> Error: Missing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 is needed by
> package madwifi-hal-kmdl-2.6.22.9-91.fc7

This all means that yum was going to uninstall 2.6.22.9-91.fc7.

> 
> ...then with...
> 
> [root at localhost ~]# yum --skip-broken update
> Loading "skip-broken" plugin
> Setting up Update Process
> Resolving Dependencies
> **** Checking packages for dependency problems
> **** Checking for dep problems  : kernel - 2.6.23.1-10.fc7.i686
> --> Running transaction check
> ---> Package kernel.i686 0:2.6.23.1-10.fc7 set to be updated
> --> Processing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 for package:
> madwifi-kmdl-2.6.22.9-91.fc7
> --> Processing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 for package:
> fuse-kmdl-2.6.22.9-91.fc7
> --> Processing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 for package:
> madwifi-hal-kmdl-2.6.22.9-91.fc7
> --> Finished Dependency Resolution
> ****   Failed
> ****     Missing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 is needed
> by package madwifi-kmdl-2.6.22.9-91.fc7
> ****     Missing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 is needed
> by package fuse-kmdl-2.6.22.9-91.fc7
> ****     Missing Dependency: /boot/vmlinuz-2.6.22.9-91.fc7 is needed
> by package madwifi-hal-kmdl-2.6.22.9-91.fc7
> **** Checking for dep problems  : kernel - 2.6.22.9-91.fc7.i686
> --> Running transaction check
> --> Finished Dependency Resolution
> ****   OK : kernel.i686 0-2.6.22.9-91.fc7 - None
> **** Packages with dependency resolving errors
> **** kernel - 2.6.23.1-10.fc7.i686
> ****   2
> ****   2
> ****   2
> **** End Checking packages for dependency problems
> --> Running transaction check
> --> Finished Dependency Resolution
> 
> Dependencies Resolved
> 
> =============================================================================
>  Package                 Arch       Version          Repository        Size
> =============================================================================
> 
> Transaction Summary
> =============================================================================
> Install      0 Package(s)
> Update       0 Package(s)
> Remove       0 Package(s)
> 
> Is this ok [y/N]: y
> Downloading Packages:
> Running rpm_check_debug
> Running Transaction Test
> Finished Transaction Test
> Transaction Test Succeeded
> Running Transaction
> 
> Complete!
> [root at localhost ~]#
> 
> ...as they say on the internets,  "Wait, what?"

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.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.atrpms.net/pipermail/atrpms-users/attachments/20071031/6f23dabb/attachment-0001.bin