From: Karl Fogel <kfogel@red-bean.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: bazaar: "unable to obtain lock"
Date: Tue, 29 Dec 2009 12:40:29 -0500 [thread overview]
Message-ID: <873a2tof02.fsf@red-bean.com> (raw)
In-Reply-To: <f7ccd24b0912290914l449a9af5q9127efd50f05de51@mail.gmail.com> (Juanma Barranquero's message of "Tue, 29 Dec 2009 18:14:07 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
>Trying to commit right now produces the following message:
>
>Unable to obtain lock
>sftp://bzr.savannah.gnu.org/srv/bzr/emacs/trunk/.bzr/branch/lock
>held by bob@gnu.org on host benthic [process #13025]
>locked 6 hours, 10 minutes ago
>Will continue to try until 18:17:32, unless you press Ctrl-C
>If you're sure that it's not being modified, use bzr break-lock
>sftp://bzr.savannah.gnu.org/srv/bzr/emacs/trunk/.bzr/branch/lock
I don't know how often this is likely to happen, nor exactly what
circumstances cause it (some kind of uncompleted transaction?). I
assume if bob confirms he's not active, then you can break the lock.
But still, if this happens a lot, it's going to be very annoying.
Does anyone know if bzr+ssh:// access would avoid this? That's the
access method the bzr developers recommend; the Savannah ticket about it
is https://savannah.gnu.org/support/?107077.
-Karl
next prev parent reply other threads:[~2009-12-29 17:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 17:14 bazaar: "unable to obtain lock" Juanma Barranquero
2009-12-29 17:40 ` Karl Fogel [this message]
2009-12-29 17:44 ` Juanma Barranquero
2009-12-29 18:42 ` Karl Fogel
2009-12-29 20:39 ` Juanma Barranquero
-- strict thread matches above, loose matches on Subject: below --
2009-12-29 23:53 Robert J. Chassell
2009-12-30 3:39 ` Karl Fogel
2009-12-30 15:15 ` Robert J. Chassell
2009-12-31 19:14 ` Karl Fogel
2010-01-01 0:19 ` Robert J. Chassell
2009-12-31 19:15 ` Karl Fogel
2009-12-30 16:43 ` Robert J. Chassell
2009-12-30 17:25 ` Andreas Schwab
2009-12-30 21:46 ` Robert J. Chassell
2009-12-30 22:18 ` Andreas Schwab
2009-12-31 1:48 ` Robert J. Chassell
2009-12-31 4:29 ` Óscar Fuentes
2009-12-31 6:59 ` Óscar Fuentes
2009-12-31 11:32 ` Robert J. Chassell
2009-12-31 14:57 ` James Cloos
2009-12-30 23:34 ` Kevin Ryde
2009-12-31 0:30 ` Óscar Fuentes
2009-12-31 0:44 ` Lennart Borgman
2009-12-31 1:07 ` Óscar Fuentes
2009-12-31 1:24 ` Lennart Borgman
2010-01-03 22:38 ` Kevin Ryde
2010-01-04 7:05 ` Eli Zaretskii
2010-01-05 21:20 ` Kevin Ryde
2010-01-01 9:59 ` Stephen J. Turnbull
2010-01-01 10:16 ` Óscar Fuentes
2010-01-01 16:42 ` Jason Earl
2009-12-30 9:19 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=873a2tof02.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.