On Mon, 16 Jun 2014 22:36:02 +0800, Someone wrote:
I ran "sudo yum update -y" a few days ago, as I often do,
and I saw the
following error:
Error: Package:
kmod-VirtualBox-3.14.6-200.fc20.x86_64-4.3.12-1.fc20.2.x86_64
(rpmfusion-free-updates)
Requires: kernel-uname-r = 3.14.6-200.fc20.x86_64
Installed: kernel-3.14.4-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.14.4-200.fc20.x86_64
Installed: kernel-3.14.5-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.14.5-200.fc20.x86_64
Installed: kernel-3.14.7-200.fc20.x86_64 (@updates)
kernel-uname-r = 3.14.7-200.fc20.x86_64
Available: kernel-3.11.10-301.fc20.x86_64 (fedora)
kernel-uname-r = 3.11.10-301.fc20.x86_64
Available: kernel-debug-3.11.10-301.fc20.x86_64 (fedora)
kernel-uname-r = 3.11.10-301.fc20.x86_64+debug
Available: kernel-debug-3.14.7-200.fc20.x86_64 (updates)
kernel-uname-r = 3.14.7-200.fc20.x86_64+debug
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
So I ran "sudo yum update -y --skip-broken", as suggested, and the
update completed without incident. Then I left my machine alone for a
few days, and came back to it figuring that I should run another update,
so I did, and I received the same error. Does this indicate that
anything worrisome is wrong?
You cannot let Yum remove old kernel packages from your installation,
if a package like kmod-VirtualBox still requires that kernel.
And, regardless, is there anything I could
do to rectify the issue so that I don't keep having to run yum update
commands with the --skip-broken option?
Once you've booted with a newer kernel, you could uninstall older kernel
packages *and* any kmod packages for those kernels.