emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bzr not working?


From: Tim Cross
Subject: Re: bzr not working?
Date: Wed, 12 Oct 2011 10:35:13 +1100

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.

Given the recent discussions regarding git and if git is now being
updated regularly, I'm thinking maybe the simplest solution is to just
switch to git as it has better emacs integration anyway.

Tim


On Mon, Oct 10, 2011 at 10:53 PM, Tim Cross <address@hidden> wrote:
> On Mon, Oct 10, 2011 at 7:27 PM, Eli Zaretskii <address@hidden> wrote:
>>> Date: Mon, 10 Oct 2011 19:00:34 +1100
>>> From: Tim Cross <address@hidden>
>>> Cc: address@hidden
>>>
>>> On Mon, Oct 10, 2011 at 6:39 PM, Eli Zaretskii <address@hidden> wrote:
>>> >> Date: Mon, 10 Oct 2011 17:08:54 +1100
>>> >> From: Tim Cross <address@hidden>
>>> >> Cc: address@hidden
>>> >>
>>> >> 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.  So you are not alone.  Posted 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?  Or
>> was it almost immediate?  For "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
>
>
> --
> Tim Cross
>



-- 
Tim Cross
Phone: 0428 212 217



reply via email to

[Prev in Thread] Current Thread [Next in Thread]