From owner-freebsd-stable@FreeBSD.ORG Tue Sep 7 03:43:43 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C073C16A4CE for ; Tue, 7 Sep 2004 03:43:43 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6563B43D41 for ; Tue, 7 Sep 2004 03:43:43 +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 i873hBkG000336; Mon, 6 Sep 2004 20:43:13 -0700 From: kstewart To: freebsd-stable@freebsd.org Date: Mon, 6 Sep 2004 20:43:39 -0700 User-Agent: KMail/1.7 References: <413BC4CD.5090201@hamla.org> <200409052337.01634.kstewart@owt.com> <413D21D4.9070109@hamla.org> In-Reply-To: <413D21D4.9070109@hamla.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409062043.39277.kstewart@owt.com> cc: Maxim Maximov cc: Sahil Tandon Subject: Re: portsdb -Uu results in coredump X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Sep 2004 03:43:43 -0000 On Monday 06 September 2004 07:49 pm, Sahil Tandon wrote: > kstewart wrote: > > There is a bug in ruby that shows up as a bus error. Follow the topic on > > -ports@. There are several ways to alter the INDEX[-5] so that it occurs > > less frequently. > > Occurs less frequently? That's not what I'm looking for. Is there a > *fix* for the root cause? I haven't seen one. I have seen comments but when ruby is updated, you will probably be seeing a fix. > > > I started using portindexdb because it doesn't error off. I also don't > > use categories, which it doesn't produce. > > I'm using portsindexsb as a work around, but it still doesn't address or > solve the problem which makes portsdb -Uu fail. I've tried removing and > re-extracting the ports tree and doing whatever else was suggested in > the -ports@ mailing list(s) - to no avail. > I am also running portindexdb for that reason. For what I use INDEX-5.db for, portindexdb works just fine. We may have to wait until the port freeze is over. So far, I am only having to use in on my RELENG_5 machine. It cvsups port-all 2x a day as a cronjob and moving a "#" from one command ot another in the script isn't much work :). Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/