[ 
https://issues.apache.org/jira/browse/SVN-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17093477#comment-17093477
 ] 

Daniel Shahaf commented on SVN-4854:
------------------------------------


I think that might be a bug in 1.8.15 that has been fixed.

svnmucc is a thin wrapper around the svn_delta_editor_t interface.  That
interface is very sensitive to order of operations, so I wouldn't expect
svnmucc to reorder its operation arguments.

The first operation, «mkdir /foo/bar», would fail with "/foo doesn't
exist" — if it ran, which it didn't get a chance to.  Before even
starting the edit drive, svnmucc reviewed the set of operations and
determined, without contacting the server, that the given sequence of
operations cannot possibly succeed _regardless of the current state of
the repository_: in the editor interface, «mkdir /foo» fails when /foo
exists, and the previous command, «mkdir /foo/bar», can only succeed if
/foo exists.  So you got an error about /foo existing.

However, as you say, the error message is inaccurate.  It's not that
/foo exists in the repository; it's that it is _implied_ to exist by an
earlier command.

I vote to reword the error message.


> a problem of svnmucc mkdir
> --------------------------
>
>                 Key: SVN-4854
>                 URL: https://issues.apache.org/jira/browse/SVN-4854
>             Project: Subversion
>          Issue Type: Bug
>          Components: svnmucc
>    Affects Versions: 1.10.6
>         Environment: CentOS 6.6
> Subversion 1.10.6
>            Reporter: haiyuan qian
>            Priority: Major
>
> # /usr/local/bin/svnmucc -U URL -m MESSAGE mkdir '/parent/subdir' mkdir 
> '/parent'
> svnmucc: E160020: Path 'parent' already exists
>  
> But:
> # /usr/local/bin/svnmucc -U URL -m MESSAGE mkdir '/parent' mkdir 
> '/parent/subdir' 
> r506 committed by root at 2020-04-27T12:18:21.419619Z
> It works. 
>  
> In the version 1.8.15, both of these two commands can be run;
> Also the error of the first command is definitely wrong. The '/parent' 
> directory does not exist.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to