Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-4372

Better serf error for unlocking stolen lock

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.8.x
    • 1.10-consider
    • libsvn_ra_serf
    • None

    Description

      Lock a file in a working copy, steal the lock, then attempt to unlock the
      original working copy.
      
      svnadmin create repo --compatible-version 1.7
      svn -mm import repo/format file://`pwd`/repo/A/f
      svn co http://localhost:8888/obj/repo wc
      svn lock wc/A/f
      svn lock --force http://localhost:8888/obj/repo/A/f
      svn unlock wc/A/f
      
      The server responds to the UNLOCK with a 400 Bad Request.  With 1.7/neon the
      client reports:
      
      svn: warning: W160040: No lock on path 'f' (400 Bad Request)
      
      160040 is SVN_ERR_FS_NO_SUCH_LOCK. with 1.8/serf the client reports:
      
      svn: warning: W175002: Unlock request failed: 400 Bad Request
      
      175002 is SVN_ERR_RA_DAV_REQUEST_FAILED
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            philipm Philip Martin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: