portsdb and ruby bug on 4-STABLE
itetcu at people.tecnik93.com
Wed Sep 8 16:35:29 PDT 2004
On Thu, 09 Sep 2004 09:22:33 +1000
Rob B <rbyrnes at mailshack.com> wrote:
> At 09:46 AM 8/09/2004, Mike Edenfield wrote:
> >Michael Nottebrock wrote:
> >>A better workaround is this:
> >>1.) Install the databases/ruby-bdb port.
> >>2.) Set an environment variable PORTS_DBDRIVER to bdb-btree (or bdb_hash)
> >>This will change the portsdb's database backend from the libc-builtin
> >>bdb1 to a later berkeley db (you can set which one via the WITH_BDB_VER
> >>switch in the ruby-bdb port).
> >>You can also change the driver for pkgdb by setting PKG_DBDRIVER.
> >IMO, this is the best solution so far. So I would like to mention that
> >the easiest way to do this would be to add the following lines to your
> >ENV['PORTS_DBDRIVER'] = 'bdb_btree'
> >ENV['PKG_DBDRIVER'] = 'bdb_btree'
> >This way, all of the package tools will always see the replacement driver,
> >regardless of the state of the environment when you run them :)
> For the record - Alpha arch does not exhibit this problem. This is on both
> 5.3-BETA and 4.10-STABLE
How sure are you ?
I have a 5.3-BETA3 that's OK, a 5.2.1R that's not and one that's OK (all
i386). The only difference between them is that the one on which portsdb
crashes is from CD and the other are upgraded by source.
Unregistered ;) FreeBSD "user"
5.3-BETA3 - try `sysctl debug.witness_watch=0`
and prepare to fly :-)
More information about the freebsd-ports