On Tue, Jan 02, 2007 at 11:10:34AM -0800, Sebastien Delafond wrote: > I just uploaded a new version of python-libgmail to the archive (sid, > priority=normal): it closes #405304, which is of severity "important" > (it will break basic functionality for many many users).
> libgmail's last upstream release was in August 2006, so I had to > package a CVS snapshot to fix the problem: there is unfortunately no > way I can pinpoint what specific change in the past 5 month fixes this > problem, hence the new version (0.1.5.1+cvs20070102-1). > There hasn't been any major code overhaul in libgmail since their > latest official release, though, so I trust this should be fine, and > hopefully this package can make it in etch if you so decide. No, it's not fine. The time for new upstream versions is past; the freeze policy allows for targetted fixes only, and by your own admission this update is anything but a targetted fix. If you and upstream could manage to identify an isolated fix for bug #405304, that would be accepted; a 3000-line upstream diff will not. Thanks, -- 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]
