[Python-Dev] OK, so how do I make CVS actually *work*?

[Greg Stein]

On Thu, Jul 06, 2000 at 08:18:04AM -0400, Eric S. Raymond wrote:
> Greg Stein <gstein@lyra.org>:
> > I used:
> > 
> > $ cvs -z3 -d :ext:gstein@cvs.python.sourceforge.net:/cvsroot/python co python
> > 
> > The instructions on SF didn't quite work. Adding the :ext: in made it work
> > fine for me. I'm using CVS 1.10.6
> 
> snark:~/WWW/python$ cvs -z3 -d :ext:esr@cvs.python.sourceforge.net:/cvsroot/python co python
> esr@cvs.python.sourceforge.net's password: 
> cvs checkout: warning: unrecognized response `' from cvs server
> cvs checkout: warning: unrecognized response `Welcome to cvs1.sourceforge.net' from cvs server
> cvs checkout: warning: unrecognized response `' from cvs server
> cvs checkout: warning: unrecognized response `This is a restricted Shell Account' from cvs server
> cvs checkout: warning: unrecognized response `You cannot execute anything here.' from cvs server
> cvs checkout: warning: unrecognized response `' from cvs server
> cvs [checkout aborted]: end of file from server (consult above messages if any)
> 
> That didn't work either. Anyone got any other ideas?
> 
> I seem to have CVS 1.10.7.

The response looks like the bare text you get when you "ssh" directly to the
server. It prints some stuff then closes the connection.

This would indicate to me that your CVS isn't passing the command over to
the SF machine. Put this file into, say, /tmp/ssh-verbose:

#!/bin/bash
echo COMMAND: $@
exec /usr/bin/ssh -v $@

then do:

$ export CVS_RSH=/tmp/ssh-verbose
$ cvs ... same as above

You should get a long stream of debug output. Right after you enter your
password, you should see a couple lines like:

debug: Sending command: cvs server
debug: Entering interactive session.

If not, then I'd suspect the CVS is invoking SSH incorrectly. The first line
of output should look like:

cvs log: warning: unrecognized response `COMMAND: cvs.python.sourceforge.net
-l gstein cvs server' from cvs server

That `... cvs server' in the command string is the key. I suspect those two
words aren't in your command string, so SSH is just opening an interactive
shell.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/