Comment 22 for bug 321176

All -
      I am not quite sure how to proceed. I can confirm the issue is the use of deprecated classes. Running alarm-clock using Python 2.5 on Jaunty resolves the issue with alarm-clock. Having 2.5 installed along-side 2.6 broke all kinds of other things in my VM, I wouldn't suggest it. Python should be handling the errors a lot better, c'est la vie.
     I have managed to patch my local copy, it seems to be working fine. I can;
              1. Post the diffs where google can find them, people will have to apply the patches.
              2. Fork the project, post the updated code to github then forget about.
              3. Fork the project, rename/rebrand it, ask the MOTU's to add it to the repos.
                       3a. We are way, way past the Jaunty hard freeze, this likely wouldn't happen soon.
                       3b. Also, I hate to do that to the original developer.
              4. Something else? Can I get my patch added to the current package with the original developer?

Suggestions?

BTW - We might be to late already - https://bugs.launchpad.net/ubuntu/+source/alarm-clock/+bug/363937

C