Date: Fri, 3 Sep 2004 12:46:38 -0700 From: kstewart <kstewart@owt.com> To: freebsd-questions@freebsd.org Cc: elcoocooi@earthlink.net Subject: Re: portupgrade, portsdb -U failing, ruby dumping core Message-ID: <200409031246.38397.kstewart@owt.com> In-Reply-To: <20040903193850.GB22237@happy-idiot-talk.infracaninophile.co.uk> References: <200409031511.06720.elcoocooi@earthlink.net> <BF3FDA7930BE33498DE948349DFFFC630139B99A@apollo.howesmacnaghten.local> <20040903193850.GB22237@happy-idiot-talk.infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409031246.38397.kstewart>