What version of the Subversion client were you using?
If necessary, could you supply the entire working copy, and identify
which file you tried to update? If it was a very recent Subversion,
and this happened, then it's a bug we should investigate.
-Karl
Hari Kodungallur <hkodungallur@gmail.com> writes:
> At the top level of our working copy we did
>
> svn update <one-file>
>
> Our repository is kinda very large. Apparently even though the update
> was for only one file, it is going through the entire WC, as it is
> taking a huge amount of time to just this one update.
> At some point of time, we did a CTRL-C and interrupted the svn update.
> After this, the WC seems to have gotten corrupted. It keeps telling me
> that the working copy is locked and asked to do a 'svn cleanup'. But
> svn cleanup gives the following error
>
> svn: Can't open directory '<somedir>/.svn/tmp': No such file or directory
>
> The <somedir>/.svn did not have the tmp directory and just so that I
> can somehow proceed, I created that directory. So it goes beyond that
> and gives the same error for the next directory, and the next and so
> on. Obviously for a size of WC we have, we can not create tmp
> directories everywhere. Is there any way we can get out of this? The
> WC has several local changes and so its not that useful to checkout a
> new WC.
>
> I would grately appreciate it if you can suggest some workarounds.
>
> Thanks
>
> -Hari
> SpikeSource Inc.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 14 05:46:15 2005