Description of problem: [landon4@x1-6-00-b0-d0-16-1c-01 QtFigs4]$ su - Password: [root@x1-6-00-b0-d0-16-1c-01 ~]# yum update Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package kmod-nvidia.i686 0:100.14.19-18.lvn8 set to be updated --> Processing Dependency: kmod-nvidia-2.6.23.1-49.fc8 for package: kmod-nvidia --> Running transaction check ---> Package kmod-nvidia-2.6.23.1-49.fc8.i686 0:100.14.19-18.lvn8 set to be updated --> Processing Dependency: kernel-i686 = 2.6.23.1-49.fc8 for package: kmod-nvidia-2.6.23.1-49.fc8 --> Finished Dependency Resolution Error: Missing Dependency: kernel-i686 = 2.6.23.1-49.fc8 is needed by package kmod-nvidia-2.6.23.1-49.fc8 [root@x1-6-00-b0-d0-16-1c-01 ~]# Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: yum update 1. 2. 3. Actual results: Expected results: Additional info:
something is wrong with a mirror. I have that kernel installed. yum clean all yum update
kmod-nvidia is from livna, and it is dependent on a kernel package that isn't available on most mirrors yet.
this: yum install kmod-nvidia worked fine after installing F8 and solved the problem of the screensaver running slow (same problem on F7 This yum install kmod-nvidia was recommended on the Mauriat Miranda site for F8
yum updates are breaking dependencies with livna kmods now, i think, because something is making yum try to remove the old kernel when it updates to a new one. since i started using fc6, it has always allowed the latest kernel to live side by side with the one it replaced for safety. this stopped when i installed f8. we can download the kernel manually and install with rpm -i though, i hear.
true? (1) I installed F8 and the automatic yum did an instant update (2) I installed livna (3) I did a yum install kmod-nvidia (details on the other OS) and solved my screensaver running too slow) (4) and later came a automatic yum update that got the error I had seen no kernel updates at any point
(In reply to comment #4) install_only moved to the yum core and no longer is a yum plugin. If you just updated you installation you might need to adjust your configuration to reflect that. Have a look into the yum config files shipped with the current yum.
the initial comment in this bug looks like mirror issues (the kmod from livna was available before the Fedora mirror had the matching kernel for it) Comment #4 is likely about Bug 330711 Comment #5 -- no idea what that's about without a detailed error message, but likely 330711 as well *** This bug has been marked as a duplicate of 330711 ***