Dear Jamil, Jamil Said Jr. wrote: > I read your email and my understanding is that only the unstable version > 5.34 and beyond will be fixed? What about the stable version 5.30?
That's next. If bugs are not security issues, they always should be fixed first in unstable, bascially as a proof that the fix works. The Stable Release Managers usually won't accept uploads to stable-proposed-updates or stable-updates, if the accordings bugs are not already fixed in unstable. It's a little bit more difficult in this case as the bug is still dormant on unstable. But the code for it is definitely there and so there's something to fix there, too. Actually Tormod wanted to fix stable first as the issue is more "urgent" there and I (as the one who was asked to sign/sponsor the upload) insisted on fixing it in unstable first. You can verify that the fix works on unstable (where the message is not yet triggered if the time in you computer is correct) by comparing the behaviour of 5.34-1 and 5.34-2 with the following command: faketime -f "+2y" xscreensaver-command -prefs With 5.34-1 you get an additional popup, with 5.34-2 you no more get it. The faketime command is part of the faketime package, so you might need to install that first. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE