From owner-freebsd-ports Wed Mar 12 9:58:49 2003 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 C1CDB37B401 for ; Wed, 12 Mar 2003 09:58:48 -0800 (PST) Received: from phobos.raisdorf.net (phobos.raisdorf.net [195.244.235.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id B388743F3F for ; Wed, 12 Mar 2003 09:58:45 -0800 (PST) (envelope-from hscholz@raisdorf.net) Received: by phobos.raisdorf.net (Postfix, from userid 66) id 9E91023845; Wed, 12 Mar 2003 18:00:07 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by platypus.lan.raisdorf.net (Postfix) with ESMTP id 6559E5C37; Wed, 12 Mar 2003 17:37:41 +0100 (CET) Received: from platypus.lan.raisdorf.net ([127.0.0.1]) by localhost (platypus.lan.raisdorf.net [127.0.0.1:10024]) (amavisd-new) with ESMTP id 48632-06; Wed, 12 Mar 2003 17:37:39 +0100 (CET) Received: from goanna.lan.raisdorf.net (goanna.lan.raisdorf.net [10.10.1.2]) by platypus.lan.raisdorf.net (Postfix) with SMTP id BEC975C17; Wed, 12 Mar 2003 17:37:39 +0100 (CET) Date: Wed, 12 Mar 2003 17:31:01 +0100 From: Hendrik Scholz To: "William N. Culler Jr." Cc: ports@FreeBSD.org Subject: Re: Seahorse 0.7.1 build freeze Message-Id: <20030312173101.52e35303.hscholz@raisdorf.net> In-Reply-To: <20030312100119.4f5cb0d8.william@neo.rr.com> References: <20030312100119.4f5cb0d8.william@neo.rr.com> Reply-To: hendrik@scholz.net X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! On Wed, 12 Mar 2003 10:01:19 -0500 "William N. Culler Jr." wrote: > It just stops right here. I have had this problem since the upgraded > version of Seahorse was submitted. I have been checking the mailing > lists everyday, but I haven't seen anyone else say anthing about it > so, I might be the only one it is happening to. I am just wondering > if there is anything I can do to get past it. I don't have a solution (yet) but alteast I can confirm the problem. Same problem here on -current with recent ports. Hendrik -- Hendrik Scholz - - http://raisdorf.net/ Chemnitzer Linuxdays OS Fingerprinting slides are available on website! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message