From owner-freebsd-questions@FreeBSD.ORG Wed Jun 23 08:58:54 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 0B574106566B for ; Wed, 23 Jun 2010 08:58:54 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (gate6.infracaninophile.co.uk [IPv6:2001:8b0:151:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 66FBA8FC26 for ; Wed, 23 Jun 2010 08:58:53 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o5N8wlVq042619 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 23 Jun 2010 09:58:47 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4C21CCC7.1060908@infracaninophile.co.uk> Date: Wed, 23 Jun 2010 09:58:47 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: n dhert References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.96.1 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_50,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade -af in FreeBSDupdate to 8.0 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: Wed, 23 Jun 2010 08:58:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/06/2010 08:29:41, n dhert wrote: > Why does it stop? Can it be avoided? Or can I make portupgrade -af start > from where it got so far in the first run ? portupgrade is written in ruby -- having its command interpreter ripped out from underneath it does tend to cramp its style somewhat. Actually, the specific reason it crashes is the ruby-18-dbXX module, which also needs to be recompiled. The best way around the problem is to delete portupgrade and everything it depends on, and then reinstall from the ports directly: # pkg_deinstall -Rf portupgrade-2.4.6_4,2 # cd /usr/ports/ports-mgmt/portupgrade # make install # make clean If you do this first, you can then run portupgrade -af, which will recompile ruby and dependencies, but because everything is already recompiled, its compatible and you don't get a crash. > I could do # portupgrade -af again, but this is again "everything" (11 > hours)... Fix portupgrade as shown above, then run something like this: # portupgrade -x ">=2010-06-23" -af This says: "upgrade everything, except those packages installed more recently than 2010-06-23." You should chose the date where you *started* your original portupgrade -af session. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwhzMcACgkQ8Mjk52CukIzDsACeNRckO4634CcnAKcBPDduooos afIAnRsAWncQzPAndKR7v6ulNYdHIEXF =oSps -----END PGP SIGNATURE-----