On Tue, Sep 13, 2016 at 02:33:29PM +0200, Lucas Nussbaum wrote: > This is a case where there's no easy way to track affected releases. But > in doubt, it's better to err on the side of considering a release > affected.
Yes, I fully agree, especially in this case where the build is made in unstable and packages are usually expected to propagate to testing (so it would be just a matter of time that it happens in testing too). Thanks.
