On 11/22/2011 12:13 PM, Matthew Garrett wrote: > 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. > For those having trouble - one pragmatic way is just to download the f16 3.1.x source rpm and rebuild it on F15 - VB will now work fine. Of course - caution drove the renaming of this kernel to 2.6.41 so it could break ... that said it does work fine for me ... gene/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
