bzr rm warns about files in symlink target directory
Bug #245045 reported by
Russ Brown
This bug report is a duplicate of:
Bug #128562: bzr commit FILE breaks when given symlink as argument.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
I just tried to bzr rm a symlink which pointed at a directory. I did not have a slash appended to the filename.
bzr acted as though the symlink was a real directory, with the files in the target directory listed as unknowns:
bzr: ERROR: Can't safely remove modified or unknown files:
<file list>
Workaround is to just use --force (nothing other than the symlink is removed, but it certainly gives the impression that they will be). The user experience could definitely do with being improved a little here. :)
Changed in bzr: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in bzr: | |
status: | Triaged → Confirmed |
tags: | added: rm |
To post a comment you must log in.
I have just seen this behaviour too.
using --force worked.