docbook-apps

  • 1.  DocBook snapshot SVN problem

    Posted 05-03-2013 16:26
    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




  • 2.  Re: [docbook-apps] DocBook snapshot SVN problem

    Posted 05-03-2013 16:42
    Bob,

    if that working copy doesn't contain any local edits, I suggest you
    simply blow away the tree and check out out from scratch.

    Stefan

    --

    ...ich hab' noch einen Koffer in Berlin...




  • 3.  Re: [docbook-apps] DocBook snapshot SVN problem

    Posted 05-03-2013 18:12
    Hi Bob,

    Am Freitag, 3. Mai 2013, 09:25:43 schrieb Bob Stayton:
    >
    > svn: Write-lock stolen in 'contrib/tools/pawson'
    >
    > 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.

    Maybe a corrupted filesystem? Not sure what system you use, but I found this:

    http://svn.haxx.se/users/archive-2004-06/0001.shtml

    Try running a check program.


    --
    Gruß/Regards
    Thomas Schraitle




  • 4.  RE: [docbook-apps] DocBook snapshot SVN problem

    Posted 05-03-2013 19:48
    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


  • 5.  Re: [docbook-apps] DocBook snapshot SVN problem

    Posted 05-04-2013 15:38
    On 05/03/2013 02:47 PM, honyk wrote:
    > But I don't know if something like this is applicable to this situation.

    Now that you mention it, that's probably what happened in this case.

    Thanks,
    David




Related Content