From owner-freebsd-ports@FreeBSD.ORG Thu Dec 17 12:45:24 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 0E835106566B for ; Thu, 17 Dec 2009 12:45:24 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id BCAD48FC08 for ; Thu, 17 Dec 2009 12:45:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 4E4A5A0326; Thu, 17 Dec 2009 07:27:30 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1ogj0Vtq33F; Thu, 17 Dec 2009 07:27:30 -0500 (EST) Received: from localhost (daemon.egr.msu.edu [35.9.44.65]) by mx.egr.msu.edu (Postfix) with ESMTP id E3F4AA0308; Thu, 17 Dec 2009 07:27:27 -0500 (EST) Received: by localhost (Postfix, from userid 21281) id C53E891EDF; Thu, 17 Dec 2009 07:27:27 -0500 (EST) Date: Thu, 17 Dec 2009 07:27:27 -0500 From: Adam McDougall To: Jimmy Renner Message-ID: <20091217122727.GF10902@egr.msu.edu> References: <7314e5020912161917s355d02c9l16c996043c753044@mail.gmail.com> <19241.45040.505925.616766@jerusalem.litteratus.org> <20091217052400.GC32037@lonesome.com> <20091217102102.15241asjv1rqmqzo@kilroy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091217102102.15241asjv1rqmqzo@kilroy> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-ports@freebsd.org 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 12:45:24 -0000 On Thu, Dec 17, 2009 at 10:21:02AM +0100, Jimmy Renner wrote: 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. Some of that sounds true to my experience, for a while I've noticed while installing a new port with portupgrade that it will install the default dependencies before prompting with the options screen to find out which ones I want. For example if I do 'portupgrade -N postfix' on a fresh system, it will first install pcre and THEN prompt me to (de)select pcre or any of the other optional deps. 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. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"