From owner-freebsd-ports@FreeBSD.ORG Fri Aug 21 19:29:17 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 5E94D106568C for ; Fri, 21 Aug 2009 19:29:17 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id E59208FC1D for ; Fri, 21 Aug 2009 19:29:16 +0000 (UTC) Received: (qmail 24647 invoked by uid 399); 21 Aug 2009 19:29:12 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 21 Aug 2009 19:29:12 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4A8EF583.8090806@FreeBSD.org> Date: Fri, 21 Aug 2009 12:29:07 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.22 (X11/20090729) MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <4A89CB20.3000408@quip.cz> <4A8E2121.6040507@FreeBSD.org> <4A8E8ACA.3060705@quip.cz> In-Reply-To: <4A8E8ACA.3060705@quip.cz> X-Enigmail-Version: 0.95.7 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org Subject: Re: portmaster is not always recursive 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: Fri, 21 Aug 2009 19:29:17 -0000 Miroslav Lachman wrote: > Doug Barton wrote: >> Unfortunately it didn't quite keep up with the times when some code >> paths were added (such as -r and the new code to do multiple ports on >> the same command line) and it was not always being unset when it >> should have been. The more common code paths (one port on the command >> line, or -a) didn't have this problem, which along with the fact that >> it only happened with certain combinations of out of date dependencies >> is why the bug went undiagnosed for so long. > > Code for multiple ports can explain my problems discribed with > amavisd-new and spamassassin, as I use upgrade of more ports in one > command very often. Ok, that's good to know. > I can confirm that bug was fixed in 2.10, it passed my test with -r > jpeg-7 ;) Also good news. :) I'm actually pretty confident at this point that this bug was the cause of most, if not all of the "oops, portmaster missed a dependency update" problems that other users have reported but have never been able to give me the info I needed to reproduce. Doug -- This .signature sanitized for your protection