When the time zone is set to a "right" zone, the
conflict detection logic fails, preventing any issue
from being edited.  The "right" time zones (such as
"right/EST5EDT") are leap-second corrected, and
currently have a 22-second offset from uncorrected time.

When this offset is in place, parts of Roundup use the
time with the correction, and parts use without.  For
example, the specific issue we were working with had a
last activity time of "2004-11-26.23:10:02" according
to the web interface, but the database internally
listed "20041126231024.912868".

We are using Roundup version 0.7.9 with the SQLite
backend.  This may not apply to other back-ends.  We
were able to restore functionality by setting
TZ=EST5EDT when running Roundup.