t politely - ask why you would prefer this workaround
> as opposed to replacing `portsdb -Uu` with `portindex && portindexdb`,
> other than to avoid having to install extra software?
>
> I can imagine a few, but I value your opinion.
Not having to install any extra softwar
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`
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
e you tried replacing the portsdb-sequence with `portindex &&
> portindexdb`?
Not yet; but I will. I was reading over the thread(s) mentioned by
racerx last night.
> So:
>
> - cvsup (or whatever tool you use)
> - portindex
> - portindexdb
> - portversion -vL = (or w
eplacing the portsdb-sequence with `portindex &&
> portindexdb`?
>
> So:
>
> - cvsup (or whatever tool you use)
> - portindex
> - portindexdb
> - portversion -vL = (or whatever switches you use)
>
> The upside to using portindex is that it merges changes instead of
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
- por
- 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
[EMAIL PROTECTED]>
To: "Donald J. O'Neill" <[EMAIL PROTECTED]>
Cc: "Steve Hodgson" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; "kstewart" <[EMAIL PROTECTED]>
Sent: Sunday, September 05, 2004 3:17 AM
Subject: Re: portindex/portindexdb
_
On Sat, Sep 04, 2004 at 02:43:51PM -0500, Donald J. O'Neill wrote:
> This is not a moot point. I've been struggling with this problem
> since this morning. The problem would just not go away.
Yes. Yesterday morning, I cvsup'd as usual and everything happened to
work OK. Tried again this mornin
Hello Mattthew,
This is not a moot point. I've been struggling with this problem
since this morning. The problem would just not go away.
After I cvsup the ports, I use "make index" and then portversion
-rRvc. I also run script whenever I cvsup, portupgrade, or install
a new port. On 090104 I c
On Sat, Sep 04, 2004 at 11:08:49AM +0100, Steve Hodgson wrote:
> > FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It
> > doesn't have the problem with ruby bus erroring like portsdb -u does.
> This also works for me on 5.2.1-p9. Am I missing something in asking why
> couldn't
>
> FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It
> doesn't have the problem with ruby bus erroring like portsdb -u does.
>
> Kent
This also works for me on 5.2.1-p9. Am I missing something in asking why
couldn't "portsdb -u" be replaced by portindex? Obviously this couldn
er words I want to do this:
> cvsup ...
> portindex
> portindexdb
> portversion -v | grep "<"
>
> Lucas Holt
FWIW, portindexdb will generate INDEX-5.db just fine on 5-current. It doesn't
have the problem with ruby bus erroring like portsdb -u does.
Kent
--
On Thu, 2 Sep 2004, Lucas Holt wrote:
After seeing several posts recently on portindex, I decided to try it out.
Most of the posts claimed you had to run portsdb -u after portindex.
You *can* run it after portindex, but the man page for portsdb says it
is "automatically updated on demand when it
After seeing several posts recently on portindex, I decided to try it
out. Most of the posts claimed you had to run portsdb -u after
portindex.
Is it safe to use portindexdb instead of portsdb -u?
Another words I want to do this:
cvsup ...
portindex
portindexdb
portversion -v | grep "<
19 matches
Mail list logo
