Announcement

Collapse
No announcement yet.

Debian 7.1: kdesvn/rapidsvn libraries links bloken

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Debian 7.1: kdesvn/rapidsvn libraries links bloken

    Hi, I have a Debian 7.1 (Squeeze) OS with subversion client packages installed from wandisco repo (i.e. libsvn1 version 1.8.1-1+WANdisco).
    When I try to launch svn clients provided by debian repository, like kdesvn or rapidsvn, they fail complaining
    error while loading shared libraries: libsvn_client-1.so.1: cannot open shared object file: No such file or directory

    In order to make kde and rapidsvn work I had to manually symlink some of the libraries provided by libsvn1, namely
    • /usr/lib/libsvn_client-1.so.1
    • /usr/lib/libsvn_diff-1.so.1
    • /usr/lib/libsvn_fs-1.so.1
    • /usr/lib/libsvn_ra-1.so.1
    • /usr/lib/libsvn_repos-1.so.1
    • /usr/lib/libsvn_subr-1.so.1
    • /usr/lib/libsvn_wc-1.so.1
    • /usr/lib/libsvn_delta-1.so.1


    I've seen a guy complaining for the same on kdesvn issue tracker, and the solution was replacing wandisco package with the distribution one. I hope filing the issue here could lead to better integration.
    Cheers
    Davide

  • #2
    Same for me, still now with Ubuntu saucy 13.10 (64bit)...

    Originally posted by davide.cavestro View Post
    Hi, I have a Debian 7.1 (Squeeze) OS with subversion client packages installed from wandisco repo (i.e. libsvn1 version 1.8.1-1+WANdisco).
    When I try to launch svn clients provided by debian repository, like kdesvn or rapidsvn, they fail complaining
    error while loading shared libraries: libsvn_client-1.so.1: cannot open shared object file: No such file or directory

    In order to make kde and rapidsvn work I had to manually symlink some of the libraries provided by libsvn1, namely
    • /usr/lib/libsvn_client-1.so.1
    • /usr/lib/libsvn_diff-1.so.1
    • /usr/lib/libsvn_fs-1.so.1
    • /usr/lib/libsvn_ra-1.so.1
    • /usr/lib/libsvn_repos-1.so.1
    • /usr/lib/libsvn_subr-1.so.1
    • /usr/lib/libsvn_wc-1.so.1
    • /usr/lib/libsvn_delta-1.so.1


    I've seen a guy complaining for the same on kdesvn issue tracker, and the solution was replacing wandisco package with the distribution one. I hope filing the issue here could lead to better integration.
    Cheers
    Davide

    Comment


    • #3
      Hi,

      Just wondering if apt shows any dependencies or anything that needs fixing (but won't be due to available versions) showing at all?

      Comment


      • #4
        Hi,

        no other dependencies are broken, and the SVN binary is the only one to be non-standard (i.e. not included in the official Ubuntu 'saucy salamander' distribution, which includes instead svn 1.7.9).
        I executed all the packages fix commands like "sudo apt-get autoclean", "sudo apt-get autoremove", "sudo apt-get update && sudo apt-get upgrade", but everything is fine.
        The problem is that to use kdesv or rapidsvn, one has to symlink the mentioned libraries, otherwise these svn related softwares won't work.

        I also have the same issue on Ubuntu 13.10 (32bit).

        Cheers


        P.S.: Do someone know any simple and straightforward way to "undo" the SVN binary replacement? I mean how to remove the WANDisco additional repository for apt, and to return to the official svn 1.7.9 binary included in Ubuntu 13.10?
        That's also a problem for me, because when I try to remove the additional WANDisco repo, the apt system complains about unresolved dependencies and I can't use svn anymore, until I re-add the WANDisco repo (with the new svn binary) and then everything works fine again (just because I already symlinked the mentioned libraries of course).

        Comment


        • #5
          Thanks for that, I'll pass on the above and see if there's anything we can do about that one and keep you posted.

          As for removing it, probably best to sudo apt-get remove --auto-remove subversion before commenting or removing the repo from your sources.list as that way there shouldn't be anything installed from that repo to cause dependency issues. You should then be able to update and install the standard version without issue.

          Hope that helps.

          Comment


          • #6
            It seems the problem is just different library symlinks, I worked around the problem with these:

            cd /usr/lib
            sudo ln -s libsvn_subr-1.so.0 libsvn_subr-1.so.1
            sudo ln -s libsvn_diff-1.so.0 libsvn_diff-1.so.1
            sudo ln -s libsvn_fs-1.so.0 libsvn_fs-1.so.1
            sudo ln -s libsvn_ra-1.so.0 libsvn_ra-1.so.1
            sudo ln -s libsvn_repos-1.so.0 libsvn_repos-1.so.1
            sudo ln -s libsvn_wc-1.so.0 libsvn_wc-1.so.1

            Comment


            • #7
              Hi, sorry we didn't come back to you and really glad you found a workaround - thanks very much for letting us know

              Comment


              • #8
                Sorry, that's the very same thing we did, but it's quite a "dirt" solution.
                I'd like to signal the problem to who builds the package to avoid to have to manually symlink those libraries.

                Originally posted by skaplon View Post
                It seems the problem is just different library symlinks, I worked around the problem with these:

                cd /usr/lib
                sudo ln -s libsvn_subr-1.so.0 libsvn_subr-1.so.1
                sudo ln -s libsvn_diff-1.so.0 libsvn_diff-1.so.1
                sudo ln -s libsvn_fs-1.so.0 libsvn_fs-1.so.1
                sudo ln -s libsvn_ra-1.so.0 libsvn_ra-1.so.1
                sudo ln -s libsvn_repos-1.so.0 libsvn_repos-1.so.1
                sudo ln -s libsvn_wc-1.so.0 libsvn_wc-1.so.1

                Comment


                • #9
                  I believe there's now a patch for Debian based distros which should resolve this, I've just raised a task to get that added to our binaries - I'll update when it's done. Basically it comes down to the differences between the SVN packages that are installed by apt and the ones installed from our site/repo. The third party apps are built for the binaries in apt, which are older than the ones we offer - that's why they're looking for different libraries.

                  I'll update this thread once things are sorted.

                  Comment

                  Working...
                  X