From owner-freebsd-ports-bugs@FreeBSD.ORG Mon Dec 20 07:59:40 2004 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1887C16A4CE for ; Mon, 20 Dec 2004 07:59:40 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D4C243D53 for ; Mon, 20 Dec 2004 07:59:39 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id E8D0B20F75 for ; Mon, 20 Dec 2004 08:59:37 +0100 (CET) Received: by taz.hsc.fr (Postfix, from userid 1001) id B250D4552; Mon, 20 Dec 2004 15:59:41 +0800 (SGT) Date: Mon, 20 Dec 2004 15:59:41 +0800 From: Yann Berthier To: freebsd-ports-bugs@FreeBSD.org Message-ID: <20041220075941.GB711@hsc.fr> Mail-Followup-To: freebsd-ports-bugs@FreeBSD.org References: <200411091520.iA9FKLOn076263@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411091520.iA9FKLOn076263@freefall.freebsd.org> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 6.0-CURRENT User-Agent: Mutt/1.5.6i Subject: Re: ports/73688: net/netdude: port does not compile X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Dec 2004 07:59:40 -0000 On Tue, 09 Nov 2004, Volker Stolz wrote: > The following reply was made to PR ports/73688; it has been noted by GNATS. > > From: "Volker Stolz" > To: freebsd-gnats-submit@freebsd.org, vman@tmok.com, > yb@sainte-barbe.org > Cc: > Subject: Re: ports/73688: net/netdude: port does not compile > Date: Tue, 09 Nov 2004 16:17:38 +0100 > > Dear maintainer, please look into this issue! Bento and I failed to reproduce the build error, and the PR originator didn't replied to my inquiries, so I think you can close this PR Thanks, - yann