Ben Collins-Sussman wrote:
>> Examples for Subversion's complaints:
>> "Execute: Update
>> Error while performing action: Working copy '...path...' not locked"
>> "Execute: Update
>> Error while performing action: REPORT request failed on
>> '...path.../!svn/vcc/default'
>> File not found: transaction '77', path '...path...'"
>
> Can you please show us a specific example? Like a transcript?
Hi Ben,
thanks for that ultra-quick answer :-)
Okay, here's a transcript, using the commandline this time:
[mwolff@BigBlueThingy lastresort]$ svn update module
svn: Working copy 'module/crm/schnelleintrag' not locked
The directory "schnelleintrag", in this case, has been in the main
repository before, but has then been deleted from there and moven out
to a spezialized repository, so it's now regarded unversioned by
Subversion when appearing in this working copy.
Currently, I can't reproduce the transaction error mentioned earlier
though, as I've tried to update only the directory that SVN complained
about, which was successful, and now I don't get the error anymore
even when doing a batch update on the parent directory.
>> Is there any way how I can just recursively update a whole working
>> copy without Subversion complaining about unversioned files?
>
> No. 'svn up' absolutely will not overwrite unversioned files. But it's
> not entirely clear that's the problem here. Those errors above look
> strange, like you're doing something really bad to your working copy.
It's not the point that I want it to overwrite unversioned files, it
just shouldn't complain when there are unversioned files in the same
directory as the working copy. The files wouldn't be overwritten by
any file under version control because they don't exist in the repository.
CU
Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 9 17:41:55 2004