Changes between Version 111 and Version 112 of TracSubversion

Timestamp:

Sep 2, 2012, 7:36:22 PM (12 years ago)

Author:

Christian Boos

Comment:

in the check list as well, differentiate between pre and post 1.0 for enabling the svn components; also move some Mac OS X specific stuff out of the way

TracSubversion

@@ -262 +262 @@
  A good way to diagnose a //DLL load failed// error is to use the [http://www.dependencywalker.com/ depends.exe] tool from the console in which you'd run python.exe, and do a `depends.exe absolute-path-to/python.exe` instead. Then, press `F7` (//Start Profiling...// - you need at least version 2.0 of depends.exe) and type `from svn import core` at the Python prompt in the new cmd window. This will try to load the bindings, but this time you'll be able to see //why// this fails, by spotting the .DLLs shown in red in the Module list, and there are really lots of options here ;-)
 
+ '''Mac OS X Users'''
+
+ Subversion 1.5.X defaults installs in /opt/subversion/. The svn.pth solution works up to this point, but Trac will still be unhappy: you will need to copy `/opt/subversion/lib/svn-python/svn` &  `/opt/subversion/lib/svn-python/libsvn` on top of  `/System/Library/Frameworks/Python.framework/Versions/Current/Extras/lib/python/libsvn` and `/System/Library/Frameworks/Python.framework/Versions/Current/Extras/lib/python/svn`.
+
 
  2. Check the version
@@ -281 +285 @@
  In particular, pay attention to the `.../lib/svn-python/libsvn/_core.so` file and see if its 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`).
 
- 4. Have you got SVN disabled in your trac.ini file for some reason.
-
- For whatever reason, you may have trac.versioncontrol.* set to disabled in your trac.ini file. If so, set it/them to enabled (or simply delete the offending lines, since I believe they are enabled by default.)
+ 4. Have you got SVN disabled in your trac.ini file?
+
+ Starting with Trac 1.0, the Subversion components need to be explicitly enabled. See [#tracopt] above, if you haven't yet.
+
+ Before Trac 1.0, the Subversion specific modules were always enabled, but even then it could happen that for some reason, people had explicitly disabled those and possibly forgot about it. If so, set it/them to enabled (or simply delete the offending lines, since I believe they are enabled by default.)
  {{{
 [components]
@@ -293 +299 @@
 trac.versioncontrol.svn_prop.subversionpropertyrenderer = enabled
  }}}
-
-'''And if it doesnt....??'''
-
-(Mac OS X) Subversion 1.5.X defaults installs in /opt/subversion/. The svn.pth solution works up to this point, but Trac will still be unhappy: you will need to copy /opt/subversion/lib/svn-python/svn &  /opt/subversion/lib/svn-python/libsvn on top of  /System/Library/Frameworks/Python.framework/Versions/Current/Extras/lib/python/libsvn and /System/Library/Frameworks/Python.framework/Versions/Current/Extras/lib/python/svn. 
+ (so again, the above module `svn_fs`/`svn_prop` names are only valid before Trac 1.0, see [#tracopt] starting from 1.0)
 
  3. If you're using Apache / mod_python (Linux/Windows) (first tip)