Probelms and Inconsistencies with Portupgrade

Aeefyu afu-subscribed-list at
Thu Mar 25 01:47:05 PST 2004

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.

Webcraft Solutions -
You know you've been spending too much time on the computer when your
friend misdates a check, and you suggest adding a "++" to fix it.

More information about the freebsd-ports mailing list