explorer should invoke qbzr with same bzr

Bug #656072 reported by Gordon Tyler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Explorer
Fix Released
Medium
Gordon Tyler

Bug Description

I have bzr 2.2.0 installed on my system and bzr.dev branched into my working area. If I invoke bzr-explorer using bzr.dev, when it invokes qbzr commands such as qconfig, it uses the bzr 2.2.0 installed at the system level instead of bzr.dev.

This means that if I am doing combined development on bzr and qbzr, with changes in bzr that the changes in qbzr depend on, I cannot test using bzr-explorer because it will crash. For example, say I have added the mergetools module to bzrlib in bzr.dev, if I reference that from a qbzr command, I can use that qbzr command from the commandline in my working area just fine but if I try to invoke that qbzr command from bzrdev explorer then it fails with an ImportError for the mergetools module.

Relevant section from bzr.log:

Wed 2010-10-06 20:44:23 -0400
0.152 bazaar version: 2.3.0dev2
0.152 bzr arguments: [u'explorer']
0.253 failed to load compiled extension: No module named _static_tuple_c
0.254 failed to load compiled extension: cannot import name _btree_serializer_pyx
0.260 looking for plugins in C:/Users/Owner/AppData/Roaming/bazaar/2.0/plugins
0.260 looking for plugins in C:\dev\bzr\mergetools\bzrlib\plugins
0.274 encoding stdout as sys.stdout encoding 'cp437'
0.394 failed to load compiled extension: No module named _rio_pyx
0.398 failed to load compiled extension: No module named _dirstate_helpers_pyx
0.420 failed to load compiled extension: No module named _known_graph_pyx
0.632 failed to load compiled extension: No module named _bencode_pyx
0.696 loading explorer extensions for clothes [u'Bazaar support', u'Register on Launchpad']
0.754 setting preference toolbar-contents to expanded (was expanded)
0.756 setting preference workingtree-default-to-edit to True (was True)
0.756 setting preference custom-dialogs to true (was true)
0.756 setting preference language to en_US (was en_US)
0.756 setting preference location-selector-style to tree (was tree)
0.806 failed to load compiled extension: No module named _chk_map_pyx
0.823 failed to load compiled extension: No module named _annotator_pyx
0.828 failed to load compiled extension: No module named _knit_load_data_pyx
0.854 failed to load compiled extension: No module named _groupcompress_pyx
4.383 Deprecated function called
Called from:
  File "C:\dev\bzr-explorer\trunk\lib\app_suite.py", line 120, in lookup
    result = self._lookup_here(cmd_id, context, location_type)
  File "C:\dev\bzr-explorer\trunk\lib\app_suite.py", line 138, in _lookup_here
    return command_to_args(result, context)
  File "C:\dev\bzr-explorer\trunk\lib\app_suite.py", line 150, in command_to_args
    return shlex_split_unicode(command_to_expanded(template, context))
  File "C:\dev\bzr\mergetools\bzrlib\symbol_versioning.py", line 98, in decorated_function
    trace.mutter_callsite(4, "Deprecated function called")

Wed 2010-10-06 20:44:27 -0400
0.042 bazaar version: 2.2.0
0.042 bzr arguments: [u'qconfig']
0.075 looking for plugins in C:/Users/Owner/AppData/Roaming/bazaar/2.0/plugins
0.075 looking for plugins in C:/Program Files (x86)/Bazaar/plugins
0.076 Plugin name explorer already loaded
0.076 Plugin name qbzr already loaded
0.153 encoding stdout as osutils.get_user_encoding() 'cp1252'
0.204 Traceback (most recent call last):
  File "C:\dev\qbzr\mergetools\lib\commands.py", line 166, in run
  File "C:\dev\qbzr\mergetools\lib\commands.py", line 504, in _qbzr_run
  File "bzrlib\lazy_import.pyo", line 122, in __call__
  File "bzrlib\lazy_import.pyo", line 89, in _replace
  File "bzrlib\lazy_import.pyo", line 192, in _import
  File "C:\dev\qbzr\mergetools\lib\config.py", line 27, in <module>
ImportError: cannot import name mergetools

Related branches

Gordon Tyler (doxxx)
description: updated
description: updated
Revision history for this message
Alexander Belchenko (bialix) wrote : Re: [Bug 656072] [NEW] explorer should invoke qbzr with same bzr

Can you enable debug mode and check the command-line which is used to
launch qconfig?

I'm not quite understand why you have this effect. in lib/explorer.py we
have proper detection of bzr excutable, see method _get_bzr_executable,
and method run_bzr_gui.

My best guess is: some code does not use _get_bzr_executable and just
invokes `bzr qconfig`, which indeed will run your system bzr.

Revision history for this message
Gary van der Merwe (garyvdm) wrote :

I think this may have been fixed in 1.1.0. Please check.

Revision history for this message
Gordon Tyler (doxxx) wrote :

I was using trunk of bzr-explorer, unless that's not the same as 1.1.0. I'll try debug mode to see what the commandline is.

Revision history for this message
Gordon Tyler (doxxx) wrote :

BTW, I'm not getting any email for comments on this bug and I've double-checked that it's not being junk-filtered. LP bug?

Revision history for this message
Martitza (martitzam) wrote :

fyi. I originally encountered this problem on Lucid with Explorer 1.1.1 and also lp:bzr-explorer (head) as of three days ago. So it's not Windows-specific.

Revision history for this message
Gordon Tyler (doxxx) wrote :

Test bzr-explorer 1.1.2dev with --dry-run, when I use the Log command on a branch I get the following:

Command: C:\Python26\python.exe
Parameters:
C:\dev\bzr\mergetools\bzr
qlog

However, when I go to the User Settings I get this:

Command: bzr
Parameters:
qconfig

I'll poke into the code to see if I can fix it.

Changed in bzr-explorer:
assignee: nobody → Gordon Tyler (doxxx)
status: New → In Progress
Changed in bzr-explorer:
importance: Undecided → Medium
milestone: none → 1.1.2
Changed in bzr-explorer:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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