> But I'm not sure how to fix this problem. > (Is it valid to downgrade qdbm's versions lower than 1.8.3 ...?)
The problem I've encountered is specifically with "gdbm_open". The version exported from QDBM overwrites the GDBM version for code running under mod_perl because PHP in Debian is now built with QDBM. gdbm_open() is failing silently when our mod_perl code tries to tie() to a GDBM database. Even if this is a fixable bug in the QDBM version of gdbm_open I'm not sure it's desirable to be using symbols out of different libraries without even realizing it. Would it be appropriate to split QDBM into a package with GDBM compatibility and one without? To get around the problem so we can upgrade our web servers we removed all gdbm_ functions from QDBM and installed a local replacement for the Debian package. I can provide patches if you want to go this route.
