2012/3/21 Daniel Hartwig <mand...@gmail.com>: > In this case, enough information is present (the failing call stack) > to look at the code and determine if there is some problem with the > parser or API use (the same kind of issues you enumerate). The > original system state is not required to do this. > > From your report I presume that you have not performed an > investigation but rather dismiss this one because it is old. > > If that is correct then I will keep this on my radar to look at. > > If you have looked at the code--or otherwise investigated the > issue--and determined it is now ok then I will not bother.
No, I haven't performed any detailed investigation. I just followed the reasoning that I just explained in my previous e-mail (which is not exactly the same as "dismiss it because it's old", but there we go). Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
