From owner-freebsd-ports@FreeBSD.ORG Tue Sep 7 07:40:15 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 83DCA16A4CE for ; Tue, 7 Sep 2004 07:40:15 +0000 (GMT) Received: from elephant.ru.ac.za (elephant.ru.ac.za [146.231.128.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF3A743D1F for ; Tue, 7 Sep 2004 07:40:14 +0000 (GMT) (envelope-from gatkinson@rucus.ru.ac.za) Received: from iguana.ru.ac.za ([146.231.128.7]:52831) by elephant.ru.ac.za with smtp (Exim 4.41 (FreeBSD)) id 1C4aaF-0002nk-EB for freebsd-ports@freebsd.org; Tue, 07 Sep 2004 09:40:07 +0200 Received: (qmail 3039 invoked from network); 7 Sep 2004 07:40:07 -0000 Received: from singularity.graham.ru.ac.za (HELO rucus.ru.ac.za) (146.231.150.2) by iguana.ru.ac.za with SMTP; 7 Sep 2004 07:40:07 -0000 Message-ID: <413D65D7.1090000@rucus.ru.ac.za> Date: Tue, 07 Sep 2004 09:40:07 +0200 From: Greg Atkinson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en, en-us MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.9 (----) Subject: portsdb -u & ruby core dumps 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: Tue, 07 Sep 2004 07:40:15 -0000 Hi I am also experiencing this problem, have done some digging and have come up with this alternative: 1. Install the port "sysutils/portindex" 2. Run "portindex" and "portindexdb" as root or using sudo. (Do this in place of running "portsdb -Ufu") These two operations generate the INDEX files. I am open to correction but by the look of things: "portindex" = "portsdb -U" && "portindexdb" = "portsdb -u" (or at least something quite similar). This solved the problem for me, I hope it does the same for you. I am able to use "portupgrade" and the like again. Of course it doesn't solve the current glitch in portsdb but it is an effective alternative for now. :) Greg _________________________________________________ Greg Atkinson B.Sc. Rhodes University South Africa