Date: Fri, 3 Sep 2004 13:16:46 -0700 From: kstewart <kstewart@owt.com> To: freebsd-questions@freebsd.org Cc: Nico Meijer <nico.meijer@zonnet.nl> Subject: Re: portupgrade, portsdb -U failing, ruby dumping core Message-ID: <200409031316.47014.kstewart@owt.com> In-Reply-To: <4138CE4E.9080500@zonnet.nl> References: <200409031511.06720.elcoocooi@earthlink.net> <200409031246.38397.kstewart@owt.com> <4138CE4E.9080500@zonnet.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 03 September 2004 01:04 pm, Nico Meijer wrote: > Hey Kent, > > > 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. > > One of my 4.10-p2 servers exhibited the same behaviour with portsdb -u > (after 'make index' in /usr/ports). > > Haven't touched the rest, yet... ;-) > > Kaboom, it said... Nico I have been following the comments. I thought that is was strange that it only happended for me on 5.3-beta. I have a very different mix of ports on 5.x and your environment affects the "make index". My cvsup mirror updates at 30 minutes after the hour on the odd numbered hours and so what I was using was the same mirror state on 4.x and 5.x. FWIW, a "make fetchindex" on 5.x also died. Something has happened that is beyond Kris' test script. 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?200409031316.47014.kstewart>