Re: [Savannah-hackers] Re: url: obsoleting /cvs

[Loic Dachary]

Dave Love writes:
 > >>>>> Loic Dachary writes:
 > 
 >  >   I failed to explain that you should use ssh, as explained in
 > 
 >  > http://savannah.gnu.org/cvs/?group_id=98
 > 
 >  >   Sorry about that,
 > 
 > That doesn't tell me what I need to know to try ssh again.  It says
 > 
 >    You
 >    have to register a CVS/SSH Shared key in the Account Maintenance page
 >    for the machine from which you run cvs.
 > 
 > but `Account Maintenance' isn't linked and I couldn't find what it's
 > referring to.

        It is now linked to https://savannah.gnu.org/account/editsshkeys.php
 
 > The URL above implies that I should set up SSH only to use SSH v1,
 > which I don't wish to do.  I guess it's possible to do it
 > machine-by-machine, in which case the instructions should be explicit.

        It is a bit problematic to include instructions for every 
implementation of ssh. They do not really have the same conventions. 
The instructions included in the page are valid for existing implementations
but going into more details is harder. I guess we should write a page that
explains in detail how to do it for each flavor of ssh. 

        The easiest way in your case is to write a script named ssh1
(unless it already exists which is possible) that "exec ssh -1" or whatever
your ssh flavor use to switch to Protocol 1.

 > Telling people to `export CVS_RSH=ssh' without qualification seems
 > unwise, partly because that's bash-specific as far as I know, and
 > partly because it might clobber uses of remote CVS repositories which
 > don't use SSH.

        That will have no impact on other cvs protocols (pserver, kserver
or gserver).

 > Since I seem to have lost access to the old repository I can't
 > currently work on w3 and url.
 > 
 > Is the same thing going to happen with the Emacs repository?

        It only happened with w3 and url because wmperry told us to go ahead.
We would not do this on our own. 

        I understand you are stuck and I'm very sorry for that. If
this is too much of a burden for you could you synchronize with your
co-developers (and wmperry specifically) ? We can go back to the old
way of doing things without much efforts.  There are good reasons to
get rid of pserver access but not at the cost of preventing people to
work on their projects. It is definitely better to switch to ssh access
while pserver is still working and not because pserver cease to work.

        Cheers,

-- 
Loic   Dachary         http://www.dachary.org/  address@hidden
24 av Secretan         http://www.senga.org/      address@hidden
75019    Paris         T: 33 1 42 45 09 16          address@hidden
        GPG Public Key: http://www.dachary.org/loic/gpg.txt