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 12:40:29 -0500 Message-ID: <873a2tof02.fsf@red-bean.com> References: Reply-To: Karl Fogel NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262108591 23613 80.91.229.12 (29 Dec 2009 17:43:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 29 Dec 2009 17:43:11 +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 18:43:04 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 1NPg63-0007UB-7M for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 18:43:03 +0100 Original-Received: from localhost ([127.0.0.1]:47216 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPg63-00015s-47 for ged-emacs-devel@m.gmane.org; Tue, 29 Dec 2009 12:43:03 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPg3g-0008Ge-Aa for emacs-devel@gnu.org; Tue, 29 Dec 2009 12:40:36 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPg3b-0008EW-Qk for emacs-devel@gnu.org; Tue, 29 Dec 2009 12:40:35 -0500 Original-Received: from [199.232.76.173] (port=45758 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPg3b-0008EO-Ej for emacs-devel@gnu.org; Tue, 29 Dec 2009 12:40:31 -0500 Original-Received: from sanpietro.red-bean.com ([66.146.206.141]:49688) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NPg3b-0007oE-2n for emacs-devel@gnu.org; Tue, 29 Dec 2009 12:40:31 -0500 Original-Received: from localhost ([127.0.0.1]:35357 helo=floss ident=kfogel) by sanpietro.red-bean.com with esmtp (Exim 4.71) (envelope-from ) id 1NPg3Z-0000en-Ey; Tue, 29 Dec 2009 11:40:29 -0600 In-Reply-To: (Juanma Barranquero's message of "Tue, 29 Dec 2009 18:14:07 +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:118940 Archived-At: Juanma Barranquero 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