| 130 | | Note that the notes below about Subversion releases below 1.4 are mostly there for historical reasons. Everyone should be using at least 1.6.x these days. We make no guarantee about running an old version of Subversion with a recent version of Trac, though there are good chances that Subversion 1.4 still works with Trac 0.13dev. |
| 131 | | |
| 132 | | === Trac and Subversion 1.0 === |
| 133 | | This is the oldest supported Subversion version. |
| 134 | | |
| 135 | | === Trac and Subversion 1.1 === |
| 136 | | This release introduced the `fsfs` repository backend, |
| 137 | | which is to be preferred over the `bdb` one (see #571 for example). |
| 138 | | When creating a repository with this Subversion version, |
| 139 | | take care of using the `--fs-type fsfs` switch with the `svnadmin create` |
| 140 | | command. |
| 141 | | Version 1.1.4 is the last stable one for that maintenance branch. |
| 142 | | |
| 143 | | === Trac and Subversion 1.2 === |
| 144 | | This release makes the `fsfs` storage the default. |
| 145 | | Version 1.2.3 is the last stable one for that maintenance branch. |
| 146 | | |
| 147 | | If you switched from a previous version to this one, chances are that you had |
| 148 | | a Berkeley DB repository. It would be a good idea to switch that repository |
| 149 | | to the FSFS backend. google:svn+convert+bdb+to+fsfs. |
| 150 | | |
| 151 | | === Trac and Subversion 1.3 === |
| 152 | | This is the newest major release for Subversion, and it is currently |
| 153 | | support by Trac 0.9.x and beyond, with a few caveats. |
| 154 | | |
| 155 | | ==== Trac and Subversion 1.3.0 ==== |
| 156 | | |
| 157 | | There are a few known issues with the stock 1.3.0 version: |
| 158 | | * Issue #2472 (spurious exception) [[BR]] |
| 159 | | which can be fixed by applying this |
| 160 | | [/trac/ticket/2472#change_12 patch] to |
| 161 | | `subversion/bindings/swig/python/svn/core.py` [[BR]] |
| 162 | | Should be fixed in Subversion 1.3.1 (!r17992). |
| 163 | | * Issue #2620 (memory leak) [[BR]] |
| 164 | | which can be fixed by applying this |
| 165 | | [/trac/ticket/2620#change_10 patch] to |
| 166 | | `subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c`. [[BR]] |
| 167 | | Should be fixed in Subversion 1.3.1 (!r18230). |
| 168 | | |
| 169 | | With those fixes, I've been able to use the Subversion backend |
| 170 | | flawlessly "in production", since end of January 2006. |
| 171 | | |
| 172 | | However, some people are seeing yet another problem, which requires |
| 173 | | one more fix: |
| 174 | | * Issue #2611 (intermittent fatal error, manifesting itself with `"argument number 0: a 'apr_pool_t *' is expected"` messages in the log and segfault of the apache server) [[BR]] |
| 175 | | was supposedly fixed by applying this |
| 176 | | [attachment:ticket:2611:application_pool_race_condition_fix.txt patch] to |
| 177 | | `subversion/bindings/swig/include/proxy_apr.swg`. |
| 178 | | Note that after applying this patch, the SWIG bindings would have to be regenerated, |
| 179 | | as explained [comment:ticket:2611:16 here]. |
| 180 | | It should be emphasized that a compatible version of SWIG |
| 181 | | must be used (`1.3.24`, `1.3.25`). [[BR]] |
| 182 | | The issue was supposed to be fixed in Subversion 1.3.1, as the above patch was integrated as !r18721, but actually the patch was not enough to solve the issue. See below. |
| 183 | | |
| 184 | | ==== Trac and Subversion 1.3.1 ==== |
| 185 | | |
| 186 | | As mentioned above, the issues found with 1.3.0 should be fixed |
| 187 | | by 1.3.1. This is mostly true, except for #2611. |
| 188 | | |
| 189 | | '''Issue #2611 was confirmed to still exists in Subversion 1.3.1''' and also in the stock 1.3.2, |
| 190 | | when compiled using the pre-generated bindings that were produced using SWIG 1.3.25[[br]] |
| 191 | | So it seems the patch discussed above was not enough to solve the problem. |
| | 130 | Note that the notes below about Subversion releases below 1.6 are mostly there for historical reasons. Everyone should be using at least 1.6.x these days. We make no strong guarantee about running an old version of Subversion with a recent version of Trac, though there are good chances that Subversion 1.4 still works with Trac 0.13dev. |
| | 131 | |
| | 132 | Note that Trac always had issues with Subversion repositories using the Berkeley DB backend. If you happen to have such a repository, it would be a good idea to switch it to the FSFS backend if you intend to use it together with Trac. See google:svn+convert+bdb+to+fsfs. |
| | 133 | |
| | 134 | === Trac and Subversion 1.4 === |
| | 135 | |
| | 136 | Trac used to work well with Subversion 1.4. |
| | 137 | |
| | 138 | This is now the oldest supported Subversion version (older versions might work, see [[.@105#TracandSubversion1.0|version 105]] of this page, but we make no guarantee). |
| | 139 | |
| | 140 | I've noticed that there has been some improvements to the `ra` layer ... unfortunately not available yet for the Python bindings |
| | 141 | |
| | 142 | Also, that version supports SWIG 1.3.29, but so far I used the 1.3.25 pre-generated wrappers that are bundled with the tarball. |
| | 143 | |
| | 144 | '''Issue #2611 was [comment:ticket:2965:14 confirmed] to be still be present for 1.4 (and probably newer versions of svn as well). |
