Date: Thu, 25 Mar 2004 06:23:47 -0800 From: Kent Stewart <kstewart@owt.com> To: freebsd-ports@freebsd.org Cc: freebsd-questions@freebsd.org Subject: Re: Probelms and Inconsistencies with Portupgrade Message-ID: <200403250623.47386.kstewart@owt.com> In-Reply-To: <4062AA80.9020104@aeefyu.net> References: <4060F9C0.5080102@aeefyu.net> <200403251905.04769.anubis357@optusnet.com.au> <4062AA80.9020104@aeefyu.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403250623.47386.kstewart>