RE: [docbook-apps] DocBook snapshot SVN problem

["honyk" <j.tosovsky@email.cz>]

This locking can be caused by operating multiple users on the given local
SVN copy. And only that user who 'locked' that folder can clean it up.
Besides intentional locking also auto-locking is employed during some
operations and if something fails, the affected folder stays locked. 

On windows this can happen e.g. when local copy is created and regularly
updated with the admin account, but some files modified and committed by
user accounts. In some situations the user is unable to update some folders
because of the lock. When admin logs in and performs cleanup operation,
everything works fine again. 

But I don't know if something like this is applicable to this situation.

Jan


> -----Original Message-----
> From: Bob Stayton [mailto:bobs@sagehill.net]
> Sent: Friday, May 03, 2013 6:26 PM
> To: DocBook Apps
> Subject: [docbook-apps] DocBook snapshot SVN problem
> 
> I'm investigating the problem with the DocBook XSL snapshot builds, and
> it
> seems SVN is having a
> problem that I don't understand.
> 
> $ svn cleanup
> svn: Write-lock stolen in 'contrib/tools/pawson'
> 
> $ svn update
> svn: Working copy '.' locked
> svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> details)
> 
> And running "svn cleanup" does not remove the lock.
> 
> I get this error only on the snapshot machine, not my home machine.  So
> I
> think it is a problem with the snapshot machine's working copy.
> 
> Anyone know how to fix this?  I could probably check out a new working
> copy,
> but that takes awhile and I would rather fix it with some kind of
> unlock
> command.
> 
> Bob Stayton
> Sagehill Enterprises
> bobs@sagehill.net
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org