From owner-freebsd-ports@FreeBSD.ORG Wed May 6 17:35:03 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BBC2106564A for ; Wed, 6 May 2009 17:35:03 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from QMTA05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [76.96.62.48]) by mx1.freebsd.org (Postfix) with ESMTP id B23518FC0A for ; Wed, 6 May 2009 17:35:02 +0000 (UTC) (envelope-from corky1951@comcast.net) Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA05.westchester.pa.mail.comcast.net with comcast id oEpm1b0071HzFnQ55HMiCk; Wed, 06 May 2009 17:21:42 +0000 Received: from comcast.net ([98.203.142.76]) by OMTA14.westchester.pa.mail.comcast.net with comcast id oHMg1b0191f6R9u3aHMhKJ; Wed, 06 May 2009 17:21:42 +0000 Received: by comcast.net (sSMTP sendmail emulation); Wed, 06 May 2009 10:21:39 -0700 Date: Wed, 6 May 2009 10:21:39 -0700 From: Charlie Kester To: freebsd-ports@freebsd.org Message-ID: <20090506172138.GA54310@comcast.net> Mail-Followup-To: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Mailer: Mutt 1.5.x X-Composer: VIM 7.2 User-Agent: Mutt/1.5.18 (2008-05-17) Subject: why does portsmon think my port is no longer valid? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2009 17:35:03 -0000 http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=ncdu The portsmon page for one of the ports I maintain says it is no longer a valid port. "sysutils/ncdu is no longer a valid port: (deleted but missing from /usr/ports/MOVED)" I recently submitted an update for ncdu 1.5, and it is now in the ports tree and installs without any problem. Does the portsmon statement simply mean that it hasn't been packaged yet, or is there some other issue that needs to be addressed?