From owner-freebsd-ports@FreeBSD.ORG Fri Apr 10 12:57:12 2009 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 56164106564A for ; Fri, 10 Apr 2009 12:57:12 +0000 (UTC) (envelope-from parv@pair.com) Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.124]) by mx1.freebsd.org (Postfix) with ESMTP id 105CA8FC3B for ; Fri, 10 Apr 2009 12:57:11 +0000 (UTC) (envelope-from parv@pair.com) Received: from localhost.hawaii.res.rr.com ([72.130.250.168]) by hrndva-omta04.mail.rr.com with ESMTP id <20090410125711.EZAE19377.hrndva-omta04.mail.rr.com@localhost.hawaii.res.rr.com>; Fri, 10 Apr 2009 12:57:11 +0000 Received: from holstein.holy.cow (localhost [127.0.0.1]) by localhost.hawaii.res.rr.com (Postfix) with ESMTP id 4F2D532B0; Fri, 10 Apr 2009 02:57:34 -1000 (HST) Received: (from parv@localhost) by holstein.holy.cow (8.13.8/8.13.8/Submit) id n3ACvXRs003978; Fri, 10 Apr 2009 02:57:33 -1000 (HST) (envelope-from parv@pair.com) X-Authentication-Warning: holstein.holy.cow: parv set sender to parv@pair.com using -f Date: Fri, 10 Apr 2009 02:57:33 -1000 From: parv@pair.com To: utisoft@gmail.com Message-ID: <20090410125733.GA3645@holstein.holy.cow> Mail-Followup-To: utisoft@gmail.com, FreeBSD Mailing List References: <20090409163749.GA6149@holstein.holy.cow> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: FreeBSD Mailing List Subject: Re: Portupgrade still broken? 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: Fri, 10 Apr 2009 12:57:13 -0000 in message , wrote Chris Rees thusly... > > 2009/4/9 Parv : > > in message , > > wrote Chris Rees thusly... > >> > >> I recall from http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/047319.html > >> that there was a bug in portupgrade last year, causing it to break > >> when a port is recursively (-R) upgraded; it's surfacing for me > >> too :( ... > >> [chris@amnesiac]/usr/ports/ports-mgmt/portupgrade% sudo portupgrade > >> -rR emacs xterm curl php5-mbstring > >> otp-md5 488 am9338 ext ... > >> /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' > >> from /usr/local/sbin/portupgrade:614:in `main' ... > > Does this Perl (5.8 & onwards) program ... > > > > http://www103.pair.com/parv/comp/src/perl/check-portupgrade-00 > > > > > > ... produces anything when run *without any arguments*? > > > > Purpose of the program is to find a port name (based on directory > > name in /var/db/pkg) which fails to match the regular expression > > /^(.+)-([^-]+)$/ used in pkginfo.rb, among other files of > > portupgrade. ... > No, sorry, no messages :( Thank you Chris & Kent. No output means that all the port names (based on directory names) match the expected format in pkginfo.rb which tries to parse the names. So that implies that whatever name is being sent to pkginfo.rb is not really a port name per expectation. Internal API seemed to have changed (since whenever), but somebody failed to update the name parsing code, and/or to generate the complete name from partial name before passing it to port name-version parsing code. What was the last working version? It would be simpler for this Ruby simpleton to generate a patch than to debug through the stack trace. - Parv --