unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: bzr not working?
Date: Thu, 13 Oct 2011 10:13:33 +1100	[thread overview]
Message-ID: <CAC=50j9gxuRULe96auEhkdqcFPnEQSRfA9F4nWhB1_DNew9jiw@mail.gmail.com> (raw)
In-Reply-To: <83ty7ewqeu.fsf@gnu.org>

On Wed, Oct 12, 2011 at 7:43 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Wed, 12 Oct 2011 10:35:13 +1100
>> From: Tim Cross <theophilusx@gmail.com>
>> Cc: emacs-devel@gnu.org
>>
>> Has anyone heard anything more regarding a resolution for this issue?
>> I've heard nothing from the savannah admins and stil cannot access the
>> bzr repository.
>
> You didn't subscribe to savannah-hackers-public, and evidently don't
> read the archives, so you are unaware of the continuing discussion on
> this matter.  Please look in the archives, if you are interested.
>
> In a nutshell, after a day and a half of testing on 3 different
> machine, my conclusion is that the problem I succeeded to reproduce is
> a different problem.  It evidently causes any bzr connection that
> takes longer than 1 hour to be forcibly dropped after precisely 1
> hour.  (Due to the long time, I can only reproduce this with an
> initial "bzr branch" command, and only on machines with slow
> connection.)  There's probably some timeout somewhere on savannah, and
> savannah admins will be looking for it.
>
> But that is not your problem, because you reported a much faster
> disconnect.  So I suggest that you run "bzr -Dhpss pull" on the
> machine where this happens, and post the last portion of the .bzr.log
> file as a followup to your original message.  That should give the
> savannah admins information about what happens in the transport that
> causes the problem.
>
> TIA
>
>

I have sent another message to the savannah list with the output from
-Dhpss. I also tried accessing another bzr repository on savannah
(color-theme) and got the same error. However, I can access bzr
repositories on other hosts, such as launchpad.net with no problems,
so it does seem to be savannah specific. I can also use the git
mirrors on savannah with no problems, which is what I'm doing now to
update my emacs code.

While I would prefer to use bzr as it is the 'official' repository,
using git is actually more convenient, seems faster and has better
emacs integration. Now that the git mirror is being updated regularly,
I'm happy to use it for the time being, so this issue is less urgent
for me than it was.

Tim

-- 
Tim Cross
Phone: 0428 212 217



  reply	other threads:[~2011-10-12 23:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-09 22:24 bzr not working? Tim Cross
2011-10-09 22:41 ` Carsten Mattner
2011-10-09 23:13   ` Tim Cross
2011-10-10  3:56 ` Eli Zaretskii
2011-10-10  5:01   ` Tim Cross
2011-10-10  5:59     ` Eli Zaretskii
2011-10-10  6:08       ` Tim Cross
2011-10-10  6:41         ` Eli Zaretskii
2011-10-10  7:39         ` Eli Zaretskii
2011-10-10  8:00           ` Tim Cross
2011-10-10  8:27             ` Eli Zaretskii
2011-10-10 11:53               ` Tim Cross
2011-10-11 23:35                 ` Tim Cross
2011-10-12  8:43                   ` Eli Zaretskii
2011-10-12 23:13                     ` Tim Cross [this message]
2011-10-19 21:33                       ` Tim Cross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC=50j9gxuRULe96auEhkdqcFPnEQSRfA9F4nWhB1_DNew9jiw@mail.gmail.com' \
    --to=theophilusx@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).