From owner-freebsd-ports@FreeBSD.ORG Fri Jul 15 12:54:27 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A09916A41C for ; Fri, 15 Jul 2005 12:54:27 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FAB343D6D for ; Fri, 15 Jul 2005 12:54:24 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from tirun (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id 2C59F7F for ; Fri, 15 Jul 2005 08:54:23 -0400 (EDT) From: "Brandon S. Allbery KF8NH" To: freebsd-ports@freebsd.org In-Reply-To: <20050715124604.GB84686@heechee.tobez.org> References: <42D7AB39.30803@acm.org> <20050715124604.GB84686@heechee.tobez.org> Content-Type: text/plain Date: Fri, 15 Jul 2005 08:54:21 -0400 Message-Id: <1121432061.69679.3.camel@tirun> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: portupgrade problems on 4.x X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jul 2005 12:54:27 -0000 On Fri, 2005-07-15 at 14:46 +0200, Anton Berezin wrote: > On Fri, Jul 15, 2005 at 02:25:29PM +0200, Jake Lloyd wrote: > > [Failed `Inappropriate file type or format'] [Updating the portsdb > > in /usr/ports ... - 13190 port entries found > > .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000........./usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:613: > > [BUG] Segmentation fault > > ruby 1.8.2 (2004-12-25) [i386-freebsd4] > > > > Abort (core dumped) > > Just another data point - I also experienced that after ruby upgrade on > a couple of 4.X systems. I believe this is a known problem with the Berkeley DB in the base system which has proved very difficult to track down; nobody's been able to pin down the exact circumstances in which it's triggered. The workaround is to tell portupgrade to use a format other than bdb1_btree: export PKG_DBDRIVER=bdb1_hash export PORTS_DBDRIVER=bdb1_hash or install a recent portupgrade configured with the option to use BerkeleyDB from ports instead of the 1.85 in the base. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH