From owner-freebsd-questions@FreeBSD.ORG Wed Sep 8 22:07:38 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE84D16A4CE for ; Wed, 8 Sep 2004 22:07:38 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22C0F43D2D for ; Wed, 8 Sep 2004 22:07:38 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id i88M73kG002574; Wed, 8 Sep 2004 15:07:05 -0700 From: kstewart To: freebsd-questions@freebsd.org Date: Wed, 8 Sep 2004 15:07:34 -0700 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409081507.34392.kstewart@owt.com> cc: Mark Rowlands Subject: Re: portupgrade broken? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Sep 2004 22:07:38 -0000 On Wednesday 08 September 2004 02:28 pm, Mark Rowlands wrote: > Updating the ports index ... Generating INDEX.tmp - please > wait..Warning: Duplicate INDEX entry: freeciv-gtk2-1.14.1 > > Warning: Duplicate INDEX entry: mod_jk2-apache2-2.0.2 > > Warning: Duplicate INDEX entry: mod_rpaf-ap2-0.5 > > Done. > > done > > [Updating the portsdb in /usr/ports ... - 11733 port > entries found > .........1000.........2000.........3000.........4000.........5000....... > ..6000.........7000.........8000..../usr/local/lib/ruby/site_ruby/1.8/po > rtsdb.rb:587: [BUG] Bus Error > > ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > > > got the above on 4-10 with portsdb -uU > > > > recvsupped ports ...got same > > reinstalled portupgrade ..... got same > > removed /usr/ports/ > > removed refuse files, cvsupped , got same > > > > > > any thoughts? > Visit an archive of ports@ and do a search on PORTS_DBDRIVER. Then choose your way of solving the problem. I set the environmental PORTS_DBDRIVER=bdb1_hash and it seems to work just fine. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/