Bugzilla Bug 233683

Virtualbox-bin-1.6.2 has fetch restriction, but the required file is no longer
available for download as version 1.6.4 has been released. An ebuild for 1.6.4
- which is the file one can download now - is necessary.

Reproducible: Always

where does the package vbox-kernel-module-src come from? does anyone know? It
seems to be required for virtualbox-modules but 1.6.4 version is not there
anywhere.

Hi all,

(In reply to comment #0)
> Virtualbox-bin-1.6.2 has fetch restriction, but the required file is no longer
> available for download as version 1.6.4 has been released. An ebuild for 1.6.4
> - which is the file one can download now - is necessary.

Since the Sun acquisition of Innotek/VirtualBox there are some bit problems
with downloads, a VirtualBox told me that they are working on this issue, 
so in a near future they will be able to offer the PUEL edition of VirtualBox
on their website[1] without restrictions (aka without fetch-restrictions for
the gentoo users).

Atm they are not able to offer/control this files stored on the Sun Download
Center (SDLC).

(In reply to comment #1)
> where does the package vbox-kernel-module-src come from? does anyone know? It
> seems to be required for virtualbox-modules but 1.6.4 version is not there
> anywhere.

I don't know the reason but in the last two releases this file vanished (its no
more released as separate package), so i decided to do a tarball for this
package an to host it on gentoo mirrors, the package is released under the GPL
version 2 in addition i asked permission to do so, atm you can find it on my
own webspace[2]

A version bump is now available on jokey's overlay[3] for testing, please give
it a try.

[1] http://www.virtualbox.org/download/
[2] http://gentoo.zerodev.it/files/vbox-kernel-module-src-1.6.4.tar.bz2
[3] https://overlays.gentoo.org/dev/jokey/browser/trunk/app-emulation/

(In reply to comment #2)
> Hi all,
> 
> (In reply to comment #0)
> > Virtualbox-bin-1.6.2 has fetch restriction, but the required file is no longer
> > available for download as version 1.6.4 has been released. An ebuild for 1.6.4
> > - which is the file one can download now - is necessary.
> 
> Since the Sun acquisition of Innotek/VirtualBox there are some bit problems
> with downloads, a VirtualBox told me that they are working on this issue, 
> so in a near future they will be able to offer the PUEL edition of VirtualBox
> on their website[1] without restrictions (aka without fetch-restrictions for
> the gentoo users).
> 
> Atm they are not able to offer/control this files stored on the Sun Download
> Center (SDLC).
> 
> (In reply to comment #1)
> > where does the package vbox-kernel-module-src come from? does anyone know? It
> > seems to be required for virtualbox-modules but 1.6.4 version is not there
> > anywhere.
> 
> I don't know the reason but in the last two releases this file vanished (its no
> more released as separate package), so i decided to do a tarball for this
> package an to host it on gentoo mirrors, the package is released under the GPL
> version 2 in addition i asked permission to do so, atm you can find it on my
> own webspace[2]
> 
> A version bump is now available on jokey's overlay[3] for testing, please give
> it a try.
> 
> [1] http://www.virtualbox.org/download/
> [2] http://gentoo.zerodev.it/files/vbox-kernel-module-src-1.6.4.tar.bz2
> [3] https://overlays.gentoo.org/dev/jokey/browser/trunk/app-emulation/
> 

there is a nasty bug with 1.6.4 where an ever growing debug log is written to
user's home dir. any idea if there is a fix for it?

(In reply to comment #3)
> there is a nasty bug with 1.6.4 where an ever growing debug log is written to
> user's home dir. any idea if there is a fix for it?

Yes it was a glitch discovered only after the release,
you can simply disable logging via an environment variable to fix this
issue[1]:

export VBOX_LOG_DEST=nofile

a note was added on virtualbox's site[2]

[1] http://forums.virtualbox.org/viewtopic.php?t=8358#30807
[2] http://www.virtualbox.org/wiki/Downloads

(In reply to comment #3)
In order to simplify users' life, i added an env.d to export the 
environment variable:
VBOX_LOG_DEST=nofile

This assures that in this release logging will be disabled by default,
updated ebuilds (for virtualbox and virtualbox-bin) are on jokey's overlay[1].

[1] https://overlays.gentoo.org/dev/jokey/browser/trunk/app-emulation/

what's stopping it from going into portage tree? even as masked package?

(In reply to comment #6)
> what's stopping it from going into portage tree? even as masked package?
> 

nothing technically, it's only a matter of time, i don't have access to the
portage tree (because i'm not a dev), this task will be accomplished by someone
else (eg:jokey) please hang on :D

since people need to download the .run anyways, splitting off the modules
doesnt really gain much except create a weird black box without documentation
as to how this magic tarball was made.  please convert
virtualbox-modules-1.6.4.ebuild to simply use the same .run file as
virtualbox-bin-1.6.4.  it's simple once you set S to ${WORKDIR}/src and have it
use the same unpacking method.

since you already need to agree to the license when downloading the file,
there's no need to check_license in the ebuild.  please apply these changes to
the virtualbox-bin-1.6.4 ebuild:
-DESCRIPTION="Softwarefamily of powerful x86 virtualization"
+DESCRIPTION="family of powerful x86 virtualization products for enterprise as
well as home use"
-       elog "Please from the site:"
+       elog "Please download the package from the site:"
-       check_license

Created an attachment (id=162484) [details]
2.6.27.patch

I needed this patch to compile the virtualbox module under 2.6.27-rc2.

any ETA on this reaching portage tree? masked or not.

within the next 20 minutes ;)
InCVS now

(In reply to comment #11)
> within the next 20 minutes ;)
> InCVS now
> 

is the variable for turning debugging off set in the env.d? I don't see it set
in a new login.

(In reply to comment #12)
> is the variable for turning debugging off set in the env.d? I don't see it set
> in a new login.
sorry i wasn't able to reply, after some test with env.d variable i found that
in some scenarios (eg: when VirtualBox is not launched via shell) it still
produce huge logs, so i setted the variable in the wrapper, the version
commited in portage uses this approach too.