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

Re: Semantics of locking a "revision"

From: Stefan Sperling <stsp_at_elego.de>
Date: Tue, 18 Dec 2012 18:26:55 +0100

On Tue, Dec 18, 2012 at 05:14:18PM +0000, Julian Ruhe wrote:
> Hello,
>
> if I co a working copy with -rREV with REV older than HEAD, I am able to get a lock on any file. But it seems to me, that the lock is never published to the server as no "svn info URL" shows an existing lock on the file on any working revision, while the lock is existing in my wc (displayed by svn status / info).
>
> So what is the purpose of having an isolated lock in my wc? Did I miss something?
>
> Best regards,
> J. Ruhe
>
> p.s. Using svn 1.7.6 (win32 cygwin client), svn 1.7.7 (debian server)

With a 1.7.x build of Subversion, in a simple test over ra_local
(i.e. a file:// URL) I get this:

Updated to revision 1.
$ svn lock alpha
svn: warning: W160042: Lock failed: newer version of '/trunk/alpha' exists
$ svn up -r2
Updating '.':
At revision 2.
$ svn lock alpha
svn: warning: W160042: Lock failed: newer version of '/trunk/alpha' exists
$ svn up -rHEAD
Updating '.':
U alpha
Updated to revision 3.
$ svn lock alpha
'alpha' locked by user 'stsp'.

So obviously I cannot reproduce the issue.
Can you please provide more details?

Are you sure the file you're trying to lock is out-of-date?

Which repository access method are you using (http://, svn://, ...)?
Received on 2012-12-18 18:27:47 CET

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.