"Noah Kantrowitz" <[email protected]> writes: > Yes, you changed things and it needs to make sure the nothing bad has > happened.
Then, what's the point of allowing relative paths on trac.ini for repository_dir? Besides, what's the rationale for *refusing* to do certain things instead of just showing the prominent warning? (Trac refuses to browse the repository until the resync is done. It is happy showing the Timeline, though). I want to remove this check but first I'll like to be sure that there is no real requirement for a resync when trac+svn are moved elsewhere. Thanks Noah. >> Theoretically trac 0.11 supports relative paths for repository_dir. >> >> I change trac.ini, execute a resync and all seems okay. Copied both >> trac and svn directories maintaining the relative directory structure >> to other machine and after starting trac it complains with a message >> on all pages saying: >> >> Warning: Can't synchronize with the repository (The 'repository_dir' >> has changed, a 'trac-admin resync' operation is needed.). Look in the >> Trac log for more information. >> >> so I look into the database and it contains an absolute directory. It >> seems that trac admits the relative dir from trac.ini but converts to >> absolute before storing it into the database. >> >> Is this intended? -- Óscar --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
