' \,=./ `o
Dustin Cavanaugh, (o o)
--=--=--=--=--=--=--=--=--=--ooO--(_)--Ooo--
System Analyst
University of California, San Diego
9500 Gilman Drive
La Jolla, CA 92093-0903
[EMAIL PROTECTED]
858.534.9781
858.534.8610 (FAX
At 12:05 PM 3/22/2002 , David Everly wrote:
Is there some technique I can use to prevent my developers from
directly altering the cvs repository and force them to use cvs
commands instead?
If developers don't have direct access to the repository (they can't log
onto the repository machine) then
I'm attempting to build cvs server from distribution source. The machine is
Solaris 7. After configuring the software with configure
--without-gssapi, I then did a make and got the following fatal errors
when the make attempted to create cvs:
gcc -g -O2 -o cvs add.o admin.o annotate.o ...
I thought of this right after my first posting and tried
./configure --without-gssapi --without-krb4 and got the same errors.
At 11:45 AM 3/14/2002 , Eric Siegerman wrote:
On Thu, Mar 14, 2002 at 10:54:59AM -0800, Dustin Cavanaugh wrote:
I'm attempting to build cvs server from
That did the trick, so here's the solution one more time for knuckleheads
like me who can't seem to get it right! ;)
1) If a previous 'make' was unsuccessful, do a 'make clean' and 'make
distclean' BEFORE attempting to configure again.
2) './configure --without-gssapi --without-krb4'
3) make
4)
Environment: cvs 1.11.1p running on unix. Clients are mostly wincvs1.13.7+
(in-house modifications to prevent password display on the screen), plink
for ssh connection. Developers have valid login on unix server and are
members of the cvs and users groups.
How do I protect the repository from
At 10:10 AM 3/11/2002 , Douglas Finkle wrote:
Environment: cvs 1.11.1p running on unix.
Clients are mostly
wincvs1.13.7+
(in-house modifications to prevent password display on the
screen)
Huh?
Huh what?
plink for ssh connection.
Also, use Pageant on Windows. UNIX will require
2 things:
1) Stylized text. Yes I know better ... eudora puts a gray bar down the
side of repeated messages instead of the usual . Just to be interesting,
there's no obvious way of turning it off, so I gotta remember to manually
remove it myself. :(
2) The best repository advice I've gotten
I chose to use ssh because: 1) kerberos was not set up on my servers, and
2) its a pain to install and configure, and 3) I have to have secure
connections.
The server is Solaris and the clients are Windows. Thus far, there have
been NO connection problems. Clients all have WinCvs(1.3b6),
I have a community sandbox that I use for cvsweb that has to be updated
after ever commit. commitinfo handles pre-commit processing ... is there a
similar file or technique for post-commit processing?
___
Info-cvs mailing list
[EMAIL PROTECTED]
So, is it necessary to chgrp to cvs every new project that I add to the
repository?
It's not necessary if you set your repository up correctly. My
repository has the following permissions:
$ ls -ld /var/cvs
drwxrwsr-x 16 root cvs 4096 Dec 19 15:34 /var/cvs
My repository is on unix (Sun); the owner is cvs and the group is cvs.
Whenever a user changes one of the Administrative database files, cvs
complains of Permission denied. Users (developers) are members of the cvs
group (though its not their primary group).
I notice that when the database is
I've run into a problem I couldn't find described in the cvs archives. When
committing one of the database files, I get a permission denied:
...
cvs server: Rebuilding administrative file database
cvs server: cannot remove .#modules: Permission denied
cvs server: cannot rename modules to
Did I misunderstand how to use this response? From WinCVS 1.3.6.1b6, I used
the command line option from the Admin dropdown menu:
cvs update -c
update: invalid option -- c
Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev]
...
(Specify the --help global option for a list
14 matches
Mail list logo
