Source: unixodbc Source-Version: 2.2.4-10 We believe that the bug you reported is fixed in the latest version of unixodbc, which is due to be installed in the Debian FTP archive: godbcconfig_2.2.4-10_alpha.deb to pool/main/u/unixodbc/godbcconfig_2.2.4-10_alpha.deb gtkodbcconfig0_2.2.4-10_alpha.deb to pool/main/u/unixodbc/gtkodbcconfig0_2.2.4-10_alpha.deb libodbcinstq1_2.2.4-10_alpha.deb to pool/main/u/unixodbc/libodbcinstq1_2.2.4-10_alpha.deb odbcinst1_2.2.4-10_alpha.deb to pool/main/u/unixodbc/odbcinst1_2.2.4-10_alpha.deb unixodbc-bin_2.2.4-10_alpha.deb to pool/main/u/unixodbc/unixodbc-bin_2.2.4-10_alpha.deb unixodbc-dev_2.2.4-10_alpha.deb to pool/main/u/unixodbc/unixodbc-dev_2.2.4-10_alpha.deb unixodbc_2.2.4-10.diff.gz to pool/main/u/unixodbc/unixodbc_2.2.4-10.diff.gz unixodbc_2.2.4-10.dsc to pool/main/u/unixodbc/unixodbc_2.2.4-10.dsc unixodbc_2.2.4-10_alpha.deb to pool/main/u/unixodbc/unixodbc_2.2.4-10_alpha.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