Hi Christian, 2016-07-01 10:03 GMT+02:00 Christian Hofstaedtler <z...@debian.org>: > * Balint Reczey <bal...@balintreczey.hu> [160630 00:20]: > [..] >> >>> I plan updating Jessie's version through jessie-proposed-updates, since >> >>> the issue is marked as no-DSA. >> >> >> >> This can probably still go through debian-security? >> > >> > I'll ask them, showing the proposed diff. >> >> I asked, but here is no clear new decision regarding handling the issue >> in Jessie. > > Jessie has the exact same issue, right?
Yes, with a slightly different set of patches to fix it. Security Team still prefers the package to go through proposed-updates which I will initiate soon after a last set of testing in Jessie. Cheers, Balint > >> While reading all the bug reports related to the crash I noticed that >> the fix introduced a memory leak which is fixed in successive commits. > > Right, I knew about that but already had forgotten again. > >> I have added them to the update growing it significantly, but at least >> we don't introduce a regression with the fix. >> Please see the diff attached and also in the git repository as separate >> commits. > > Wow that's a ton of patches on top. Look at least logically > consistent to me. > > -- > ,''`. Christian Hofstaedtler <z...@debian.org> > : :' : Debian Developer > `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 > `- >
