Edgewall Software
Modify

Opened 19 years ago

Closed 19 years ago

Last modified 18 years ago

#2772 closed defect (worksforme)

No module named svn

Reported by: anonymous Owned by: Jonas Borgström
Priority: normal Milestone:
Component: general Version: 0.9.4
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Matthew Good)

Connecting to Subversion is not possible, but Trac does install correctly. I am using Subversion 1.3.0 with SWIG bindings 1.3.28. I have tried installing 0.10dev and it can't connect to subversion 1.3.0 either, but with different error.

I don't know whether I should try to install subversion 1.2.3 or just not worry about having subversion intregrated.

Traceback (most recent call last):
  File "/home/agsubversion/packages/lib/python2.3/site-packages/trac/web/cgi_frontend.py", line 130, in run
    dispatch_request(req.path_info, req, env)
  File "/home/agsubversion/packages/lib/python2.3/site-packages/trac/web/main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "/home/agsubversion/packages/lib/python2.3/site-packages/trac/web/main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "/home/agsubversion/packages/lib/python2.3/site-packages/trac/versioncontrol/web_ui/browser.py", line 78, in process_request
    repos = self.env.get_repository(req.authname)
  File "/home/agsubversion/packages/lib/python2.3/site-packages/trac/env.py", line 155, in get_repository
    from trac.versioncontrol.svn_fs import SubversionRepository
  File "/home/agsubversion/packages/lib/python2.3/site-packages/trac/versioncontrol/svn_fs.py", line 25, in ?
    from svn import fs, repos, core, delta
ImportError: No module named svn

Attachments (0)

Change History (6)

comment:1 by Matthew Good, 19 years ago

Resolution: worksforme
Status: newclosed

Installation support should be requested on the MailingList as indicated in the instructions when creating a ticket. You've probably installed the SVN Python bindings in a non-standard location that needs added to the PYTHONPATH, or you've installed them for the wrong Python version.

comment:2 by anonymous, 18 years ago

trac - as with most python software - doesn't document that you need to install mysterious svn python bindings nor does it indicate where to get them.

in reply to:  2 comment:3 by Matthew Good, 18 years ago

Description: modified (diff)

Replying to anonymous:

trac - as with most python software - doesn't document that you need to install mysterious svn python bindings nor does it indicate where to get them.

Did you bother to look at the documentation: TracInstall#VersionControlSystem

comment:4 by anonymous, 18 years ago

Different anon here. I read those directions but its still unclear to me ;-) It states that it uses SWIG which is included in the Subversion distribution. I already installed Subversion 1.3.2 so I should have SWIG then, correct? Or do you mean included within the source code distribution (vs. binary distribution)? And thus one is always required to perform a source code build because the SWIG stuff isn't included in Subversion binary distributions by default?

Further, you state "if installed with SWIG bindings…" - how can one determine if SWIG is already installed within Subversion? What files should I look for?

in reply to:  4 comment:5 by Emmanuel Blot, 18 years ago

Replying to anonymous:

I already installed Subversion 1.3.2 so I should have SWIG then, correct?

It would help if you specify which OS you're using, and which distribution in case you run Linux.

  • On Windows, the Python wrappers are available as an additionnal package, available from the same directory than the regular binaries.
  • On Linux, Python wrappers usually come within their own package (for ex. on Debian you need to install 'python-subversion' package)
  • If you install from the sources (rebuilding Subversion), tools, librairies, wrappers for various languages such as PERL and Python come altogether bundled within the same archive.

This is why you need to specify which kind of installation you're using.

how can one determine if SWIG is already installed within Subversion? What files should I look for?

SWIG is the tool to generate the PERL/Python/… wrappers from the original C/C++ source. You don't need SWIG if you do not want to recompile the wrappers from the source. The "SWIG wrappers" means (here) the Python-to-Subversion wrappers that have been generated with the help of SWIG.

Look in your Python site-packages directory: if the Python/Subversion wrappers have been installed, you should see two directories named "svn" and "libsvn".

Please ask further installation questions to the MailingList.

comment:6 by zafar466@…, 18 years ago

hello

iwant to install and configure svn, version 1.3.2 (r19776).plzz help me regarding this matter.iam using red hat linux enterprise.

its urgent. regards zafar

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.