Using SVN: My own file is locked

[CindyBrockGA]

This is not a problem isolated to me. When I run "Pending Checkins," I see a file where the status is "Locked" and the user is my name. How do you unlock this file? If you try to check it in, you get an error message (and the message is different between different systems even though we are using the same version of Flare and checking in/out of the same SVN system).

Thanks!

Cindy

[Nita Beck]

Hi Cindy,

Welcome to the forums!

Yeah, this happens to me now and then. You'll need to use TortoiseSVN to open the repository. Browse to the folder that contains the locked file. If the folder holds a lot of files, sort the file list by the Locked column. Right-click the file that is locked and click Break Lock. That should do it.

BTW, you do not need to close the Flare project before breaking the lock.

[MarinaMichaels]

If you have a lot of locked files to unlock, you don't have to unlock them one at a time. In regular Windows Explorer (not in the Tortoise Repo-browser), right-click on the folder containing the locked files, choose TortoiseSVN, then choose Release lock. If you also have the Tortoise Repo-browser open, it (the Repo-browser) won't update; you'll have to close and reopen it.

[Nita Beck]

If you have a lot of locked files to unlock, you don't have to unlock them one at a time. In regular Windows Explorer (not in the Tortoise Repo-browser), right-click on the folder containing the locked files, choose TortoiseSVN, then choose Release lock. If you also have the Tortoise Repo-browser open, it (the Repo-browser) won't update; you'll have to close and reopen it.

Thanks for the tip! I'll have to test this soon.

Then again... won't that unlock files that someone else has locked? I wouldn't want to unlock those...

[Mark from Brooklyn]

Thanks for your reply here, Nita. Using the Repository Browser per your instructions helped me with a similar problem. (I had edited and saved some files and so they were locked, then my laptop died due to a dead battery; after I restarted I eventually discovered that Flare saw those files as still locked in that earlier session, and nothing I did in the current session could undo or override that.) In my case, neither Clean Up nor Release Lock nor Break Lock in Windows Explorer resolved the problem, regardless of the directory level at which I issued those commands, but going into the Repository Browser did.

Thanks again.

[Msquared]

The first thing I try in these sort of situations is Source Control > Refresh, either on the file, or at folder level. This updates Flare to match the actual status of the files in the source control system.

This is a useful command, but be aware that I use Perforce, not SVN, so there may be other things coming into play here too that I'm not aware of.

I usually check out via Flare, but check in directly from Perforce, as that gives me a bit more control over Perforce changelists etc. This means that Flare often thinks my files are in a different state from the actual state in Perforce, so I use this often.