colo-mv prints error message at the end
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr-colo |
Confirmed
|
Medium
|
Unassigned |
Bug Description
with bzr.exe 2.4b1 and latest colo from trunk + my patch to support hidden names in subdirs I got this:
C:\Temp>bzr colo-init 1
C:\Temp\1>bzr clist
* trunk
C:\Temp\1>bzr colo-branch --no-switch foo
Branched 0 revision(s).
C:\Temp\1>bzr clist
foo
* trunk
C:\Temp\1>bzr colo-mv foo .hidden/foo
bzr: ERROR: No such file: u'C:/Temp/
branches/foo'
.bzr.log:
Tue 2011-05-03 15:16:31 +0300
0.390 bazaar version: 2.4b1
0.390 bzr arguments: [u'colo-mv', u'foo', u'.hidden/foo']
0.531 looking for plugins in C:\work\
0.718 looking for plugins in C:/Program Files/Bazaar/
0.718 Plugin name colo already loaded
0.718 Plugin name explorer already loaded
0.718 Plugin name qbzr already loaded
1.046 encoding stdout as sys.stdout encoding 'cp866'
1.156 Transferred: 0kB (0.0kB/s r:0kB w:0kB)
1.156 Traceback (most recent call last):
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "bzrlib\
File "C:\work\
File "bzrlib\
File "bzrlib\
NoSuchFile: No such file: u'C:/Temp/
1.156 return code 3
summary: |
- colo-mv prints with error message at the end + colo-mv prints error message at the end |
Changed in bzr-colo: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
But the branch has been moved successfully. So I think error message comes from some object that still thinks the branch at the old location.