From owner-freebsd-current@FreeBSD.ORG Fri Feb 10 22:27:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E704A16A420 for ; Fri, 10 Feb 2006 22:27:35 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from ms-smtp-01.rdc-nyc.rr.com (ms-smtp-01-smtplb.rdc-nyc.rr.com [24.29.109.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82D0743D45 for ; Fri, 10 Feb 2006 22:27:35 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-01.rdc-nyc.rr.com (8.13.4/8.13.4) with ESMTP id k1AMPs6Y000384 for ; Fri, 10 Feb 2006 17:25:55 -0500 (EST) Received: by mail.scottro.net (Postfix, from userid 1001) id BCB535C34; Fri, 10 Feb 2006 17:27:33 -0500 (EST) Date: Fri, 10 Feb 2006 17:27:33 -0500 From: Scott Robbins To: freebsd-current@freebsd.org Message-ID: <20060210222733.GA70832@mail.scottro.net> Mail-Followup-To: freebsd-current@freebsd.org References: <1139607813.23382.20.camel@zappa.Chelsea-Ct.Org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <1139607813.23382.20.camel@zappa.Chelsea-Ct.Org> User-Agent: mutt-ng/devel-r581 (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: Portsnap support on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2006 22:27:36 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Feb 10, 2006 at 04:43:33PM -0500, Paul Mather wrote: > I've noticed lately a lot of "succeeds port" messages when I run > portversion (from the portupgrade port) to list which of my packages are > out of date and require updating. These messages are incorrect (i.e., > the "port has" version identified by portversion is older than that in > the actual port Makefile), and I don't get incorrect identifications > from either pkg_version or portmanager. (I also don't get this problem > on a RELENG_6 system I have, either.) > > After a little looking, I discovered that my /usr/ports/INDEX-7 file is > not being updated. Investigation of the portsnap source reveals that it > only actually generates INDEX, INDEX-5, and INDEX-6 from portsnap > updates in extract_indices(); it doesn't generate INDEX-7. > > So, is /usr/sbin/portsnap currently supported on CURRENT? It appears to > keep /usr/ports up to date, just not the index file. For now, I've > switched to using sysutils/portmanager from ports for upgrading ports, > but I'm not entirely happy with that for a variety of reasons. Plus, > some /usr/ports/UPDATING instructions advocate using portupgrade > explicitly, so it would be nice to have portupgrade working fully. :-) > I had the same problem (on CURRENT, with 6.x working perfectly.) Like you I tracked it down to the INDEX file not being updated. My temporary hack is to simply rn pkgdb -Fu (hrm, who thought of those flags?) :) before running portversion. - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Drusilla: Your face is a poem. I can read it. Xander: It doesn't say 'spare me' by any chance? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD7RNV+lTVdes0Z9YRAut+AJ9DHw6gITkhvEFcaMIuQwBUmSiYzACghlWG ya2mwldzlGpP0Eq2XUxQXVU= =9/Uh -----END PGP SIGNATURE-----