From owner-freebsd-ports@FreeBSD.ORG Fri May 18 21:06:21 2007 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52B6416A400 for ; Fri, 18 May 2007 21:06:21 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 429B113C45B for ; Fri, 18 May 2007 21:06:21 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id CB27B1A3C19 for ; Fri, 18 May 2007 14:07:15 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 65AB3513FC; Fri, 18 May 2007 17:06:20 -0400 (EDT) Date: Fri, 18 May 2007 17:06:20 -0400 From: Kris Kennaway To: Kris Kennaway , ports@FreeBSD.org Message-ID: <20070518210620.GA51371@xor.obsecurity.org> References: <20070510212817.GA67897@xor.obsecurity.org> <20070513192328.GA53744@graf.pompo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070513192328.GA53744@graf.pompo.net> User-Agent: Mutt/1.4.2.2i Cc: Subject: Re: HEADS UP: xorg 7.2 ready for testing X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2007 21:06:21 -0000 On Sun, May 13, 2007 at 09:23:28PM +0200, Thierry Thomas wrote: > Le Jeu 10 mai 07 ? 23:28:17 +0200, Kris Kennaway > ?crivait?: > > > We're asking all FreeBSD ports committers and other interested > > developers to participate in this process: it's now up to you guys to > > test the upgrade and report problems you encounter, before we unleash > > it on the general user base. > > The first part of this upgrade is still going on on this machine where > several heavy ports are installed, and I have got another problem with > JDK-13: for some reason, it seems to be identified as Solaris2, and that > causes problems. This is a known problem for which I think the java maintainers have a fix pending. Kris