From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Morris Newsgroups: gmane.emacs.devel Subject: Re: what's the matter with the bzr server? Date: Fri, 07 Jun 2013 12:06:21 -0400 Message-ID: References: <87r4ge2tqq.fsf@kanis.fr> <83y5amtf30.fsf@gnu.org> <83wqq6teii.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1370621187 3302 80.91.229.3 (7 Jun 2013 16:06:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 7 Jun 2013 16:06:27 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jun 07 18:06:28 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UkzBL-00019M-Om for ged-emacs-devel@m.gmane.org; Fri, 07 Jun 2013 18:06:27 +0200 Original-Received: from localhost ([::1]:53868 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UkzBL-0001gg-A4 for ged-emacs-devel@m.gmane.org; Fri, 07 Jun 2013 12:06:27 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43638) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UkzBI-0001gS-4o for emacs-devel@gnu.org; Fri, 07 Jun 2013 12:06:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UkzBG-0004ko-KK for emacs-devel@gnu.org; Fri, 07 Jun 2013 12:06:24 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:56289) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UkzBG-0004kj-I8 for emacs-devel@gnu.org; Fri, 07 Jun 2013 12:06:22 -0400 Original-Received: from rgm by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1UkzBF-0001Ks-IX; Fri, 07 Jun 2013 12:06:21 -0400 X-Spook: spy basement kilo class quiche FSF airframe Gazprom X-Ran: \l@QFFMcGM]JH,yuH){qC`b#};)4cA+7z;z;E.@2`y3:LVs+.fRG|!e\_0di'h.i:DRd@n X-Hue: magenta X-Attribution: GM In-Reply-To: <83wqq6teii.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Jun 2013 13:13:25 +0300") User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:160231 Archived-At: Firstly, it is sort of flattering that people think emacs-devel can fix every problem in the known universe, but isn't it kind of obvious that we don't manage the GNU infrastructure, and that this is not the right address for problems with Savannah? I don't know how many times this needs to be said. Anyway, we are here now, and by a total coincidence I can actually look into this as of a few days ago. Eli Zaretskii wrote: >> > bzr branch bzr+ssh://ivankanis@bzr.savannah.gnu.org/emacs/trunk trunk >> > Connection Timeout: disconnecting client after 300.0 seconds Don't know where that comes from. AFAIK there is no timeout on bzr+ssh. There is a 5 hour time out on anonymous bzr:// access, which seems reasonable. Nothing has changed in this area recently AFAIK. >> Someone or something has reset the timeout to a ridiculously small >> value. Please ask on Savannah-hackers-public@gnu.org to fix this; it >> was 4 or even 8 hours last time I checked. > > Actually, I take that back: I just tried this myself, and it is > working for 600 sec already without timing out. Stay tuned. Indeed. (But please everybody don't go hammering the server to check what the value is for you.) Hmm, seems this may be internal to bzr: https://bugs.launchpad.net/bzr/+bug/1112797 Maybe it is only supposed to affect commit though? I can see the 300 sec timeout in the logs on the server...