Changes between Version 81 and Version 82 of TracModPython

Timestamp:

Aug 18, 2006, 5:44:19 PM (18 years ago)

Author:

Christian Boos

Comment:

Added a troubleshooting section for Subversion errors that are specific to mod_python.

TracModPython

@@ -69 +69 @@
 Note that if you're using '''Subversion''', you will often have to add the path to the Subversion bindings there, as the bindings are often found outside of the site-packages area (e.g. could be /opt/subversion-1.3.0/lib/svn-python).
 
+Be also careful about really using the !PythonPath directive, and ''not'' `SetEnv PYTHONPATH`, as the latter won't work.
 
 == Setting up multiple projects ==
@@ -214 +215 @@
 Also, seems like in FreeBSD some environment(maybe ldconfig) update is required right after installation of trac for trac-admin actually started working. I've missed the exact requirement, but noticed that immediately after installation trac-admin refused to do initenv, but after I relogged in to different shell - all worked perfectly. 
 
+=== Subversion issues ===
+
+If you get the following Trac Error `Unsupported version control system "svn"` only under mod_python, though it works well on the command-line and even with TracStandalone, chances are that you forgot to add the path to the Python bindings with the [TracModPython#ConfiguringPythonPath PythonPath] directive.
+
+If this is not the case, it's possible that you're using Subversion libraries that are binary incompatible with the apache ones (an incompatibility of the `apr` libraries is usually the cause). In that case, you also won't be able to use the svn modules for Apache (`mod_dav_svn`).
+
 === Using {{{/trac}}} root URL ===