From owner-freebsd-questions@FreeBSD.ORG Tue Oct 18 20:41:50 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E128616A41F for ; Tue, 18 Oct 2005 20:41:50 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail23.sea5.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9087543D45 for ; Tue, 18 Oct 2005 20:41:50 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 15809 invoked from network); 18 Oct 2005 20:41:49 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail23.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 18 Oct 2005 20:41:49 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 8DFDC3E; Tue, 18 Oct 2005 16:41:48 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Rem P Roberti References: <435558E2.1040900@comcast.net> From: Lowell Gilbert Date: 18 Oct 2005 16:41:48 -0400 In-Reply-To: <435558E2.1040900@comcast.net> Message-ID: <44sluyr20j.fsf@be-well.ilk.org> Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: FreeBSD Subject: Re: Portversion question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2005 20:41:51 -0000 Rem P Roberti writes: > I have crontab run cvsup, and make a new port index for me nightly. > This morning I ran portversion -l and found that there was a package > it regarded as not being up to date. However, neither portmanager or > portupgrade picked up the non-current package. Why would portversion > indicate a package that is not up to date, and either of the two > upgrade programs not find it also? A bug? A port that was moved? [see /usr/ports/MOVED] There are probably other possible reasons, but you didn't give us much to go on... -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/