I'm really starting to think this is happening on the SourceForge side.  Sorry I
can't help you any more than this.

Noel




[EMAIL PROTECTED] on 06/06/2000 07:10:15 PM

To:   [EMAIL PROTECTED], [EMAIL PROTECTED]
cc:   [EMAIL PROTECTED]
Subject:  Re: CVS access using SSH






>OK. This kinda tells me your CVSROOT should point to the one without "cvs.".
>
>>Does CVS use the CVSROOT to fire off the SSH command? Can CVS be instructed to
>use a location for SSH other than CVSROOT?
>
>I don't understand your questions. Can you explain a bit more?
>
>>Or is there a way to get CVS to drop the "cvs." when executing SSH, but to
>include "cvs." for everything else?
>
>I'm not convinced that this would be a viable workaround. Have you tried to
>remotely execute a command using SSH? Maybe this is where it's going wrong?
>
>Noel

If I edit the CVSROOT (actually by changing the ROOT file found in the CVS
subdirectory), here is the result:

C:\src>cvs -t co -c
CVS.EXE checkout: notice: main loop with
CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot/panjasource
> Starting server: ssh panjasource.sourceforge.net -l sheldon_samuels cvs server
Cannot access /cvsroot/panjasource/CVSROOT
No such file or directory

You can see that now SSH works without asking for a password, but I get an
errorthat no file or directory is found. And this specific project does have
files and has been imported, checked out, updated, etc. through CVS by entering
a password everytime. So I can either have CVS work properly or have SSH work,
but not both.

For completeness, here is the same action, with cvs. in the root path.

C:\src>cvs -t co -c
CVS.EXE checkout: notice: main loop with
CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot/panjasource

 -> Starting server: ssh cvs.panjasource.sourceforge.net -l sheldon_samuels cvs
server
Password:

Now the cvs command works, but I was required to enter a password.  The only
difference being the fact that "cvs." is entered in the CVSROOT path.

Does this help explain the problem?

Thanks.
Sheldon Samuels







This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.

Reply via email to