![](https://seccdn.libravatar.org/avatar/541f0424df99fb299635f2b0c46454b0.jpg?s=120&d=mm&r=g)
On 2015-08-19 12:54, Takashi Iwai wrote:
On Wed, 19 Aug 2015 12:47:16 +0200, Michal Marek wrote:
On 2015-08-19 12:42, Jiri Slaby wrote:
On 08/19/2015, 12:29 PM, Michal Marek wrote:
As maintainer of VirtualBox on openSUSE, I would like to know how to prevent this in the future. My understanding of the build process is rather rudimentary.
The "proper" fix would be to reintroduce the ksym() dependencies, i.e. make the KMPs depend on the kernel ABI checksums rather than the kernel release string.
Which leads to another question: why do we still fight with kabi in opensuse when we don't leverage from that?
That's a good question. I personally do not think that it makes sense to keep the kabi in openSUSE.
It makes our lives easier in one side, but also makes hard in another side. It means that we need to publish the kernel update and the updates of the all KMPs in a shot. Otherwise it'll break the system.
To make it clear: Given the decision to drop ksym() dependencies, I do not think it makes sense to keep the kabi. I would of course prefer having the ksym() dependencies and maintaining the kabi.
And rpm / zypper doesn't detect it... (the update of kernel won't be blocked by the lack of KMP). Or was it already improved?
It does not detect it, because we enable multiversion for the kernel packages by default. Michal -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org