tag 585392 + moreinfo
thanks
Questions:
* Does this bug hold back mysql-5.1 or squeeze? It doesn't seem to
have, but some tools seem to report this bug as being in squeeze.
* Is this reproducible anywhere? I haven't found any evidence that it is.
* Does this bug not affect mysql 5.1? If this is a valid bug, then it
seems likely it'll be in version 5.1 too, but I haven't looked at what
code is involved and if the security fix is different in 5.1 than the
5.0 security patch.
Since the reporter has not responded to questions in a while I'm tagging
this bug moreinfo. I do not maintain this package, but I haven't seen any
of the packagers comment.
* A diff of the pre-security update and post-security update would be
nice.
* A comment from the maintainers about the reproducibility of this bug
would be nice. I personally can't see any reason for this bug, but I
haven't dug into the source code yet.
Thanks,
Drew Daniels
Resume: http://www.boxheap.net/ddaniels/resume.html
P.S.: Please CC me in responses.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
