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

SVN Status B broken lock

From: Denis Gregoire <denis_greg_at_hotmail.com>
Date: 2007-11-01 20:34:04 CET

Hi all, we are currently in the process of using Enterprise Architect
through SVN Subversion. We are encountering a little problem using it.
When doing a Checkout of a package, EA reports "Checkout failed".
After investigation, it appears to be a problem with SVN.

Behind the scene, EA is calling 4 command lines:
svn status --show-updates --verbose "Sensors\Model\foo.xml"
=
stdout
               16 5 cotes Sensors\Model\foo.xml
Status against revision: 16
stderr
.
.
.
svn update "Sensors\Model\foo.xml"
=
stdout
At revision 16.
stderr
.
.
.
svn lock -m " " "Sensors\Model\foo.xml"
=
stdout
'foo.xml' locked by user 'toto'.
stderr
.
.
.
svn status --show-updates --verbose "Sensors\Model\foo.xml"
=
stdout
     B 16 5 cotes Sensors\Model\foo.xml
Status against revision: 16
stderr

I run those same 4 command line manually through a console, and I get
the same result, so it really does not appear to be a EA problem, but
Subversion one.

the 3 first command runs succesfully, The problem is with that last
one (svn status --show-updates --verbose "Sensors\Model\foo.xml"),
Which show me a status of B, which means the lock is broken!!

Can someone tell me why a lock can be broken, and how can we fix a
broken lock?

Note that we are using SSL, and put write access restriction on
specific folder. If we remove those restriction, everything is working
fine. But the test has been runned with an admin user that have write
access to every repository.

Any help/hint will be appreciated.

Thx

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 1 20:34:25 2007

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.