[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "cvs: command not found" but path is ok
From: |
Eric Siegerman |
Subject: |
Re: "cvs: command not found" but path is ok |
Date: |
Tue, 13 May 2003 15:12:09 -0400 |
User-agent: |
Mutt/1.2.5i |
On Tue, May 13, 2003 at 08:40:58AM -0500, Phil R Lawrence wrote:
>
> Eric Siegerman <address@hidden> wrote:
> > On Tue, May 13, 2003 at 05:10:50AM -0500, Phil R Lawrence wrote:
> > > address@hidden phil $ env | grep CVS
> > > CVSROOT=:ext:address@hidden:/home/prl2/projects/cvs
> > > CVS_RSH=ssh
> > > ["cvs checkout Term-Interact" dies with:
> > > /usr/bin/bash: cvs: command not found
> > > ]
> >
> > Try adding (exported of course):
> > CVS_SERVER=/usr/local/bin/cvs
> >
> Hmmm. still no luck. Any other ideas?
>
> address@hidden cvsclient $ env | grep CVS
> CVSROOT=:ext:address@hidden:/home/prl2/projects/cvs
> CVS_SERVER=/usr/local/bin/cvs
> CVS_RSH=ssh
>
> address@hidden cvsclient $ cvs checkout Term-Interact
> /usr/bin/bash: /usr/local/bin/cvs: No such file or directory
> cvs [checkout aborted]: end of file from server (consult above messages if
> any)
Grasping at straws: The CVSROOT appears to have changed. I
expect that's because you censored it the first time ... but if
the change is for real, are you sure there's a /usr/local/bin/cvs
on louie1?
Failing that, this is pretty weird.
Try "cvs -t checkout Term-Interact". In the trace output, the
"Starting server:" line shows you the exact command that the
client CVS is using to (try to) to fire up the server. That'll
give you something to work with; see if you can get a CVS server
running independently of the client. (You can't do anything
useful with it; just see whether you can launch it.)
The CVS server's not very talkative. It just appears to swallow
whatever you type at it. But you can recognize it as follows:
- type a CTRL-D
- type a CTRL-J
It'll say something about "dying gasps" and then exit.
--
| | /\
|-_|/ > Eric Siegerman, Toronto, Ont. address@hidden
| | /
My Wine works. However it crashes about half the time on startup.
Apparently their simulation of windoze API is getting too accurate. :)
- Kyle Sallee