One of the issues in our issue tracker fails to display in the web interface because the exception in the summary.

The backtrace and issue history is listed in the appended text file.

This is using 1.4.6 with Python 2.4.

Maybe <Date 2008-09-11.14:02:59.998> was somehow rounded to :60?

I just got the same crash in roundup-admin and web interface.
In my case I got a journal entry with <Date 2010-10-28.14:34:60.000000>

My very ugly workaround was to change _utc_to_local() in roundup/date.py to:

    try:
        ...existing code...
    except ValueError:
        return (1970,1,1,12,0,0)

Same problem here with the current Ubuntu (maverick) version of roundup,
which they call 1.4.13-3.1 (so presumably based on 1.4.13) using Python
2.6.6.

I reported this as an issue with Ubuntu's roundup package here:
https://bugs.launchpad.net/ubuntu/+source/roundup/+bug/673677
I fixed the problem locally by capping the seconds field to the range
0..59 (see patch behind that link).

Meta-question: should I not bother submitting roundup bugs at Ubuntu's
launchpad site? The previous issue I reported there did not get any
reaction after more than a year:
https://bugs.launchpad.net/ubuntu/+source/roundup/+bug/469013