roundup writes to stderr on launch, causes (spurious?) crash report after login

Bug #469013 reported by Malte Helmert
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
roundup (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: roundup

Starting the roundup init script causes a deprecation warning to be written to stderr:
======================================================================
helmert@alfons:~$ sudo /etc/init.d/roundup start
Starting Roundup HTTP-Server:/usr/lib/python2.6/dist-packages/roundup/hyperdb.py:26: DeprecationWarning: the sets module is deprecated
  from sets import Set
/usr/lib/python2.6/dist-packages/roundup/password.py:24: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha, md5, re, string, random
/usr/lib/python2.6/dist-packages/roundup/password.py:24: DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import sha, md5, re, string, random
/usr/lib/python2.6/dist-packages/roundup/mailer.py:9: DeprecationWarning: the MimeWriter module is deprecated; use the email package instead
  from MimeWriter import MimeWriter
 roundup-server.
======================================================================

As a consequence, I get a (spurious) notification after login that the roundup server crashed.

ProblemType: Bug
Architecture: i386
Date: Sun Nov 1 18:12:43 2009
DistroRelease: Ubuntu 9.10
Package: roundup 1.4.4-4+lenny1ubuntu1
PackageArchitecture: all
ProcEnviron:
 LC_TIME=de_DE.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_PAPER=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: roundup
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Malte Helmert (helmert) wrote :
Revision history for this message
Malte Helmert (helmert) wrote :

This does not appear to happen any more in maverick, so maybe this one can be closed.

Revision history for this message
Hans Joachim Desserud (hjd) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in roundup (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.