Re: CVS checkout problems

[Carl Chen]

Hi,

In CVSROOT/config file, a parameter LockDir can set for the lock file. And
this directory should be rwxrwxrwx permission. Or you can set lockdir for
each project.
After you set, all lock file like #xxxxx.lock will be generated under this
directory.
Please try it. 

-----邮件原件-----
发件人: address@hidden
[mailto:address@hidden 代表
address@hidden
发送时间: 2007年3月16日 01:00
收件人: address@hidden
主题: (瑞星提示-此邮件可能是垃圾邮件)info-cvs Digest, Vol 52, Issue 15

Send info-cvs mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.nongnu.org/mailman/listinfo/info-cvs
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of info-cvs digest..."


Today's Topics:

   1. CVS checkout problems (address@hidden)
   2. Re: CVS checkout problems (Larry Jones)
   3. Re: branch deletion (Cloud Burst)


----------------------------------------------------------------------

Message: 1
Date: 14 Mar 2007 11:34:27 -0700
From: address@hidden
Subject: CVS checkout problems
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"

Hi everybody, i have a CVS Server running on GNU/Linux (Debian). The
server uses ssh authentication.

All users use Tortoise CVS client to connect that server.

I have defined the project structure and i've defined the suiable
permissions and all necesary groups/subgroups.

The problem is, when a user needs checkout a specified directory
(DIR1), he needs write permissions on DIR1 because the checkout
process create a temporally file called #cvs.lock. I want users only
can checkout DIR1, not checkin, and if i granted read only permissions
to DIR1 files in order to avoid users overwrite any existent file they
can overwrite it anyway because DIR1 has +w for the cvs group.
On the other hand, .... if i set -w to DIR1 they can't create
DIR1\#cvs.lock file and checkout process fails.

Could someone please help me with this ?

Thanks in advance.



------------------------------

Message: 2
Date: Wed, 14 Mar 2007 16:55:04 -0400 (EDT)
From: address@hidden (Larry Jones)
Subject: Re: CVS checkout problems
To: address@hidden
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

address@hidden writes:
> 
> The problem is, when a user needs checkout a specified directory
> (DIR1), he needs write permissions on DIR1 because the checkout
> process create a temporally file called #cvs.lock.

That's discussed in the manual, along with the solution:

        <http://ximbiot.com/cvs/manual/cvs-1.11.22/cvs_2.html#SEC13>

-Larry Jones

Hmm... That might not be politic. -- Calvin




------------------------------

Message: 3
Date: Wed, 14 Mar 2007 17:20:47 -0700
From: Cloud Burst <address@hidden>
Subject: Re: branch deletion
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

On Wed, 14 Mar 2007 09:28:23 -0500, "seetha natarajan"
<address@hidden> wrote:

>Hi,
>
>how can I delete a branch I wrongly created?
>
>I tried the command: *cvs tag -d -b <branch-name> *
>
>but it doesn't work and the wrong branch still exists!
>
>I dont want to delete the contents of the branch though.

Add "-B" to your command line.


------------------------------

_______________________________________________
info-cvs mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/info-cvs


End of info-cvs Digest, Vol 52, Issue 15
****************************************