•  
      request #9081 With SVN 1.8, Tuleap SVN plugin user interface displays an exception
    Infos
    #9081
    Marc TERRIER (mterrier)
    2018-05-07 15:46
    2016-04-18 15:30
    9308
    Details
    With SVN 1.8, Tuleap SVN plugin user interface displays an exception

    When SVN 1.8 is installed, the user interface of the Tuleap SVN plugin displays the following exception, right from the start, before the user has done anything:

    An Exception Has Occurred
    
    Python Traceback
    
    Traceback (most recent call last):
      File "/usr/share/viewvc/lib/viewvc.py", line 3814, in main
        request.run_viewvc()
      File "/usr/share/viewvc/lib/viewvc.py", line 296, in run_viewvc
        import vclib.svn
      File "/usr/share/viewvc/lib/vclib/svn/__init__.py", line 27, in <module>
        from svn import fs, repos, core, delta
    ImportError: No module named svn
    
    
    SCM/Subversion
    8.13
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    Declined
    2018-05-07
    Attachments
    Empty
    References

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2018-05-07 15:46
    Declining this in favor of request #11467.

    It looks like the Subversion 1.8 from Wandisco has been built against Python 2.7 so it does not work out of the box.

    • Status changed from Verified to Declined
    • Close date set to 2018-05-07
    User avatar
    Marc TERRIER (mterrier)2016-04-18 15:50

    The machine I tested on runs CentOS 6.7. Only Subversion and related packages, such as mod_dav_svn, have been updated to 1.8. Yes, subversion-python is installed (1.8.15), and no, it doesn't change anything.

    
     
    User avatar
    Thomas Gerbet (tgerbet)2016-04-18 15:41
    last edited by: Thomas Gerbet (tgerbet) 2016-04-18 15:44
    In CentOS 7, the Subversion package does not directly provide the Python bindings. I'm guessing that's the same for your package. Did you try to install subversion-python?

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Marc TERRIER (mterrier)2016-04-18 15:40
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes