Re: [viewvc-users] ViewVC

Charles Hardin wrote:
> All,
> 
>     I am currently setting up ViewVC to tie in with subversion. My
> server is CentOS. I ran yum install subversion and everything went ok.
> I got python errors in ViewVC, so I went back and discovered it was
> using Python2.4 to run from, and the subversion install put them under
> /usr/lib/Python2.3/site-releases/svn. Python 2.4 is under
> /usr/local/lib so I copied the svn folder over to
> /usr/local/lib/Python2.4/site-releases/svn and the error changed
> slightly. I still appear to be missing part of the bindings. Errror
> below:
> 
> An Exception Has Occurred
> Python Traceback
> 
> Traceback (most recent call last):
>   File "/home/sforge/public_html/gamma/viewvc/lib/viewvc.py", line 3753, in main
>     request.run_viewvc()
>   File "/home/sforge/public_html/gamma/viewvc/lib/viewvc.py", line
> 259, in run_viewvc
>     import vclib.svn_ra
>   File "/home/sforge/public_html/gamma/viewvc/lib/vclib/svn_ra/__init__.py",
> line 23, in ?
>     from vclib.svn import Revision, ChangedPath, _datestr_to_date,
> _compare_paths, _cleanup_path
>   File "/home/sforge/public_html/gamma/viewvc/lib/vclib/svn/__init__.py",
> line 27, in ?
>     from svn import fs, repos, core, delta
>   File "/usr/local/lib/python2.4/site-packages/svn/fs.py", line 28, in ?
>     import libsvn.fs
> ImportError: No module named libsvn.fs
> 
> 
> I have checked all over my server and cannot find this file. A google
> search suggested make swig-py and make install-swig-py in the source
> directory to fix the problem, but as I installed from yum I dont have
> a source directory. I did try to use the current source release but
> ran into issues with APR, beyond the scope of this list and this
> particular problem. Is there anything else I should install from yum?

The Subversion Python bindings are broken into two modules:  "svn" and "libsvn".

"svn" contains submodules "repos", "fs", "core", etc. all written in pure
Python.  Files are named like

   svn/repos.py[c]    ### .pyc if byte-compiled already, .py otherwise
       fs.py[c]
       core.py[c]
       ...

"libsvn" contain submodules named similarly, but are C-compiled Python
extensions with Python-based wrappers.  Files are named like:

   libsvn/_repos.so
          _fs.so
          _core.so
          ...
          repos.py[c]
          fs.py[c]
          core.py[c]
          ...

I don't know much about CentOS, but is possible that yum dropped the "svn"
module in one place and the "libsvn" module elsewhere?  Can you ask yum to
list the file locations that it uses for the Subversion python bindings
package?  Maybe that will tell you were it stuck the "libsvn" stuff.

(For the record, this is really a conversation best had over on
[email protected], though.)

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2357522

To unsubscribe from this discussion, e-mail: [[email protected]].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkoj4U4ACgkQokEGqRcG/W6n6ACgppvZNIsLHoTgSS5dVkzF636G
odUAnRoDcXjzbzfOOYRbMP+3iX1se0TL
=oTCw
-----END PGP SIGNATURE-----