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

RE: cannot break lock due to no matching lock-token

From: Giulio Troccoli <Giulio.Troccoli_at_uk.linedata.com>
Date: Wed, 14 Apr 2010 15:42:10 +0100

Please, don't top-post (now see below)

>

Linedata Services (UK) Ltd
Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
Registered in England and Wales No 3027851 VAT Reg No 778499447

-----Original Message-----

> From: Tom Jones [mailto:Tom.Jones_at_woodward.com]
> Sent: 14 April 2010 15:38
> To: 'users_at_subversion.apache.org'
> Subject: RE: cannot break lock due to no matching lock-token
>
> Thanks,again.
>
> So, I am running subversion on a Windows2003 server. The URL
> for the repository is svn://servername/reponame. The file in
> question is reportedly in a project folder in a trunk (URL
> svn://servername/reponame/project/trunk/filefolder/filename.xy
> z) HOWEVER, the file no longer exists because it was deleted
> at some point, but the repository still thinks there is a
> lock on this non-existent filename.xyz. The file DOES exist
> in an earlier tag, but there is no link between that file and
> the current trunk.
>
> I tried issuing commands using the standard DOS command
> prompt window. I can get info on the project folders (e.g.
> svn info svn://servername/reponame/project/trunk/filefolder/)
> but I cannot do anything with the filename that is associated
> with this error: "cannot verify lock on path... ; no
> matching lock- token available. If you wish to break the
> lock, use the 'Check for Modification' dialog" Checking for
> modifications does not help because the working folder
> associated with this lock no longer exists either.
>
>

If you have access to the the server have you tried using

svnadmin lslocks

and then

svnadmin rmlocks
?

G
Received on 2010-04-14 16:42:42 CEST

This is an archived mail posted to the Subversion Users mailing list.

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