After trying my patch in a clean jaunty chroot, it appears I haven't fixed the Ctrl-C issue. There are quite a few differences between my dev installation and Curses.py vs. what's currently in Jaunty. I've been exchanging emails with Jim Pryor, who had contributed several patches to the project, and we're throwing around some ideas and trying to get to the bottom of it. It appears to be a problem only in the Curses UI, the others are fine.
There has been some discussion about intended behaviour, after looking at the code, it would seem the proper way to shutdown the curses interface is to press the 'q' key. This works in Jaunty, but Curses.py leave the console in a pretty broken state that requires you to type "reset" in order to fix it -- this appears to be a completely seperate issue. With regards to the two deprecation warnings, the md5 warning was fixed in git on Dec. 24 (commit c58860). I think it would be a good idea to sync the current jaunty package with what is in git. The ssl patch has not yet been applied upstream (http://software.complete.org/software/issues/show/110) but it might be good to include it in the jaunty package until that happens. One more note, the Ctrl-C ticket on complete.org was filed against "site.complete.org" instead of "offlineimap", so it may not be on John's radar yet. I haven't had time to update that but I will this evening if you don't get to it first. I haven't given up on the Ctrl-C/Broken console issue yet though, I'll keep you posted. Sorry for the verbosity ;) -- python 2.6 transition breaks Ctrl-C to abort offlineimap https://bugs.launchpad.net/bugs/339932 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
