PDA

View Full Version : yum update "Missing Dependency" issue



dciarnie
27th July 2007, 11:32 PM
I just tried to do a yum update and got the following:

Resolving Dependencies
--> Running transaction check
---> Package kernel-devel.i686 0:2.6.22.1-33.fc7 set to be updated
---> Package bind-chroot.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package kernel.i686 0:2.6.22.1-33.fc7 set to be updated
---> Package bind-utils.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package caching-nameserver.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package bind.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package bind-libs.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package kernel-headers.i386 0:2.6.22.1-33.fc7 set to be updated
--> Processing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 for package: fuse-kmdl-2.6.22.1-27.fc7
--> Processing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 for package: nvidia-graphics100.14.11-kmdl-2.6.22.1-27.fc7
--> Processing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 for package: ivtv-kmdl-2.6.22.1-27.fc7
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel-devel.i686 0:2.6.22.1-33.fc7 set to be updated
---> Package bind-chroot.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package kernel-devel.i686 0:2.6.21-1.3228.fc7 set to be erased
---> Package kernel.i686 0:2.6.22.1-33.fc7 set to be updated
---> Package kernel.i686 0:2.6.21-1.3228.fc7 set to be erased
---> Package bind-utils.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package caching-nameserver.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package bind.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package bind-libs.i386 31:9.4.1-8.P1.fc7 set to be updated
---> Package kernel-headers.i386 0:2.6.22.1-33.fc7 set to be updated
--> Processing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 for package: fuse-kmdl-2.6.22.1-27.fc7
--> Processing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 for package: nvidia-graphics100.14.11-kmdl-2.6.22.1-27.fc7
--> Processing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 for package: ivtv-kmdl-2.6.22.1-27.fc7
--> Finished Dependency Resolution
Error: Missing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 is needed by package fuse-kmdl-2.6.22.1-27.fc7
Error: Missing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 is needed by package nvidia-graphics100.14.11-kmdl-2.6.22.1-27.fc7
Error: Missing Dependency: /boot/vmlinuz-2.6.22.1-27.fc7 is needed by package ivtv-kmdl-2.6.22.1-27.fc7

I don't understand why I am getting the Missing Dependency error. /boot/vmlinuz-2.6.22.1-27.fc7 exists so the dependency isn't missing.

If anyone could shed any light on this, it would be greatly appreciated.

Thanks,
Dan.

leigh123linux
27th July 2007, 11:37 PM
--> Package kernel.i686 0:2.6.22.1-33.fc7 set to be updated

Gnafu the Great
27th July 2007, 11:43 PM
I'm getting a similar error in FC6; it wants to update FUSE and it needs /boot/vmlinuz-2.6.22.1-24.fc6 :p. It's in updates-testing, but I'm just wondering why a FUSE update in updates is calling for a kernel update in updates-testing.

EDIT: In these situations, I suggest you update everything else and wait for them to fix it :p.

dciarnie
27th July 2007, 11:48 PM
--> Package kernel.i686 0:2.6.22.1-33.fc7 set to be updated

I still don't get it. 2.6.22.1-27 is not being removed; the previous version is. 2.6.22.1-27 will still be there for fuse/nvidia/ivtv assuming that I boot to that kernel. I know that I will need to install the new fuse/nvidia/ivtv kernel modules to match the new kernel but that shouldn't be an issue.

This hasn't been an issue for past kernel updates so I don't understand why it is now.

lazlow
28th July 2007, 12:55 AM
I do not know if this is it or not, but when -27 was installed on my machine it decided to install the 586 version(all the rest were 686 versions). This caused a lot of hate and discontent. I would check to make sure the -27 was 686.

Gnafu the Great
29th July 2007, 12:22 AM
Just so you know, my FUSE update worked just now on my FC6 box. All is better now :D.

dciarnie
30th July 2007, 04:11 AM
Good to hear.

I finally worked around the problem by removing the three problem kernel modules, updating the kernel and then re-installing the kernel modules that matched the new kernel.

I can only assume that the reason that the problem occurred is that the fuse/nvidia/ivtv modules were inadvertently marked as requiring an update. An update implies replacement which is not appropriate for kernel modules.

Dan