> Le 23/05/2013 15:59, Philip Martin a écrit : > > HOUDROGE Rami <rami.houdr...@thalesgroup.com> writes: > >> I am experiencing a problem that has been reported a couple of times >> accross the web. >> >> 1. new file >> 2. add file >> 3. commit file >> 4. lock file >> 5. modify file >> 6. commit file >> >> and that last commit fails with the following error : >> >> Cannot verify lock on path '...'; no matching lock-token available. >> >> [cid:part1.03020408.00020306@thalesgroup.com] >> >> I am certain no one stole the lock and I am also certain that, >> locally, only one working copy has the lock. > > Run 'svn info' on the working copy file to see the lock token in the > working copy. Run 'svn info' on the URL to see the lock token in the > repository. How do the locks compare (token, username, date)? > > -- > Certified & Supported Apache Subversion Downloads: > http://www.wandisco.com/subversion/download >
On Thu, May 23, 2013 at 4:04 PM, HOUDROGE Rami <rami.houdr...@thalesgroup.com> wrote: > They're the same. > > Local file : > Lock Token: opaquelocktoken:2a0cb251-8e5c-4b2e-9eb2-282abb2d67e6 > Lock Owner: houdroge > Lock Created: 2013-05-23 15:14:37 +0200 (jeu., 23 mai 2013) > > Remote file : > Lock Token: opaquelocktoken:2a0cb251-8e5c-4b2e-9eb2-282abb2d67e6 > Lock Owner: houdroge > Lock Created: 2013-05-23 15:14:37 +0200 (jeu., 23 mai 2013) > > Rami, Can you please try to reproduce this with commandline svn, and provide us a full transcript of what you do to reproduce this (maybe with a test file / test repository)? Or even better, a fully self-contained reproduction script (I guess you're on Windows, so see [1] for a template of a .bat reproduction script). [1] http://subversion.apache.org/docs/community-guide/repro-template.bat -- Johan
