| Summary: | app-emulation/virtualbox-ose should not inform about new upstream versions | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Fabian Köster <gentoo> |
| Component: | Current packages | Assignee: | Patrick Lauer <patrick> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | CC: | polynomial-c, swapon |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 320595 | ||
| Bug Blocks: | |||
| Attachments: | ebuild which unsets VBOX_WITH_UPDATE_REQUEST | ||
|
Description
Fabian Köster
2010-06-14 22:58:57 UTC
Created attachment 235329 [details]
ebuild which unsets VBOX_WITH_UPDATE_REQUEST
Could you please test if this is still an issue with virtualbox-ose-3.1.8? I've
been told in #vbox that this is no longer a problem with >=virtualbox-3.1
In case you don't know how to install a not yet stable virtualbox here's a
small on-eliner:
for pkg in $(qlist -CIq virtualbox) ; do echo "~${pkg}-3.1.8" >>
/etc/portage/package.keywords ; done
You need qlist from app-portage/portage-utils package to make the above
one-liner work.
I removed .VirtualBox, emerged virtualbox-3.1.8, started it and there is neither an update-message, nor a registration-request, so this should be fixed in 3.1.8 (and above?) app-emulation/virtualbox-3.1.8 got stable on x86 and amd64 (#bug 320595), so this is fixed too. |