Re: svn: Working copy path 'some/file.c' does not exist in repository

On Mar 18, 2005, at 8:58 AM, Brass Tilde wrote:

>>> I have never seen 'cleanup' do anything useful. As far as I can
>>> tell it
>>> is a no-op :)
>>>
>>
>> 'svn cleanup' is not the proper response to any random client error.
>> In
>> fact, it's *only* useful for errors that say "working copy is locked,
>> run cleanup." :-)
>
> If that's the case, can that routinue not simply be run automatically
> when
> that error is encountered, and the option removed from the public
> interface?
>
>

No, for the same reason that 'svnadmin recover' can't run automatically.

When a client operation tries to use a working copy and discovers a
lockfile, there's no way it can know whether it's okay to blow away the
lockfile. Some other client might be using the working copy at the
same time. That's the whole point of working copy lockfiles -- to
prevent two independent processes from, say, trying to edit an
.svn/entries file at the same time. Only a user can know whether it's
safe to seize exclusive control over a working copy and run
journals/remove lockfiles.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 18 16:22:18 2005