[Pkg-libvirt-maintainers] Bug#697852: python-libvirt: should have a "lockstep" dependency on libvirt0

[Simon McVittie]

Package: python-libvirt
Version: 0.9.12-5
Severity: important

I upgraded libvirt-bin and libvirt0 to the version from experimental
without also upgrading python-libvirt. When I next tried to run virt-manager
it failed with:

> ImportError: /usr/lib/libvirt.so.0: version `LIBVIRT_PRIVATE_1.0.0'
> not found (required by /usr/lib/python2.7/dist-packages/libvirtmod.so)

Upgrading to python-libvirt/experimental resolved this.

It's OK for python-libvirt to use private symbols from libvirt0, because
it comes from the same source package; but if it's going to do that, then
it should have a strict dependency on libvirt0 (= ${binary:Version}) so
they always get upgraded together.

Regards,
    S

-- System Information:
Debian Release: 7.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages python-libvirt depends on:
ii  libaudit0           1:1.7.18-1.1
ii  libavahi-client3    0.6.31-1
ii  libavahi-common3    0.6.31-1
ii  libc6               2.13-38
ii  libcap-ng0          0.7.3-1
ii  libdbus-1-3         1.6.8-1
ii  libdevmapper1.02.1  2:1.02.74-6
ii  libgcrypt11         1.5.0-3
ii  libgnutls26         2.12.20-3
ii  libnl-3-200         3.2.7-4
ii  libnl-route-3-200   3.2.7-4
ii  libnuma1            2.0.8-1
ii  libsasl2-2          2.1.25.dfsg1-6
ii  libvirt0            1.0.1-4
ii  libxml2             2.8.0+dfsg1-7
ii  libyajl2            2.0.4-2
ii  python              2.7.3-3

Versions of packages python-libvirt recommends:
ii  libvirt-bin  1.0.1-4

python-libvirt suggests no packages.

-- no debconf information