From owner-freebsd-questions@FreeBSD.ORG Fri Sep 3 19:46:47 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 AC64D16A4CE for ; Fri, 3 Sep 2004 19:46:47 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50B6C43D3F for ; Fri, 3 Sep 2004 19:46:47 +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 i83JkFkG022670; Fri, 3 Sep 2004 12:46:16 -0700 From: kstewart To: freebsd-questions@freebsd.org Date: Fri, 3 Sep 2004 12:46:38 -0700 User-Agent: KMail/1.7 References: <200409031511.06720.elcoocooi@earthlink.net> <20040903193850.GB22237@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040903193850.GB22237@happy-idiot-talk.infracaninophile.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409031246.38397.kstewart@owt.com> cc: Steve Hodgson cc: elcoocooi@earthlink.net Subject: Re: portupgrade, portsdb -U failing, ruby dumping core 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: Fri, 03 Sep 2004 19:46:47 -0000 On Friday 03 September 2004 12:38 pm, Matthew Seaman wrote: > On Fri, Sep 03, 2004 at 08:18:04PM +0100, Steve Hodgson wrote: > > I've removed the ports tree and that didn't work. Given that it appears > > to be a problem in the ports tree (someone [sorry, I've deleted the > > email] said they have narrowed it down), I was planning on leaving it for > > now and just cvsupping regularly. > > That would be me: > > > http://lists.freebsd.org/pipermail/freebsd-ports/2004-September/015847.html > > It's an odd one all right -- whatever it is that is blowing portsdb's > tiny mind is not at all obvious. There doesn't appear to be any > problems with any of the ports modified around the time that ruby > started dumping core. > I am only seeing it on 5.3-beta. I use portindex to genereate INDEX on my 4.x machines and ruby isn't dumping on them. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html Support the Bison at http://www.buffalofieldcampaign.org/