Announcement

Collapse
No announcement yet.

Commit problem--User does not own lock on path

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Commit problem--User does not own lock on path

    Yes it\'s me again. I tried searching online & don\'t see a solution to this. When I commit I get this message.

    Commit failed (details follow):
    User Ron does not own lock on path \'/Trunk/bin/Release/c380.txt\' (currently
    locked by John)
    If you want to break the lock, use the \'Check For Modifications\' dialog.

    I don\'t see anything regarding any \'locks\' in the \'Check For Modifications\' dialog.
    I tried going to the highest folder & choosing \'release lock\', but I get the message \"There is nothing to unlock. No file has a lock in this working copy.\"

    Thanks
    Ron

  • #2
    Re:Commit problem--User does not own lock on path

    The other use also shows that he has no locks.
    Ron

    Comment


    • #3
      Re:Commit problem--User does not own lock on path

      I don\'t use TortoiseSVN but this
      http://tortoisesvn.net/docs/release/...locking-status
      seems to indicate that you click the \"Check Repository\" button to get information about locks held in other working copies.

      Comment


      • #4
        Re:Commit problem--User does not own lock on path

        Yes, you need to first click on \"check repository\" in the check-for-modifications dialog. Then the locked files will show up and the \"break lock\" entry in the context menu shows up for those files.

        Or you can right-click on the locked file, choose \"get lock\" and then check the box \"steal lock\" to steal the lock from the other user.

        Comment

        Working...
        X