Changes between Version 38 and Version 39 of TracSubversion

Timestamp:

Mar 29, 2007, 8:57:45 AM (17 years ago)

Author:

Christian Boos

Comment:

Add a check list in the #Troubleshooting section

TracSubversion

@@ -149 +149 @@
 This kind of error seems to happen frequently. Sometimes it seems to be related to the Trac cache being out-of-sync and needing a manual `resync` (#2739, #3301, #3728); this can happen if the repository was rebuilt and its UUID hasn't changed. Sometimes it seems to be because the repository is temporarily unavailable (#2346), and sometimes, we simply don't know yet (#3773, #3861, #3875).
 
+==== Check list ====
+
+When there's some trouble using the Subversion bindings, 
+it usually help to perform the following checks:
+
+ 1. Verify that you can load the bindings using the Python interactive interpreter
+
+{{{
+$ python
+Python ...
+>>> from svn import core
+}}}
+If this succeeds, that's a good start.
+
+If it doesn't,  it usually means that your bindings are located in 
+a place they can't be loaded from. So either move the `svn` and `libsvn` 
+found in the /opt/subversion-xxx/lib/svn-python folder (or similar)
+into your site-packages folder, or add the above folder to your PYTHON_PATH, 
+or create a [http://docs.python.org/lib/module-site.html svn.pth] file 
+in your Python site-packages folder with the above folder path as its 
+single line content.
+
+ 2. Check the version
+{{{
+>>> (core.SVN_VER_MAJOR, core.SVN_VER_MINOR, core.SVN_VER_MICRO, core.SVN_VER_PATCH)
+(1, 4, 3, 3)
+}}}
+Verify that the version given back matches your expectation.
+
+ 3. Check that you're using the right binaries (Linux)
+
+Get the pid of the above running Python interpreter (i.e. once the
+binding is loaded), and get the list of the libraries used by looking at the
+corresponding map file.
+
+e.g.
+{{{
+cat /proc/10213/maps | grep .so | cut -d/ -f2- | sort -u
+}}}
+
+In particular, pay attention to the `.../lib/svn-python/libsvn/_core.so` file 
+and see if it's location seems to be consistent with both those of the other
+svn libraries (`.../lib/*.so`) and the location of the Python code part of the 
+bindings (`.../lib/svn-python/svn/core.py`).
+
+ 3. If you're using Apache / mod_python (Linux)
+
+Get a similar list of libraries, but this time for one of your httpd process.
+Then compare the two, and pay attention to any difference between the `svn` 
+libraries and the `apr` libraries. You ''have to'' have compatible APR libraries
+between Apache and Subversion, otherwise you risk to get a wide variety of subtle
+errors (e.g. #4985).
 
 == Known Issues ==