Cannot tell bzr that a directory is moved after it has happened
Bug #115605 reported by
Nicholas Allen
This bug report is a duplicate of:
Bug #107967: Using bzr mv --after on a directory (as opposed to a filename) fails.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
New
|
Undecided
|
Unassigned | ||
Bug Description
If a directory gets moved by another tool and then you tell bzr that by running the command:
bzr mv old_dir new_dir
bzr compains with the following error:
bzr: ERROR: Could not move to dir.new: dir.new is not versioned
It works for files but not directories which seems a bit inconsistent...
Revision history for this message
| Bubba Siggler (bud3) wrote | #1 |
To post a comment you must log in.
Hi,
What file was deleted by what tool. Would this be local is there any way you think I can help.
best regards
bubba