Summary: | =app-emulation/virtualbox-modules-4.1.8 stabilization request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ihar Hrachyshka <ihar.hrachyshka> |
Component: | [OLD] Keywording and Stabilization | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | israel.lugo, mephinet, nitro, njsg, patrick, swapon |
Priority: | Normal | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 399807, 403441 | ||
Bug Blocks: |
Description
Ihar Hrachyshka
2012-01-27 10:43:30 UTC
Agreed. For further information please see bug 389953, of which 400871 is a duplicate. We first need a fix for bug #399807 before we can stabilize any newer version. It looks like this bug applies to all versions of 4.1.x, which means it affects the current stable version of vbox as well. However, 4.1.4 cannot be used with the current stable kernel, whereas 4.1.8 can. I don't think stabilizing 4.1.8, which fixes aa very obvious application-breaking problem (after an emerge -u world), should be held up because of a separate bug that affects both versions. Granted, bug 399807 should be addressed as soon as possible, but given the circumstances it shouldn't be considered a blocker for this. So stable virtualbox is broken in the tree for several weeks. Any obstacles to fix this issue? As Jared said, there is no reason to wait until another bug is fixed. virtualbox-4.1.8 is finally stable... |