GNOME Bugzilla – Bug 348722
bzr directory scan fails due to an undefined variable
Last modified: 2010-10-02 01:22:24 UTC
Version used: 1.1.4 When I attempt to browse the differences in one of my bzr-controlled directories, it never finishes the recursive directory scan and dumps the following traceback into the terminal: Traceback (most recent call last):
+ Trace 69633
ret = task()
self.vc.cache_inventory(rootname)
self._tree_cache = self.lookup_tree(rootdir)
tree_state[os.path.join(rootdir, entry[2:])] = cur_state
A patch to fix this is forthcoming.
Created attachment 69625 [details] [review] patch to define the variable before it's used in the loop
That patch looks like it fixes the symptom but I think is incorrect. State should be set to one of the _vc.STATE_* constants. I've cc'd the author of this file.
aaron bentley: *ping*
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Please reopen this bug report. Detailed reproduction steps can be found here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565253 At least the traceback is almost the same.
So please tell us the exact meld version you use.
The Debian bug report was created using 1.3.0, and I reproduced it now using 1.3.1: mkdir foo cd foo/ mkdir bar touch bar/foobar bzr init . bzr st bzr add bar/ bzr st bzr ci -m'commit' bzr move bar zork echo "some edits" > zork/foobar bzr st bzr diff meld . ... Traceback (most recent call last):
+ Trace 222118
self._tree_cache = self._lookup_tree_cache(directory)
I posted a patch to the meld mailing list that should fix a variety of bzr problems, including this one. See: http://mail.gnome.org/archives/meld-list/2010-August/msg00021.html I'm not a bzr user however, so I'd appreciate testing by people who are.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.