Re: [beuc@gnu.org: Re: [Savannah-hackers-public] bzr move from sftp:// to bzr+ssh:// [done]]
Andreas Schwab
> What does this mean? What was the problem with sftp:// that
> necessitated this rather, er, sudden move?
It's ridiculous slowness.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Eli Zaretskii
> Date: Sun, 10 Oct 2010 14:56:38 +0200
> Mail-Copies-To: never
>
> >> We tried to find contributors to move bzr repositories from sftp:// to
> >> bzr+ssh:// , however this proved unsuccessful.
> >>
> >> This is becoming a problem, with some of you switching away from bzr
> >> for that reason.
>
> What does this mean? What was the problem with sftp://
It's slow and inefficient. We've been told by Bazaar developers to
switch to bzr+ssh (a.k.a. "smart server") since day one, when we
started to complain about the slowness.
Now we will see if the smart server is indeed a solution to our
problems or part of them. But at least Bazaar developers will no
longer have an excuse.
> that necessitated this rather, er, sudden move?
Sudden my foot! It took 10 months to get there, and in the end all
that was needed was a determined sysadmin.
B Smith-Mannschott
>
> FYI
>
> ------- Start of forwarded message -------
> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE
> autolearn=unavailable version=3.3.1
> Date: Sun, 10 Oct 2010 13:57:17 +0200
> From: Sylvain Beucler <be...@gnu.org>
> To: savannah-ha...@gnu.org
> Subject: Re: [Savannah-hackers-public] bzr move from sftp:// to bzr+ssh://
> [done]
> In-Reply-To: <2010101010...@perso.beuc.net>
>
> Hi,
>
> The migration should be completed now.
>
> bzr:// and bzr+ssh:// are enabled.
> sftp:// is disabled.
>
> Your project bzr page is updated with the new URLs, e.g.:
> https://savannah.gnu.org/bzr/?group=emacs
> https://savannah.gnu.org/bzr/?group=pdf
>
The instructions on these pages are certain to be frustrating for a newbie:
> For a repository with separate branch directories (trunk, devel, …), use:
>
> bzr branch bzr://bzr.savannah.gnu.org/emacs/branch
There is no branch named "devel". There is no obvious way to learn the
names of available branches. Should we guess?
> http://bzr.savannah.gnu.org/lh/emacs
the web-based repository browser
is broken:
> "loggerhead disabled due to unstability; if you're interesting in maintaining it, please contact us"
s/unstability/instability/
> For a repository with only a top-level .bzr directory, use:
> bzr branch bzr://bzr.savannah.gnu.org/emacs
What does that even mean? Is it some sort of mangled allusion to 'bzr
init' versus 'bzr init-repository'? It doesn't work as written since
'emacs' is not a branch.
// Ben
Lars Magne Ingebrigtsen
> It's slow and inefficient. We've been told by Bazaar developers to
> switch to bzr+ssh (a.k.a. "smart server") since day one, when we
> started to complain about the slowness.
Why didn't we switch to brz+ssh a long time ago? This is the first I've
heard of it...
--
(domestic pets only, the antidote for overdose, milk.)
la...@gnus.org * Lars Magne Ingebrigtsen
Eli Zaretskii
> Mail-Copies-To: never
>
> Eli Zaretskii <el...@gnu.org> writes:
>
> > It's slow and inefficient. We've been told by Bazaar developers to
> > switch to bzr+ssh (a.k.a. "smart server") since day one, when we
> > started to complain about the slowness.
>
> Why didn't we switch to brz+ssh a long time ago? This is the first I've
> heard of it...
Reportedly, there were some untold difficulties to do so. Given the
number of minutes it took today, I have my doubts.
If you really want the details, they should be in the archives of
savannah-hackers-public mailing list.
Eli Zaretskii
> From: B Smith-Mannschott <bsmit...@gmail.com>
>
> > Your project bzr page is updated with the new URLs, e.g.:
> > https://savannah.gnu.org/bzr/?group=emacs
> > https://savannah.gnu.org/bzr/?group=pdf
> >
>
> The instructions on these pages are certain to be frustrating for a newbie:
>
> > For a repository with separate branch directories (trunk, devel, …), use:
> >
> > bzr branch bzr://bzr.savannah.gnu.org/emacs/branch
>
> There is no branch named "devel". There is no obvious way to learn the
> names of available branches. Should we guess?
"bzr branches" should tell you the names, but it can be slow with
remote repositories.
The name of the branch you want is "trunk". There's another branch
you may want, called "emacs-23", for the bug-fix releases of Emacs
23.x.
Eli Zaretskii
> Date: Sun, 10 Oct 2010 10:36:07 -0400
> Cc: emacs...@gnu.org
>
> > There is no branch named "devel". There is no obvious way to learn the
> > names of available branches. Should we guess?
>
> "bzr branches" should tell you the names, but it can be slow with
> remote repositories.
For the record, it took me 6 minutes to get all the branches in the
Emacs repository from a Windows machine that sits behind a 5MBps
link. On a GNU/Linux machine that is on T1, it took 8 seconds.
Richard Stallman
heard of it...
Because there are not enough people helping on Savannah.
We need more people there. Would anyone like to help?