I am running to pretty much dead end. It is extremely frustrating .... It seems that swig binding issue is one of the leading installation issues with trac and yet there is only a scattered documentation on this.
I am trying to post to swig, svn and python newsgroups but not expecting to get much help there. Robert On Jun 26, 7:50 am, Rob13 <[EMAIL PROTECTED]> wrote: > thank you for your reply, but I am getting a bit confused. I have > build originally subversion with > the following configure: > > ./configure --with-apr=/usr/local/apr --with-apr-util=/usr/local/apr -- > with-apxs > =/usr/sbin/apxs --with-berkeley-db=/usr/local/lib > > when I run cat config.log | grep PYTHON. > I get: PYTHON='/usr/bin/python' > and running "which python" also confirms this directory > so the subversion did use python 2.3.4. > > Given that you are saying that svn 1.4.3 comes already with swig > wrappers, > it should have worked. However it did not. (I also tried to rebuild > swig-py > but it was throwing gcc error so I could not rebuild it from within > the downloaded > svn source. When I did "swig -version" it reported 1.3.21 located in > usr/bin/swig. > > When I read that svn 1.4.3 only works with 1.3.25 of swig I assumed > this must > be the culprit and build swig 1.3.29, then rebuild svn from source > again with different > configure this time: > ./configure --with-apr=/usr/local/apr --with-apr-util=/usr/local/apr -- > with-apxs > =/usr/sbin/apxs --with-berkeley-db=/usr/local/lib --with-swig=/usr/ > local/swig1.3 > .29/bin/swig > > followed by building swig-py. The thing is this did not work either > and swig -version > still shows 1.3.21, but I am receiving the very same trac error as > before: > > Warning: Can't synchronize with the repository (Unsupported version > control system "svn". Check that the Python bindings for "svn" are > correctly installed.) > > Am I missing something here? > > Robert > > On Jun 26, 12:02 am, Christian Boos <[EMAIL PROTECTED]> wrote: > > > Rob13 wrote: > > > Hello, > > > > I know swig binding has been discussed on numerous > > > occasions but I have a very unique case that I cannot > > > seem to solve. Here it is: > > > > I have installed trac on Linux CentOS 4.x and everything > > > seems to work except svn browsing. It reports: > > > > Unsupported version control system "svn". Check that the Python > > > bindings for "svn" are correctly installed. > > > > What strange though is that I was able to install swig-py > > > and it created /svn-python bindings that I have then added to > > > PYTHONPATH. Further, I tried 1.3.25 and 1.3.29 version of swig > > > as per the recommendation for 0.11dev version of trac and > > > it still does not work. > > > > Furthermore, I run trac on other server where the swig-binding > > > installation worked without any need to download specific > > > version of swig (I just ran make swig-py from subversion 1.4.3 > > > source). > > > If all you need is 'make swig-py' and 'make install-swig-py'), then you > > don't need SWIG at all, as Subversion 1.4.3 comes with pre-generated > > wrappers. > > > > The two servers are identical except the python version. The server > > > where it worked is Python 2.4.3. The server where it does not (even > > > with trying different version of swig) runs Python 2.3.4. > > > If you have multiple versions of Python installed, be careful to > > configure subversion with the correct Python version, the one you're > > going to use the bindings with. > > Check with: cat config.log | grep PYTHON. > > > Please double check thehttp://trac.edgewall.org/wiki/TracSubversionpage. > > > -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
