Date: Tue, 07 Oct 2008 13:12:07 -0600 From: "Janky Jay, III" <jankyj@unfs.us> To: freebsd-ports@freebsd.org Subject: Re: portupgrade fails - how to fix? Message-ID: <48EBB487.3090706@unfs.us> In-Reply-To: <48EB6635.6040707@gwdg.de> References: <ef8c8a880810041600w5cc10e25ne314d4671cc309ee@mail.gmail.com> <ef8c8a880810070007g41b4a639h8e1ed673e0da67ba@mail.gmail.com> <20081007082129.GA32825@holstein.holy.cow> <48EB6635.6040707@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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? Regards, 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@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@kg-work2# 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 "freebsd-ports-unsubscribe@freebsd.org" > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFI67SGGK3MsUbJZn4RAjNYAJ0ZNy67xbtOLr5z2RI9LewLWHH8fQCeKMeH uptpup+aiMAI+qXqjiDfhsw= =+MDn -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48EBB487.3090706>