On Sun, May 25, 2008 at 01:16:26AM +1000, Steffen Joeris wrote: > > I haven't had time to take a deep look at the issue. Anyways, uploading > > 1.1.24 in unstable (which was planned) should fix this. Is an update > > for stable required ? Or is the security team already working on it? > Thanks for your efforts. > Depending on how stable the new upstream release is, maybe it could be > uploaded with a higher urgency. For the testing-security team, it would be > great to get that bug fixed in testing. > > cc'ing the stable-security team for reaching a decision on stable.
I uploaded 1.1.24-1 fixing this issue to unstable, at urgency: high. I also prepared a 1.1.19-1etch1 release targetted at stable-security. Shall I proceed uploading it to security-master ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
