From owner-freebsd-ports-bugs@FreeBSD.ORG Tue Jun 1 11:00:14 2010 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 924DA106567E for ; Tue, 1 Jun 2010 11:00:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (unknown [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8218F8FC1C for ; Tue, 1 Jun 2010 11:00:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o51B0EJ3016698 for ; Tue, 1 Jun 2010 11:00:14 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o51B0E9Y016695; Tue, 1 Jun 2010 11:00:14 GMT (envelope-from gnats) Date: Tue, 1 Jun 2010 11:00:14 GMT Message-Id: <201006011100.o51B0E9Y016695@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Max Brazhnikov Cc: Subject: Re: ports/146707: devel/boost-* update to 1.43 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Max Brazhnikov List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2010 11:00:14 -0000 The following reply was made to PR ports/146707; it has been noted by GNATS. From: Max Brazhnikov To: Alexander Churanov Cc: bug-followup@freebsd.org, churanov.port.maintainer@gmail.com Subject: Re: ports/146707: devel/boost-* update to 1.43 Date: Tue, 1 Jun 2010 14:54:35 +0400 On Mon, 31 May 2010 21:25:05 +0400, Alexander Churanov wrote: > Folks, > > THIS REQUIRES TESTING. > > The patch looks sane. > > In order to approve Boost update to 1.43, I have to verify that > dependent ports are fine with the new version. In recent years > failures of dependent ports to build or run with a newer version of > Boost were a major obstacle in updating. So then, I am going to > minimize the impact and find most of issues while testing. > > I started testing update to 1.43 a week ago. I expect the process to > be completed in 1-2 weeks, if no major issues are found. We can request exp run for this update. It takes less then two weeks. Max