From owner-freebsd-ports@FreeBSD.ORG Sun Jul 24 19:37:28 2005 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6905C16A41F; Sun, 24 Jul 2005 19:37:28 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2726F43D45; Sun, 24 Jul 2005 19:37:27 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 1493229B1; Sun, 24 Jul 2005 14:37:26 -0500 (CDT) Date: Sun, 24 Jul 2005 14:37:26 -0500 To: Tobias Roth Message-ID: <20050724193726.GA11019@soaustin.net> References: <17123.1272.243457.460650@bhuda.mired.org> <20050724032900.GA24567@xor.obsecurity.org> <17123.44634.790191.549056@bhuda.mired.org> <20050724155225.GA10448@soaustin.net> <20050724184444.GA2527@droopy.unibe.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050724184444.GA2527@droopy.unibe.ch> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: ports@freebsd.org, Mark Linimon , Kris Kennaway , Mike Meyer , sem@freebsd.org Subject: Re: Recursive dependency? 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: Sun, 24 Jul 2005 19:37:28 -0000 On Sun, Jul 24, 2005 at 08:44:44PM +0200, Tobias Roth wrote: > > So does this mean that 37596 needs to be reopened? Sem? > > 'Someone' was me, and I can confirm that 37596 still is a problem > as of today with -STABLE. That's why I pointed Mike to it and asked > him to keep sem@ in the loop. OK, as bugmeister I'm going to reopen it and mark it as 'suspended' while the fix is being worked on, because it's my belief that that's the way it should have been set in the first place. I'm quite aggressive in closing PRs ... when it's clear the problem has been fixed or the circumstances no longer relevant, but that doesn't sound like the case here. mcl