revert fails on deleted versioned directory replaced with unversioned file
Bug #1733997 reported by
Paul Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
Recently I ended up in a situation where "bzr revert" could not help me. Below is a minimal recreation of the problem.
[agnew(work)] dpkg-query -W bzr
bzr 2.7.0+bzr6619-
[agnew(work)] bzr --version | head -n1
Bazaar (bzr) 2.8.0dev1
[agnew(work)] mkdir a
[agnew(work)] cd a
[agnew(a)] bzr init
Created a standalone tree (format: 2a)
[agnew(a)] mkdir b
[agnew(a)] touch b/c
[agnew(a)] bzr add .
adding b
adding b/c
[agnew(a)] bzr ci -m 1
Committing to: /tmp/work/a/
added b
added b/c
Committed revision 1.
[agnew(a)] rm -rf b
[agnew(a)] touch b
[agnew(a)] bzr revert
K b => b/
bzr: ERROR: No final name for trans_id 'new-3'
file-id: None
root trans-id: 'new-0'
[agnew(a)] _
To post a comment you must log in.