Your message dated Fri, 16 Jul 2010 02:19:54 +0000
with message-id <[email protected]>
and subject line Re: Can't reproduce with 4.8.24-1
has caused the Debian Bug report #441932,
regarding DB_HASH support broken in BerkeleyDB 4.6.19 ?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
441932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441932
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: db
Version: 4.6.19
Severity: important
http://groups.google.com/group/comp.databases.berkeley-db/browse_thread/thread/abf12452613ca7ec
causes the python test suite to crash.
--- End Message ---
--- Begin Message ---
On Sun, Dec 13, 2009 at 12:14:29PM +0000, brian m. carlson wrote:
> I tried compiling the file given in the link with libdb4.8-dev
> (4.8.24-1) on amd64/sid and did not experience any crash. Results:
>
> lakeview ok % ./db-test
> running in /tmp/cdbtest.gFu8jC.
> put with x = 0
> put with x = 50
> put with x = 100
> put with x = 150
> put with x = 200
> put with x = 250
> put with x = 300
> put with x = 350
> put with x = 400
> put with x = 450
> put with x = 500
> put with x = 550
> put with x = 600
> put with x = 650
> put with x = 700
> put with x = 750
> put with x = 800
> put with x = 850
> put with x = 900
> put with x = 950
> DB_ENV->remove: method not permitted after handle's open method
> done.
> remember to rm -r /tmp/cdbtest.gFu8jC
>
> Is this sufficient, or do I need to test on another architecture
> (powerpc or sparc)?
Closing due to lack of response.
--- End Message ---
