Comment 12 for bug 742186

On Mon, Mar 28, 2011 at 3:53 AM, Gary van der Merwe <email address hidden> wrote:
> qbzr <= 0.20 - Uses bzrlib configobj
> qbzr trunk r1356 - Uses python configobj
> qbzr >= trunk r1357 - Uses either python or bzrlib configobj
>
> Danie, you said that the issue was fix by installing python-configobj.
> If I understand everything correctly, the only way that that was
> possible, is if you had qbzr trunk version r1356 installed.  The ppa
> version of bzr that you are using does have bzrlib configobj according
> to Max, and then ever version of qbzr would have worked.  Please check
> the path of the copy of qbzr that is beening used by running bzr pulgins
> -v .

The issue is in the packaging. As you say, the ppa version of bzr that
you are using does have bzrlib configobj. But qbzr
0.20.0-1~bazaar1~maverick1 in the PPA is carrying a patch to use the
system lib:

$ head -n 1 debian/changelog
qbzr (0.20.0-1~bazaar1~maverick1) maverick; urgency=low
$ cat debian/patches/02-configobj.diff
=== modified file 'lib/util.py'
--- old/lib/util.py 2011-02-01 09:43:36 +0000
+++ new/lib/util.py 2011-02-06 12:48:37 +0000
@@ -51,7 +51,7 @@
     osutils,
     urlutils,
 )
-from bzrlib.util.configobj import configobj
+import configobj
 from bzrlib.plugins.qbzr.lib import trace
 from bzrlib.workingtree import WorkingTree
 from bzrlib.transport import get_transport