From owner-freebsd-ports@FreeBSD.ORG Tue Oct 7 14:25:50 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC10C1065686 for ; Tue, 7 Oct 2008 14:25:50 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id 5D7DD8FC19 for ; Tue, 7 Oct 2008 14:25:50 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from wald.nfv.gwdg.de ([134.76.242.31] helo=pc028.nfv) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1KnClE-0000FJ-UQ; Tue, 07 Oct 2008 15:38:01 +0200 Message-ID: <48EB6635.6040707@gwdg.de> Date: Tue, 07 Oct 2008 15:37:57 +0200 From: Rainer Hurling User-Agent: Thunderbird 2.0.0.17 (X11/20080929) MIME-Version: 1.0 To: parv@pair.com References: <20081007082129.GA32825@holstein.holy.cow> In-Reply-To: <20081007082129.GA32825@holstein.holy.cow> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie Cc: Torfinn Ingolfsen , freebsd-ports@freebsd.org Subject: Re: portupgrade fails - how to fix? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Oct 2008 14:25:50 -0000 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 , > 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: - (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