RE: Info-cvs Digest, Vol 3, Issue 6
Marc, Check the "cvs history" command. It can tell you the date that tags were applied. Cheers, Matt Date: Tue, 4 Feb 2003 11:37:24 -0500 From: "Marc Tessier" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Extracting multiple TAG at the same time Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: list Message: 8 Hi everyone I am wandering if there is any options to extract the most recent = version of a list of TAG? I have tag A, B, C and the I want to get the = most recent files of all three in one cvs checkout or cvs export so I = don't have to check the files version one by one.=20 thanks Marc ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Can't do setuid
On Tue, Feb 04, 2003 at 06:29:04PM -0500, Greg A. Woods wrote: > [ On Tuesday, February 4, 2003 at 17:48:24 (-0500), Eric Siegerman wrote: ] > > chmod -R g+w > > find . -type d -print0 | xargs -0 chmod g+s > > You don't want the ,v files to be writable by anyone. So, just this: > > find . -type d -print0 | xargs -0 chmod g+sw Doh! I'm obviously more sleepy than I thought. Thanks, Greg. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / A distributed system is one on which I cannot get any work done, because a machine I have never heard of has crashed. - Leslie Lamport ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Can't do setuid
[ On Tuesday, February 4, 2003 at 17:48:24 (-0500), Eric Siegerman wrote: ] > Subject: Re: Can't do setuid > > That should only have been done on the directories, NOT on the files. > However, everything should be g+w. So from a standing start, > it'd be something like: > chmod -R g+w > find . -type d -print0 | xargs -0 chmod g+s You don't want the ,v files to be writable by anyone. So, just this: find . -type d -print0 | xargs -0 chmod g+sw -- Greg A. Woods +1 416 218-0098;<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: CVS/Root should record the CVS_RSH environment value...
Greg Woods wrote: > > An extension along the lines: > > :ext-rsh:user@host:/path/to/repo > That could solve the problem as well, but seems to me to be > the wrong approach Indeed, it's not general enough. I wonder if it's not better to have a single file under the CVS subdirectory that encapsulates all the "environmental" info needed for cvs to operate on that work area. Something like CVS/Environment, containing: CVSROOT=... # why have a separate Root and Repository file? CVS_RSH=... # anything else Or any of these entries could be split up enough to make external text processing easier (like Root and Repository are separated these days). -- Shankar. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS/Root should record the CVS_RSH environment value...
[ On Tuesday, February 4, 2003 at 12:35:03 (-0800), Kaz Kylheku wrote: ] > Subject: Re: CVS/Root should record the CVS_RSH environment value... > > What's unfortunate is that the repository identification syntax does > not experss the protocol, so you have to use the CVS_RSH hack to do so, > relying on command compatibility of ssh and rsh. No, that's not the prolem. The _protocol_ in both instances is identical from CVS' point of view. All we're changing is the tool used to invoke the remote execution. This tool's name should be recorded along with the the $CVSROOT information since these two pieces of information undoutably go hand-in-hand. > An extension along the lines: > > :ext-rsh:user@host:/path/to/repo > :ext-ssh:user@host:/path/to/repo > > could be the thing. That could solve the problem as well, but seems to me to be the wrong approach -- Greg A. Woods +1 416 218-0098;<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Can't do setuid
On Tue, Feb 04, 2003 at 04:35:47PM -0500, Brian Kowald wrote: > For my whole repository, I set the file and directory owner to cvs and the > group to cvsusers. I did this recursively. Setting the group is good. Setting the owner doesn't help much; as you've discovered, it doesn't stay set for very long... > I set "set group id bit" for the entire repository with'chmod -R g+s'. > This is so that new files will have the correct group and owner. That should only have been done on the directories, NOT on the files. However, everything should be g+w. So from a standing start, it'd be something like: chmod -R g+w find . -type d -print0 | xargs -0 chmod g+s (That's with GNU findutils. Without it, the g+s pipeline is harder to do both safely and quickly. This has been discussed here in the past; see the archives for details). Of course, from your current state, your task is to turn *off* setgid on the files, not to turn it *on* on the directories... A couple more steps are needed: - Add the users to group "cvsgroup" (then have them log in again to pick up the change) - Make sure that users' umasks do NOT include the 020 bit, i.e. that they create files group-writable. Of course, this has possibly-unpleasant ramifications for non-CVS files; the CVSUMASK environment variable *might* be of help, depending on your setup. > When > I go and look at the repository, the owner has changed to the user doing the > cvs command. That's as expected. Once the group stuff that we're talking about is set up properly, this behaviour shouldn't cause any problems. (Indeed, working around this is a lot of the point of the group stuff in the first place.) > When I execute a cvs update, I get the error message "Can't do setuid' I have a few thoughts, but nothing concrete: - Do you have setuid or setgid enabled on the CVS executable itself? If so, turn them off. - One of the other suggestions might fix it (especially turning off setgid on the ,v files). - That message doesn't seem to occur in CVS 1.11.5. Which version are you using? If it's an old one, try upgrading. - Or are you using another implementation, e.g. WinCVS, cvsnt, etc.? If so, you might have better luck on the appropriate list. -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont.[EMAIL PROTECTED] | | / A distributed system is one on which I cannot get any work done, because a machine I have never heard of has crashed. - Leslie Lamport ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Can't do setuid
I'm trying to get the permissions working for my repository. For my whole repository, I set the file and directory owner to cvs and the group to cvsusers. I did this recursively. I set "set group id bit" for the entire repository with'chmod -R g+s'. This is so that new files will have the correct group and owner. When I execute a cvs update, I get the error message "Can't do setuid' When I go and look at the repository, the owner has changed to the user doing the cvs command. How should this be set up? Brian ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: CVS/Root should record the CVS_RSH environment value...
On Tue, 4 Feb 2003, Greg A. Woods wrote: > Date: Tue, 4 Feb 2003 14:19:34 -0500 (EST) > From: Greg A. Woods <[EMAIL PROTECTED]> > Reply-To: CVS-II Discussion Mailing List <[EMAIL PROTECTED]> > To: CVS-II Discussion Mailing List <[EMAIL PROTECTED]> > Subject: CVS/Root should record the CVS_RSH environment value... > > It is _VERY_ unfortunate that CVS/Root does not record the setting of CVS_RSH. What's unfortunate is that the repository identification syntax does not experss the protocol, so you have to use the CVS_RSH hack to do so, relying on command compatibility of ssh and rsh. Then the purpose of CSV_RSH would be relegated to selecting an alternate rsh implementation, not to switch to a different rsh-compatible transport. An extension along the lines: :ext-rsh:user@host:/path/to/repo :ext-ssh:user@host:/path/to/repo could be the thing. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
CVS/Root should record the CVS_RSH environment value...
It is _VERY_ unfortunate that CVS/Root does not record the setting of CVS_RSH. $ cvs -t status Makefile -> main loop with [EMAIL PROTECTED]:/cvs -> Starting server: rsh anoncvs.comstyle.com -l anoncvs cvs server ^?cvs [status aborted]: received interrupt signal ksh: exit code: 1 $ CVS_RSH=ssh cvs -t status Makefile -> main loop with [EMAIL PROTECTED]:/cvs -> Starting server: ssh anoncvs.comstyle.com -l anoncvs cvs server === File: Makefile Status: Up-to-date Working revision:1.89 Repository revision: 1.89/cvs/src/Makefile,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) Gr -- Greg A. Woods +1 416 218-0098;<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]> ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Extracting multiple TAG at the same time
Marc Tessier writes [in one very long line]: > > I am wandering if there is any options to extract the most recent > version of a list of TAG? I have tag A, B, C and the I want to get the > most recent files of all three in one cvs checkout or cvs export so I > don't have to check the files version one by one. No. You're expected to tag all the files in a module, not just some of them. -Larry Jones Mom must've put my cape in the wrong drawer. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Extracting multiple TAG at the same time
Hi everyone I am wandering if there is any options to extract the most recent version of a list of TAG? I have tag A, B, C and the I want to get the most recent files of all three in one cvs checkout or cvs export so I don't have to check the files version one by one. thanks Marc ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs