There seems to be an issue between VirtualBox and kmod-VirtualBox (see output below).  The kmods seem to be on version 4.3.26, while VirtualBox is on 4.3.20.  Will we be getting the 4.3.26 version of VirtualBox soon?



$ sudo yum install kmod-VirtualBox
Loaded plugins: langpacks
Resolving Dependencies
--> Running transaction check
---> Package kmod-VirtualBox.x86_64 0:4.3.26-1.fc21.1 will be installed
--> Processing Dependency: kmod-VirtualBox-3.19.2-201.fc21.x86_64 >= 4.3.26-1.fc21.1 for package: kmod-VirtualBox-4.3.26-1.fc21.1.x86_64
--> Running transaction check
---> Package kmod-VirtualBox-3.19.2-201.fc21.x86_64.x86_64 0:4.3.26-1.fc21.1 will be installed
--> Processing Dependency: VirtualBox-kmod-common >= 4.3.26 for package: kmod-VirtualBox-3.19.2-201.fc21.x86_64-4.3.26-1.fc21.1.x86_64
--> Finished Dependency Resolution
Error: Package: kmod-VirtualBox-3.19.2-201.fc21.x86_64-4.3.26-1.fc21.1.x86_64 (rpmfusion-free-updates)
           Requires: VirtualBox-kmod-common >= 4.3.26
           Installed: VirtualBox-4.3.20-3.fc21.x86_64 (@rpmfusion-free-updates)
               VirtualBox-kmod-common = 4.3.20-3.fc21
           Available: VirtualBox-4.3.20-1.fc21.x86_64 (rpmfusion-free)
               VirtualBox-kmod-common = 4.3.20-1.fc21
           Available: VirtualBox-guest-4.3.20-1.fc21.x86_64 (rpmfusion-free)
               VirtualBox-kmod-common = 4.3.20-1.fc21
           Available: VirtualBox-guest-4.3.20-3.fc21.x86_64 (rpmfusion-free-updates)
               VirtualBox-kmod-common = 4.3.20-3.fc21
 You could try using --skip-broken to work around the problem