Yanglong Zhu writes:Good question. That single sentence made me aware that CVS does need a valid OS user for writing. Karl Fogel and Moshe Bar seem to impress me otherwise.
Fatal error, aborting.
cvs: no such user
*Is* there a user named "cvs" on that system (the server)? If not, why are you trying to run as that user?
Now I aliased the file/fold owner to a OS user cvs_user in the passwd file in the CVSROOT. But it still causes problems.
For example, I modified a file (index.html), then tried to update
cvs -d :pserver:[EMAIL PROTECTED]/path/to/CVSrootDir update
cvs server: cannot open /root/.cvsignore: Permission denied
cvs server: Updating sequeN
cvs server: conflict: sequeN/index.html is modified but no longer in the repository
C sequeN/index.html
When I issue commit, I got this:
cvs -d :pserver:[EMAIL PROTECTED]/path/to/CVSrootDir commit -m "Test commit"
cvs commit: Examining sequeN
cvs server: Up-to-date check failed for `sequeN/index.html'
cvs [server aborted]: correct above errors first!
I think this is permission problem. There are two sets of permissions. The OS level permission and the CVS system permission. I am completely confused about the CVS permissions. How do they work?
-Larry Jones
In my opinion, we don't devote nearly enough scientific research to finding a cure for jerks. -- Calvin
_______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
