> From: [email protected]
> To: [email protected]
> CC: [email protected]
> Subject: Re: Possible bug in error message E160020
> Date: Mon, 15 Dec 2014 11:10:59 +0000
>
> Benoit de Biolley <[email protected]> writes:
>
> > this bugs is on the eror message that outputs the source directory in place
> > of the destination directory.
> >
> > when i'm executing this :
> >
> > "svn --non-interactive copy --file
> > C:\Users\xxx\AppData\Local\Temp\maven-scm-1138477127.commit --revision 6237
> > http://svn.xxx.be/xxx-svn/pow/trunk/
> > http://svn.xxx.be/xxx-svn/pow/tags/R4.10.1t";
> >
> > error message is :
> > svn: E160020: Path 'trunk' already exists
> >
> > error message should be :
> > svn: E160020: Path 'R4.10.1t' already exists
>
> The error is that trunk already exists, inside R4.10.1t. The target of
> the copy is either the final destination or the parent of the final
> destination depending on the state of the repository. This is the same
> as the Unix cp command, but can be confusing:
>
> svnadmin create repo
> svn mkdir -mm file://`pwd`/repo/A
> svn cp file://`pwd`/repo/A ^/B # creates ^/B
> svn cp file://`pwd`/repo/A ^/B # creates ^/B/A
> svn cp file://`pwd`/repo/A ^/B # error A, i.e. ^/B/A, exists
>
> We probably ought to put the full path in the error message so that it
> is easier to understand.
>
> --
> Philip Martin | Subversion Committer
> WANdisco // *Non-Stop Data*
I think you're right.
Do you will create an "improvement" in the issue tracker ?
