From owner-freebsd-ports@FreeBSD.ORG Tue Oct 7 21:30:09 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 131E9106564A for ; Tue, 7 Oct 2008 21:30:09 +0000 (UTC) (envelope-from tingox@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id BB3048FC13 for ; Tue, 7 Oct 2008 21:30:08 +0000 (UTC) (envelope-from tingox@gmail.com) Received: by qw-out-2122.google.com with SMTP id 9so855215qwb.7 for ; Tue, 07 Oct 2008 14:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=x5Tnywj5ot5Qz7hFkPHH26B3x7sGCfmauqOVLgh9v9A=; b=QL5bDpa6KEEOhATDLrq1fyKyn9NjV3FCHBZHryReGBf3lhXtp35SF2TIaaly86x/ua h8njrVQ/LQu1gNY03alKfw2xW5k03x6SeQIKwSnwPRlUJUYQhA93jCv6U3cmTOm+KvmU VtvtoRkoDP81Z/VRFW58XNBHJH7tHNWy1SEkE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qokJdd24+QnjQdpobeTlVwCyzH7cd1N82/TE+2d2CUTjSSBJAT9OuhdaKoAB0fL3O9 erAjIgqp5CsHJeJLMpLRM0kK8fPO5UIKeohPV3/Xt4DkfRBDxtKAoDVK7SaAklad1VnM Vy+U2wGMYH61lq02tsMQWEtc0FX6NsODplmas= Received: by 10.214.43.18 with SMTP id q18mr8956545qaq.12.1223415006968; Tue, 07 Oct 2008 14:30:06 -0700 (PDT) Received: by 10.214.25.9 with HTTP; Tue, 7 Oct 2008 14:30:06 -0700 (PDT) Message-ID: Date: Tue, 7 Oct 2008 23:30:06 +0200 From: "Torfinn Ingolfsen" To: freebsd-ports@freebsd.org In-Reply-To: <20081007082129.GA32825@holstein.holy.cow> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081007082129.GA32825@holstein.holy.cow> 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 21:30:09 -0000 Hello, On Tue, Oct 7, 2008 at 10:21 AM, Parv wrote: > Is your version of portupgrade is the latest in the ports? (So that > I can install the same & investigate.) Yes - always. I think I even stated in my first message that the ports tree was updated. >> 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 ... You mean with the version numbers? Any port names listed above or in my initial message re non-ambiguous. FWIW, I use /bin/sh as myt shell. Always. > 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. It might be, but where does it encounter that problem? I have done 'pkgdb -F' - it didn't find any problems. And why doesn't portupgrade find the same problem with any individual port when I try portupgrade on them one-by-one? > If portupgrade is indeed successful individually for all the above > listed ports, then the second scenario is more likely (the "non-port > thing" one). Well, I can't understand where portupgrade picks up that from, unless there is a flaw / error in portupgrade itself. I am a quite experienced user of portupgrade (I have used it for many years), so let me put a few notes here: 1) ambiguous names - if given, portupgrade will ask which ones you want (eg. 'firefox') 2) non-existent names - portupgrade will skip those, like so: root@kg-quiet# portupgrade -R nonexistant [Exclude up-to-date packages done] 3) portupgrade used to have no problems with the way I am using it, ie. portupgrade -R port1 port2 port3 port4 ... Hope this helps. -- Regards, Torfinn Ingolfsen