> The most significant of it being the version number of the package on > which you encountered the bug. Could you tell us which it is? Of course - I thought without version header it's opened against version in sid Version: 1:1.4.21.2~dfsg-2