Edit report at http://bugs.php.net/bug.php?id=51086&edit=1
ID: 51086
Comment by:
Reported by: seanius at debian dot org
Summary: will not work with libdb4.8
Status: Closed
Type: Bug
Package: DBM/DBA related
Operating System: *
PHP Version: 5.3, 6 (2010-02-19)
Assigned To: sixd
New Comment:
Just a thought: what about leaving this open until oracle releases a new
libdb, and then committing a second patch that refuses to accept db4.8 <
the fixed version via config.m4? either way, thanks for looking at
this.
Previous Comments:
------------------------------------------------------------------------
[2010-03-05 07:54:17] sixd@php.net
The next patchset of Berkeley DB 4.8 will possibly have the root cause
fixed and the undefined behavior that DBA was depending on reverted.
In the meantime I've merged a fix and a workaround to PHP 5.2.14-dev,
PHP 5.2.3-dev and PHP 6.0.
Note: now when using Berkely DB 4.8 prior or equal to 4.8.26, the
workaround causes a message regarding meta data to be suppressed when
opening the database. This causes a diff in a few cases where that
message was previously displayed in DB 4.7, but prevents the message
incorrectly displaying in all other tests.
------------------------------------------------------------------------
[2010-03-05 07:45:30] sixd@php.net
Automatic comment from SVN on behalf of sixd
Revision: http://svn.php.net/viewvc/?view=revision&revision=295847
Log: Fixed bug #51086 (DBA DB4 doesn't work with Berkeley DB 4.8)
------------------------------------------------------------------------
[2010-03-02 17:12:03] sixd@php.net
The Berkeley DB developers are reviewing this.
------------------------------------------------------------------------
[2010-02-19 09:05:25] seanius at debian dot org
-Summary: will not build/work with libdb4.8
+Summary: will not work with libdb4.8
-Operating System: Debian (and others)
+Operating System: *
-PHP Version: 5.3.1
+PHP Version: 5.3, 6 (2010-02-19
heh, seems we're stepping on each other's toes now. i'll set the stuff
back that i just clobbered, and promise to be quiet for a few hours :)
actually it won't build correctly against db4.8. i had to modify the
snapshot to link against db4.8, as otherwise you see
http://bugs.php.net/bug.php?id=51062 , though
apparently that's a bogus
issue, hrm... :)
------------------------------------------------------------------------
[2010-02-19 09:00:54] seanius at debian dot org
-Summary: will not work with libdb4.8
+Summary: will not build/work with libdb4.8
-Operating System: *
+Operating System: Debian (and others)
-PHP Version: 5.3, 6 (2010-02-19)
+PHP Version: 5.3.1
sorry for all the noise, when trying the latest snapshot it apparently
unpacked on top of a previous snapshot in which i had been investigating
the issue. the tests fail in the new snapshot with more than just the
NOTICE error (i had been playing with the open flags as mentioned
previously). the actual failure diff looks like:
TEST 1/25 [ext/dba/tests/bug36436.phpt]
========DIFF========
001+ Notice: dba_popen(): fop_read_meta:
/home/sean/Download/php5.3-201002190730/ext/dba/tests/test0.dbm:
unexpected file type or format in
/home/sean/Download/php5.3-201002190730/ext/dba/tests/bug36436.php on
line 6
002+
003+ Notice: dba_popen():
/home/sean/Download/php5.3-201002190730/ext/dba/tests/test0.dbm: Invalid
type 5 specified in
/home/sean/Download/php5.3-201002190730/ext/dba/tests/bug36436.php on
line 6
004+
005+ Warning:
dba_popen(/home/sean/Download/php5.3-201002190730/ext/dba/tests/test0.dbm,c):
Driver initialization failed for handler: db4: Invalid argument in
/home/sean/Download/php5.3-201002190730/ext/dba/tests/bug36436.php on
line 6
001- resource(%d) of type (dba persistent)
002- string(3) "XYZ"
003- string(1) "X"
004- string(1) "Y"
005- ===DONE===
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=51086--
Edit this bug report at http://bugs.php.net/bug.php?id=51086&edit=1