Redmine

The problem results from the timestamps' format change from "seconds since epoch" to "microseconds since epoch" in Trac 0.12

While trying to migrate my Trac environments I got straight down to the code and reinvented the wheel by making a similar patch

I am pretty sure that neither mine nor Michalis' one do not remain compatible with trac 0.11, since they neither check the version of trac database schema nor perform any heurestics on the timestamps themselves. Before merging into mainstream, of course this needs to be done.

If someone can send me a trac-0.12 database containing some sample data, I can try to fix it.

The trac migration script also does not handle the new trac 0.12 syntax for commit messages via the commit hook scripts. Pre 0.12, commit messages were of the form

{{{
(In [\d+]) Commit message.
}}}

In [(\d+)/(\S+)]:
{{{
#!CommitTicketReference repository="\S+" revision="\d+" 
Commit message
}}}

The following replacement addresses this issue while maintaining revision links (place before the "# Revision links" comment):

commit_re = /^In \[(\d+)\/\S+\]:[\r\n]+\{\{\{[\r\n]+#!CommitTicketReference repository="\S+" revision="\d+"[\r\n]+(.*)[\r\n]*\}\}\}[\r\n]*/m
text = text.gsub(commit_re, '(In [\1]) \2') 

This problem exists since trac database version 23 (see http://trac.edgewall.org/attachment/ticket/6466/6466-microsecond-times-r8770.patch ).
"trac.system" table should be checked; when "database_version" has an "value" > 22, all time-values should be divided by 1000000, as they have been converted to microseconds.

Can you try this patch:
http://www.redmine.org/issues/14567