After cvsup of ports tree to get updated portupgrade with maintainer's "quick fix", portupgrade is still unable to portupgrade other ports. New errors reported are as follows: # portupgrade -R aspell-0.50.5_2 /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 # Fix: Don't know How-To-Repeat: Cvsup ports tree to latest Portupgrade portupgrade Attempt to use portupgrade to update another port
Responsible Changed From-To: freebsd-ports-bugs->knu Over to maintainer
Is there any problems with the latest portupgrade?
Hi, ----- Original Message ----- From: "kuriyama@freebsd.org" To: To freebsd-gnats-submit@freebsd.org Date: Tue, 10 Aug, 2004 03:02 BST Subject: Re: ports/68191: Maintainer's Quick Fix to portupgrade introduces new error when using portupgrade [WAS: ports/681 > Is there any problems with the latest portupgrade? No, all's fine at present. Regards, Stacey
State Changed From-To: open->closed Submitter reported that problem seemed to be fixed at now.