Bug#948180: found 948180 in 4.1.2+dfsg-5, closing 948180

[Salvatore Bonaccorso]

Hi Markus,

On Sun, Jan 05, 2020 at 01:26:37PM +0100, Markus Koschany wrote:
> Am 05.01.20 um 06:44 schrieb Salvatore Bonaccorso:
> > found 948180 4.1.2+dfsg-5
> > close 948180 4.2.0+dfsg-1
> > thanks
> 
> You could have kept the bug report open until the issue is really fixed
> in unstable. I didn't see the new version in experimental until after I
> filed the bug report but sometimes such versions will stay there a long
> time for various reasons. There are tools like apt-listbugs that will
> warn unstable users about RC bugs but only if someone files bug reports.

The BTS (ans various tools) can handle the version tracking (and even
close a bug with multiple versions, this is actually what for instance
happends if a fix goes in as well via stable and oldstable and
contains a respective bug closer as well) -- this is the reason why I
first marked 4.1.2+dfsg-5 as found (which contains the bug), and then
one can close the bug (BTS will still see that it's unfixed in
unstable accordingly).

So either the fix then goes in by cherry-picking fixes for unstable on
top of 4.1.2+dfsg-5 or it goes in via a subsequent upload to unstable
of the 4.2.0 version.

See as well the respective graph the BTS know: https://bugs.debian.org/cgi-bin/version.cgi?absolute=0;fixed=4.2.0%2Bdfsg-1;found=4.1.2%2Bdfsg-5;info=1;package=opencv;collapse=1

HTH,

Regards,
Salvatore