Date: Sat, 5 Aug 2017 13:26:19 +0200 From: CeDeROM <cederom@tlen.pl> To: Mike Clarke <jmc-freebsd2@milibyte.co.uk> Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org>, freebsd-pkg@freebsd.org Subject: Re: VirtualBox bridged networking stopped working after upgrading host to 11.1 RELEASE Message-ID: <CAFYkXj=rDXe5n2Xbq%2B44Dy1%2ByFO2JZSvfphMO5xyKxSg4XXkug@mail.gmail.com> In-Reply-To: <20170804111018.5f4459b2@curlew> References: <20170802211628.1e40814f@curlew> <20170802190734.3f95f36e@Papi> <20170803125642.4e4133ff@curlew> <20170804111018.5f4459b2@curlew>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 4, 2017 at 12:10 PM, Mike Clarke <jmc-freebsd2@milibyte.co.uk> wrote: > On Thu, 3 Aug 2017 12:56:42 +0100 > Mike Clarke <jmc-freebsd2@milibyte.co.uk> wrote: > >> It looks like the problem is related to virtualbox-ose-kmod installed >> from the FreeBSD package repository not being compatible with 11.1. >> >> I'm running virtualbox-ose-5.1.26 and virtualbox-ose-kmod-5.1.26 on >> 11.1-RELEASE. Rebuilding virtualbox-ose-kmod from ports and keeping >> virtualbox-ose from packages fixed the problem. > > On further thoughts I suppose there's no way of avoiding this. > virtualbox-ose-kmod requires kernel source files in /usr/src in order > to build so we can't assume that virtualbox-ose-kmod from the package > repository will be compatible with any release version above x.0 Packages are not built against a RELEASE? 11.1 is a RELEASE so it should get packages than 11.0? If not, pkg should clearly get such mechanism, at least for some specific cases.. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXj=rDXe5n2Xbq%2B44Dy1%2ByFO2JZSvfphMO5xyKxSg4XXkug>