CVS import doubles directory name in repository, why?

qhhatman · 02-26-2009, 09:37 PM

I'm just setting up a new server with Ubuntu 8.10 (intrepid Ibex) and an creating the CVS repository. When I when to create my first project in the repository I did the standard command: cvs import -m "create proj" abcd comp start
The result in the repository was .../cvsroot/abcd/abcd/myDirs
Why did it create directory abcd twice? I expected .../cvsroot/abcd/myDirs.
When I tried this command: cvs import -m "msg" abcd/efgh comp start
it created: .../cvsroot/abcd/efgh/abcd/efgh/myDirs
I am running the cvs import command from the directory containing abcd and directly under abcd are several directories (none named abcd) I'm referring to as myDirs above. I guess I can make this work but I would just as soon it didn't double up the directories as it is doing.
Thanks in advance for any input on this.

tronayne · 02-28-2009, 06:16 AM

From what you entered, it looks like you're doing it properly

Code:

cvs import -m "message" repository vendor-tag release-tag

so I'd wonder about environment settings and the like; e.g., are you using a local repository address (CVSROOT=/usr/local/cvsroot) or server

Code:

:pserver:userid@server.network:/usr/local/cvsroot

(although I cannot imagine that would be a problem, you never know).

If you're using pserver, you do have these in /etc/services?

Code:

cvspserver      2401/tcp   #CVS network server
cvspserver      2401/udp   #CVS network server
cvsup           5999/tcp   #CVSup file transfer/John Polstra/FreeBSD

(the last one isn't strictly necessary, but the first two are) and you have this
in /etc/inetd.conf?

Code:

# CVS - Concurrent Versions System
2401    stream  tcp     nowait  root    /usr/bin/cvs    cvs -f --allow-root=/usr/local/cvsroot pserver

If you're using pserver, have you got a file, .cvspass in your home directory.

Other than those, did you remember to run cvs init after initially defining the CVSROOT environment variable; do you have the CVSROOT directory tree in /usr/local/cvsroot (or wherever your CVSROOT lives). Can you create files in the repository (I've actually seen this kind of thing when for some reason a user does not have permission to write in the repository -- but that was long, long ago). Did you put a passwd file in /usr/local/cvsroot/CVSROOT and have you logged in (if you're using pserver).

I can't really think of anything other than those that might -- might! -- cause this condition but something you can try is blow away /usr/local/cvsroot, make sure you have CVSROOT defined properly, do mkdir /usr/local/cvsroot, set the group on that directory to what you want then run cvs init and see what you happens. Who knows what evil lurks in the night, eh.

Hope this helps some.

qhhatman · 03-02-2009, 07:22 PM

Thanks for the input tronayne. I'm only working on the local setup at the moment. I've done all the stuff you've suggested and still have the same situation going on. Really strange. It is good to hear you saying the same things I'm doing. Helps me to know I'm not a complete idiot--which I have been known to be in the past :-). If you get any more ideas please let me know. All the best to you.

qhhatman · 03-04-2009, 03:33 AM

Well now I'm feeling sheepish for being so stupid. My problem was that I didn't cd into the directory that I was creating the module for. In my initial example I should have first done cd abcd, but I didn't. I mistakenly thought that when I called out the directory name abcd in the cvs import command it was to tell the command which directory I wanted to import and it would just look below that one for the files. I was wrong. So I post this so that others running into my errant thinking don't get the same results as me. Cheers.

tronayne · 03-04-2009, 06:10 AM

Hey, stuff happens -- been there, did that, suffered the consequences and slings and arrows of outrageous fortune. It's really fun when you do it in the parent directory and wind up with your entire development tree in one repository directory...

Glad you figured it out.