From owner-freebsd-current@FreeBSD.ORG Fri Feb 10 21:43:42 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 ED94416A420 for ; Fri, 10 Feb 2006 21:43:42 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A80A43D55 for ; Fri, 10 Feb 2006 21:43:42 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-71-254-44-94.roa.east.verizon.net [71.254.44.94]) by gromit.dlib.vt.edu (8.13.4/8.13.4) with ESMTP id k1ALheVA014212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 10 Feb 2006 16:43:41 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.4/8.13.4) with ESMTP id k1ALhY0L027293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 10 Feb 2006 16:43:35 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.4/8.13.4/Submit) id k1ALhYvw027292 for freebsd-current@freebsd.org; Fri, 10 Feb 2006 16:43:34 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) From: Paul Mather To: freebsd-current@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Fri, 10 Feb 2006 16:43:33 -0500 Message-Id: <1139607813.23382.20.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Subject: 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 21:43:43 -0000 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. :-) This is the version of portsnap I'm using: $FreeBSD: src/usr.sbin/portsnap/portsnap/portsnap.sh,v 1.14 2006/01/22 23:48:0 7 cperciva Exp $ My version of CURRENT is FreeBSD 7.0-CURRENT #0: Thu Feb 9 10:59:56 EST 2006. Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa