Patch #5764

migrate_from_trac does not support trac 0.12

Added by Michalis Miatidis almost 7 years ago. Updated almost 4 years ago.

Status:NewStart date:2010-06-27
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Importers
Target version:Candidate for next minor release

Description

I attempted to migrate a trac 0.12 project to Redmine 0.9.4 and encountered the following two errors:

1. I had no clue that the project ID should be given in lowercase:

...
Target project identifier []: ETrackProject
Unable to create a project with identifier 'ETrackProject'!
rake aborted!
undefined method `reload' for nil:NilClass
C:/redmine-0.9.4/lib/tasks/migrate_from_trac.rake:685:in `target_project_identifier'
...

2. Importer was not able to handle time format of trac 0.12 database. Trac seems to keep times as Epoch at fixed length adding trailing '0's.

...
Migrating components................................
Migrating milestones.rake aborted!
bignum too big to convert into `long'
C:/redmine-0.9.4/lib/tasks/migrate_from_trac.rake:104:in `at'
...

I attach a patch that resolved for me the above. I am not sure if it remains compatible with trac 0.11

migrate_from_trac.diff Magnifier (1.35 KB) Michalis Miatidis, 2010-06-27 13:36


Related issues

Related to Redmine - Defect #6868: migrate_from_trac and trac 0.12 Reopened 2010-11-11
Related to Redmine - Patch #14567: migrate_from_trac.rake does not convert timestamps in Tra... New

History

#1 Updated by Michał Wróbel over 6 years ago

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.

#2 Updated by Jean-Philippe Lang over 6 years ago

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

#3 Updated by Blake Matheny over 6 years ago

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.
}}}

With the multi-repository support in version 0.12 the message changed to:
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 just basically converts the new commit message style to the old one.

#4 Updated by Etienne Massip about 6 years ago

  • Target version set to Candidate for next minor release

#5 Updated by Johannes Weberhofer about 4 years ago

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.

#7 Updated by Toshi MARUYAMA almost 4 years ago

  • Related to Patch #14567: migrate_from_trac.rake does not convert timestamps in Trac database version 23 added

Also available in: Atom PDF