Date: Wed, 8 Apr 2009 13:51:48 +0100 From: Chris Rees <utisoft@googlemail.com> To: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Portupgrade still broken? Message-ID: <b79ecaef0904080551x74c80227h1a4ba5d2adcca905@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Dear all on freebsd-ports@, I recall from http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/0= 47319.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? Chris --=20 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b79ecaef0904080551x74c80227h1a4ba5d2adcca905>