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
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
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
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
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
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
- 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:
>
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
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
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
Hi All,
My apologies for another "me too": using portindex and portindexdb
solved the issue for me. portupgrade does its miracles again.
Bye... Nico
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubs
11 matches
Mail list logo