Portupgrade still broken?

[Chris Rees]

2009/4/8 Kent Stewart <kstewart at owt.com>:
> On Wednesday 08 April 2009 05:51:48 am Chris Rees wrote:
>> Dear all on freebsd-ports@,
>>
>> I recall from
>> http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html
>> that there was a bug in portupgrade last year, causing it to break when a
>> port is recursively (-R) upgraded; it's surfacing for me too :(
>>
>> Is the bug still there, or is my pkgdb hosed? If so, how do I fix it?
>
> I still get the optparse.rb:787:in stop. It seems to happen quicker, when you
> have a larger number of ports in the rR tree. I hadn't updated my ports since
> 4 Apr. I did a cvsup update and and checked to see how many needed updating.
> There were 15 ports. I then did a "portupgrade -rRp libxcb" and it died
> fairly quickly. Libxcb on my system, has 173 ports that depend on it.
>
> I find that "portupgrade -pa" works for me.
>
> Kent

That's a bugger, I may check out portmaster. Thanks for all the replies.

Chris

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?