From owner-freebsd-ports@FreeBSD.ORG Wed Apr 8 13:17:04 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 E1E681065674 for ; Wed, 8 Apr 2009 13:17:03 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-ew0-f171.google.com (mail-ew0-f171.google.com [209.85.219.171]) by mx1.freebsd.org (Postfix) with ESMTP id 4AC7A8FC14 for ; Wed, 8 Apr 2009 13:17:03 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by ewy19 with SMTP id 19so122739ewy.43 for ; Wed, 08 Apr 2009 06:17:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=c/J/IWH5UlmImngXUzmP/2awXHd6pPNEOsyX8Zr/u6k=; b=D2Y/tefAKAu8EizdsDtDz9covEfLvTDYSTxpVfa0ZD4g/ReGTodSkzaM+srUOIGbKb fMPvKvU4OGT193mIZEYkjsiFiEZju5S6fToZIOA6KNspDYcQ5rXY5IbW+VclRvhC+X9M SIzdtwMd+9C2kwXhmQTmXqDGhxRQeSjjT07Ug= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=qQmpSRbj5n4NXDDF53u3M3jQlzTWS3eA5lakIq2ce0fh/sfNmpITTMgiLaGUPYKjId fJUFMF9r59s1qcuM4nww9ukyJz1+RurJdEXdZo/gmAwjhLeAb+Rdi4/nHIl1t3Qq4ozW 0sJJBz74HIE3g/leSA2HvNEiOSh2g7QDWzXww= MIME-Version: 1.0 Received: by 10.210.27.20 with SMTP id a20mr1113829eba.81.1239195108788; Wed, 08 Apr 2009 05:51:48 -0700 (PDT) Date: Wed, 8 Apr 2009 13:51:48 +0100 Message-ID: From: Chris Rees To: FreeBSD Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Portupgrade still broken? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2009 13:17:04 -0000 Dear all on freebsd-ports@, I recall from http://lists.freebsd.org/pipermail/freebsd-ports/2008-March/0= 47319.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? Chris --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail?