Noah Kantrowitz wrote: > On a related not, can anyone say if #2611 is still seen with Subversion > 1.4 or not?
After a lot of turmoil, it would seem that I cannot reproduce the #2611 problem anymore. It's all stable on my site now, with subversion 1.4.0. I tried with and without the workaround mentioned with the "PythonInterpreter trac" setting in each of the apache vhost files, but that made no difference at all. My setup includes the following: trac-0.9.6 subversion-1.4.0 swig-1.3.27 apache2-2.2.0 apache2-mod_python-3.1.3 python-2.4.2 All on a SuSE Linux 10.1 box. I would have wanted to go back to subversion 1.3.0 to verify this, but I just haven't got the time. It's working for me now. Hope this helps /Lars > --Noah > > Manuzhai wrote: >> On 9/15/06, Rainer Sokoll <[EMAIL PROTECTED]> wrote: >>> if I upgrade subversion to 1.4 and dump/load the repositories to benefit >>> from subversion's new file format - will that affect trac (0.9.6) in any >>> way? >> Trac seems to work just fine for me with Subversion 1.4. But, I am >> running 0.10b1. However, the dump/load cycle doesn't matter; all that >> is hidden from Trac behind Subversion's API. >> >> Regards, >> >> Manuzhai >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
