Am 27.07.19 um 13:55 schrieb Michal Suchánek:
On Sat, 27 Jul 2019 11:36:36 +0200 Michal Suchánek
wrote: On Fri, 26 Jul 2019 13:55:34 -0500 Larry Finger
wrote: On 7/26/19 1:20 PM, Michal Suchánek wrote:
On Fri, 26 Jul 2019 11:56:47 -0500 Larry Finger
wrote: What is the magic incantation needed for the VirtualBox spec file so that the kernel modules in the virtualbox-host-kmp package will be built when the kernel changes?
I thought this was being done correctly, but situations such as noted in boo#1142995 keep popping up.
There is a magic incantation in kernel-default-base that reportedly works for Factory. For Leap release repos you need to arrange something with Maintenanace because released packages are not rebuilt otherwise. Technically it should not be required for the release repos, either.
Actually, the failure noted above was for Tumbleweed.
In Factory Virtualbox KMPs should already depend on the kernel version they were built against and become uninstallable when the kernel changes. However, it is not OBS itself checking this rebuild condition. There is a bot somewhere which checks this and rebuilds the packages from time to time. Apparently you can get broken packages released or completely broken Factory due to bad timing. Having a snapshot always checked for uninstallable packages before it is released should be doable, though.
And it is done but Virtualbox has been the single KMP that does not have the dependency that triggers the rebuild. This looks like a bug in Virtualbox itself. There are KMP macros provided by kernel that add dependency on kernel version in Factory/TW and kernel symbols on Leap.
The problem AFAICS is, that virtualbox provides two KMP packages, for host and guest. The macros cannot handle that from what I can see (but I might be not reading them correctly). OTOH it looks totally unnecessary to split the KMPs for host and guest: host modules are loaded manually by a service before the vbox service is started. They will not be loaded in a vbox guest anyway. Right now, virtualbox-host-kmp conflicts with virtualox-guest-kmp to enforce "no stupid config", but this could be solved the same by conflictiong virtualbox with virtualbox-guest-tools and having a common virtualbox-kmp package which contains host and guest modules. Size is also not really an issue, because each kmp package is ~850kb installed size. Larry, would you be interested in a submitrequest that changes the package to one common kmp package using the %kernel_module_package macro and shifts around the conflicts in the userspace packages? Best regards, Stefan -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org