I will have somebody on the sf end take a look on Monday. It might take a couple of days, but I do think we can help out this week.
If you could upload the JSON dump somewhere so that I can have somebody on our end test with that actual data, that would probably make this go more quickly. --Mark Ramm On Sat, Feb 26, 2011 at 9:10 PM, Christoph Zwerschke <[email protected]> wrote: > After the SF hosted trac option turned out to be unusable for our purposes > (it's only trac 11.2, no plugins installable, no API or database access > etc.), I tried the second (and preferred) option for hosting the TG tracker > on SF today, the Allura tracker. > > The following scripts already exist to export from Trac as JSON and then > import JSON to Allura: > > http://sourceforge.net/p/allura/git/ci/e1c0a20357afc3af25f470cc3488ad3d5127c352/tree/migrate-3rdparty/ > > It turned out that the trac export script does not work with trac 0.10 which > we are running on our old server, so as a first step I have migrated it to > trac 0.12 on my own server. > > There were several more small problems with the export script which I could > fix easily. The script also stumbled over a oversized ticket containing only > Chinese spam (#852) which I have deleted already. > > So I have now a ~10MB JSON file with our trac database. > > Btw, there are ~1905 tickets for TG1 and ~540 tickets for TG2. > > When I tried to import that to Allura, I got an "Request Entity Too Large" > error - obviously because the import script tries to import everything with > one API call only. So I modified the import script to read the data in > chunks (slicing the artifacts list), but now I only get internal server > errors with no further clue what's wrong. The error message says more info > may be available in the server error log, but only SF staff has access to > that log. > > Another problem that needs to be solved if we go this way, is the user > mapping from our old Trac accounts to SF accounts. The import script has a > usermap option, and maybe we will be able to map some users through their > email addresses, but this is also something that can be only done by SF > staff. > > @Mark: Any chance you will be able to solve these problems in the short run? > If not, I suggest we migrate to Florent's server for the time being. > However, since Trac cannot work with remote repositories, this also means we > will have to move the repositories there. We can consider moving to SF at a > later time again. > > -- Christoph > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears Trunk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears-trunk?hl=en. > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
