Hi, Dmitry Smirnov wrote (12 Dec 2012 01:16:15 GMT) : > There were no reply from maintainer in #688574 so perhaps it would > be better to set Daniel as owner of this bug...
Please do it if you feel it's useful. A full new upstream version was uploaded to unstable since then, so an update in testing would now have to go through t-p-u. Given the crash fixed by 4.2.0+20120521-3 has severity normal, I'm unsure it's worth the effort. Dmitry, you filed the unblock request that is now outdated, what do you think? > IMHO even if fix is not implemented properly it is still prevent certain > crashes which can't be worse than what's in testing right now. I'm not sure this would be worse than what's in testing right now, but let's acknowledge that the fix has potential for future regressions, and does not only bring good: using internal implementation details of other libraries results in code that can break without notice, in the future, when the depended upon library is updated. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
