When VirtualBox.org first posted Sun VirtualBox 3.0.6, it used build 52128. However a long standing bug was resolved (see URL), and they quietly replaced 3.0.6 build 52128 with 3.0.6 build 52130. The major version stayed the same, so for people with app-emulation/virtualbox-bin already installed, we didn't get notified of the update (and so we have the bugged version). I suggest creating a -r1 of virtualbox-bin-3.0.6 which will download the new version. Reproducible: Always Steps to Reproduce: 1. emerge virtualbox-bin Actual Results: Downloads the old version of 3.0.6 (build 52128). Expected Results: Download the new version of 3.0.6 (build 52130).
(In reply to comment #0) > When VirtualBox.org first posted Sun VirtualBox 3.0.6, it used build 52128. > However a long standing bug was resolved (see URL), and they quietly replaced > 3.0.6 build 52128 with 3.0.6 build 52130. Yes, same bad habit by VirtualBox upstream and _still without_ notification... > we didn't get notified of the update (and so we have the bugged version). sure as usual ;) Well i'm unable to find any news about this silent update, for this reason i wrote an email to upstream[1], i want to know why this updated affected only amd64 (and what kind of update). For the moment thanks for your feedback [1] http://vbox.innotek.de/pipermail/vbox-dev/2009-September/001821.html
Today upstream replied to my previous answer[1], as Frank said the silent bump was due a critical bug[2] that afflicts amd64 platforms, and the official announcement will appear later.. app-emulation/virtualbox-bin was updated to 3.0.6-r1 on jokey's overlay[3] [1] http://vbox.innotek.de/pipermail/vbox-dev/2009-September/001822.html [2] http://www.virtualbox.org/ticket/616 [3] http://overlays.gentoo.org/dev/jokey
+ 17 Sep 2009; Patrick Lauer <patrick@gentoo.org> + +virtualbox-bin-3.0.6-r1.ebuild: + Bump for #285228, fixes silent upstream tarball change madness. Thanks to + X-Drum for fixing and testing.
