From owner-freebsd-current@FreeBSD.ORG Wed Oct 27 05:36:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0F6C16A4CE for ; Wed, 27 Oct 2004 05:36:01 +0000 (GMT) Received: from hotmail.com (bay2-dav9.bay2.hotmail.com [65.54.246.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id B44A043D45 for ; Wed, 27 Oct 2004 05:36:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 26 Oct 2004 22:36:01 -0700 Received: from 24.24.201.219 by BAY2-DAV9.phx.gbl with DAV; Wed, 27 Oct 2004 05:35:16 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Andre Guibert de Bruet" References: <20041027010516.Y42571@alpha.siliconlandmark.com> Date: Tue, 26 Oct 2004 22:35:16 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 27 Oct 2004 05:36:01.0447 (UTC) FILETIME=[D807AB70:01C4BBE6] cc: freebsd-current@freebsd.org Subject: Re: Portupgrade -af question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 27 Oct 2004 05:36:02 -0000 I was planning to recompile portupgrade manually first. But I didn't know/remember that it was dependent on ruby. So here is what I'm gonna do step by step: 1. cvsup src to 5.3-RELEASE (when it becomes available) 2. cvsup the ports tree to the latest skeleton - still using the 5.2 system 3. upgrade kernel + world (including the mergmaster step, of course) I will follow the official updating guide step by step and very carefully 4. double-check if ftp and http connection is still working with new kernel 5. recompile ruby manually 6. recompile portupgrade manually 7. portupgrade -af -P 8. recompile the few ports that needs special options and/or local patching I believe this will work and will save a lot of time! Thanks again for the help!! Zoltan ----- Original Message ----- From: "Andre Guibert de Bruet" To: "Zoltan Frombach" Cc: Sent: Tuesday, October 26, 2004 10:08 PM Subject: Re: Portupgrade -af question > > On Tue, 26 Oct 2004, Zoltan Frombach wrote: > >> Thank you for your prompt reply! All of the mentioned conditions are true >> in my case, so I guess this is the way I'm gonna go. I have a few ports >> that I compile with custom command line options, but I can always >> re-compile those later just by issuing individual portupgrade -f portname >> commands. My main point is to shorten the downtime this server must >> suffer at the "upgradathon". ;-) > > Just as a word of caution, when jumping between versions of FreeBSD, you > should upgrade ruby and portupgrade manually first and then performing the > portupgrade on all ports. This isn't documented, but I've run into > instances where some changes to the base system broke ruby... > > Regards, > Andy > > | Andre Guibert de Bruet | Enterprise Software Consultant > > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"