From owner-freebsd-questions@FreeBSD.ORG Thu May 20 00:00:27 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D244A1065670 for ; Thu, 20 May 2010 00:00:27 +0000 (UTC) (envelope-from osp@aloha.com) Received: from relay.pixi.com (relay.pixi.com [206.127.224.101]) by mx1.freebsd.org (Postfix) with ESMTP id A0FF38FC08 for ; Thu, 20 May 2010 00:00:27 +0000 (UTC) Received: from yoda.pixi.com (yoda.pixi.com [206.127.224.41]) by relay.pixi.com (8.13.8+Sun/8.13.6) with ESMTP id o4K00Otf015346 for ; Wed, 19 May 2010 14:00:24 -1000 (HST) Received: from webmail.pixi.com (yoda.pixi.com [206.127.224.120] (may be forged)) by yoda.pixi.com (8.13.1/8.13.1) with SMTP id o4K00OI1017924 for ; Wed, 19 May 2010 14:00:24 -1000 Message-Id: <201005200000.o4K00OI1017924@yoda.pixi.com> To: freebsd-questions@freebsd.org From: osp@aloha.com Date: Wed, 19 May 2010 14:00:24 HST X-Posting-IP: 141.190.32.71 X-Mailer: Endymion MailMan Standard Edition v3.2.19 Subject: Re: 7.2 to 8.0 upgrade issues X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2010 00:00:27 -0000 On Tue, 18 May 2010 13:28:46 -0500 Adam Vande More wrote: > On Tue, May 18, 2010 at 2:28 AM, n dhert wrote: > > > Upgrading a freebsd7.2 (i386) system to 8.0 > > After > > # freebsd-update -r 8.0-RELEASE upgrade > > # freebsd-update install > > reboot > > # freebsd-update install > > I did > > # portupgrade -af --batch --yes > > after 17 hours (mostly during the night..), it finished with > > ---> ** Upgrade tasks 425: 199 done, 1 ignored, 3 skipped and 1 failed > > (no error messages here..) > > Unfortunately, I didn't log the screen output to a file .. > > - how can I find out what port failed and which where skipped and ignored? > > - is it normal this didn't recompile all 425 ports? > > - to rebuild the failed port: is # portupgrade -fr OK? > > > .. > but make sure you're following /usr/ports/UPDATING. This is extremely important. The UPDATING file is in reverse chronological order and each ent list the port affected. I am a fan of portupgrade. To get a list of ports that are not up to date use pkg_version -v. At this point you should not need the -f option to portupgrade. No need to waste time rebuilding ports that do not ned rebuilding. portupgrade -a should be all you need. Another way to reveal what did not get updated is to run portupgrade -an The -n will cause portupgrade to show what it would do without actually doing anything. This won't help when port B depends on something in port A that will be updated. Another portupgrade option that may help you is -R. Put it all together and you get portupgrade -aR --batch Note that the handbook does not show -a and -R being used together. My thinking is that without the -R a new version of an existing port that requires something new -- that you do not already have -- will fail. Rather unlikely, to start with portupgrade -a --batch and use -R only if you still getb errors. Gary Dunn Open Slate Project