Changes between Version 4 and Version 5 of TracSubversion
- Timestamp:
- Mar 27, 2006, 11:27:13 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracSubversion
v4 v5 63 63 which can be fixed by applying this 64 64 [/trac/ticket/2472#change_12 patch] to 65 `subversion/bindings/swig/python/svn/core.py` 65 `subversion/bindings/swig/python/svn/core.py` [[BR]] 66 Should be fixed in Subversion 1.3.1 (!r17992). 66 67 * Issue #2620 (memory leak) [[BR]] 67 68 which can be fixed by applying this 68 69 [/trac/ticket/2620#change_10 patch] to 69 `subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c`. 70 `subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c`. [[BR]] 71 Should be fixed in Subversion 1.3.1 (!r18230). 70 72 71 73 With those fixes, I've been able to use the Subversion backend … … 81 83 as explained in [/trac/ticket/2611#change_21 here]. 82 84 It should be emphasized that a compatible version of SWIG 83 must be used (`1.3.24`, `1.3.25` and possibly(?) `1.3.28`). 85 must be used (`1.3.24`, `1.3.25`). [[BR]] 86 Should be fixed in Subversion 1.3.1 (!r18721). 84 87 85 Using Subversion 1.3.0 and SWIG 1.3.28 causes no problems or issues described above and requires no modifications to the stock code. 88 Someone wrote: ''Using Subversion 1.3.0 and SWIG 1.3.28 causes no problems or issues described above and requires no modifications to the stock code.'' 89 90 I'd be interested to see what backs up the above claim. 91 It doesn't seem to me that either 1.3.0 or 1.3.1 actually support 92 SWIG 1.3.28. 93 However, the Subversion trunk does, and probably 1.3.2 will too 94 (see [http://svn.collab.net/repos/svn/branches/1.3.x/STATUS STATUS]). 95 [[BR]] --cboos 96 97 98 ==== Trac and Subversion 1.3.1 ==== 99 100 As mentioned above, the issues found with 1.3.0 should be fixed 101 by 1.3.1. 102 However, I've not ''yet'' tried 1.3.1. so I can't tell for sure 103 that there won't be any issues... 104 86 105 87 106 == Asking for More Support About Subversion ==