Fixed in changeset:   6531:82f870433b18

Fix is to trap the syntax error and use re to replace 1234L with 1234 then
re-eval the tuple repr string. Original reporter told me (via irc) that
the patch worked.

I am not generating a script to fix the entries in the database for two reasons:

1. the bug that generated the ID as a long rather than as a string was fixed
   at least 15 (1.2.0 oct 2006 or prior) years ago. So newer trackers won't
   have the issue.

2. this only shows up when displaying the history for tickets modified using unfixed
   old code. So the runtime delay of the fixup at display time should only happen for
   older ticket that are less likely to be displayed.