UnicodeEncodeError on mv of a deleted non-ascii file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Low
|
Martin Packman |
Bug Description
Trying to `bzr mv` a versioned file that has been deleted or renamed outside of bzr throws a UnicodeEncodeError, for instance with the commands:
bzr init
bzr mkdir £
rmdir £
bzr mv £ d
This results in the following traceback:
Traceback (most recent call last):
File ".../bzrlib/
return the_callable(*args, **kwargs)
File ".../bzrlib/
ret = run(*run_argv)
File ".../bzrlib/
return self.run(
File ".../bzrlib/
return self._operation
File ".../bzrlib/
File ".../bzrlib/
result = func(*args, **kwargs)
File ".../bzrlib/
File ".../bzrlib/
File ".../bzrlib/
return unbound(self, *args, **kwargs)
File ".../bzrlib/
File ".../bzrlib/
return unbound(self, *args, **kwargs)
File ".../bzrlib/
File ".../bzrlib/
UnicodeEnco
As always, calling str() on a path is bogus.
Related branches
- Jelmer Vernooij (community): Approve
-
Diff: 34 lines (+13/-3)2 files modifiedbzrlib/tests/blackbox/test_mv.py (+11/-0)
bzrlib/workingtree.py (+2/-3)
Changed in bzr: | |
importance: | Undecided → Low |
status: | New → Confirmed |
description: | updated |
Changed in bzr: | |
assignee: | nobody → Martin Packman (gz) |
status: | Confirmed → In Progress |
Changed in bzr: | |
milestone: | none → 2.5b5 |
status: | In Progress → Fix Released |