I have the same trouble with portupgrade some times:
Am 07.10.2008 10:21 (UTC+1) schrieb Parv:
Mind that I am looking at the problem purely from a programmer's
perspective. I am a rather light user of portupgrade (mainly "pkgbd
-F") & don't upgrade the port itself much.
With that out of the way ...
in message <[EMAIL PROTECTED]>,
wrote Torfinn Ingolfsen thusly...
And here portupgrade fails again, on another machine:
Is your version of portupgrade is the latest in the ports? (So that
I can install the same & investigate.)
[EMAIL PROTECTED] portupgrade -R nasm pcre xterm mplayer gscan2pdf ImageMagick
What are the exact names of the ports|packages installed? Many ways
to list; here is a simple one ...
sh
pkg_info -Qox nasm pcre xterm mplayer gscan2pdf ImageMagick \
| sed -e 's/:/ /'
# Type exit to exit /bin/sh session; missing here as it might
# actually exit your actual shell session.
/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'
Seems like portupgrade is dying when a port name-version format does
not match the expected regular expression. Or, the program
encounters a non-port string.
I think, Parv is right here. For example in some cases portupgrade
fails, when the port name is not clear enough. I just saw that
'portupgrade -R gimp' failed, when there are 'gimp-app' and 'gimp'
installed and portupgrade had to find the right port.
Rainer
As always, a single port as the argument to portupgrade doesn't
fail.
If portupgrade is indeed successful individually for all the above
listed ports, then the second scenario is more likely (the "non-port
thing" one).
- Parv
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
