Working copy XXX locked and cleanup failed in SVN

前端 未结 30 2662
鱼传尺愫
鱼传尺愫 2020-11-28 17:26

I get this error when I do an svn update:

Working copy XXXXXXXX locked Please execute \"Cleanup\" command

When I

相关标签:
30条回答
  • 2020-11-28 17:31

    Do not delete your solution!

    in the .svn folder you have a file called lock it is 0 bytes long

    You can delete all these files from all the .svn folders in your solution and it will work

    It worked in my case

    0 讨论(0)
  • 2020-11-28 17:32

    In Versions under Mac OS: Action -> Cleanup working copy locks at...

    0 讨论(0)
  • 2020-11-28 17:33

    The easiest way to do this is show hidden folders and then open the .SVN folder. You should see a zero KB file named "lock" deleting this will fix the problem

    0 讨论(0)
  • 2020-11-28 17:36

    Start Search....Lock...Select all files listed and delete..fixed

    0 讨论(0)
  • 2020-11-28 17:36

    In-place unversioning of the files, and a fresh checkout into the same location, has solved this problem for me.

    In TortoiseSVN, to do an in-place unversioning, right-drag the root folder of the working copy from the file list onto itself in the directory tree, and choose "SVN Export versioned items here" from the pop-up menu. TortoiseSVN notices that the destination is the same as the source, and suggests unversioning the working copy.

    After unversioning, do a fresh checkout into the same folder (which now contains an unversioned copy of all the files you had). TortoiseSVN will warn you that you are checking out into an existing folder, but you can go ahead.

    After this, cleanups, updates and other operations worked without a hitch. Since both of the above steps preserve local modifications, there should not be any loss of information (but backing the working copy up before this may nevertheless be a good idea).

    One warning: If the working copy contains mixed versions or uncommitted property changes, that information WILL be lost. For me, this is not a common occurrence, and given the choice of a corrupt working copy or losing uncommitted property changes, I tend to opt for the latter.

    0 讨论(0)
  • 2020-11-28 17:37

    In my case I solved it by manually deleting a record in the SQLite ".svn\wc" file lock record in the WC_LOCK table.

    I opened the "WC" file with SQLite editor and executed

    delete from WC_LOCK
    

    screenshot showing all entries purged from WC_LOCK

    Following eakkas's comment, you might need to delete all the entries from WORK_QUEUE table as well.

    0 讨论(0)
提交回复
热议问题