CODEWITHSUNDEEP
linuxcvs
user1116805
user1116805

Reputation: 31

cvs command on Ubuntu 11.10 seems broken?

I have a clean install of Ubuntu 11.10 on my laptop. I installed CVS with the command "sudo apt-get install cvs". I have never had any trouble with the CVS command before, but in this case, I get this:

$ cvs
cvs checkout: No CVSROOT specified!  Please use the `-d' option
cvs [checkout aborted]: or set the CVSROOT environment variable.

The real puzzle to me is why it is assuming the "checkout" command. That doesn't happen in other installations, where it just gives a usage message. But, OK, there is no CVSROOT defined, so if I define one, say like this: 

$ export CVSROOT=:pserver:[email protected]:/cvsroot

I then get another very strange message, which again indicates that it is assuming "checkout":

$ cvs
co: invalid option -- 'z'
Usage:
  cvs checkout [-ANPRcflnps] [-r rev] [-D date] [-d dir]
  [-j rev1] [-j rev2] [-k kopt] modules...

This isn't just with the plain "cvs" command, by the way - cvs login, cvs checkout, cvs update and cvs someGobbledegook all give the same result.

Any ideas what to try next?

Upvotes: 1

Views: 2957

Answers (1)

paulsm4
paulsm4

Reputation: 121649

1) CVS should be installable and should work fine on any version of Ubuntu (and Debian, and Fedora, etc etc)

2) Your "export" syntax (at least what you posted) is incorrect:

# BAD
export CVSROOT=export CVSROOT=:pserver:[email protected]:/cvsroot

# BETTER
export CVSROOT=:pserver:[email protected]:/cvsroot

3) Make sure /cvsroot exists and has appropriate permissions.

Since you're using pserver (not really a good idea, but...) make sure user "me.abc.com" is defined in your /cvsroot/passwd file

4) Make sure the "cvs" command isn't aliased

5) Make sure the pserver service is configured, enabled and running (again, pserver isn't necessarily a good idea)

6) This link is probably still applicable to your version of Ubuntu:

https://help.ubuntu.com/10.04/serverguide/C/cvs-server.html

ADDENDUM: 7) Check your firewall (port 2401)

8) Take a Wireshark trace: see if there's any attempted connections

Upvotes: 1

Related Questions