From owner-freebsd-ports@FreeBSD.ORG Wed Apr 8 14:54:42 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 EB2BA106566B for ; Wed, 8 Apr 2009 14:54:41 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [64.146.239.50]) by mx1.freebsd.org (Postfix) with ESMTP id 754708FC16 for ; Wed, 8 Apr 2009 14:54:41 +0000 (UTC) (envelope-from kstewart@owt.com) Received: from kstewart2.owt.com (kstewart2.owt.com [64.146.237.228]) (authenticated bits=0) by smtp.owt.com (8.13.8/8.13.8) with ESMTP id n38EZfXI017650; Wed, 8 Apr 2009 07:35:41 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=owt.com; s=default; t=1239201342; bh=Vj81XSXL+JqFFSc3KniBbFUUhyUg+Er2tR1pgt4lur0=; h=From:To:Subject:Date:References:In-Reply-To:MIME-Version: Content-Type:Content-Transfer-Encoding:Message-Id; b=GCVS34wD1y159 vg3TxnUjmIR6Mw7fwFfQRcU+w9w7h67MfzEK79CkPXBMVEiXlkAhZDBm9lw9BpYVcD/ tkS6VSvhYHPKmhObtAqq5/OvTc5IUsXwtXGxygXvijrHma79lYvNBCAF4JKe+750cC6 lLS1uBhzTMigasQfH58VkYwI= From: Kent Stewart To: freebsd-ports@freebsd.org, utisoft@gmail.com Date: Wed, 8 Apr 2009 07:35:40 -0700 User-Agent: KMail/1.9.10 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904080735.40746.kstewart@owt.com> Cc: 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: Wed, 08 Apr 2009 14:54:42 -0000 On Wednesday 08 April 2009 05:51:48 am Chris Rees wrote: > Dear all on freebsd-ports@, > > 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% portupgrade --version > portupgrade 2.4.6 > > Is this a 'fixed' version, or not? I think it's the most recent... > > [chris@amnesiac]/usr/ports/ports-mgmt/portupgrade% sudo portupgrade > -rR emacs xterm curl php5-mbstring > otp-md5 488 am9338 ext > Password: > [Updating the pkgdb in /var/db/pkg ... - 263 > packages found (-3 +3) (...)... done] > [Gathering depends for editors/emacs > ........................................................................... >............................................................................ >............................................................................ >.................................................................... done] > [Exclude up-to-date packages > ........................................................................... >............ done] > /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' > from /usr/local/sbin/portupgrade:613:in `each' > from /usr/local/sbin/portupgrade:613:in `main' > from /usr/local/sbin/portupgrade:588:in `catch' > from /usr/local/sbin/portupgrade:588:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:1305:in `call' > from /usr/local/lib/ruby/1.8/optparse.rb:1305:in `parse_in_order' > from /usr/local/lib/ruby/1.8/optparse.rb:1301:in `catch' > from /usr/local/lib/ruby/1.8/optparse.rb:1301:in `parse_in_order' > from /usr/local/lib/ruby/1.8/optparse.rb:1249:in `catch' > from /usr/local/lib/ruby/1.8/optparse.rb:1249:in `parse_in_order' > from /usr/local/lib/ruby/1.8/optparse.rb:1243:in `order!' > from /usr/local/lib/ruby/1.8/optparse.rb:1236:in `order' > from /usr/local/sbin/portupgrade:565:in `main' > from /usr/local/lib/ruby/1.8/optparse.rb:787:in `initialize' > from /usr/local/sbin/portupgrade:229:in `new' > from /usr/local/sbin/portupgrade:229:in `main' > from /usr/local/sbin/portupgrade:2208 > > > > > Is the bug still there, or is my pkgdb hosed? If so, how do I fix it? I still get the optparse.rb:787:in stop. It seems to happen quicker, when you have a larger number of ports in the rR tree. I hadn't updated my ports since 4 Apr. I did a cvsup update and and checked to see how many needed updating. There were 15 ports. I then did a "portupgrade -rRp libxcb" and it died fairly quickly. Libxcb on my system, has 173 ports that depend on it. I find that "portupgrade -pa" works for me. Kent > > Chris -- kent Stewart Richland, WA http://users.owt.com/kstewart/index.html