Changing kernel API / Breaking VirtualBox - update criteria violation?
Matthew Garrett
mjg59 at srcf.ucam.org
Tue Nov 22 17:13:30 UTC 2011
On Tue, Nov 22, 2011 at 06:00:43PM +0100, 80 wrote:
> The failure is due to Fedora *non-upstream* versionning scheme,
> VirtualBox has *already* fixes the API/ABI issue upstream relying on
> the kernel version (since 3.2 RC). It has nothing to do with the
> kernel non-stable ABI policy (which is notorious).
> The least we can do is helping third-party packagers to fix this
> issue, not slamming the door on their face.
The supported way to provide a module for Fedora is to have it in the
upstream kernel source. Anything else is explicitly not supported.
--
Matthew Garrett | mjg59 at srcf.ucam.org
More information about the devel
mailing list