From owner-freebsd-questions@FreeBSD.ORG Fri Apr 11 08:40:58 2003 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 D3FDC37B401 for ; Fri, 11 Apr 2003 08:40:58 -0700 (PDT) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id C43BC43FCB for ; Fri, 11 Apr 2003 08:40:56 -0700 (PDT) (envelope-from mwm-dated-1050507656.dbb250@mired.org) Received: (qmail 38608 invoked from network); 11 Apr 2003 15:40:56 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 11 Apr 2003 15:40:56 -0000 Received: by guru.mired.org (tmda-inject, from uid 100); Fri, 11 Apr 2003 10:40:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16022.57863.507872.15319@guru.mired.org> Date: Fri, 11 Apr 2003 10:40:55 -0500 To: Gary Dunn In-Reply-To: <20030410204346.60b66625.knowtree@aloha.com> References: <20030410204346.60b66625.knowtree@aloha.com> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.73 (Jet Pilot) cc: freebsd-questions@freebsd.org Subject: Re: portupgrade: reverting to a previous version 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: Fri, 11 Apr 2003 15:40:59 -0000 In <20030410204346.60b66625.knowtree@aloha.com>, Gary Dunn typed: > Recently I upgraded postgresql using portupgrade. The upgrade involved a > change in data file formats. I should have dumped my database first, so > that I could import the data into the new version. Since portupgrade did > the make; make install "automatically" I never had the opportunity to > discover this fact until it was too late. The new version of postgresql > will not open my database :-( Right. One of the drawbacks of portupgrade over portversion is that you aren't forced to edit the portupgrade script. You should always do that anyway, so you can check for things like this. I also use that as a chance to remove ports that I'm no longer using. > I understand that portupgrade saves the old version of a port. True? Can > somebody explain how I can recover that version? My plan is to go back to > the old version, dump the data, then go forward again to the new version. > Is there a better way? I think your plan is the best you can do. As far as I know, portuprade removes the backup copy as part of the cleanup after a successful install. They are normally put in /var/tmp, unless you twiddle environment variables. See the portupgrade man page for details on this. When I ran into a similar problem - I had removed postgresql only to find that the port wouldn't build - I used cvs to fetch an old copy of the postgresql port. See for information on setting up anonymous cvs access. should have the information you need to figure out what date to go back to, but is unaccountably empty. See the cvs man page - specifically checkout and the -D option - for information on getting cvs to check out older versions of files. If you've subscribe to one of the distributions - recommended - you may well find a postgresql package you can use on one of them. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information.