From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: bazaar: "unable to obtain lock" Date: Tue, 29 Dec 2009 13:42:50 -0500 Message-ID: <87eimdmxjp.fsf@red-bean.com> References: <873a2tof02.fsf@red-bean.com> Reply-To: Karl Fogel NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1262112196 2594 80.91.229.12 (29 Dec 2009 18:43:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2009 18:43:16 +0000 (UTC) Cc: Emacs developers To: Juanma Barranquero Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 29 19:43:08 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NPh27-0000kB-UL for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 19:43:04 +0100 Original-Received: from localhost ([127.0.0.1]:49665 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPh28-00025S-6v for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 13:43:04 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPh22-00025D-SH for emacs-devel@gnu.org; Tue, 29 Dec 2009 13:42:58 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPh1x-00024Z-8G for emacs-devel@gnu.org; Tue, 29 Dec 2009 13:42:57 -0500 Original-Received: from [199.232.76.173] (port=42358 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPh1w-00024V-TA for emacs-devel@gnu.org; Tue, 29 Dec 2009 13:42:53 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.206.141]:41378) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NPh1w-0000rC-LM for emacs-devel@gnu.org; Tue, 29 Dec 2009 13:42:52 -0500 Original-Received: from localhost ([127.0.0.1]:44403 helo=floss ident=kfogel) by sanpietro.red-bean.com with esmtp (Exim 4.71) (envelope-from ) id 1NPh1u-0002zu-P0; Tue, 29 Dec 2009 12:42:50 -0600 In-Reply-To: (Juanma Barranquero's message of "Tue, 29 Dec 2009 18:44:02 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:118953 Archived-At: Juanma Barranquero writes: >On Tue, Dec 29, 2009 at 18:40, Karl Fogel wrote: >> I don't know how often this is likely to happen, nor exactly what >> circumstances cause it (some kind of uncompleted transaction?). =C2=A0I >> 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?