Re: [another "me too"] Re: portindex/portindexdb

2004-09-07 Thread Matthew Seaman
On Tue, Sep 07, 2004 at 07:38:07PM +0200, Nico Meijer wrote: > Hi Matthew, > > >Another workaround is simply to set: > > > >PORTS_DBDRIVER=bdb1_hash > > > >in your environment, and then use portsdb and portupgrade as usual. > > May I bluntly - yet politely - ask why you would prefer this work

Re: [another "me too"] Re: portindex/portindexdb

2004-09-07 Thread Nico Meijer
Hi Matthew, Another workaround is simply to set: PORTS_DBDRIVER=bdb1_hash in your environment, and then use portsdb and portupgrade as usual. May I bluntly - yet politely - ask why you would prefer this workaround as opposed to replacing `portsdb -Uu` with `portindex && portindexdb`, other th

Re: [another "me too"] Re: portindex/portindexdb

2004-09-07 Thread Joe Altman
On Tue, Sep 07, 2004 at 07:24:49AM +0100, Matthew Seaman wrote: > > Another workaround is simply to set: > > PORTS_DBDRIVER=bdb1_hash This is the Berkeley, AKA Sleepycat, bdb? I ask because I am also (suddenly) encountering the famous Exim "Failed to open DBM file /var/spool/exim/db/retry fo

Re: [another "me too"] Re: portindex/portindexdb

2004-09-07 Thread Joe Altman
On Tue, Sep 07, 2004 at 06:32:23AM +0200, Nico Meijer wrote: > Hi Joe, > > >Sigh: > > Lighten up! ;-) Hehthanks, I will. > >/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > >[BUG] Bus Error > >ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Have you tried replacing the portsdb-sequence with

Re: [another "me too"] Re: portindex/portindexdb

2004-09-06 Thread Matthew Seaman
On Tue, Sep 07, 2004 at 06:32:23AM +0200, Nico Meijer wrote: > Hi Joe, > > >Sigh: > > Lighten up! ;-) > > >/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: > >[BUG] Bus Error > >ruby 1.8.2 (2004-07-29) [i386-freebsd4] > > Have you tried replacing the portsdb-sequence with `portindex && > port

Re: [another "me too"] Re: portindex/portindexdb

2004-09-06 Thread Nico Meijer
Hi Joe, Sigh: Lighten up! ;-) /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd4] Have you tried replacing the portsdb-sequence with `portindex && portindexdb`? So: - cvsup (or whatever tool you use) - portindex - portindexdb - portversion -vL

Re: [another "me too"] Re: portindex/portindexdb

2004-09-06 Thread antenneX
- Original Message - From: "Joe Altman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, September 06, 2004 7:35 PM Subject: Re: [another "me too"] Re: portindex/portindexdb > On Mon, Sep 06, 2004 at 09:20:14AM +0200, Nico Meijer wrote: >

Re: [another "me too"] Re: portindex/portindexdb

2004-09-06 Thread Joe Altman
On Mon, Sep 06, 2004 at 09:20:14AM +0200, Nico Meijer wrote: > Hi Donald, > > >Nico - I suggest you try it again tomorrow. I thought I had it fixed > >yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is > >again seg faulting for me. Not going into a loop and continuously > >seg fa

Re: [another "me too"] Re: portindex/portindexdb

2004-09-06 Thread Nico Meijer
Hi Donald, Nico - I suggest you try it again tomorrow. I thought I had it fixed yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is again seg faulting for me. Not going into a loop and continuously seg faulting, but bad enough. After cvsupping my ports tree, running portindex (not

Re: [another "me too"] Re: portindex/portindexdb

2004-09-05 Thread Donald J. O'Neill
Nico - I suggest you try it again tomorrow. I thought I had it fixed yesterday. Then I re-cvsup'd today and redid my things. Ruby18 is again seg faulting for me. Not going into a loop and continuously seg faulting, but bad enough. Don Donald J. O'Neill [EMAIL PROTECTED] <>> On