Fair enough. I actually addressed the error message that occurred on my installation when I ran trac-admin resync. The error message was something along the lines of "svn not a valid version control" if I recall correctly. When I traced this error and brought it to the attention of this group, I was forwarded to a place where it was consistently stated that my python-swig bindings weren't properly in place.
This actually confused me, since I would have been under the impression that if my python bindings weren't properly set up that I'd see far worse than an error when I run the resync command and only the resync command. What may have been occurring is that resync is running correctly and then it spits out an error condition after the fact. It ends up that our SVN repository has quite a few changesets -- enough where it takes about 20 minutes to reload the node_change table from scratch. The "solution" I had always gone to was deleting all entries in the node_change table and just loading the timeline view via the web. For some reason I had convinced myself that there was a resync call that occurred in the code executed by trac, but it could have been that the resync command was working but it was just slow. In any case, this resync bit had nothing to do with the ability of Trac working with a remote repository, I just mentioned it as really being the only problem I've had with my Trac installation --- one that had me thinking I might consider a more "robust" backend like postGRES or mySQL. If there's something about setting up the SVNSYNC that you want to know more about --- which is different (in my mind at least) than the problem I have with trac-admin <path-to-env> resync, please let me know and I'll try to clarify. Best, Vincent ----- Original Message ---- From: jmt4b04d4v <[EMAIL PROTECTED]> To: Trac Users <[email protected]> Sent: Wednesday, August 1, 2007 1:06:27 AM Subject: [Trac] Re: Remote SVN Repository followup On 31 jul, 16:51, cobwebsmasher <[EMAIL PROTECTED]> wrote: > Hi. Saw a thread about trying to use remote SVN Repositories and wanted to > throw my 2 cents in, apologies if the 2 cents are an unnecessary tip. This 2 cents can be really valuable (for documentation purposes in this ML). > My understanding is that Trac HAS to be pointing to a local version of SVN. > I'm not sure why it would be an issue to refer to an NFS mount of said SVN > repository (well I can think of a few reasons, but that's not what I'm here > to talk about), but I've been warned off of that path. > > The path I ended up taking was utilizing svnsync > (http://svn.collab.net/repos/svn/trunk/notes/svnsync.txt) > > Using svnsync to create a read only repository on the machine that my Trac > installation lived on (and pointed to) works wonderfully. OCASSIONALLY, I > have run into issues where the node_changes database goes wonky and I have to > clear those entries and let Trac rebuild them again (using trac-admin resync > supposedly, but I always seem to get a strange error message). As this solution seems more naturally than using Remote SVN Access (RA), I think it's worth to mention more about the error message you pointed, maybe it can be fixed, maybe it could prevent us from using this solution. Best regards, -------------------------------------------------------- Johans Marvin Taboada Villca -`^_^´- .o0O( 2007-04-24, Bienvenida Bebecita ) -------------------------------------------------------- Adm. Laboratorio de Desarrollo de Software Carreras de Informática y Sistemas UMSS, Cochabamba Bolivia -------------------------------------------------------- ____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
