Hi, On Sat, Mar 31, 2018 at 6:39 AM, Vagrant Cascadian <vagr...@debian.org> wrote: > Though, while using backports works around the issue, it would be ideal > to get it fixed in stretch as well...
Yes, unfortunately that requires identifying the real root cause and which of hundreds of changes between 2.3 and 2.6 fixes the bug, which is not especially appealing. So unless you feel strongly about it I'll probably close this bug and mark it fixed in 2.6-1. Thanks.
