Probelms and Inconsistencies with Portupgrade

Kent Stewart kstewart at
Thu Mar 25 06:24:01 PST 2004

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

What do you see? There aren't many things that would create a broken 


Kent Stewart
Richland, WA

More information about the freebsd-ports mailing list