Issue 2507 --no-unlock keeps lock of deleted files too -> renaming of folders is impossible

Hi,

I'm having some issue with deleted but locked files as already described in issue 2507:

> 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:

A further side-effect of this problem/issue affects all further renamings of folders containing these locked but deleted files. This means that you can not rename any folders containing these files.

Are you planning to fix this in future releases?

Is there any way to unlock these deleted files to bring the repository back in a "consistent" state? A new software release will not solve my problem with a existing repository. Please help me to find an easy migration strategy form a repository with deleted but locked files to a repository without.

Cheers,
Florian
_______________________________________________________________________
Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos.
Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=022222

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 27 14:25:34 2006