From owner-freebsd-ports@FreeBSD.ORG Thu Apr 14 05:24:25 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5188D16A4CE for ; Thu, 14 Apr 2005 05:24:25 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 184B643D4C for ; Thu, 14 Apr 2005 05:24:25 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id BA4A614952; Thu, 14 Apr 2005 00:24:24 -0500 (CDT) Date: Thu, 14 Apr 2005 00:24:24 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: Joel Hatton In-Reply-To: <425DF4F6.2000708@its.uq.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: ports@FreeBSD.org Subject: Re: index generation error X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Apr 2005 05:24:25 -0000 On Thu, 14 Apr 2005, Joel Hatton wrote: > I've had an index generation error for a couple of days. I'm running > the standard supfile for ports, and cvsup'ing from a local mirror. If that's the case, you almost surely want to run 'make fetchindex' which will fetch a copy of /usr/ports/INDEX that will reflect the latest metadata for ports. It is continually updated. Since we went to that technology a few months ago, it obviated the need for most people to build their own copies of INDEX. (Exceptions include people that use non-default site options that change the dependencies, and sites that refuse any port or category.) There is a little bit of cvsup magic that is (or was) necessary to avoid the INDEX file automatically being deleted on updates. Please see /usr/ports/UPDATING for more information about all of this. mcl