Source: pike7.2 Source-Version: 7.2.580-3 We believe that the bug you reported is fixed in the latest version of pike7.2, which is due to be installed in the Debian FTP archive: pike-crypto_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike-crypto_7.2.580-3_i386.deb pike-gdbm_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike-gdbm_7.2.580-3_i386.deb pike-gz_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike-gz_7.2.580-3_i386.deb pike-image_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike-image_7.2.580-3_i386.deb pike-mysql_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike-mysql_7.2.580-3_i386.deb pike-pg_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike-pg_7.2.580-3_i386.deb pike7.2-crypto_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-crypto_7.2.580-3_i386.deb pike7.2-gdbm_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-gdbm_7.2.580-3_i386.deb pike7.2-gl_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-gl_7.2.580-3_i386.deb pike7.2-gtk_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-gtk_7.2.580-3_i386.deb pike7.2-gz_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-gz_7.2.580-3_i386.deb pike7.2-image_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-image_7.2.580-3_i386.deb pike7.2-mysql_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-mysql_7.2.580-3_i386.deb pike7.2-odbc_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-odbc_7.2.580-3_i386.deb pike7.2-pg_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-pg_7.2.580-3_i386.deb pike7.2-sane_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2-sane_7.2.580-3_i386.deb pike7.2_7.2.580-3.diff.gz to pool/main/p/pike7.2/pike7.2_7.2.580-3.diff.gz pike7.2_7.2.580-3.dsc to pool/main/p/pike7.2/pike7.2_7.2.580-3.dsc pike7.2_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike7.2_7.2.580-3_i386.deb pike_7.2.580-3_i386.deb to pool/main/p/pike7.2/pike_7.2.580-3_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