From owner-freebsd-ports@FreeBSD.ORG Tue May 12 20:48:49 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 E621A1065670 for ; Tue, 12 May 2009 20:48:49 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id C970B8FC15 for ; Tue, 12 May 2009 20:48:49 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 855998C063; Tue, 12 May 2009 15:48:49 -0500 (CDT) Date: Tue, 12 May 2009 15:48:49 -0500 From: Mark Linimon To: freebsd-ports@freebsd.org Message-ID: <20090512204849.GA30745@lonesome.com> References: <20090506172138.GA54310@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090506172138.GA54310@comcast.net> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: why does portsmon think my port is no longer valid? 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: Tue, 12 May 2009 20:48:50 -0000 On Wed, May 06, 2009 at 10:21:39AM -0700, Charlie Kester wrote: > Does the portsmon statement simply mean that it hasn't been packaged > yet, or is there some other issue that needs to be addressed? The latter (a bug in portsmon :-) ) There is some leakage of things that come and go in MOVED. Doing a manual rescan of ports/MOVED fixes the problem ... then it recurs. One of these days I'm going to fix that ... mcl