Nicolas DHOMONT a écrit : > Matthew Gillen wrote: >>> Nicolas DHOMONT wrote: >>> >>>> Hello >>>> >>>> I'm moving my trac+svn system from one server to another. >>>> >>>> Former server : >>>> trac : 0.9.4 >>>> svn : 1.2.3 (r15833) >>>> OS : ? : red hat (I'm not sure) >>>> >>>> New server : >>>> trac : 0.10.1 (no other choice or I didn't find how to have the choice) >>>> svn : 1.3.2 (r19776) >>>> system : Gentoo >>>> >>>> >>> What versions of sqlite do each of those systems have? >>> I'd say your problem is probably a version mismatch on sqlite. You can >>> either >>> synchronize the gentoo box's version with the RH one, or do a dump-to-sql / >>> reload-from-sql sequence. >>> >> >> Oops, Rainer is right, disregard my advice. I forgot about that problem with >> 0.10.1. >> >> Matt > First of all : thanks for fast answers. > > After reading them, I found out that, in fact, the only thing I know > about former server is the version of trac (0.9.4). > I don't have access to any other information on this server because > it's owned by another company that developed my software. > I'm in a process of getting all materials back on my server. > > Anyway, now I know the exacts spec of former server: > OS : debian > svn : 1.2.3dfsg1-3 > sqlite : 2.8.16-1 > sqlite3 : 3.3.5-0.2 > > > And here is the sqlite3 version of my new server. > --- > ~ # sqlite3 -version > 3.3.5 > --- > > In addition, I tried to use my trac env without upgrade it and I got > an error dealing with database. > I also tried to open the database with sqlite but : > > --- > ~ # sqlite /path/to/env/project-name/db/trac.db > Unable to open database "/path/to/env/project-name/db/trac.db": file > is encrypted or is not a database > --- > > I guess the database is a 'sqlite3' version > > I checked trac.ini and I can see this line : > database = sqlite:db/trac.db > Is it good? > > Now trying a dump-to-sql / reload-from-sql : > sqlite3 trac.db .dump > trac.dump > rm trac.db > sqlite3 trac.db > .read trac.dump > .quit > chown apache ... > > Seems that it's better : commit is shown in timeline without > restarting apache and resync env (even if I got errors from times to > times). > Anyway, it's far better than before. > > > I didn't understand how to upgrade to 0.10.3 (I'm a noob in gentoo > admin), so unless I get some good pointers, I will stay like that :o) > > > Tks for support > > Nicolas arf : I still got the same errors. For my fist commit it worked fine, but for second commit, I had to restart apache and then resync env again :-(
According to the other answers, I think upgrading to 0.10.3 (or downgrading to 0.9.4) is the last solution. I know that this is not the purpose of this mainling-list but : I would appreciate some help/pointers with installing a version of trac that I can't see when I enter emerge -s trac Nicolas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
