From owner-freebsd-questions@FreeBSD.ORG Sun Apr 4 13:41:48 2004 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 E1A4816A4CE for ; Sun, 4 Apr 2004 13:41:48 -0700 (PDT) Received: from cromagnon.cullmail.com (cromagnon.cullmail.com [67.33.58.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8250943D49 for ; Sun, 4 Apr 2004 13:41:48 -0700 (PDT) (envelope-from jamoore@cromagnon.cullmail.com) Received: from cromagnon.cullmail.com (localhost.cullmail.com [127.0.0.1]) i34Kivub059262 for ; Sun, 4 Apr 2004 15:44:57 -0500 (CDT) (envelope-from jamoore@cromagnon.cullmail.com) Received: from localhost (localhost [[UNIX: localhost]]) by cromagnon.cullmail.com (8.12.10/8.12.10/Submit) id i34Kipt0059032 for freebsd-questions@freebsd.org; Sun, 4 Apr 2004 15:44:51 -0500 (CDT) (envelope-from jamoore) From: Jay Moore To: freebsd-questions@freebsd.org Date: Sun, 4 Apr 2004 14:44:47 -0600 User-Agent: KMail/1.5.4 References: <200404040153.11429.jaymo@cromagnon.cullmail.com> <200404041510.10437.jaymo@cromagnon.cullmail.com> <200404041329.13586.kstewart@owt.com> In-Reply-To: <200404041329.13586.kstewart@owt.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200404041544.48281.jaymo@cromagnon.cullmail.com> Subject: Re: ports hosed X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jaymo@cromagnon.cullmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Apr 2004 20:41:49 -0000 On Sunday 04 April 2004 03:29 pm, Kent Stewart wrote: > > Well, done is done... no way I can "back up", and re-visit questions > > that I've already answered incorrectly. And meanwhile my machine is > > still crunching forward with the last "portupgrade -a" that I did - > > this will likely continue for quite some time as it reports 211 ports > > (and this # keeps growing!) I believe I've lost control of the f**g > > thing... > > > > So - is there a way to go back to "ground zero"?... to just remove > > everything from the ports tree, and re-install from the 5.2 cd? > > I got to thinking about this more. I think you should have taken care of > all of the problems in /usr/ports/UPDATING before you fire off > portupgrade -a. You would have probably still bumped into the openssl > problem but it is a good idea for a start. Agreed... _if_ I had known to read /usr/ports/UPDATING I might have avoided the chaos I've created. For that matter if I'd known that the K3b port was going to suck down a bazillion dependencies, I would have foregone this whole quagmire :) But I didn't. I've learned a little bit, but I am where I am, and I have no confidence that this thing is going to conclude in a stable situation anytime soon - at least not without a lot more time and effort. So - again, is there any way to cleanly remove and re-install the entire ports tree from the 5.2 cd? Thanks, Jay