From owner-freebsd-questions@FreeBSD.ORG Thu Mar 25 06:24:01 2004 Return-Path: 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 724CA16A4CE; Thu, 25 Mar 2004 06:24:01 -0800 (PST) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id E65E143D1D; Thu, 25 Mar 2004 06:24:00 -0800 (PST) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i2PEN68a030132; Thu, 25 Mar 2004 06:23:08 -0800 From: Kent Stewart To: freebsd-ports@freebsd.org Date: Thu, 25 Mar 2004 06:23:47 -0800 User-Agent: KMail/1.6.1 References: <4060F9C0.5080102@aeefyu.net> <200403251905.04769.anubis357@optusnet.com.au> <4062AA80.9020104@aeefyu.net> In-Reply-To: <4062AA80.9020104@aeefyu.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200403250623.47386.kstewart@owt.com> cc: Aeefyu cc: freebsd-questions@freebsd.org Subject: Re: Probelms and Inconsistencies with Portupgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2004 14:24:01 -0000 On Thursday 25 March 2004 01:46 am, Aeefyu wrote: > anubis wrote: > >>My problems surfaced when I updated Portupgrade with reference to > >>item 20040226 in /usr/ports/UPDATING (though I suspect this is just > >>a catalyst -- actual problem lies elsewhere) > > > > I had a similar problem. I saw another thread where they suggested > > getting rid of your refuse file, cvsup the ports tree again then > > portsdb -uU > > Worked for me. No more errors. > > The cvsup refuse file would be manually generated *ignored ports > directory, right? Unless cvsup (from ports) comes with a default > refuse file, I dont have any. Then it has to be something like your path provides access to the wrong make or something like that. For example, # which make /usr/bin/make What do you see? There aren't many things that would create a broken INDEX. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html