From owner-freebsd-questions@FreeBSD.ORG Wed Jan 26 17:09:43 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E21D16A4CE for ; Wed, 26 Jan 2005 17:09:43 +0000 (GMT) Received: from out008.verizon.net (out008pub.verizon.net [206.46.170.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id F209A43D31 for ; Wed, 26 Jan 2005 17:09:42 +0000 (GMT) (envelope-from reso3w83@verizon.net) Received: from ringworm.mechee.com ([4.26.84.7]) by out008.verizon.net ESMTP <20050126170942.KQVW17379.out008.verizon.net@ringworm.mechee.com>; Wed, 26 Jan 2005 11:09:42 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id D07972CE741; Wed, 26 Jan 2005 09:05:57 -0800 (PST) From: "Michael C. Shultz" To: Bart Silverstrim Date: Wed, 26 Jan 2005 09:05:57 -0800 User-Agent: KMail/1.7.2 References: <200501260836.41851.reso3w83@verizon.net> <526a9e88ed7a008ceb2bae527f2761f3@chrononomicon.com> In-Reply-To: <526a9e88ed7a008ceb2bae527f2761f3@chrononomicon.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501260905.57540.reso3w83@verizon.net> X-Authentication-Info: Submitted using SMTP AUTH at out008.verizon.net from [4.26.84.7] at Wed, 26 Jan 2005 11:09:42 -0600 cc: FreeBSD Questions Subject: Re: portmanager loop? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 17:09:43 -0000 On Wednesday 26 January 2005 08:50 am, you wrote: > On Jan 26, 2005, at 11:36 AM, Michael C. Shultz wrote: > > Bart, here is what I think will happen based on what I see here, I > > think > > it will get past XFree-4-servers ok, but the next program that > > needs dri is going to bring the wrong one back in and so the > > looping will start on something else. If I were you I would hold > > off updating for now until I can give you a certain fix. > > Is there an easy way to check what is depending on the dri? My > system said it only had the one installed...most likely meaning that > just dri is causing the looping (correct?). Or it is the two dri's > having the same version reported? I have both currently off the > system. > > At any rate it got past the first loop stage, and it managed to > update a few more ports. If it starts with looping again, I won't be > any worse off than I was before (hopefully); I'd kill the looping > again when it isn't at a "installing" set of outputs and let you know > where it stalled again. > > Thanks for the updates... > > -Bart OK, hope it works for you. wrapper-1.0_3 also has a dependency on dri. I can now verify this is how things are supposed to be as of today: mike@/usr/ports/x11-servers/XFree86-4-Server>make all-depends-list /usr/ports/graphics/xfree86-dri mike@/usr/ports/x11/wrapper>make all-depends-list /usr/ports/graphics/xfree86-dri As long as you don't see /usr/ports/graphics/dri being built you will be OK.