Okay, now you are just making things confusing! ;) Doing so yields the following result:
1.4.2 which I am struggling to understand... since subversion outputs v1.5.5 when you browse the repo... and was clearly built from 1.5.5 source... however, to add more to the mix, if I do "yum list subversion" it also reports 1.4.2??? could there be multiple subversions installed on the server in different locations (I know this is the trac user group...) and different things are pulling from different installations?? Thanks... On May 10, 7:31 am, Emmanuel Blot <[email protected]> wrote: > > yes, I have already rebuilt the swig bindings... svn shipped with and > > built v1.3.29... a trac/svn page said this was a bad version, so I had > > manually rebuilt them at v1.3.25, the trac recommended version, but > > still have he same issue... > > Are you sure your system does not have an older version of the Python > bindings that could be loaded and used instead of the one you built? > > Try loading SVN bindings from Python interactive command prompt and > get the actual SVN library revision > > python > import svn.core > print "%d.%d.%d" % (svn.core.SVN_VER_MAJOR, svn.core.SVN_VER_MINOR, > svn.core.SVN_VER_MICRO) > > be sure to run "python" with the same uid as the web server. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
