Several solutions to SVN being locked

With SVN, the problem of being locked and unable to submit is often encountered. When choosing to unlock, it prompts that no files are locked, which is a headache.
Here are several solutions for SVN being locked:

1. Use the "Clean up" function after this problem occurs. If it still doesn't work, go directly to the upper-level directory, execute "Clean", and then "renew".

2. Sometimes if you see that a folder in a package does not have the SVN logo, you can directly delete it manually with "Ctrl+Delete", then "clean up", and finally "update" or "submit".

3. Sometimes some files cannot be submitted and updated, and there is a hint of lock: first click the file, then getLock, then select stealLock, and then release lock

. 4. Teach you the most ruthless trick in the project If there is a file deadlock that cannot be solved, ask all the people in the development to upload and unlock the file, and clear the repository address: installation directory: SvnTracsnprojectsdblocks All content in the folder path. Everything is ok!

Tips: In

Subversion 1.3.2, when anonymous access is enabled and the authz function is used to restrict anonymous access, the phenomenon of being prompted to be LOCKed when checking out will appear.
From Gimhoy's Blog: http://blog.gimhoy.com/archives/svn- locked-solution.html