Hi Andreas, On Mon, Jun 05, 2017 at 01:10:32PM +0200, Andreas Moog wrote: > Version: 11.0+dfsg-1 > > I totally missed to close this report. This has been fixed.
While that's good to hear, the found and fixed versions given in this bug report don't seem to fit: | Found in version 11.0+dfsg-2 | Fixed in version 11.0+dfsg-1 See also https://bugs.debian.org/cgi-bin/version.cgi?fixed=11.0%2Bdfsg-1;found=nzbget%2F11.0%2Bdfsg-2;info=1;package=nzbget;collapse=1;absolute=0 So according to your last mail (cited in this mail) the bug has been fixed in a version (11.0+dfsg-1) lower than the version it was reported against (11.0+dfsg-2). This means that the bug tracking system currently thinks the bug is still present in the current versions of nzbget in Debian Jessie, Stretch and Unstable. The link above shows that nicely. Can you please check both, found and fixed versions and set them to the correct versions? Thanks in advance! Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
