TSVN delete with "keep locks"

I think that this is a bug in Subversion itself, but was using TSVN.

Subversion seems to remember locks after deleting a file, if the file
was locked when it was committed, and "keep locks" was selected.

Versions: client: TSVN 1.3.5 or 1.4.0RC1, server: Subversion 1.3.2 on
Apache 2.0.55.

Summary/Recipe:

1) Add file (needs-lock).

2) Commit file.

3) Lock file.

4) Delete file (TSVN delete).

5) Commit with "keep lock".

6) Add a new file with same name (needs lock).

7) Commit file -- fails because "File 'xxx' already exists".

Work-around:

A) Update to revision (when file existed).

B) Check for modifications (on server).

C) Right-click and "break lock".

It seems like this would be common enough that it would have been found
already, but I haven't found a specific reference to it. It's not a big
problem, but it is annoying.

Thanks in advance for any info/advice. (Is this known? Fixed in SVN
1.4? Or maybe not?)

Also, is there a way to have "keep locks" set by default in the commit
dialog?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Thu Aug 17 07:34:54 2006