[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: permission problem - cannot checkout

From: Roni Abusch
Subject: RE: permission problem - cannot checkout
Date: Tue, 6 Nov 2001 09:20:49 +0200

Thanks Markus, but I have a problem with that - that means that everyone can
go stright to the reporitory and delete projects\files (even accidentaly).
Is there a way that everyone will be able to use CVS and it's projects,
without having permissions to the repository?

-----Original Message-----
From: Markus Warg [mailto:address@hidden
Sent: Monday, November 05, 2001 13:30
To: Roni A.
Cc: address@hidden
Subject: Re: permission problem - cannot checkout


I'm not a cvs guru, but here is how we got things going:

the repository needs to be group writable for a group that all users,
that want to access the cvs, belong to.

If all users are in the group "developers", then all files and
directorys must belong to this group. Directories must be rwx for
group, too (usually drwxrwxr-x).


On Mon, 05 Nov 2001, Roni A. wrote:

> I'm new at CVS, and I tried for the first time to start a project in it.
> I've imported my sources and created a project in CVS, but for some
> I'm the only one that can use it. When other people are trying to checkout
> this project, they get the following message:
> cvs checkout: Updating Proj1
> cvs checkout: failed to create lock directory for `/home/cvsroot/Proj1'
> (/home/cvsroot/Proj1/#cvs.lock): Permission denied
> cvs checkout: failed to obtain dir lock in repository
> cvs [checkout aborted]: read lock failed - giving up
> Can please someone help me and tell me what did I do wrong?
> _______________________________________________
> Info-cvs mailing list
> address@hidden

Markus Warg
VIA NET.WORKS Deutschland GmbH, Bismarckstrasse 120, D-47057 Duisburg
Geschäftsführung: Matt Nydell, Wim Vink. Amtsgericht Duisburg, HRB 7672
Phone: +49 203-3093 159, Fax: +49 203-3093 112
E-Mail: address@hidden
Alle Angebote sind unverbindlich.
Auftraege erledigen wir zu unseren allgemeinen Geschaeftsbedingungen.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]