Re: CVS help needed urgently!

[Todd Denniston]

Sadia Tahseen wrote, On 03/10/2008 05:42 PM:
> Hi ,
>  I am facing the problem booth on client and server side.
> Please look below for the errors I get.
<SNIP>
> <todd said>
> If you are using NIS/LDAP then all the clients have the same user names, 
> passwords and groups.
> But you have not indicated that the systems are using NIS/LDAP or independent 
> user authentication/authorization configurations.
> </todd said>
>
> HERE USERS HAVE NIS AND EACH USER HAS AN INDEPENDANT 
> USER AUTHENTICATION TO ACCESS THE SYSTEMS IN NETWORK
<todd said>
Thanks, that makes thinking about this stuff easier.
</todd said>

> > so do I need to make any changes to it so that they 
> > can access the cvsgroup I created with gid 800?
<SNIP>
> <todd said>
> then as sadia on cvs_server:
> cd /appl/src/cvs/
> mkdir JavaAppl
> pwd #assumption it returns /appl/src/cvs/
> export CVSROOT=/appl/src/cvs/JavaAppl
> cvs init
> mkdir JavaAppl/projectdir
> chown :sadiascvsgroup JavaAppl/projectdir
> chmod g+rws JavaAppl/projectdir
> #you'll want to tighten up security on the following directory later.
> chown :sadiascvsgroup JavaAppl/CVSROOT
> chmod g+rws JavaAppl/CVSROOT
> </todd said>
>
> ERROR:
> address@hidden chmod g+rws JavaAppl/CVSROOT
> chmod: changing permissions of `JavaAppl/CVSROOT': Operation not permitted

<todd said>
There are only two reasons I can think of for that to fail.
try (on cvs_server, as sadia)
`ls -ld /appl/src/cvs/JavaAppl \
        /appl/src/cvs/JavaAppl/CVSROOT \
        /appl/src/cvs/JavaAppl/projectdir`

The reasons are:
1) sadia does not own those directories.
2) those directories are on an nfs server/NAS which is being very pedantic 
about WHO can set those things.
Did the `chmod g+rws JavaAppl/projectdir` work or give the same error?
</todd said>

> <todd said>
> then as sadia on a_workstation:
> export CVSROOT=:ext:cvs_server:/appl/src/cvs/JavaAppl
> export CVS_RSH=ssh
> cvs checkout projectdir
> date > projectdir/mydate
> cvs add projectdir/mydate
> cvs commit -m"a comment" projectdir/mydate
> </todd said>
>
>
> ERRORS:
> address@hidden ~]$ cvs checkout projectdir
> address@hidden's password:
> ? projectdir/mydate
> cvs checkout: Updating projectdir

<todd said>
Looks like you have a repository that already contains the mydate file, that 
should be a good thing, except I was about to have you create the file.
</todd said>

> address@hidden ~]$ cvs add projectdir/mydate
> address@hidden's password:
> cvs add: in directory .:
> cvs [add aborted]: there is no version here; do 'cvs checkout' first

<todd said>
on workstation as sadia, please provide:
`ls -ld ~/projectdir/; ls -l ~/projectdir/`
</todd said>

> address@hidden ~]$ cvs commit -m "a comment" projectdir/mydate
> cvs commit: use `cvs add' to create an entry for projectdir/mydate
> cvs [commit aborted]: correct above errors first!


<todd said>
Are you sure you are feeding me the errors in the order you got them, I 
expected a DIFFERENT error at this point????
something is highly amiss at this point.
You probably have leftovers from several attempts of getting setup at this 
point, some of which probably have permission/ownership problems. (probably 
something owned by root that should be owned by sadia.)
There are two ways out that I can think of.
1) remove the repository and sandboxes that you have created so far and start 
following the email with the description again fresh, if this fails go to 
method 2, while indicating this one failed and how.
2) we have to look at the permission/ownership of everything in $CVSROOT and 
the sandboxes, and then determine what changes have to be made.

The second method is significantly more pain in my book, but it is you who 
gets to pick the method.
</todd said>




<todd said>
BTW anyone who has a better (easier to understand) way to present how to get a 
repository setup and requisite system config, PLEASE give me a hand here.
</todd said>

--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter