On Wed, Apr 29, 2020 at 6:42 PM Anton Shepelev <anton.txt_at_gmail.com> wrote:
> Nathan Hartman:
> > If the command line client, are you in a working copy directory
> > when you run the "svn update" command?
> That was my initial suggestion, too, but when I tried `svn up' at a
> random location that was not an SVN working directory it printed:
> Skipped '.'
> Summary of conflicts:
> Skipped paths: 1
> which is not very polite. I expected:
> svn: E155007: 'C:\Program Files\Far Manager' is not a working copy
Interesting. I think you are using an older Subversion client. For
example, Subversion 1.8.14 prints this when I run "svn update" in a
random non-working-copy directory:
Summary of conflicts:
Skipped paths: 1
But Subversion 1.13.0 prints this:
junk $ svn up
svn: E155007: None of the targets are working copies
I haven't checked in which version of Subversion the message changed.
Anyway, for the OP, my original suggestion is to try another command
like 'svn info' in the same directory and see what happens. Also, if
we could have more contextual information on what led up to the error,
svn version, etc., that might help diagnose it.
Received on 2020-04-30 01:33:48 CEST