(following up on Trac users) On 8/3/2010 3:31 AM, Justin Moninger wrote:
I recently installed a new Trac instance on RHEL 5 (x86_64) and upgraded to the latest SVN from Collabnet 1.6.12. I'm not a python guy, but after some fiddling I got everything up and running perfectly, minus the SVN repo browser. Doing a trac-admin repository resync works great and loads my 450+ revisions. Before going back and adding the necessary SVN hooks I tried just viewing the repo via the repository browser. From tailing the log I get the following error:2010-08-02 17:32:07, 588 Trac[svn_fs] INFO: Failed to load Subversion bindings Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/Trac-0.12-py2.4.egg/trac/ versioncontrol/svn_fs.py", line 265, in __init__ _import_svn() File "/usr/lib/python2.4/site-packages/Trac-0.12-py2.4.egg/trac/ versioncontrol/svn_fs.py", line 68, in _import_svn from svn import fs, repos, core, delta File "/opt/CollabNet_Subversion/lib/svn-python/svn/fs.py, line 19, in ? from libsvn.fs import * File "/opt/CollabNet_Subversion/lib/svn-python/libsvn/fs.py, line 7, in ? import _fs ImportError: /opt/CollabNet_Subversion/lib/libsvn_ra_serf-1.so: undefined symbol: apr_file_buffer_set I tried Googling the problem for several hours, but to no avail. There were only a couple references to "undefined symbol: apr_file_buffer_set". I also tried installing/overriding the python/ svn bindings by installing the RHEL 1.4.x subversion-python RPM which resulted in the inability for Trac to read the repo since it was created with SVN 1.6. I guess my question is, do I just have bad bindings, or did Collabnet or subversion possibly remove something from the svn-python bindings which is used by Trac. My apologies for not going through the code more, but I'm just a Linux admin with a bit of Java and Perl knowledge.
This is simply a mismatch for the apr (or apr-util) library. The CollabNet libraries have been built against another (newer?) version of the APR than the one you have on your system (usually part of the httpd package). Try to see in their release notes which compatible version of //Apache// they advise you to use, and install and use that as well. Or simpler, use another web front end like trac.fcgi on top of lighttpd, as the latter doesn't use apr itself, so you won't have to deal with this .so hell ;-)
-- Christian
Best regards, Justin
-- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
