This happens for some commands, for example: bzr qbranch, bzr qupdate. Reason seems to be that the Python wrapper does not pass the actual argv[0] (/usr/bin/bzr-python2.7 was passed in my case), at least with dev-vcs/bzr-2.5.1-r1. Relevant lines from /usr/lib/python2.7/site-packages/bzrlib/plugins/qbzr/lib/subprocess.py: script = sys.argv[0] ... script = os.path.abspath(script) if os.path.basename(script) != "bzr": after hacking this if condition, I was able to get rid of the error. This bug is related to both bzr (how it's run) and qbzr (the 'if' condition). dev-vcs/bzr-2.5.1-r1 was built with the following: USE="curl sftp -doc -test" PYTHON_TARGETS="python2_7 -python2_6" dev-vcs/qbzr-0.23.0 was built with the following: USE="" dev-python/python-exec-0.3.1 was built with the following: USE="" PYTHON_TARGETS="jython2_5 jython2_7 pypy1_9 pypy2_0 python2_5 python2_6 python2_7 python3_1 python3_2 python3_3" # ls -l /usr/bin/bzr lrwxrwxrwx 1 root root 11 07-14 21:34 /usr/bin/bzr -> python-exec Reproducible: Always
Unfortunately I cannot reproduce. Please try with QBZR 0.23.1, also I will commit Bazaar 2.6.0 shortly.
It didn't help. Did you try to (and if not, could you) run bzr qupdate and let it update a working directory (ie. not only display a window)? Please don't mind me asking this, I'm wondering what is going on with it.
Just confirming the ability to reproduce this on qbzr 0.23.1 and bzr 2.5.1-r1.
is this happening on a fully updated system? (python handled has changed a lot since 2013)
