Date: Wed, 8 Apr 2009 07:35:40 -0700 From: Kent Stewart <kstewart@owt.com> To: freebsd-ports@freebsd.org, utisoft@gmail.com Subject: Re: Portupgrade still broken? Message-ID: <200904080735.40746.kstewart@owt.com> In-Reply-To: <b79ecaef0904080551x74c80227h1a4ba5d2adcca905@mail.gmail.com> References: <b79ecaef0904080551x74c80227h1a4ba5d2adcca905@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :( > > [chris@amnesiac]/usr/ports/ports-mgmt/portupgrade% portupgrade --version > portupgrade 2.4.6 > > Is this a 'fixed' version, or not? I think it's the most recent... > > [chris@amnesiac]/usr/ports/ports-mgmt/portupgrade% sudo portupgrade > -rR emacs xterm curl php5-mbstring > otp-md5 488 am9338 ext > Password: > [Updating the pkgdb <format:bdb_btree> in /var/db/pkg ... - 263 > packages found (-3 +3) (...)... done] > [Gathering depends for editors/emacs > ........................................................................... >............................................................................ >............................................................................ >.................................................................... done] > [Exclude up-to-date packages > ........................................................................... >............ done] > /usr/local/lib/ruby/site_ruby/1.8/pkginfo.rb:74:in `initialize': : Not > in due form: <name>-<version> (ArgumentError) > from /usr/local/sbin/portupgrade:614:in `new' > from /usr/local/sbin/portupgrade:614:in `main' > from /usr/local/sbin/portupgrade:613:in `each' > from /usr/local/sbin/portupgrade:613:in `main' > from /usr/local/sbin/portupgrade:588:in `catch' > from /usr/local/sbin/portupgrade:588:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:1305:in `call' > from /usr/local/lib/ruby/1.8/optparse.rb:1305:in `parse_in_order' > from /usr/local/lib/ruby/1.8/optparse.rb:1301:in `catch' > from /usr/local/lib/ruby/1.8/optparse.rb:1301:in `parse_in_order' > from /usr/local/lib/ruby/1.8/optparse.rb:1249:in `catch' > from /usr/local/lib/ruby/1.8/optparse.rb:1249:in `parse_in_order' > from /usr/local/lib/ruby/1.8/optparse.rb:1243:in `order!' > from /usr/local/lib/ruby/1.8/optparse.rb:1236:in `order' > from /usr/local/sbin/portupgrade:565:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:787:in `initialize' > from /usr/local/sbin/portupgrade:229:in `new' > from /usr/local/sbin/portupgrade:229:in `main' > from /usr/local/sbin/portupgrade:2208 > > > > > 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 > > Chris -- 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?200904080735.40746.kstewart>