FreeBSD Port: virtualbox-ose-4.3.36 - Gone from FreeBSD 11.0?

[Enzmann, Alexander R.]

Thanks, that info helps. I can wait a week or so while the fixes swim downstream. I can also toggle the machine in question to 10.2 or 10.3 while I wait.

Really appreciate the quick feedback. This is one of the things that makes this so great.

Xander



Sent with Good (www.good.com)
________________________________
From: Guido Falsi <mad at madpilot.net>
Sent: Monday, February 29, 2016 5:03:55 PM
To: Enzmann, Alexander R.; vbox at FreeBSD.org
Cc: ports at FreeBSD.org
Subject: Re: FreeBSD Port: virtualbox-ose-4.3.36 - Gone from FreeBSD 11.0?

On 02/29/16 21:17, Enzmann, Alexander R. wrote:
> Help,
>
> I've been using FreeBSD 11.0 for close to a year, and recently ran into a problem.  Virtualbox-ose has disappeared from the list of packages (e.g., http://pkg.freebsd.org/freebsd:11:x86:64/latest/All/), and when I build from source (portsnap fetch, then make install), virtualbox complains about a version mismatch with the kernel and VMs don't run.
>
> Is this simply a timing thing as VirtualBox is updated to match recent 11.0 changes, or will there be a long term problem?
>

FreeBSD head r295983 introduced a problem, later solved in r296075,
which caused building kernel modules from ports to fail. This has also
been reported in bugzilla. [1]

Unluckily the machines building ports for head have been updated to a
revision affected by that problem, so the build for the port has failed.
The package will be available again once the cluster machines are
updated to a newer snapshot unaffected by this bug (I don't know how
often those are updated).

So it's definitely a short term problem, actually already solved in the
repositories, which isn't virtualbox or ports fault either.

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207561

--
Guido Falsi <mad at madpilot.net>