portupgrade error when using -R
Robert Huff
roberthuff at rcn.com
Tue Jan 20 07:23:50 PST 2009
Christer Solskogen writes:
> ---> Session ended at: Tue, 20 Jan 2009 13:53:33 +0000 (consumed 00:00:17)
> /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:931:in `new'
> from /usr/local/sbin/portupgrade:931:in `do_upgrade'
> from /usr/local/sbin/portupgrade:815:in `main'
> from /usr/local/sbin/portupgrade:811:in `each'
> from /usr/local/sbin/portupgrade:811:in `main'
> from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize'
> from /usr/local/sbin/portupgrade:229:in `new'
> from /usr/local/sbin/portupgrade:229:in `main'
> from /usr/local/sbin/portupgrade:2208
I get this occasionally, and not just on a particular port.
Only specifying the base portname (i.e. "libgtop" instead of
"libgtop-2.24.3" seems to increase the chances - but does not
guerrantee - this will happen.
Robert Huff
More information about the freebsd-ports
mailing list