bzr (0.16) rm --new fails
Bug #118688 reported by
Andrew Voznytsa
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Low
|
Unassigned |
Bug Description
command sequence:
mkdir work
cd work
touch file.1
touch file.2
bzr init
bzr add
bzr rm --new file.2
bzr: ERROR: Can't remove changed or unknown files:
added:
file.2
Use --keep to not delete them, or --force to delete them regardless.
bzr commit -m "initial commit"
bzr status -r 0
added:
file.1
file.2
System WinXP SP2, bzr 0.16 with bzr tools.
P.S.
MSYS commands were used to show command sequence and simply things for non-Windows developers.
To post a comment you must log in.
Um... I don't see a "--new" flag.
Basically, the question is whether "bzr rm file.2" should be deleting the file, or just marking it as not versioned.
We don't know whether you added the file by accident because:
a) You thought it would be interesting, but have decided you don't like it (bzr rm --force to delete it from disk)
b) It is an important file that shouldn't be versioned (say a local configuration file, or a temporary file) then you want "bzr rm --keep" so that we just don't version it.
I'd like more information before I decide how to triage this. Since we don't have a --new flag, I don't really know what you are trying to do.