From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Locks on the Bzr repository Date: Thu, 19 Aug 2010 12:43:39 -0400 Message-ID: References: <4C6D57EE.70109@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1282236736 11407 80.91.229.12 (19 Aug 2010 16:52:16 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 19 Aug 2010 16:52:16 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jason Rumney Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 19 18:52:14 2010 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.69) (envelope-from ) id 1Om8La-000429-Fv for ged-emacs-devel@m.gmane.org; Thu, 19 Aug 2010 18:52:10 +0200 Original-Received: from localhost ([127.0.0.1]:46613 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Om8LZ-0003Xd-JN for ged-emacs-devel@m.gmane.org; Thu, 19 Aug 2010 12:52:09 -0400 Original-Received: from [199.232.76.173] (port=49014 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Om8DQ-0007PK-3e for emacs-devel@gnu.org; Thu, 19 Aug 2010 12:43:44 -0400 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Om8DO-0003Zo-L6 for emacs-devel@gnu.org; Thu, 19 Aug 2010 12:43:43 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:60193) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Om8DO-0003Zj-E9 for emacs-devel@gnu.org; Thu, 19 Aug 2010 12:43:42 -0400 Original-Received: from dann by fencepost.gnu.org with local (Exim 4.69) (envelope-from ) id 1Om8DL-0005jt-QG; Thu, 19 Aug 2010 12:43:39 -0400 In-Reply-To: <4C6D57EE.70109@gnu.org> (Jason Rumney's message of "Fri\, 20 Aug 2010 00\:12\:30 +0800") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (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:128878 Archived-At: Jason Rumney writes: > On 19/8/2010 11:40 PM, Stefan Monnier wrote: >> A couple times now, I've had the following kind of message when trying >> to commit: >> >> Unable to obtain lock sftp://bzr.sv.gnu.org/srv/bzr/emacs/trunk/.bzr/branch/lock >> held by jasonr@gnu.org on host wanchan [process #23356] >> locked 28 minutes, 51 seconds ago >> >> The first time I thought it was a stale lock so I broke it, but then it >> came right back, so I suspect it might be due to something else. >> Could it be that bzr grabs the lock when you do "bzr commit" and keep it >> held for as long as you're editing the commit message? > > I don't think editing the commit message is the problem, but the fact > that to do anything with the master repository involves downloading > and/or uploading at least 4MB of data, on a connection which > fluctuates between 0 and 100kb/s, mostly in the 6 - 20kb/s range. > >> If that's indeed the culprit, I think it's a misfeature of Bzr, but at >> least we can workaround it by using "bzr commit -m<...>", which I would >> then *strongly* recommend. > > I think the misfeature is that we are still using sftp access, which > might be OK for users in well connected parts of the world like US, > Europe and Japan, but from here is unusably slow. I have seen the lock problem happen when using -m<...> and on very well connected machine, so it's might be just bzr being bzr.