No module named configobj error with debian patched bzr-2.3.0

Bug #715067 reported by Gary van der Merwe
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
QBzr
Fix Released
Critical
Alexander Belchenko

Bug Description

In then debian bzr-2.3.0 package, bzrlib.util.configobj is removed with a patch. The qbzr debian package is patched to rather use pythons configobj, but if you install qbzr from source, it will show this error when you run it:

bzr: ERROR: No module named configobj
You may need to install this Python library separately.

We should try import the python configobj first, and only use the bzrlib copy as a fall back.

Related branches

summary: - No module named configobj error with debian bzr-2.3.0e
+ No module named configobj error with debian bzr-2.3.0
summary: - No module named configobj error with debian bzr-2.3.0
+ No module named configobj error with debian patched bzr-2.3.0
Revision history for this message
Alexander Belchenko (bialix) wrote :

I disagree. We should try to import copy from bzrlib first and only if it fails then use modules from python.

Revision history for this message
Gary van der Merwe (garyvdm) wrote : Re: [Bug 715067] Re: No module named configobj error with debian patched bzr-2.3.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/02/2011 11:31, Alexander Belchenko wrote:
> I disagree. We should try to import copy from bzrlib first and only if
> it fails then use modules from python.

For what reason? (Asking because I don't have a full understanding myself.)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAk1SYZoACgkQd/3EdwGKOh3afwCgtUwMHfUKNsMGhvC0tOV1RdNC
EwcAl33o7MNy6ra7y3KD0peVYVvYHC0=
=1S8T
-----END PGP SIGNATURE-----

Revision history for this message
Alexander Belchenko (bialix) wrote :

Gary van der Merwe пишет:
> On 09/02/2011 11:31, Alexander Belchenko wrote:
>> I disagree. We should try to import copy from bzrlib first and only if
>> it fails then use modules from python.
>
> For what reason? (Asking because I don't have a full understanding myself.)

For the consistency with bzrlib.

original bzrlib/config.py only tries to import as:

from bzrlib.util.configobj import configobj

Importing python-wide library first you potentially get versions
mismatch for non-patched bzr.

Revision history for this message
Alexander Belchenko (bialix) wrote :

Gary, your fix completelly broke qbzr + bzr.exe. After pulling lp:qbzr/0.20 I've got:

C:\work\Bazaar\plugins\qbzr>bzr qlog
bzr: ERROR: No module named configobj
You may need to install this Python library separately.

Huh?

Changed in qbzr:
importance: High → Critical
assignee: nobody → Alexander Belchenko (bialix)
status: Confirmed → In Progress
Changed in qbzr:
status: In Progress → Fix Released
Revision history for this message
Eshwar Andhavarapu (eshwar.andhavarapu) wrote :

Version 1.1.2 Bazaar Explorer

Qbzr 0.20.0

bzrlib 2.4b1

PyQt 4.7.2

Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 715067] Re: No module named configobj error with debian patched bzr-2.3.0

Eshwar Andhavarapu пишет:
> Version 1.1.2 Bazaar Explorer
>
> Qbzr 0.20.0
>
> bzrlib 2.4b1

You need either qbzr 0.20.1 then or using qbzr from trunk (branch lp:qbzr).

--
All the dude wanted was his rug back

Revision history for this message
Eshwar Andhavarapu (eshwar.andhavarapu) wrote :

Well i figured the problem started when i used the beta ppa and not the daily one. so if we stick to the beta ppa, the bug exists. And hence the reason for reporting it :)!

As much as getting the new package fixes the problem, its an issue that the package is not in the same ppa as the other 'good' ones...

Revision history for this message
Alexander Belchenko (bialix) wrote :

Eshwar Andhavarapu пишет:
> Well i figured the problem started when i used the beta ppa and not the
> daily one. so if we stick to the beta ppa, the bug exists. And hence the
> reason for reporting it :)!
>
> As much as getting the new package fixes the problem, its an issue that
> the package is not in the same ppa as the other 'good' ones...

Thank you for reporting this. Unfortunately I'm not in charge of PPA
job, so I can't comment on this. The bug is already fixed in qbzr
upstream, I think it's matter of time when the fix will appear in PPA-ed
version.

Have a nice day

--
All the dude wanted was his rug back

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.