From owner-freebsd-ports@FreeBSD.ORG Thu Sep 9 07:58:43 2004 Return-Path: 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 C755D16A4CE for ; Thu, 9 Sep 2004 07:58:43 +0000 (GMT) Received: from loki.daboyz.org (cpe-65-172-238-5.sanbrunocable.com [65.172.238.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DABE43D58 for ; Thu, 9 Sep 2004 07:58:43 +0000 (GMT) (envelope-from mike@daboyz.org) Received: by loki.daboyz.org (Postfix, from userid 1001) id 91D9A5B; Thu, 9 Sep 2004 00:58:28 -0700 (PDT) Date: Thu, 9 Sep 2004 00:58:28 -0700 From: Michael Barrett To: freebsd-ports@freebsd.org Message-ID: <20040909075828.GA83562@daboyz.org> Mail-Followup-To: freebsd-ports@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: portversion -v causes ruby to core dump X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Sep 2004 07:58:43 -0000 Hi, I just recently cvsup'd to the latest ports tree. After doing so, I ran portsdb -uU to make sure everything was kosher. After doing that however, whenever I run: #portversion -v I get the following: [Failed `Inappropriate file type or format'] [Updating the portsdb in /usr/ports ... - 11734 port entries found .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000..../usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Segmentation fault ruby 1.8.2 (2004-07-29) [i386-freebsd4] Abort trap (core dumped) I hacked around the portsdb.rb ruby file a little (as best I could, I don't know ruby at all) and added the following line just before line 587: STDERR.print pkgname That revealed that it was bailing on the following line in the /usr/ports/INDEX file: py23-PyGreSQL-3.5,1|/usr/ports/databases/py-PyGreSQL|/usr/local|A Python interface to PostgreSQL, both classic and DP-API 2.0|/usr/ports/databases/py-PyGreSQL/pkg-descr|girgen@pingpong.net|databases python|expat-1.95.8 gettext-0.13.1_1 libgnugetopt-1.2 libiconv-1.9.2_1 postgresql-7.4.5 py23-mx-base-2.0.5 python-2.3.4_2|expat-1.95.8 gettext-0.13.1_1 libgnugetopt-1.2 libiconv-1.9.2_1 postgresql-7.4.5 py23-mx-base-2.0.5 python-2.3.4_2|http://www.druid.net/pygresql/ I'm not sure what might be causing this. Anyways, here's the versions of the packages involved: /var/db/pkg/portupgrade-20040701_3 /var/db/pkg/ruby-1.8.2.p2_1 /var/db/pkg/ruby18-bdb1-0.2.2 If anyone can shed any light on what might be causing this issue, that'd be great. I use portversion/portupgrade all the time, so it'd really suck to stop using these tools now. THanks in advance for your help. -- ________________________________________________________________________ Mike Barrett | "We have veggie bacon, why don't we have mike@daboyz.org | meat fruit?" www.daboyz.org | -- My ex-coworker, Ben ------------------------+-----------------------------------------------