Source: db4.2 Source-Version: 4.2.52-17 We believe that the bug you reported is fixed in the latest version of db4.2, which is due to be installed in the Debian FTP archive: db4.2-doc_4.2.52-17_all.deb to pool/main/d/db4.2/db4.2-doc_4.2.52-17_all.deb db4.2-util_4.2.52-17_i386.deb to pool/main/d/db4.2/db4.2-util_4.2.52-17_i386.deb db4.2_4.2.52-17.diff.gz to pool/main/d/db4.2/db4.2_4.2.52-17.diff.gz db4.2_4.2.52-17.dsc to pool/main/d/db4.2/db4.2_4.2.52-17.dsc libdb4.2++-dev_4.2.52-17_i386.deb to pool/main/d/db4.2/libdb4.2++-dev_4.2.52-17_i386.deb libdb4.2++_4.2.52-17_i386.deb to pool/main/d/db4.2/libdb4.2++_4.2.52-17_i386.deb libdb4.2-dev_4.2.52-17_i386.deb to pool/main/d/db4.2/libdb4.2-dev_4.2.52-17_i386.deb libdb4.2-java_4.2.52-17_i386.deb to pool/main/d/db4.2/libdb4.2-java_4.2.52-17_i386.deb libdb4.2-tcl_4.2.52-17_i386.deb to pool/main/d/db4.2/libdb4.2-tcl_4.2.52-17_i386.deb libdb4.2_4.2.52-17_i386.deb to pool/main/d/db4.2/libdb4.2_4.2.52-17_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to