TortoiseSVN Write Lock Error?

Question

I wanted to merge my branch into the main trunk again. We did not work on this project for a week and did not commit any commits, etc. During this time period. Trying to switch from branch back to trunk and get this error:

No write-lock in 'Y:\Website\_Working Copy\app' 

I have never seen or seen this problem in the past and cannot find documentation about what is going wrong ... what could it be and what can I try?

In addition, I just updated TortoiseSVN and SVN to the latest versions to check if this will fix the damaged file, but it doesn’t work.

Answer 1

Hmm ... It's weird, but it's a problem in your working copy. I would cancel the svn switch troubleshooting with a fresh trunk check. You can then merge the branch into this new working copy.

Answer 2

I switched from branch to trunk and got the same error.

With TortoiseSvn, I was able to do a “Clean”, and this fixed the problem for me.

Answer 3

If you use TortoiseSVN, it may happen that the TSVNCache process (wayward) contains an open .svn / wc.db, which prevents the creation of a write lock on the file while the switch is running. Killing the process (or at least forcing the handle to close) will result in the release of a file descriptor that allows you to perform other operations that modify the working copy metadata.

Answer 4

I had this problem periodically, always in the same project, with every commit. Chris's answer may work (i.e., restart the TSVNCache process), but this is one.

What I decided to decide finally for me:

• 1) go to the files that TSVN complained about, and perform an SVN update for each of them, TSVN then displays a “merged file ...” message due to a committed commit, but an automatic update that failed.

• 2) after all the files have been saved and my general project directory is stable, I deleted the folder and checked it from scratch.

No more problems. Touch the tree.