From owner-freebsd-ports@FreeBSD.ORG Thu Dec 17 09:21:22 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 ABCBA106568B for ; Thu, 17 Dec 2009 09:21:22 +0000 (UTC) (envelope-from jimbo@renner.se) Received: from proxy1.bredband.net (proxy1.bredband.net [195.54.101.71]) by mx1.freebsd.org (Postfix) with ESMTP id 5FCAB8FC12 for ; Thu, 17 Dec 2009 09:21:22 +0000 (UTC) Received: from ipb2.telenor.se (195.54.127.165) by proxy1.bredband.net (7.3.140.3) id 4AD3E1C001C4E6E2 for freebsd-ports@freebsd.org; Thu, 17 Dec 2009 10:21:20 +0100 X-SMTPAUTH-B2: X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAFAMqGKUtT465S/2dsb2JhbACBS9QbhC0E X-IronPort-AV: E=Sophos;i="4.47,411,1257116400"; d="scan'208";a="16732438" Received: from ua-83-227-174-82.cust.bredbandsbolaget.se (HELO renner.se) ([83.227.174.82]) by ipb2.telenor.se with ESMTP; 17 Dec 2009 10:21:20 +0100 Received: from wpad ([127.0.0.1]:53040 helo=localhost) by renner.se with esmtp (Exim 4.71 (FreeBSD)) (envelope-from ) id 1NLCXe-000GkK-Dz for freebsd-ports@freebsd.org; Thu, 17 Dec 2009 10:21:02 +0100 Received: from 192.168.1.42 ([192.168.1.42]) by kilroy (Horde Framework) with HTTP; Thu, 17 Dec 2009 10:21:02 +0100 Message-ID: <20091217102102.15241asjv1rqmqzo@kilroy> Date: Thu, 17 Dec 2009 10:21:02 +0100 From: Jimmy Renner To: freebsd-ports@freebsd.org References: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> <19241.45040.505925.616766@jerusalem.litteratus.org> <20091217052400.GC32037@lonesome.com> In-Reply-To: <20091217052400.GC32037@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3.5) / FreeBSD-7.2 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: jimbo@renner.se X-SA-Exim-Scanned: No (on renner.se); SAEximRunCond expanded to false Subject: Re: 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 09:21:22 -0000 Quoting Mark Linimon : > On Wed, Dec 16, 2009 at 11:13:36PM -0500, Robert Huff wrote: >> 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. > > As an aside, the Severity and Priority fields have been so often abused > as to have become meaningless. Although I still try to groom the db > for "critical" ones, and thus try to get those some attention, I really > don't think the committers pay much attention. (In general I think > those should be reserved for "data corruption" and "security".) > > The longer-term solution is to remove those as user-settable fields. > >> This hard to understand given portupgrade is the recommended upgrade >> tool. > > Once the individual who was working on it gave it up to the mailing > list, it became one of those "everyone is responsible so no one is > responsible" problems. I don't have a recommended fix for this. > > Having said that, I have a ports tree as of a month ago and portupgrade > was working ok for me. I don't have the cycles to go figure out where > it fails to be able to fix it, sorry. > I don't know if your issues are related but yesterday I managed to fix a ports tree that made portupgrade crash. I wasn't aware that portupgrade looks in the options files for dependencies. I think some ports, and my guess it is those who gave me the problem, blindly pulls in dependencies without checking if they are already installed or not and it is in those cases that portupgrade can get an incorrect cyclic dependencies list. Ok, enough of my strange unproven theories. I removed a lot of the options files from /var/db/ports/... and after some point, it was actually when removing them from all the p5-* ports, portupgrade started working again. When running portupgrade again I was more restrictive with what options to actually enable and after that everything works. Don't know if that will help anyone but I though I should at least put my ideas down somewhere. / Jimmy ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.