severity 296340 important thanks On Thu, Aug 17, 2006 at 11:35:43AM -0400, Alec Berryman wrote: > My rational wasn't included with the severity increase (used bts but > didn't escape the comment):
> If this was serious enough to issue a DSA for woody/sarge, it will > again be serious enough to issue a DSA for etch; this vulnerability > should be taken care of before the release. I don't find this to be a very compelling rationale for making this a release-critical issue. In particular, the maintainer should *not* be expected to take any further action here, since the latest DSA is supposed to propagate automatically to testing and unstable from proposed-updates. And "serious enough" here was still only a DoS, which shouldn't block a package from inclusion is stable AFAICS. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
