Package: bzr-gtk Version: 0.95.0+bzr649-1 Severity: serious I get this error whenever I run bzr lately:
Unable to load plugin 'gtk'. It requested API version (1, 15, 0) of module <module 'bzrlib' from '/usr/lib/python2.5/site-packages/bzrlib/__init__.pyc'> but the minimum exported version is (1, 17, 0), and the maximum is (1, 17, 0) (Yes, I know it's not an official Debian version of bzr, but it seems like something should be done to prevent this kind of thing, at least once it's noticed -- though possibly it would help to have the nightly bzr builds numbered e.g. 1.17~dev+XXXX+YYY instead of 1.16+XXXX+YYY?) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bzr-gtk depends on: ii bzr 1.16+4523+117 easy to use distributed version co ii python 2.5.4-2 An interactive high-level object-o ii python-central 0.6.11 register and build utility for Pyt ii python-glade2 2.14.1-2 GTK+ bindings: Glade support ii python-gtk2 2.14.1-2 Python bindings for the GTK+ widge ii python-notify 0.1.1-2+b1 Python bindings for libnotify Versions of packages bzr-gtk recommends: pn bzr-dbus <none> (no description available) ii python-cairo 1.8.4-3 Python bindings for the Cairo vect ii python-gnome2-desktop 2.24.1-1 Python bindings for the GNOME desk ii python-gnomekeyring 2.24.1-1 Python bindings for the GNOME keyr pn python-gtksourceview2 <none> (no description available) pn python-nautilus <none> (no description available) pn seahorse <none> (no description available) Versions of packages bzr-gtk suggests: pn bzr-avahi <none> (no description available) ii bzr-loom 1.4.0~bzr97-1 Focused patch plugin support for B pn bzr-search <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
