Updating source

[Brandon Helsley <br...@aol.com>]

How do I update source if when I use Svn update it responds with svn: e155007 none of the targets are working copies.

Re: Updating source

[Anton Shepelev <an...@gmail.com>]

Nathan Hartman to Anton Shepelev:

> > 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:
> 
> E:\junk>svn up
> Skipped '.'
> Summary of conflicts:
>   Skipped paths: 1
> 
> But Subversion 1.13.0 prints this:
> 
> junk $ svn up
> Skipped '.'
> svn: E155007: None of the targets are working copies

Thank you. I should not have believed the handling of so basic an
error has changed so recently. It it time I upgraded my svn client.

-- 
()  ascii ribbon campaign - against html e-mail
/\  http://preview.tinyurl.com/qcy6mjc [archived]

Re: Updating source

[Nathan Hartman <ha...@gmail.com>]

On Wed, Apr 29, 2020 at 6:42 PM Anton Shepelev <an...@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:

E:\junk>svn up
Skipped '.'
Summary of conflicts:
  Skipped paths: 1

But Subversion 1.13.0 prints this:

junk $ svn up
Skipped '.'
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.

Thanks,
Nathan

Re: Updating source

[Anton Shepelev <an...@gmail.com>]

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

-- 
()  ascii ribbon campaign - against html e-mail
/\  http://preview.tinyurl.com/qcy6mjc [archived]

Re: Updating source

[Nathan Hartman <ha...@gmail.com>]

On Wed, Apr 29, 2020 at 1:10 PM Brandon Helsley <br...@aol.com>
wrote:

> How do I update source if when I use Svn update it responds with svn:
> e155007 none of the targets are working copies.
>
Are you using the svn command line client or a GUI?

If the command line client, are you in a working copy directory when you
run the "svn update" command?

If so, do other commands, such as "svn info" work correctly?

Were you using any additional options / arguments with "svn update"?

Thanks,
Nathan