New - --no-unlock keeps loc

http://subversion.tigris.org/issues/show_bug.cgi?id=2507

                 Issue #|2507
                 Summary|--no-unlock keeps lock of deleted
files too
               Component|subversion
                 Version|1.3.x
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|libsvn_client
             Assigned to|issuessubversion
             Reported by|steveking






------- Additional comments from stevekingtigris.org Sun Feb 19 08:10:35 -0800 2006 -------
As reported here:
http://subversion.tigris.
org/servlets/BrowseList?list=dev&by=thread&from=4338
23

Filing issue with permission of Ben Collins-Sussman:

When a commit deletes a file, and the --no-unlock option is
passed with 
the commit, the lock is not removed. That leaves a lock on a

non-existing file:

$ svnadmin create lockrepo
$ svn co file:///d:/test/lockrepo lockwc
$ cd lockwc
$ echo test > file
$ svn add file
$ svn ci -m ""
$ svn lock file
$ svn rm file
$ svn ci -m "" file --no-unlock
$ echo test2 > file
$ svn add file
$ svn ci -m ""
Adding           file
svn: commit failed (details follow):
svn: Cannot verify lock on path '/file'; no matching
lock-token available

I'm not sure if that really intended. Of course, the above
recipe isn't 
that 'real life', but imagine a commit with --no-unlock
where not just 
the removed file but multiple other files are committed too,
then the 
--no-unlock option makes more sense.

I think in case a file gets removed from the repository, the
lock should 
be removed too, no matter if the --no-unlock option is
passed or not.

------------------------------------------------------------
---------
To unsubscribe, e-mail: issues-unsubscribesubversion.tigris.org
For additional commands, e-mail: issues-helpsubversion.tigris.org