On Saturday, March 15, 2014 9:55:13 AM UTC-7, ONeal Freeman wrote: > > > > On Saturday, March 15, 2014 10:45:30 AM UTC-5, hasienda wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 15.03.2014 14:24, ONeal Freeman wrote: >> > Because of time constraints and the need to get the new instance >> online, >> > I used SQLite Administrator by Orbmu2k to export the table data from >> > those 0.10.4 tables with time/timechange fields into a csv and then >> > using the same application to import into the new 1.0.1 tables. >> > >> > I had to do it twice since the first time I exported data with a comma >> > as the delimiter which caused data import issues. Second export I used >> a >> > pipe as the delimiter. >> >> Bad idea to do so much by hand. I bet this causes the issues you >> experience now. Standard way is to shutdown you old Trac appliance, or >> do a db hot-copy with trac-admin, copy/move that db to new location and >> do an >> trac-admin <env> upgrade to the whole environment. >> >> See extensive upgrading guidelines in the authoritative Trac wiki >> documentation for more details [1]. >> >> Steffen Hoffmann >> >> >> [1] http://trac.edgewall.org/wiki/TracUpgrade >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.12 (GNU/Linux) >> Comment: Using GnuPG with Icedove - http://www.enigmail.net/ >> >> iEYEARECAAYFAlMkdZYACgkQ31DJeiZFuHf1FgCfQB4PIrMGV3xa6K80VHiUVQ6m >> LoAAn06Pw094h3K9M42e4Ghs4OHOb64K >> =8CGR >> -----END PGP SIGNATURE----- >> > > Good in theory but it did not work in my case since something during the > trac-admin upgrade command is wiping out some rather important db fields. > Now that's not to say that I do not have something mis-configured. This is > my first dealing with Trac from this prospective. Since I never got the > tractickettemplateplugin to work I am wondering if all of this is > associated with the BitNami install of Trac. Again, I am a novice but I > have definitely learned a lot. Please don't take any of this wrong, I > sincerely appreciate you guys helping me and your assistance has gotten me > this far. >
The upgrade appears to have been successful on Linux: - Trac 1.0.1 - Python 2.7.4 - SQLite 3.7.15.2 I'll send the file back to you so that you can evaluate and determine if you spot any issues. If you don't spot anything, at least you can use the upgraded copy rather than the one you had to manually modify. Next I'll do some testing on Windows to try and spot the issue you experienced. Could you also send me a copy of the file that has the timestamp problem? -- 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 http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
