Issue with svn bindings - Trac Users

Message from discussion Issue with svn bindings

Garrett McGrath

More options Nov 3 2006, 2:53 pm

From: "Garrett McGrath" <gmcgrath...@gmail.com>

Date: Fri, 3 Nov 2006 14:53:46 -0500

Local: Fri, Nov 3 2006 2:53 pm

Subject: Re: [Trac] Re: Issue with svn bindings

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

It means your svn Python bindings are broken in some way or another, the
problem is this never manifests quiet the same on each machine. It could
also mean that Neon (a SVN dependancy) isn't built correctly. My
recommendation. Find your neon install ( i can almost guarantee it's inside
the src folder for your svn install) and rename the folder. Go into that
folder and build new using the shared and static enables, also make sure
that neon is built against ssl. This will prevent svn from building neon
when it gets built. Then rebuild your svn by first doing a make clean and
make clean-swig-py. run ./configure (with any flags you want) do a make &&
make swig-py. then do a make install && make install-swig-py. That should
help get you on your way.

As an asside ensure that the versions of apr and apr-util that svn is
building against are correct and are infact the apache 2.2.3 ones (version
1.2.7 not 0.9.3 which is what svn comes with) I can almost guarantee that
svn is building those as well if you've unpacked the dependancies (so rename
them too and track down apr-config and apu-config and make sure they are the
right versions. apache 2.2.3 built those as apr-1-config and apu-1-config
on my system so be careful.)

I've actually written a bit about this on the svn mailing list because it
took me so long to fix, you can check there for more details (sorry I don't
have a link off hand.)

On 11/3/06, Christian Billen <cbil...@warmlyyours.com> wrote:

> Ah, looks like we're on to something:

> Python 2.4.4c1 (#2, Oct 11 2006, 21:51:02)
> [GCC 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> >>> import svn.repos
> Traceback (most recent call last):
> File "<stdin>", line 1, in ?
> File "svn/repos.py", line 19, in ?
> from libsvn.repos import *
> File "libsvn/repos.py", line 5, in ?
> import _repos
> ImportError: /usr/local/lib/libsvn_ra_dav-1.so.0: undefined symbol:
> SSL_shutdown

> What it means I am not sure yet but I'm sure you guys do :)

> C

> On 11/3/06 1:29 PM, "Garrett McGrath" <gmcgrath...@gmail.com> wrote:

> in python do this command:
> import svn.repos

> What do you get out?

> On 11/3/06, *Christian Billen* <cbil...@warmlyyours.com> wrote:

> Good afternoon,

> I am getting "Unsupported version control system "svn" when trying to
> access
> the time line or browse source from Trac 0.10 stable. I have Ubuntu 6.10,
> SVN 1.4 on apache 2.2.3 via mod_python.

> I have compiled subversion and the python bindings as such:

> ./configure --with-apr=/usr/local/apache2
> --with-apr-util=/usr/local/apache2
> --with-ssl --with-swig

> --with-neon=/us
> make
> make swig-py
> make install
> make install-swig-py

> The above steps complete successfully

> Finally I copied the libsvn and svn folder that were installed to
> /usr/local/lib/svn-python to /usr/local/python2.4/site-packages

> I can start python and do import svn without errors.

> However trac does not seem to think so.

> Internal Error

> Ticket changes event provider (TicketModule) failed:

> TracError: Unsupported version control system "svn"

> You may want to see the other kind of events from the Timeline

> I can only see Milestones and WikiChanges, Ticket and Repository fails
> with
> the same error.

> When I do browse source I see the same error "Unsupported version control
> system svn"

> Is there a step I am missing?

> Thank you

Reply to author Forward