'svnmucc' fails to process action sequences where a delete action follows
a modify/propset or another delete on the same path. This behavior is a
regression in Subversion 1.9.0 RC1 compared to 1.8.13:
echo content > file
svnmucc --root-url URL --message "r1" put file /file
svnmucc --root-url URL --message "r2" put file /file rm /file
# svnmucc: E200009: Can't delete node at 'file'
echo content > file
svnmucc --root-url URL --message "r1" put file /file
svnmucc --root-url URL --message "r2" propset prop val /file rm /file
# svnmucc: E200009: Can't delete node at 'file'
echo content > file
svnmucc --root-url URL --message "r1" put file /file
svnmucc --root-url URL --message "r2" rm /file rm /file
# svnmucc: E160013: Can't delete node at 'file' as it does not exist
# (nothing is committed to the repository, and /file still exists in HEAD)
With Subversion 1.8.13, these command sequences end without errors and
remove /file. The corresponding design decision is documented in
^/subversion/branches/1.8.x/subversion/svnmucc/svnmucc.c:460:
/* We won't fuss about multiple operations on the same path in the
following cases:
- the prior operation was, in fact, a no-op (open)
- the prior operation was a propset placeholder
- the prior operation was a deletion ... */
Major