| Summary: | please stablize app-emulation/virtualbox-4.1.24 and related vbox packages | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Flogeras <dflogeras2> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | patrick, swapon, zerochaos |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
David Flogeras
2012-12-20 02:16:42 UTC
I'd rather like to have virtualbox-4.1.24 stabilized. Please test gentoo-sources-3.6.11 with that version and report back if that works as well. Compiled and loaded up a VM on both amd64 and x86 (after upgrading to 3.6.11 on x86 since it is not yet stabled on that arch). No problems here. Thanks for testing. I will wait a couple of days before I poke arches about stabilizing this version just to get some more testing out of this. Arches please test and mark stable the following packages: =app-emulation/virtualbox-4.1.24 =app-emulation/virtualbox-additions-4.1.24 =app-emulation/virtualbox-bin-4.1.24-r1 =app-emulation/virtualbox-extpack-oracle-4.1.24 =app-emulation/virtualbox-guest-additions-4.1.24 =app-emulation/virtualbox-modules-4.1.24 =x11-drivers/xf86-video-virtualbox-4.1.24 Target keywords are: amd64 x86 since there are new vuln, we can avoid to stabilize this? (In reply to comment #5) > since there are new vuln, we can avoid to stabilize this? Which vulnerabilities are you talking about? (In reply to comment #6) > Which vulnerabilities are you talking about? He's probably talking about * http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-3221 * http://xforce.iss.net/xforce/xfdb/79380 Although I'm not sure if that has been fixed in this (4.1.24) version, as I'm having some issues accessing oracle.com today to doublecheck this. A more acurrate link http://www.oracle.com/technetwork/topics/security/cpuoct2012-1515893.html this seems to have been patched or at least a patch has been released. Some new version of vbox needs to be stabilized, no one with a stable system can use virtualbox anymore and that's really uncool. If people are unwilling to stabilize 4.1.24 then pick another version. Upstream confirmed that virtualbox-4.1.24 is not affected by CVE-2012-3221 so arches please proceed. IMHO virtualbox-4.2.x still is not ready to go stable right now. amd64 stable x86 stable. Last arch, closing |
