From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: bzr not working? Date: Mon, 10 Oct 2011 22:53:51 +1100 Message-ID: References: <83y5wtxzwv.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1318247642 27535 80.91.229.12 (10 Oct 2011 11:54:02 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 10 Oct 2011 11:54:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 10 13:53:58 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RDEQg-0000nc-C2 for ged-emacs-devel@m.gmane.org; Mon, 10 Oct 2011 13:53:58 +0200 Original-Received: from localhost ([::1]:47015 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDEQg-0006nW-10 for ged-emacs-devel@m.gmane.org; Mon, 10 Oct 2011 07:53:58 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:33729) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDEQd-0006nO-MW for emacs-devel@gnu.org; Mon, 10 Oct 2011 07:53:56 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDEQc-0000bp-OI for emacs-devel@gnu.org; Mon, 10 Oct 2011 07:53:55 -0400 Original-Received: from mail-iy0-f169.google.com ([209.85.210.169]:42733) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDEQa-0000bA-NQ; Mon, 10 Oct 2011 07:53:52 -0400 Original-Received: by iaen33 with SMTP id n33so9705142iae.0 for ; Mon, 10 Oct 2011 04:53:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=C4lF2iWJ4meuJYZvKTXmQJqydfQABTlukm9qNTJGM+o=; b=oymYUco4jj5DN8+XIxQyws/ulYmj1rt3jp6yYGKFSo7pV7kSGRis/SzAJg/IKNDNr/ k2GjSopkWgdJCrLYajVBeGnVtJglGxCr1RdIkosl6bMxxGlJOAvtn7eeOjcMyjd8fHF4 7r+6LF7sII2wxV2AbaGFaZTt9kBFFYyZGIaqc= Original-Received: by 10.231.8.18 with SMTP id f18mr8257477ibf.6.1318247631593; Mon, 10 Oct 2011 04:53:51 -0700 (PDT) Original-Received: by 10.231.12.67 with HTTP; Mon, 10 Oct 2011 04:53:51 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.210.169 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:144816 Archived-At: On Mon, Oct 10, 2011 at 7:27 PM, Eli Zaretskii wrote: >> Date: Mon, 10 Oct 2011 19:00:34 +1100 >> From: Tim Cross >> Cc: emacs-devel@gnu.org >> >> On Mon, Oct 10, 2011 at 6:39 PM, Eli Zaretskii wrote: >> >> Date: Mon, 10 Oct 2011 17:08:54 +1100 >> >> From: Tim Cross >> >> Cc: emacs-devel@gnu.org >> >> >> >> OK, so that makes two who can issue the same command as me and it >> >> would seem only me who cannot. >> > >> > I "succeeded" to reproduce this on one machine to which I have >> > access. =A0So you are not alone. =A0Posted the info to >> > savannah-hackers-public. >> > >> >> Got home and tried it on my home machine. Exactly same setup, using 64 >> bit xubuntu instead of 32 bit and all works fine with no problems! On >> the other machine, I was able to access other bzr repositories i.e. >> the VM repo on launchpad, with no problems, so whatever the issue is, >> it seems specific to the emacs repo on savannah (and maybe other bzr >> repos on savannah???). > > Is it possible that you got the error after approximately 1 hour? =A0Or > was it almost immediate? =A0For "bzr pull", I'd expect the latter, but a > full initial "bzr branch" can take an hour, depending on your > connection speed. > I'm on a fairly fast link, so I would expect a bzr branch to only take about 25-30 min max (going from memory). The current error occurs quite quickly in both cases - no real difference in time between issuing the commands and getting the error for either the pull or branch. Tim --=20 Tim Cross