[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [TSVN] Re: Problem with Lock on a deleted file

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-08-11 18:22:22 CEST

Schmidt, Maik wrote:

>> Seems you have removed the file without it being removed from the
>> repository! Use the repository browser to see if that file is still
>> there.
> Would be nice if that would be the fact. I've deleted the files via
> the repo-browser. I've just taken a look into the revision where the
> files were still there: they have the lock from our student. I've
> then installed Subversion itself and run "svnadmin lslocks" - the
> locks he had were displayed, too. Since the files are not in head
> revision anymore, I cannot remove the lock. I've tried to get them
> from the old revision into head but that does not seem to work
> because of that lock, too.

How did you get that far?
If I try to delete a file which someone has locked with the repository
browser, I get an error message. If I steal the lock first, then the
lock is gone for good too.

It would be really great if you could come up with some reproduction
recipe - you might have discovered a bug in the Subversion library.

> Question: can I remove those locks by removing the strange
> hexcode-named files under "\repository_path\db\locks\some_path"
> without crippeling the repository?

I suggest you ask this on the Subversion mailing list. They're the ones
very familliar with the repository - TSVN is just a client.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Aug 11 18:22:39 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.