On Thursday, June 27, 2013 5:00:10 PM UTC-7, northof40 wrote: > > On Friday, June 28, 2013 3:42:52 AM UTC+12, hasienda wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 27.06.2013 13:47, northof40 wrote: > > I need to get access to a TRAC repository/database which I have a > data > > backup of but not the actual environment it ran within. > > > > My primary problem is that I don't know what version of TRAC was > being > > used to write to the repository/database which I have a backup of. > > > > We believe the version of TRAC in use was 0.10.x but it's possible it > > was upgraded and that that it's 1.x.x ? > > > > I've read this document : > http://trac.edgewall.org/browser/trunk/UPGRADE > > but some of the special cases towards the bottom of the page require > > that you know the version number you're starting from (not > unreasonably !). > > > > Is there any way I could look into the backups and determine which > > version of TRAC wrote them ? > > Assuming you're talking about a Trac database copy you'll find the Trac > version in 'system' db table. > > > OK thanks I opened the trac.db sqlite database and in the system table I > have : > > name|value| > database_version|19| > repository_dir|svn:7550b826-aab1-e94c-bd31-d2cc36b48ffb:E:/data/SVN_CPO| > > > According to the comment here : http://trac.edgewall.org/ticket/6300 by > cboos 'database_version' 19 corresponds to TRAC 0.10.5 (or presumably > earlier ?) can anyone confirm that ? >
0.10.5 is at database version 20: http://trac.edgewall.org/browser/tags/trac-0.10.5/trac/db_default.py?marks=20 It looks like you want 0.10.3: http://trac.edgewall.org/browser/tags/trac-0.10.3/trac/db_default.py?marks=20 > But if you don't inherited the environment for this database, you'll > get > into trouble with attachments. The files are not stored in the database > but in a directory within the Trac environment folder. > > > I *think* I'm OK here as I have a complete copy of all the files - the top > directory of which is shown below - I think I'm OK with all that lot ? > > I'm hoping that I can make a new TRAC called, like the old one, TRAC_CPO, > and then overlay the directory structure shown below over the the default > files which would have been created. Perhaps there is a better way though ? > Would be interested to hear. > > Directory of G:\data\BUP\TRAC\20110715T201800\TRAC_CPO > > 2011-07-15 08:21 p.m. <DIR> . > 2011-07-15 08:21 p.m. <DIR> .. > 2011-07-15 08:21 p.m. <DIR> attachments > 2011-07-15 08:21 p.m. <DIR> conf > 2011-07-15 08:21 p.m. <DIR> db > 2011-07-15 08:21 p.m. <DIR> htdocs > 2011-07-15 08:21 p.m. <DIR> log > 2011-07-15 08:21 p.m. <DIR> plugins > 2007-03-03 07:36 p.m. 100 README > 2011-07-15 08:21 p.m. <DIR> templates > 2007-03-03 07:36 p.m. 28 VERSION > 2011-07-15 08:21 p.m. <DIR> wiki-macros > > Thanks again for your help and if you or anyone else can confirm I should > be using 0.10.5 that would be great. > I would probably setup a 0.10.3 instance and make sure that all of the data is intact and accessible, and then upgrade the 0.10.3 instance. Make sure to read all of the upgrade notes for 0.11 through 1.0. We've been seeing a lot of issues with attachments not being migrated when upgrading from early version of Trac to Trac 1.0. If you encounter this situation, I'd be very interested to see what is contained in your logs from the upgrade (please make sure to have logging enabled when you run the upgrade). -- 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/groups/opt_out.
