revert fails with "TypeError: 'in <string>' requires string as left operand"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Aaron Bentley |
Bug Description
First, the traceback:
$ ~/code/bzr/bzr revert
Subversion version too old for working tree support.
bzr: ERROR: exceptions.
Traceback (most recent call last):
File "/home/
return run_bzr(argv)
File "/home/
ret = run(*run_argv)
File "/home/
return self.run(
File "/home/
not no_backup, pb, report_
File "/home/
return unbound(self, *args, **kwargs)
File "/home/
report_changes)
File "/home/
delta.
File "/home/
elif to_kind in ('file' or 'symlink') and (
TypeError: 'in <string>' requires string as left operand
bzr 0.15.0dev0 on python 2.4.4.candidate.1 (linux2)
arguments: ['/home/
** please send this report to <email address hidden>
I caused this by doing a "merge --uncommitted" from a working tree with uncommitted changes to a file that doesn't exist in tree I'm merging into.
Here's the commands I used to reproduce this situation:
$ cd /tmp/
andrew@
andrew@
andrew@
andrew@
added file.txt
andrew@
added file.txt
Committed revision 1.
andrew@
andrew@
Branched 1 revision(s).
andrew@
andrew@
andrew@
added file2.txt
andrew@
added file2.txt
Committed revision 2.
andrew@
andrew@
(reverse-
andrew@
+N file2.txt.OTHER
Contents conflict in file2.txt
1 conflicts encountered.
andrew@
andrew@
(at this point the above traceback occurs)
Changed in bzr: | |
assignee: | nobody → aaron-bentley |
status: | Unconfirmed → Fix Committed |
This was merged into bzr.dev as of revno 2344.