I blindly tried to reproduce that bug on a quadri Xeon server running
sarge and was unable to reproduce it.
Note that I have absolutely no understanding of the bug issue. I was
just wandering through RC bugs
Anyway, I think the bug severity is overflated:
grave
makes the package in question unusable or mostly so, or causes
data loss, or introduces a security hole allowing access to the
accounts of users who use the package.
IMHO, important is more appropriate:
important
a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
The bug, as described, does not make the package unusable, given the
very specific way to trigger it.
It does not cause data loss, but "only" a DoS
And it does not introduce a security hole allowing access to the
accounts of users.
I hereby propose to lower the severity of this bug.
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
