I've included two examples below complete with error messages. The first is
me logged into cvs as user cvsadmin in the cvsgrp group. There are two
modules: rat and DEV. The second example is me logged in as user jschwenk
in the users group. Unfortunately, I did not set up the initial repository
nor did I install cvs. Are the files supposed to be read-only?
Example 1:
Here's the top level directory of the DEV module
drwxrwxr-x 6 sc users 1024 May 25 13:53 environments
drwxrwxr-x 11 sc users 1024 May 25 13:57 source
all the files are read-only (just listed a few)
-r--r--r-- 1 sc users 19489 May 25 12:53
IDTGUI_Bundle_de_DE.properties,v
-r--r--r-- 1 sc users 18044 May 25 12:53
IDTGUI_Bundle_en_US.properties,v
-r--r--r-- 1 sc users 1201 May 25 12:53
IDTGUI_CustomisedBundle_de_DE.properties,v
Error while accessing C:\Macros (error 2)
CVSROOT: :pserver:cvsadmin@pilot:/export/cvsroot (password authentication)
TCL is available, shell is enabled : help (select and press enter)
cvs -z9 login
(Logging in to cvsadmin@pilot)
*****CVS exited normally with code 0*****
cvs -z9 checkout -P rat (in directory C:\)
cvs checkout: in directory rat:
cvs checkout: cannot open CVS/Entries for reading: No such file or directory
cvs server: Updating rat
U rat/RatComm.java
cvs checkout: cannot open CVS/Entries.Log: No such file or directory
U rat/RatGuiPilot.java
cvs checkout: cannot open CVS/Entries.Log: No such file or directory
cvs server: Updating rat/scripts
cvs server: failed to create lock directory for
`/export/cvsroot/rat/scripts' (/export/cvsroot/rat/scripts/#cvs.lock):
Permission denied
cvs server: failed to obtain dir lock in repository
`/export/cvsroot/rat/scripts'
cvs [server aborted]: read lock failed - giving up
*****CVS exited normally with code 1*****
cvs -z9 checkout -P DEV (in directory C:\)
cvs checkout: in directory dev:
cvs checkout: cannot open CVS/Entries for reading: No such file or directory
cvs server: Updating dev
cvs server: failed to create lock directory for
`/export/cvsroot/systema/environments/dev'
(/export/cvsroot/systema/environments/dev/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
`/export/cvsroot/systema/environments/dev'
cvs [server aborted]: read lock failed - giving up
*****CVS exited normally with code 1*****
Example 2:
cvs -z9 checkout -P DEV (in directory C:\)
cvs server: Updating dev
cvs server: failed to create lock directory for
`/export/cvsroot/systema/environments/dev'
(/export/cvsroot/systema/environments/dev/#cvs.lock): Permission denied
cvs server: failed to obtain dir lock in repository
`/export/cvsroot/systema/environments/dev'
cvs [server aborted]: read lock failed - giving up
*****CVS exited normally with code 1*****
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 07, 2001 11:56 AM
To: Schwenk, Jeanie
Cc: [EMAIL PROTECTED]
Subject: Re: can't commit! permissions question
Schwenk, Jeanie writes:
>
> Who is supposed to be the owner of the files that are in the respository?
I
> can update and checkout but not commit.
Exactly what error messageare you getting?
In general, you need read access to the files and write access to the
directory. Files are owned by the last user to update them, directories
are owned by the user who added them. If you're on a SysV-like system
(most notably Linux), you may find it useful to set the SGID bit on all
the repository directories (chmod g+s) -- that will cause newly-created
directories to inherit their groupid from the parent directory instead
of using the groupid of the creator.
-Larry Jones
Hmm... That might not be politic. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
