Error copying working copy in svn turtle while committing

Question

I use Tortoise SVN to update and commit changes to the repository on the server whenever I make changes to my working copy. But after a few days, I can’t commit the changes, and I get the following error when I try to commit.

Working copy 'C:\Program Files\EasyPHP\www\project\php' locked. 'C:\Program Files\EasyPHP\www\project' is already locked. 

I tried to unlock the folder by right-clicking it and choosing Tortoise SVN> Release lock , it says

There is nothing to unlock. No file has a lock in this working copy.

What could be the problem?

Answer 1

No problem ... try the following:

• Go to the top level SVN folder.
• Right click on the folder (with your svn files)> TortoiseSVN> CleanUp

This will definitely solve your problem. I did it a lot of time ... :)

Note. Verify that the Lock Locks option is selected in the Cleanup dialog box.

Answer 2

The accepted answer did not help me. To fix this problem, I had to right-click the file that was locked, select repo-browser . This opened a popup window with the files that are on the SVN server. Then I right-clicked on the locked file and selected break lock .

When I closed the repository browser, back to Explorer, I could finally commit!

Answer 3

• Right-click the folder.
• TortoiseSVN-> Check for Changes.
• Click Check Repository.
• Lock lock for all returned files.

Answer 4

I ran into this problem. For some, I would like to point out that if it is blocked, CHECK WITH YOUR TEAM. Someone from the team may block some things because they are working on it (this allows developers to work on things that are not part of others and try to work with the same content). If so, releasing the lock and subsequent updating may lose data for the developer who blocked it.

Given this, my concern was that the “clear” option could change my working copy or delete information from the Subversion repo level. This is not relevant. The answer worked for me. Mine closed when I clicked Cancel in the middle of the update. I ended up pulling some of our branches out and I don't need the material, so I hit. My working copy closed. I could not find any documents that appeared as “locked” when I used the “release lock” command. This left me puzzled, and after some quick reading (and this topic) I tried to execute the "clear" command. After cleaning, he solved my problem and nothing else was blocked.

source: http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-locking.html

Answer 5

There are several “lock” values ​​in SVN, and some of these answers that say “lock lock” or a teammate holding the lock do not use the corresponding value for the original question. This question relates to "working locks" (i.e., they are completely local to the working copy on your computer and have nothing to do with you or teammates containing the lock / extract from the file). The accepted answer by MicroEyes refers to the correct use and is your best option when this happens.

If cleaning does not work, you may need to check out a new working copy of the project. If you have any modified, unauthorized files, you will need to copy them to a new working copy so that you do not lose your changes.

See this page in SVT Tortoise docs for three ways to use “lock”: http://tortoisesvn.net/docs/nightly/TortoiseSVN_en/tsvn-dug-locking.html

Excerpt (highlighted by me):

Three Lock Values

In this section and almost everywhere in this book, the words “lock” and “lock” describe the mechanism of mutual exclusion between users in order to avoid compromise. Unfortunately, there are two more kinds of “blocking” with which Subversion, and therefore this book, sometimes needs to be bothered.

The second working copy lock used inside Subversion to prevent collisions between multiple Subversion clients running on the same working copy. Usually you get these locks whenever a command like update / commit / ... is interrupted due to an error. These locks can be removed by running the clean copy working copy command, as described in the "Cleaning" section.

...

Answer 6

I had no idea which file has the lock, so I decided to get out of this problem:

• Go to the highest level folder
• Click clean as well as marked using clean methods → Lock locks

It worked for me.

Answer 7

I tried various things, including "Clear" in the lower subdirectories. Finally, I tried updating the top level folder. Nothing. Then I read the "Clear Top Level" prompt. I have tried this. It was possible to remove part, but the castle remained. My solution was to go back to the top level, clear and then clear every red (!) Folder that I could expand to . In the end, "Cleaned up," the update worked just fine. The “lock lock” point also looks good, except that someone on your team may have a legitimate lock on things.

Answer 8

I managed to lock myself from a file in svn - I don’t know how to do it, but when I tried to (re) lock the lock (Tortoise showed the “Get Lock” parameter for the file), he complained that there was already a lock. I tried to delete the file and commit the directory change - the same result. I tried CleanUp (including overlay update), but that also failed.

The solution was to enter the Tortoise repo browser, find the file and use the break lock function.

Answer 9

Windows Solution:

https://sourceforge.net/projects/win32svn/

1.Download it, then add it to the system path.

2. In the working directory, execute "svn clean" and "svn update" in cmd.