From owner-freebsd-current@FreeBSD.ORG Mon Jul 9 02:51:15 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3FB016A421 for ; Mon, 9 Jul 2007 02:51:15 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from smtp6.server.rpi.edu (smtp6.server.rpi.edu [128.113.2.226]) by mx1.freebsd.org (Postfix) with ESMTP id 69D0913C457 for ; Mon, 9 Jul 2007 02:51:15 +0000 (UTC) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp6.server.rpi.edu (8.13.1/8.13.1) with ESMTP id l692pD6Y030182; Sun, 8 Jul 2007 22:51:14 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <8cdf6c720707070710k2b7e030v37683e460d983bf9@mail.gmail.com> <20070708111105.C9997@fledge.watson.org> <20070708132545.5604cbe9.ubm@u-boot-man.de> Date: Sun, 8 Jul 2007 22:51:12 -0400 To: Marc "UBM" Bocklet , freebsd-current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-RPI-SA-Score: undef - spam scanning disabled X-CanItPRO-Stream: default X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.226 Cc: Subject: Re: status of 7.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jul 2007 02:51:15 -0000 At 6:07 PM -0400 7/8/07, Garance A Drosihn wrote: >At 1:25 PM +0200 7/8/07, Marc "UBM" Bocklet wrote: >> >>I'd like to do some testing, but I'm a little bit afraid of the upgrade >>procedure 6.2-stable to -current. Is it possible to do a simple upgrade >>if I follow the guidelines in UPGRADE or are there any hidden caveats? >>(like "you've to recompile all installed ports", etc. :-)) > >For what it's worth, I just recently upgraded one of my i386 machines. >I first upgraded to the latest snapshot of 6.2-stable, and then I went >from there to 7.x-current. I just did that on Friday, so I can't say >that I've tested everything yet. But so far I haven't had any problems. Okay, I just hit one non-obvious problem. On the system I had upgraded, 'portupgrade' was out-of-date, but 'ruby' had already been updated before the switch to 7.x-current. Portupgrade *was* working, but then I tried to upgrade it and it stopped working. Lots of errors, and then a program-interrupt while trying to do 'pkgdb -fu'. On a hunch, I did: cd /usr/ports/lang/ruby18 make deinstall make make install && make clean and then portupgrade went back to working fine. So, there might be some cases where you'll have to build a few ports even though they are already up-to-date. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu