From owner-freebsd-emulation@FreeBSD.ORG Thu Jun 24 08:09:39 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 3E497106566B; Thu, 24 Jun 2010 08:09:39 +0000 (UTC) (envelope-from beat@FreeBSD.org) Received: from azh-com0.aspectra.com (azh-com0.aspectra.com [212.47.170.6]) by mx1.freebsd.org (Postfix) with ESMTP id F400C8FC1B; Thu, 24 Jun 2010 08:09:38 +0000 (UTC) Message-ID: <4C2312BE.6070203@FreeBSD.org> Date: Thu, 24 Jun 2010 10:09:34 +0200 From: Beat Gaetzi User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.4) Gecko/20100623 Thunderbird/3.1 MIME-Version: 1.0 To: Andriy Gapon References: <4C230BC2.4040908@icyb.net.ua> <4C230D38.9020402@FreeBSD.org> <4C231092.7020603@icyb.net.ua> In-Reply-To: <4C231092.7020603@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Jun 2010 08:09:37.0888 (UTC) FILETIME=[96E47600:01CB1374] 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:09:39 -0000 On 06/24/10 10:00, Andriy Gapon wrote: > 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? Yes. > 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. I don't know the release date but 3.2.6_BETA2 was released two days ago so I think 3.2.6 will be released soon. Beat