Source: libmusicbrainz-2.1 Source-Version: 2.1.2-2 We believe that the bug you reported is fixed in the latest version of libmusicbrainz-2.1, which is due to be installed in the Debian FTP archive: libmusicbrainz-2.1_2.1.2-2.diff.gz to pool/main/libm/libmusicbrainz-2.1/libmusicbrainz-2.1_2.1.2-2.diff.gz libmusicbrainz-2.1_2.1.2-2.dsc to pool/main/libm/libmusicbrainz-2.1/libmusicbrainz-2.1_2.1.2-2.dsc libmusicbrainz4-dev_2.1.2-2_i386.deb to pool/main/libm/libmusicbrainz-2.1/libmusicbrainz4-dev_2.1.2-2_i386.deb libmusicbrainz4c2a_2.1.2-2_i386.deb to pool/main/libm/libmusicbrainz-2.1/libmusicbrainz4c2a_2.1.2-2_i386.deb python-musicbrainz_2.1.2-2_all.deb to pool/main/libm/libmusicbrainz-2.1/python-musicbrainz_2.1.2-2_all.deb python2.3-musicbrainz_2.1.2-2_all.deb to pool/main/libm/libmusicbrainz-2.1/python2.3-musicbrainz_2.1.2-2_all.deb python2.4-musicbrainz_2.1.2-2_all.deb to pool/main/libm/libmusicbrainz-2.1/python2.4-musicbrainz_2.1.2-2_all.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