From owner-svn-ports-all@FreeBSD.ORG Wed Jan 1 15:09:01 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 09501E24; Wed, 1 Jan 2014 15:09:01 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BECC81CEB; Wed, 1 Jan 2014 15:09:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id 9A3D9BDC44; Wed, 1 Jan 2014 16:08:59 +0100 (CET) X-Virus-Scanned: amavisd-new at absolight.net X-Spam-Flag: NO X-Spam-Score: -3.009 X-Spam-Level: X-Spam-Status: No, score=-3.009 tagged_above=-200 required=5 tests=[AWL=-0.409, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: by prod2.absolight.net (Postfix, from userid 1001) id 3AA38BDC56; Wed, 1 Jan 2014 16:08:59 +0100 (CET) Date: Wed, 1 Jan 2014 16:08:59 +0100 From: Mathieu Arnold To: Aryeh Friedman Subject: Re: svn commit: r337714 - in head/java: openjdk6 openjdk7 Message-ID: <20140101150859.GE29554@prod2.absolight.net> References: <201312271150.rBRBobTH008713@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jan 2014 15:09:01 -0000 On Tue, Dec 31, 2013 at 11:26:08PM -0500, Aryeh Friedman wrote: > How long until this bug is fixed? And does it effect already installed > versions? (we have 7 on beta2) This bug hits all the releases we have from since 8.0, so, this needs to be addressed the right way so that we don't get a massive panic wave because of people running non up-to-date kernels with updated jdk. -- Mathieu Arnold