Source: neverball Source-Version: 1.4.0-2 We believe that the bug you reported is fixed in the latest version of neverball, which is due to be installed in the Debian FTP archive: neverball-common_1.4.0-2_all.deb to pool/main/n/neverball/neverball-common_1.4.0-2_all.deb neverball-data_1.4.0-2_all.deb to pool/main/n/neverball/neverball-data_1.4.0-2_all.deb neverball_1.4.0-2.diff.gz to pool/main/n/neverball/neverball_1.4.0-2.diff.gz neverball_1.4.0-2.dsc to pool/main/n/neverball/neverball_1.4.0-2.dsc neverball_1.4.0-2_amd64.deb to pool/main/n/neverball/neverball_1.4.0-2_amd64.deb neverputt_1.4.0-2_amd64.deb to pool/main/n/neverball/neverputt_1.4.0-2_amd64.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