[jira] [Created] (SVN-4920) Deleted files breaks svn info -r HEAD output

Ond=C5=99ej Medek created SVN-4920:
---------------------------------

             Summary: Deleted files breaks svn info -r HEAD output
                 Key: SVN-4920
                 URL: https://issues.apache.org/jira/browse/SVN-4920
             Project: Subversion
          Issue Type: Bug
    Affects Versions: 1.14.2
            Reporter: Ond=C5=99ej Medek


I have an existing file {{exist.txt}}, nonexistent file {{noexist.txt}} and=
 a file which has been deleted {{deteted.txt}}. I have a SVN working copy w=
hich is at a revision with {{deteted.txt}} still existing, however, someone=
 else has deleted it in the repository already. I.e.

{code}
$ ls .
deteted.txt exist.txt
{code}

When I do {{svn info -r HEAD}} to get remote revision of these files, the d=
eleted file breaks the output:

{code}
$ svn info --show-item last-changed-revision -r HEAD deteted.txt exist.txt
svn: E160013: File not found: revision 10, path '/deteted.txt'
{code}

No result, just error. When I change the param order, I have the result for=
 the existing file:

{code}
$ svn info --show-item last-changed-revision -r HEAD exist.txt deteted.txt
1          exist.txtsvn: E160013: File not found: revision 10, path
'/deteted.txt'
{code}

However, when I do the same with nonexistent file, I have the output for th=
e existing file always regardless of the param order:

{code}
$ svn info --show-item last-changed-revision -r HEAD noexist.txt exist.txt

svn: warning: W155010: The node '...\noexist.txt' was not found.

1          exist.txt
svn: E200009: Could not display info for all targets because some
targets don't exist
{code}

I would welcome {{svn info -r HEAD}} would behave for the deleted files the=
 same way as for nonexistent ones.

See also User forum thread https://lists.apache.org/thread/lt32kkyntwfrjkpx=
sxz36dg2v6k0kmco

Note:=20
* Ideal solution is to continue processing all arguments after data errors =
and stop for other errors (internal server error, connection error, ...).
* The simplest solution is to continue processing all arguments after all e=
rrors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)