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 13:42:50 -0500 [thread overview]
Message-ID: <87eimdmxjp.fsf@red-bean.com> (raw)
In-Reply-To: <f7ccd24b0912290944p540557b3t26d1fd14d6235434@mail.gmail.com> (Juanma Barranquero's message of "Tue, 29 Dec 2009 18:44:02 +0100")
Juanma Barranquero <lekktu@gmail.com> writes:
>On Tue, Dec 29, 2009 at 18:40, Karl Fogel <kfogel@red-bean.com> wrote:
>> 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.
>
>As the break-lock help says:
>
> CAUTION: Locks should only be broken when you are sure that the process
> holding the lock has been stopped.
>
>I think someone with admin access should do the unlocking.
Hmm, I'm not sure admin access is necessary. The "process" here is
driven by bob's sftp from the client side -- if he stopped hours ago,
then the lock is almost surely just dangling on the server side.
But I don't know enough about Bazaar to be sure. Can you ask on the
Bazaar list to check?
next prev parent reply other threads:[~2009-12-29 18:42 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
2009-12-29 17:44 ` Juanma Barranquero
2009-12-29 18:42 ` Karl Fogel [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eimdmxjp.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).