Recently there was a change to how fossil rm works that completely breaks it.  Previously, you would fossil rm a file, and then you could remove the file manually.  On commit it would then register the rm just fine.

Now I get this:

<verbatim>
Total network traffic: 309 bytes sent, 3684 bytes received
fossil: not a ordinary file:
</verbatim>

The only solution is to touch that file and then commit.  Now, thinking that maybe fossil deletes the file on commit I went to check if these files are gone but they aren't.

The problem is, fossil should either do one of three things:

1) Ignore the deleted files like before on commit, since them being deleted is not an error.
2) If it requires the file to be there on commit, then after commit it should delete them otherwise major consistency problems arise.
3) Preferrably, if on fossil commit if the file is gone, then fine ignore it, if the file is there, then delete it.  Leave fossil rm as-is.

Requiring a manual delete after a commit is just making me do accounting work that fossil can figure out.