Re: Changing kernel API / Breaking VirtualBox - update criteria violation?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Am 22.11.2011 18:00, schrieb 80:
> 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.

well and why is RPMFUSION not updateing their packages as they did
also with open-vm-tools and in the case of open-vm-tools they decided
to drop the whole package

as example for vmware: VMware-Workstation 8 requires ONE single line
changed and the modules get compiled with 2.6.41

so complain rpmfusion why they are ALWAYS behind the fedora-kernel-packages
and all their kmod and so on are making troubles days and weeks before
they are push at fedora-stable repo, so the rpmfusion-maintainers should
consider to use UPDATES-TESTING to see minor issues before the endusers

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux