Ah, not sure how this works with the default database engine of trac but after the copy operation, it turns out you have to fill the new (MySQL-) database with the copied tables / data. Something along the lines of:
$ mysql -u root -p [database[ < $env/db/mysql-db-backup.sql Might be a good idea to add such a remark to the migration page? Cheers, Tom. On Monday, January 30, 2017 at 4:48:53 PM UTC+1, Tom Uijldert wrote: > > Hi, > > I'm attempting to move an existing 1.0.1 trac project (under windows, > without svn-links ) to a 1.2 project on a Linux server, using the > description found in: > > https://trac.edgewall.org/wiki/TracMigrate > > skipping the svn-part and doing the init (new), backup (old), copy and > upgrade (new). > > This all looks pokey-billy until I start the new server again (using > tracd). > The project that is presented then, is empty. > > Did I forget any extra steps that need to be done? > What am I doing wrong? > > Thanks in advance, > Tom Uijldert. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
