From owner-freebsd-ports@FreeBSD.ORG Mon Jun 7 09:04:04 2004 Return-Path: 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 2019E16A562; Mon, 7 Jun 2004 09:04:04 +0000 (GMT) Received: from cicero1.cybercity.dk (cicero1.cybercity.dk [212.242.40.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D00DD43D54; Mon, 7 Jun 2004 09:04:03 +0000 (GMT) (envelope-from lars@thegler.dk) Received: from dask.thegler.dk (port156.ds1-bav.adsl.cybercity.dk [217.157.188.161]) by cicero1.cybercity.dk (Postfix) with ESMTP id 27AB17E2C96; Mon, 7 Jun 2004 11:04:02 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by dask.thegler.dk (Postfix) with ESMTP id 736123EC0; Mon, 7 Jun 2004 11:04:01 +0200 (CEST) Message-ID: <40C42F81.20700@thegler.dk> Date: Mon, 07 Jun 2004 11:04:01 +0200 From: Lars Thegler User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Barbish3@adelphia.net References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org cc: lth@FreeBSD.org Subject: Re: FreeBSD Port: p5-Net-Netmask-1.9011 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 09:04:04 -0000 JJB wrote: > I was running 4.9 stable with what ever perl version that comes with > it, and had done pkg_add -r p5-Net-Netmask and my scripts that use > netmask were working just fine. They are stable and have not been > touched in any way. 6/2/04 I installed 4.10 stable from downloaded > cdrom1.iso file and redid pkg_add -r p5-Net-Netmask, that is when > I reported the original problem about the error message warning. > After receiving your email that you had fixed the problem I checked > and saw the package was not updated so today I installed the port > version and now I am getting the "could not parse" message. Could you specify exactly the circumstances and actual output of this, and do a send-pr(1), please. That way we can track the issue much better. /Lars