On Jul 5, 2005, at 2:50 PM, Phil wrote:
>
> This is in the case that you try to svn update a
> working copy in which one file is locked
What do you mean by "locked"?
> (not the
> first file that needs updating though). svn
> errors (as it should) and aborts the process. Any
> files already updated remain updated, any later
> files that aren't locked fail to be updated.
>
> But that's not the worst of it. The directory
> gets locked, but when you run svn cleanup it
> complains that it can't apply the updates to the
> files that have already been updated
> (specifically, it complains about the lack of
> file in .svn/tmp/filename).
>
> Even in the case that the first file is locked,
> you still end up with 0 length filename.tmp files
> existing.
>
> Is this a known problem?
Can you give us a step-by-step recipe to reproduce, so we can see
what you're describing firsthand?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 8 15:02:20 2005