[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    [Issue 3448]  svn cleanup fails, instructing to run svn cleanup
From:       Martin von Gagern <Martin.vGagern () gmx ! net>
Date:       2009-07-24 13:19:38
Message-ID: 20090724131938.7FBE7FCC363 () sc157-tigr ! sjc ! collab ! net
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=3448



User gagern changed the following:

                What    |Old value                 |New value
================================================================================
                      CC|''                        |'gagern'
--------------------------------------------------------------------------------




------- Additional comments from gagern@tigris.org Fri Jul 24 06:19:37 -0700 2009 -------
We got the "Error processing command 'committed'" here today as well. It wasn't
my PC, but someone using Tortoise 1.6.3. Here is what happened, as far as we
could piece it together. Add a grain of salt.

1. Moved files like "from/some/file" to "to/some/dir/" (right drag, move
versioned files) and marked the corresponding source directories "from/some/"
for deletion where empty (using Tortoise delete)

2. Accidentially moved a subdir "from/some/subdir/" along with the files.
Decided to undo the add (right click, Tortoise, undo add) but then canceled the
operation, as the message about deletion frightened me.

3. Unexpectedly found a whole subtree "from/some/subtree/" empty of regular
files. The directory structure was still intact. A corresponding directory
"to/some/dir/subtree" got created. In retrospect, it looks like an accidential
move of the subtree, combined with the fact that TortoiseSVN often fails to
properly update the icons displaying current status. How that move came to pass,
though, I have no clue.

4. Tried to commit stuff, in order to not lose the work so far. Got some error
message, with a lot of red lines, but don't recall the actual message.

5. Tried to update the whole working copy. Lots of conflicts reported.

6. Tried to revert the whole working copy. Reverted part of the files before
issuing an error message asking me to run cleanup.

7. Tried to cleanup the working copy. Got the message "Error processing command
'comitted'" on the directory "to/some/dir/subtree".

8. Moved the "to/some/dir/subtree" out of the working copy. Re-ran cleanup. Got
"Unable to lock 'from/some/other/subdir'", where both "from/some/other/subdir/"
and its parent "from/some/other/" are directories marked for deletion. The
command line "svn status" marks both as deleted, and the "other" as locked.

9. Gave up and created a new checkout.

If this were only happening to Tortoise, the canceled operation from 2. would be
my bet. But the fact that users from different clients and platforms experience
the same rather indicates an error in the svn client libs.
The error messages starting from 6. can be reproduced on the svn (SlikSVN) 
command line client.
Copying the "to/from/dir/subtree/" to a linux machine and running "svn cleanup"
there worked all right.
The error from the commit in 4. would probably be crucial to solving this, but I
don't think there is a way to restore or easily reproduce that.

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=463&dsMessageId=2375183

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@subversion.tigris.org].
[prev in list] [next in list] [prev in thread] [next in thread]