This is a known issue
http://subversion.tigris.org/issues/show_bug.cgi?id=2507 with a
On Thu, Jul 9, 2009 at 1:52 AM, Wilbert Jansen<wjansen_at_cordys.com> wrote:
> I tried to find this bug in the open issues on Subversion bugs, but wasn’t
> able to find it which surprises me since I’ve seen it twice in the last
> week. I ignored the first time, since that was on a repos that I was simply
> testing/hacking on and without much thought removed it and created a new
> The below describes how we got there as good as possible. Note: this is NOT
> a valid reproduction schema, as in it does not result in the bug.
> Unfortunately the second repos that had the error has been deleted at this
> time as well.
> Steps taken:
> - Created the SVN repos with Visual SVN Server 1.6.4
> - A file in the repos mhf_core.jar got renamed to mhf.jar and was
> moved to another folder (the who/how is unfortunately obscure). That worked,
> as in that the mhf.jar is present in the repos and gives no issues.
> - Tried to delete the folder that contained the original
> mhf_core.jar directly from Visual SVN manager. This gives an error that I
> don’t have a lock on mhf_core.jar (since it was created by another user.
> When logged in with the other user’s id and tried deleting, gives an error
> empty token).
> - Tried deleting by checking out the contents on file system. The
> mhf_core.jar was not present in that folder.
> - Tried deleting by Tortoise version 1.6 .3 and then do a commit.
> This does not work, it gives an error that mhf_core.jar file is locked:
> ‘Cannot verify lock on path ‘/trunk/somefolderstructure/jarfile.jar’; no
> username available’
> - The file does however no longer exist in repository. It does not
> get checked out and it is not there according to the repo browser.
> - The only way we found to remove this lock and delete the folder
> was by deleting the entire repository.
> Hopefully this gives an idea. I’ve tried to reproduce this a few times, but
> wasn’t able to. Not sure what is missing.
> The information contained in this communication is confidential, intended
> solely for the use of the individual or entity to whom it is addressed and
> may be legally privileged and protected by professional secrecy. Access to
> this message by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, or distribution of the message, or any
> action or omission taken by you in reliance on it is prohibited and may be
> unlawful. Please immediately contact the sender if you have received this
> message in error. This email does not constitute any commitment from Cordys
> Holding BV or any of its subsidiaries except when expressly agreed in a
> written agreement between the intended recipient and Cordys Holding BV or
> its subsidiaries. Cordys is neither liable for the proper and complete
> transmission of the information contained in this communication nor for any
> delay in its receipt. Cordys does not guarantee that the integrity of this
> communication has been maintained nor that the communication is free of
> viruses, interceptions or interference. If you are not the intended
> recipient of this communication please return the communication to the
> sender and delete and destroy all copies.
glasser_at_davidglasser.net | langtonlabs.org | flickr.com/photos/glasser/
Received on 2009-07-09 18:58:05 CEST