portupgrade fails - how to fix?
Janky Jay, III
jankyj at unfs.us
Tue Oct 7 19:29:27 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
Not sure how well this work as a 'workaround', but, being as I use ZSH
as my shell, I always wrap anything I'm specifically upgrading using
portupgrade with single quotes. IE:
portupgrade -rR 'some-port-2.4.1_1' 'some-other-port-1.0.5_1,3'
I haven't had any issues with this at all. Can anyone confirm if
specifying the complete port name wrapped in single quotes allows
portupgrade to finish successfully?
Janky Jay, III
Rainer Hurling wrote:
> 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 <ef8c8a880810070007g41b4a639h8e1ed673e0da67ba at mail.gmail.com>,
>> 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.)
>>> root at kg-work2# portupgrade -R nasm pcre xterm mplayer gscan2pdf
>> What are the exact names of the ports|packages installed? Many ways
>> to list; here is a simple one ...
>> 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.
>>> As always, a single port as the argument to portupgrade doesn't
>> 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 at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the freebsd-ports