From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 24 08:00:22 2010 Return-Path: Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6687106566B; Thu, 24 Jun 2010 08:00:22 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id B20448FC08; Thu, 24 Jun 2010 08:00:21 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA18066; Thu, 24 Jun 2010 11:00:20 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1ORhMB-0007kS-Qi; Thu, 24 Jun 2010 11:00:19 +0300 Message-ID: <4C231092.7020603@icyb.net.ua> Date: Thu, 24 Jun 2010 11:00:18 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100603) MIME-Version: 1.0 To: Beat Gaetzi References: <4C230BC2.4040908@icyb.net.ua> <4C230D38.9020402@FreeBSD.org> In-Reply-To: <4C230D38.9020402@FreeBSD.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-emulation@FreeBSD.org, vbox@FreeBSD.org Subject: Re: why vbox is marked broken for head? X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jun 2010 08:00:22 -0000 on 24/06/2010 10:46 Beat Gaetzi said the following: > On 06/24/10 09:39, Andriy Gapon wrote: >> >> Why vbox is marked broken for head? >> I keep using it with TRYBROKEN and see zero problems. >> Where are the bug reports? Perhaps there are specific problems that >> can be >> investigated, fixed or worked around (via configuration)? > > There are several known panics with CURRENT older than revision 209048. I see. > The port also do not build on current newer than revision 208751. This > is fixed in our development repository and we will remove the BROKEN > with the update to 3.2.6. The memchr issue? When 3.2.6 is planned? If it's soon I'd just wait, otherwise it seems to be trivial to unbreak the port for post-r209048 head. Thanks you! -- Andriy Gapon