Rebuild the subversion package against the version of libneon that's
linked to openssl rather than gnutls to work around this issue.
Instructions (run as a normal user, NOT AS ROOT):
$ mkdir -p tmp && cd tmp
$ apt-get source subversion
$ apt-get build-dep subversion
$ apt-get install fakeroot libneon26-dev
$ cd subversion-1.5.1dfsg1
$ DEB_BUILD_OPTIONS="nocheck no-javahl no-apache no-ruby" fakeroot debian/rules
binary
$ sudo dpkg -i ../libsvn1_1.5.1dfsg1-1ubuntu2_i386.deb
../subversion_1.5.1dfsg1-1ubuntu2_i386.deb
../subversion-tools_1.5.1dfsg1-1ubuntu2_all.deb
You should now see that the subversion binary is linked to libneon not
libneon-gnutls:
$ ldd `which svn` | grep neon
libsvn_ra_neon-1.so.1 => /usr/lib/libsvn_ra_neon-1.so.1 (0xb7d40000)
libneon.so.26 => /usr/lib/libneon.so.26 (0xb7d21000)
... and it should work correctly when you connect to your client-
certificate-protected repositories.
[ Note that you may want to remove the openjdk-6-jre and openjdk-6-jdk
packages if they were installed by "apt-get build-dep subversion",
especially if you use sun-java6-{jre,jdk} instead. If you don't use Java
(or only use Java applets in your web browser), though, you probably
don't care and can just ignore them. ]
--
svn over https with client certificates broken (regression in intrepid)
https://bugs.launchpad.net/bugs/294648
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
