From owner-freebsd-ports@FreeBSD.ORG Thu Dec 17 04:14:44 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 9FA361065670 for ; Thu, 17 Dec 2009 04:14:44 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 5B59B8FC08 for ; Thu, 17 Dec 2009 04:14:44 +0000 (UTC) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 16 Dec 2009 23:14:43 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.10.7-GA) with ESMTP id LHS52582; Wed, 16 Dec 2009 23:13:36 -0500 (EST) Received: from 209-6-91-204.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.91.204]) by smtp01.lnh.mail.rcn.net with ESMTP; 16 Dec 2009 23:13:37 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19241.45040.505925.616766@jerusalem.litteratus.org> Date: Wed, 16 Dec 2009 23:13:36 -0500 To: Kevin In-Reply-To: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> References: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Cc: freebsd-ports@freebsd.org Subject: portupgrade failure 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: Thu, 17 Dec 2009 04:14:44 -0000 Kevin writes: > I've been having this problem for a couple of months now, but I > just recently decided to try to fix it. I'm running FreeBSD 6.4, > and if I try to use portupgrade to upgrade something, I get an > error (seems to be the same for other ports): portupgrade (and -devel) have been broken, as you say, for several months. The maintainer, ruby@, is aware of this; a check of the PR database shows multiple open PRs, none critical but many serious going back six months and more. (see: "http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports&severity=&priority=&class=&state=&sort=none&text=portupgrade&responsible=&multitext=&originator=&release=" This hard to understand given portupgrade is the recommended upgrade tool. Robert Huff