From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: Locks on the Bzr repository Date: Fri, 20 Aug 2010 00:12:30 +0800 Message-ID: <4C6D57EE.70109@gnu.org> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1282235601 2708 80.91.229.12 (19 Aug 2010 16:33:21 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 19 Aug 2010 16:33:21 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 19 18:33:20 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 1Om83K-0008TO-40 for ged-emacs-devel@m.gmane.org; Thu, 19 Aug 2010 18:33:18 +0200 Original-Received: from localhost ([127.0.0.1]:35648 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Om7xl-0000ib-Kn for ged-emacs-devel@m.gmane.org; Thu, 19 Aug 2010 12:27:33 -0400 Original-Received: from [140.186.70.92] (port=40726 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Om7xb-0007RO-Bj for emacs-devel@gnu.org; Thu, 19 Aug 2010 12:27:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Om7jQ-0006cA-NV for emacs-devel@gnu.org; Thu, 19 Aug 2010 12:12:45 -0400 Original-Received: from mail-pz0-f41.google.com ([209.85.210.41]:40944) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Om7jQ-0006by-IO for emacs-devel@gnu.org; Thu, 19 Aug 2010 12:12:44 -0400 Original-Received: by pzk33 with SMTP id 33so1295947pzk.0 for ; Thu, 19 Aug 2010 09:12:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=YOnGWZuHhnaAH5+ZMs/1X/5qPZzMhq0d0wgkd2D7lBY=; b=AtL66EP8ivIC8E+JkCNLcYssFxY8Bq13fD2o8ywx4yYf2yWSh4v+9fUGMizXgHkIWp VQ9aoahuK8f0STiky8hrrQXvIN64UX2Nr8kUAJIgGRoQPG7qSmGIjbREuhMaam26NMOl 7GTQNE2XjoWzob7K3Szk7MgVGnDW81xWeW874= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=nfzwxmBEjo9fW6ltUVl4hpu0tICx6XzG90UZbr78UGG2rJckZA3dNcrpjBVrzAdTGO ZECgjbFO4PGF3J+xNuNaDNeCt+Dplb6rbEH+d8YtG0Fd+PrRJPgWJ1iggRya0GFMM1hO lSgzt1hf4kInvjbKquK2ZBRI9QiUJh1pFH5OI= Original-Received: by 10.142.239.19 with SMTP id m19mr8513813wfh.174.1282234363560; Thu, 19 Aug 2010 09:12:43 -0700 (PDT) Original-Received: from [192.168.249.100] ([202.87.221.130]) by mx.google.com with ESMTPS id 33sm1936820wfg.21.2010.08.19.09.12.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 19 Aug 2010 09:12:42 -0700 (PDT) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) 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:128875 Archived-At: 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.