gcommit tracebacks with Bazaar 1.8
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar GTK+ Frontends |
New
|
Undecided
|
Unassigned |
Bug Description
Bazaar 1.8rc1 and Bazaar 1.8 when installed as a system-wide installation on Fedora 9 consistently throw the error below.
Note that bzr 1.8 doesn't throw this error if invoked from the directory where the archive is unpacked:
$ bzr gcommit
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/usr/lib64/
return run_bzr(argv)
File "/usr/lib64/
ret = run(*run_argv)
File "/usr/lib64/
return self.run(
File "/home/
dlg = CommitDialog(wt)
File "/home/
self.
File "/home/
self.
File "/home/
) in iter_changes_
File "/home/
assert False, "How did we get here?"
AssertionError: How did we get here?
bzr 1.8 on python 2.5.1 (linux2)
arguments: ['/usr/bin/bzr', 'gcommit']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'bg_BG.UTF-8'
plugins:
difftools /home/kgeorge/
extmerge /home/kgeorge/
gtk /home/kgeorge/
launchpad /usr/lib64/
*** Bazaar has encountered an internal error.
Please report a bug at https:/
including this traceback, and a description of what you
were doing when the error occurred.
This happens in bzr-gtk, not bzr, so I'm reassigning there for now.