Ask Your Question

yum : manually adding dependencies [closed]

asked 2014-04-12 09:31:34 -0500

kdg1955 gravatar image

updated 2014-04-12 09:34:30 -0500

remjg gravatar image

Can I (manually) create a 'yum' dependency between a kernel package and a kmod package?

Currently I have to manually install the latest kmod version and this for each kernel update. But if the latest version of the kmod is delayed, it can lead to a little curse. Because I have to reboot to my older kernel, and wait until the kmod is generated before I can use the newest kernel.

FYI: it concerns 'kmod-VirtualBox'.

I know I can use 'akmod', but at rpmfusion the latest version of VirtualBox.x86_64 is '4.3.6-4.fc19' and for akmod-VirtualBox.x86_64 it is '4.3.6-2.fc19' ! And I suspect that this was the reason why I could not get it to work.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by kdg1955
close date 2014-04-25 03:44:53.134565

3 Answers

Sort by ยป oldest newest most voted

answered 2014-04-14 18:19:28 -0500

sergiomb gravatar image

updated 2014-04-15 13:53:03 -0500


when this happens you can update everything else with :

yum update --skip-broken

and you always have the kmod in updates-testing , so you can do:

 yum --enablerepo=rpmfusion-free-updates-testing update kernel

kernel before enter in updates enter in updates-testing and rpmfusion-free-updates-testing also build kmods for kernel in testing .

In reply:

rpm -q kmod-VirtualBox


kmod-VirtualBox is a meta-package, which sole purpose is to require the VirtualBox kernel module(s) for the newest kernel. To make sure you get it together with a new kernel.

so if you have kmod-VirtualBox installed you will need use --skip-broken and you should IMHO.

edit flag offensive delete link more


yum does not generate errors when there is a new kernel available. Thus '--skip-broken' is not applicable. The problem is that I can't put dependencies between the kernel and the installed kmod module(s). I can wait until a new stable kmod module appears and I don't need to work with the latest kernel. 'yum' is a superb product, but unfortunately it does not solve all dependencies issues and as a result there are still manual operations to carry out. I still remember the time that it did not exist, then you could spend hours working on the dependencies.

kdg1955 gravatar imagekdg1955 ( 2014-04-15 06:33:23 -0500 )edit

@sergiomb: That package was indeed not installed. I did not know it existed. I wonder if everything is progressing satisfactorily with the next kernel release. Suggestion for rpmfusion: install that package together with any kmod-VirtualBox-<kernel version>. My apologies for the misunderstanding. This means a great help. Thanks.

kdg1955 gravatar imagekdg1955 ( 2014-04-15 17:03:45 -0500 )edit

hi, kmods for 3.13.10-100.fc19 was already built , now should be publish on updates-testing soon , you may follow commits on , builds on and when is publish on the emails From:

sergiomb gravatar imagesergiomb ( 2014-04-16 11:53:51 -0500 )edit

answered 2014-04-12 09:59:59 -0500

cobra gravatar image

You cannot add your own dependency without rebuilding the RPM file. The dependency already exists the other way - the kmod is dependent upon the particular kernel version. If you kernel module was built with a dependency on the kmod, then everyone installing that kernel rpm would also need to install the kmod rpm too - and that situation would not be very nice for the community.

I understand your frustration, I had the same problem with kmod-nvidia from time to time before I moved to an AMD video chipset. The way I always worked around it was either to always postpone kernel updates for a couple of days or just not reboot at all until the kmod turned up in a later update. I did (and still do) all my updates at the command line by hand.

edit flag offensive delete link more


Thanks. I thought of a conditional dependency, eg: only if kmod-VirtualBox is installed. But if I understand you well, this is also not possible.

kdg1955 gravatar imagekdg1955 ( 2014-04-12 10:13:22 -0500 )edit

You could also exclude updates of all the packages causing troubles ( ) - in you case exclude=kernel-* *VirtualBox* , and monitor security reports in order to apply only the critical updates. Or configure oracle virtualbox repository: . Thought by past lessons, I recommend to keep virtualbox updates excluded anyway.

marcindulak gravatar imagemarcindulak ( 2014-04-12 10:40:41 -0500 )edit

answered 2014-04-14 20:38:24 -0500

mether gravatar image

You might want to consider using akmods instead of kmod's if you don't mind have a compiler installed on your system that dynamically builds the modules for the newer kernels on demand

edit flag offensive delete link more


This might be an alternative. But each time a new VirtualBox is installed it should be triggered. Otherwise I sit with the same frustration.

kdg1955 gravatar imagekdg1955 ( 2014-04-15 06:51:10 -0500 )edit

Question Tools

1 follower


Asked: 2014-04-12 09:31:34 -0500

Seen: 440 times

Last updated: Apr 15 '14