Cleanup failed, please execute the 'Cleanup' command.
Niemann, Hartmut
Hello!
Quite often - usually after directory operations that got stuck - i have to run svn cleanup.
About every other time, cleanup fails with a message box
Cleanup failed to process the following paths:
D:\............
Previous operation has not finished; run ‘cleanup’ if it was interrupted
Please execute the ‘Cleanup’ command.
Sometimes it helped to call cleanup for the working copy root, sometimes i had to try
it a few times.
Normally running svn cleanup on the command line worked.
This is with the latest 1.9 test build: “TortoiseSVN 1.9.3, Build 27163 - 64 Bit -dev, 2016/02/01 07:50:27”
but I have seen with other versions before.
It irritates me that cleanup fails with “would you please run cleanup” which i did ...
can this situation be improved?
I know that this report is very vague. What can I do to shed light onto this?
Mit freundlichen Grüßen
Dr. Hartmut Niemann
Siemens AG
MO MLT LM EN CCI 1
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Tel.: +49 9131 7-34264
Fax: +49 9131 7-26254
mailto:hartmut...@siemens.com
Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; Vorstand: Joe Kaeser, Vorsitzender; Roland Busch, Lisa Davis, Klaus Helmrich, Janina Kugel, Siegfried Russwurm,
Ralf P. Thomas; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
Rupp, Martin
Hello!
I had this issue three times today.
“svn cleanup” solved the problems but not the cleanup of Tortoise SVN.
One time I have activated the option “Break locks” in the “Cleanup” dialog of Tortoise SVN.
After that I was able to continue my work.
Unfortunately the option “Break locks” is not described in the help. I don’t know what this option does.
The cleanup of svn removes all write locks.
Maybe that is the reason why svn cleanup works and Tortoise SVN’s cleanup doesn’t.
The help of svn cleanup warns:
WARNING: There is no mechanism that will protect write locks still
being used by other Subversion clients. Running this command
while another client is using the working copy can corrupt
the working copy beyond repair!
I use locks in all my working copies and I let subversion add the property svn:needs-lock to all new files.
Maybe Tortoise SVN cannot handle locks in a right way.
With best regards,
Martin Rupp
Siemens AG
Information Technology
Power and Gas
GS IT PG XU SDF
Freyeslebenstr. 1
91058 Erlangen, Germany
Tel.: +49 9131 18-4397
Fax: +49 9131 18-5879
mailto:rupp....@siemens.com
Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Joe Kaeser, Chairman, President and Chief Executive Officer; Roland Busch, Lisa
Davis, Klaus Helmrich, Janina Kugel, Siegfried Russwurm, Ralf P. Thomas; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
Stefan Küng
> Hello!
>
> I had this issue three times today.
>
> “svn cleanup” solved the problems but not the cleanup of Tortoise SVN.
>
> One time I have activated the option “Break locks” in the “Cleanup”
> dialog of Tortoise SVN.
>
> After that I was able to continue my work.
requires a cleanup.
> Unfortunately the option “Break locks” is not described in the help. I
> don’t know what this option does.
>
> The cleanup of svn removes all write locks.
>
> Maybe that is the reason why svn cleanup works and Tortoise SVN’s
> cleanup doesn’t.
>
> The help of svn cleanup warns:
>
> WARNING: There is no mechanism that will protect write locks still
>
> being used by other Subversion clients. Running this command
>
> while another client is using the working copy can corrupt
>
> the working copy beyond repair!
>
> I use locks in all my working copies and I let subversion add the
> property svn:needs-lock to all new files.
with svn:needs-lock!
write locks are used to prevent multiple svn clients from writing at the
same time to the working copy database. Like mutexes/semaphores in
multi-threaded apps.
So you don't have to worry about your svn:needs-lock locks. And if your
working copy is not shared with other users and you don't have another
svn client running e.g. an update or some other command on that same
working copy, you *should* check the box "remove locks" when doing a
cleanup.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3161222
To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].
Niemann, Hartmut
> Cleanup removes write locks. Those are not the same locks as those set with svn:needs-lock!
> write locks are used to prevent multiple svn clients from writing at the same time to the working copy database. Like mutexes/semaphores in multi-threaded apps.
> So you don't have to worry about your svn:needs-lock locks. And if your working copy is not
> shared with other users and you don't have another svn client running e.g. an update or
> some other command on that same working copy, you *should* check the box "remove locks" when doing a cleanup.
If the "break locks" check box in svn cleanup targets database locks, not "svn:needs-lock" type locks,
could the text be changed to "remove" (as you wrote - probably not intentionally) or "clear database locks"?
In my opinion "breaking locks" is (should be) reserved for the high-level
subversion operation of me needing to change a file that my buddy reserved for himself.
If we can choose a different wording for different locks, IMHO the situation would improve.
Hartmut
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3162288