Package: libneon27-gnutls
Version: 0.29.6-2
Severity: normal

Hi,

Following today's upgrade from 0.29.6-1 to 0.29.6-2, bzr is no longer
working for me, because the bzr-svn plugin fails to load, due to an
error in loading subvertpy, with an error message that points at
libneon27-gnutls:

roland@mirexpress ~/debian/fusionforge/trunk $ bzr info
bzr: ERROR: exceptions.ImportError: Unable to load subvertpy extensions: 
/usr/lib/libneon-gnutls.so.27: undefined symbol: ne_ssl_context_get_flag
[...]
  File "/usr/lib/python2.7/dist-packages/bzrlib/plugins/svn/workingtree.py", 
line 26, in <module>
    import subvertpy
  File "/usr/lib/python2.7/dist-packages/subvertpy/__init__.py", line 130, in 
<module>
    raise ImportError("Unable to load subvertpy extensions: %s" % e)
ImportError: Unable to load subvertpy extensions: 
/usr/lib/libneon-gnutls.so.27: undefined symbol: ne_ssl_context_get_flag
[...]

Downgrading to 0.29.6-2 fixes the problem.  It may be that the problem
lies in subvertpy, but my gut feeling is that the ABI was changed
incompatibly in libneon without a bump in the soname.

Roland.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libneon27-gnutls depends on:
ii  libc6             2.13-27
ii  libcomerr2        1.42.2-1
ii  libgnutls26       2.12.18-1
ii  libgssapi-krb5-2  1.10+dfsg~beta1-2
ii  libk5crypto3      1.10+dfsg~beta1-2
ii  libkrb5-3         1.10+dfsg~beta1-2
ii  libxml2           2.7.8.dfsg-7
ii  zlib1g            1:1.2.6.dfsg-2

Versions of packages libneon27-gnutls recommends:
ii  ca-certificates  20120212

libneon27-gnutls suggests no packages.

-- no debconf information

-- 
Roland Mas

If you're ever confused as to which mode you're in, keep entering the
<escape> key until vi beeps at you.  -- nvi manual page.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to