Changes between Version 88 and Version 89 of TracSubversion

Timestamp:

Dec 30, 2010, 3:56:05 PM (13 years ago)

Author:

maddoxej

Comment:

—

TracSubversion

@@ -273 +273 @@
  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 into your site-packages folder, or add the above folder to your PYTHONPATH, 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 (an example on a FreeBSD installation, again: /usr/local/lib/pythonN.N/site-packages/). One simple solution for rpm-based operating systems, is to install the subversion-python bindings rpm. The [http://subversion.apache.org/packages.html#redhat official subversion site] points [http://summersoft.fay.ar.us/pub/subversion/latest/ here] to download those packages.
 
+ For Collabnet 1.3 on Windows the solution was {{{set PYTHONPATH=C:\csvn\lib\svn-python}}}
+
  If you get the message {{{ImportError: libsvn_swig_py-1.so.0: cannot open shared object file: No such file or directory}}} even though you can see the .so file in the correct place, then try {{{ldconfig -v}}} as root.