Geek Answers Handbook

SVN error "working copy xxx blocked" and there is no .lock file

My working copy is locked and looking for a solution to this, and I found that the .lock file must be deleted. But the problem is that there is no .lock file in my folder. How to solve it. Please help. Thanks.

+4
source share
3 answers

SVN uses hidden directories by default, .svn or _svn. Before resorting to using these folders:

Usually the best thing you can do is run a copy of TortoiseSVN (http://tortoisesvn.net/) and connect it to your repository and working directories. Turtle intercepts Explorer, so it gives you a more holistic view of the structure of your working folder. Try the Unlock command in the files / folders in question. If this works (or not), follow these steps: "Clear" the parent folder for the item in question (folder level 1 above), and then try again.

If you use Ankh or a similar VS plugin, such blocking problems can be quite common and annoying. :)

+5
source

SVN is a great tool, but has usability issues when things don’t get validated or are not perfect completely and beautifully. Its status information is stored on the server and client. The great thing is that the server never gets screwed up and it never twists the original source files.

However, I have 2 suggestions for your

  • When you have problems with the client, dont sit, investigate and debug the svn problem. This is a waste of time and effort. Know that your data is not lost and your server is just wow :).
  • Design your project elsewhere. From the old location, copy all the files to the new location (use meld, araxis merge or beyond comparison) and commit.

NOTE: DONT copies directories from the old location to the new location. As pointed out by @Steve Py, directories contain .svn folders and storage status information for this particular instance of the validation project. If necessary, create new directories in a new location and copy the files.

TIP. When you use the directory comparison tool, changing it (from right to left OR from left to right) is not REVERSE. As soon as you press this button, you are screwed :). So in the same place I was talking about, do the following :).

+1
source

If you also get the error message “ sqlite: try to write a read-only database with an error working copy xxx is blocked ”, then it seems that it can also be caused by insufficient permissions to write a working copy.

I studied this problem separately here . Fixing permissions fixed the problem.

It is frustrating that for such a simple problem there is no more suitable error!

0
source

More articles:


All Articles