entertaining newbies....
Hi guyz, I have a hard time following the FAQ of the CVS for me its not a step-by-step process Can someone lend their step-by-step notes to me Thanks Kent E. ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: pserver unrecognized auth error.
--- Larry Jones [EMAIL PROTECTED] wrote: That is interesting, that machine is still running. it is a redhat 7.1 machine on our lan with the stock cvs that came with the dist. I know I am reading the file I think I am because there are several roots defined on that machine and they have been added piece meal as we went along. The 1.11.5 machine ia a newer machine redhat 9.0. I looked at the two files yesterday when I sent the response. They are indeed different. The 7.1 machine is in heavy use so I'm not going to fiddle with it right now, but it is currently running with spaces and no '='. Thanks for the tip on the extra -f's mw- mike walster writes: I had some trouble when moving from 1.11 my server args in xinet.d/pserver were -f --allow-root /blah -f --allow-root /blah/blah etc. (note the spaces) That has never been valid syntax, I can't imagine how it worked in 1.11 unless it was some kind of local modification. I found that if I changed to my server args to -f --allow-root=/blah -f --allow-root=/blah/blah that it worked again. I have not had good luck unless I specified -f --allow-root for each dir. You need --allow-root= for each directory, but you only need one -f. Repeating it doesn't make any difference whatsoever. -Larry Jones No one can prove I did that!! -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
I am new to CVS..
Hi I am new to CVS. I had experience in Clearcase. i want to install and test on Windows platform first. Can any body give some suggestions how to start CVS (from installation,configurstion etc..) Is Server and Client s/w is separate?? Please give me some sugestions Thanks Sudheer ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
How does CVS Login Work?
I am moving a directory over from one CVS location to another. The permissions on the new directory are a bit different since it is set to 770 where I am in the group. When I try to co a project it asks me to do a cvs login. When I do cvs login username it gives me cvs login: authorization failed: server servername rejected access to directory for user username but I should have full permissions to this directory. I would like to know a bit more as to how cvs login works ... where does it store its information etc ... Tom ** The information contained herein is confidential and is intended solely for the addresse(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. ** ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
RE: cvs diff - new files
Hi, I tried -N option with cvs diff. It still does not spot files created locally. Any more ideas? I would like to know why there is such a difference when using pserver and not. Can somebody explain? Regards, Jayashree -Original Message- From: Greg A. Woods [mailto:[EMAIL PROTECTED] Sent: Tuesday, 17 June 2003 12:36 PM To: [EMAIL PROTECTED] Cc: CVS-II Discussion Mailing List Subject: Re: cvs diff - new files [ On Tuesday, June 17, 2003 at 11:24:26 (+0530), Jayashree wrote: ] Subject: cvs diff - new files I've noticed that cvs diff does not show new files when the export CVSROOT is not using pserver. Any ways by which I can find out new files to be baselined in a folder? How about trying cvs diff -N? *** This message is proprietary to Future Software Limited (FSL) and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. FSL accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. *** This e-mail puts you on notice that I will not be bound by your confidentiality notice and will feel free to review, disclose, distribute, archive, laugh at, be amused by, poke fun publicly at, and/or publish anything I get in e-mail, either directly or indirectly, and whether intended for me or not, without any further notice. If you don't feel comfortable with that, I suggest that you not send any e-mail, especially not to me or any mailing list I might subscribe to; or at least that you use strong digital encryption to ensure that your e-mail can't be read by anyone other than its intended recipient. There are many ways to do this, including using such things as PGP, Lotus Notes, S/Mime, and many other similar systems. I apologize to you if it was not your decision to add this notice to your e-mail. However, given the number of places that have legalized shrink wrap licenses and the similarity of this license to same, I feel like it is incumbent on me to put you on notice immediately regarding my rejection of your notice. Please forward it to whoever in your legal department or management chain you deem as appropriate. EULA - [ All rights to the preceeding communication are fully retained by the author, the non-exclusive right to read and/or reproduce the preceeding text is hereby licensed to the public, subject to the following conditions: (a) Scope of Use: No person may read the preceeding text without first agreeing to be bound by these conditions. Reading, perusing, scanning or otherwise viewing or percieving the preceeding text whether by visual, auditory, olfactory, gustatory or tactile manner constitutes agreement to these terms. (b) Fair Use of Material: license is granted for fair use of the preceeding material, including but not limited to reproduction in whole or in part, quoted or unquoted, so long at that use does not annoy, offend, irk, distress, disturb, bother, harry or otherwise taunt, tease, belittle, libel, slander, critisize, contradict, dispute, demean or cause to be so the author of the preceeding work. (c) Limitation of No Offense: No person reading or otherwise consuming in any way such as (but not limited to) those methods described in part (a) is permitted to be offended, annoyed, irked, distressed, disturbed, bothered, or harried by the preceeding text. If the preceding text would do so, the license for it's use is pre-emptorily withdrawn and voided prior to it's reading. (d) Waiver of Recourse: the Licensee or Potential Licensee agrees prior to acceptance of this agreement to hold harmless and indemnify the author against any claim, civil or legal, which might arise from the perusal of the preceeding material. (e) Severability: The invalidation of any part of this license agreement shall in no way void the whole or affect the application of any other part of this agreement. (f) Sense of Humor: Any potential reader without a sense of humor is referred to parts (c) and (d) of this agreement and requested to note that the lack thereof is disqualified as mitigation of any of these terms. ] If you and/or your PHB still think your mailer should automatically attach a stupid disclaimer like this one to all your outgoing e-mail then please also read this: URL:http://www.goldmark.org/jeff/stupid-disclaimers/ -- Greg A. Woods +1 416
RE: cvs diff - new files
[ On Thursday, June 19, 2003 at 20:10:11 (+0530), Jayashree wrote: ]
Subject: RE: cvs diff - new files
I tried -N option with cvs diff.
It still does not spot files created
locally.
You have to cvs add new files to CVS before it'll know about their
existance and thus be able to report their imminent creation with the
likes of cvs diff -N.
You can find a list of files that CVS doesn't know anything about with
cvs -n -q update | awk '$1 == ? {print $2}'
If you want to see a list of all the files that CVS doesn't know
anything about, _and_ include all of those it is ignoring:
cvs -n -q update -I ! | awk '$1 == ? {print $2}'
--
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: How does CVS Login Work?
[EMAIL PROTECTED] writes: cvs login: authorization failed: server servername rejected access to directory for user username That means that either the directory does not exactly match one of the server's --allow-root= options, the username is not a valid user, or the password you used was incorrect. It has nothing whatsoever to do with the permissions on any particular directory. CVS tries to log authorization failures using syslog() using the DAEMON and AUTHPRIV facilities, so check your system logs for more info. -Larry Jones My life needs a rewind/erase button. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: Input files
Hamid Ghassemi wrote: Can CVS use an input file in place of options for each individual file. We have a list of files that makes up a recipe of what source code is needed to make a product. suggestion read http://www.cvshome.org/docs/manual/cvs-1.11.6/cvs_4.html#SEC48 it tells you that cvs can internalize the recipe so you do not have to even have a separate file with the information in it. I would like to use this file as a input to a CVS command to do checkouts, tag, commit, etc. There is no interface in cvs to do it directly, however you could build a script (language of your choice) to make an interface. I would have it do something like the following. $recipe_version=v_1_1 /*maps to v1.1 ?*/ while $more_files_in_input.txt do $line = read line from input.txt $filename=$line.$1 $rcsversion=$line.$2 /* humans should ignore cvs use of rcs version numbers, and use tags */ cvs tag -r $rcsversion $recipe_version $filename done echo to get the input.txt version back for rebuild $recipe_version type \`cvs checkout -r$recipe_version module\` in an appropriate directory. echo in the mean time club the CM person until they understand echo how to use cvs tag or cvs rtag on the whole baseline echo and just keep input.txt as an artifact of the past. :) echo http://www.cvshome.org/docs/manual/cvs-1.11.6/cvs_4.html#SEC48 see the following for a bash script that does someething like you want http://mail.gnu.org/archive/html/info-cvs/2003-03/msg00251.html http://mail.gnu.org/archive/html/info-cvs/2003-03/msg00252.html Here is an example Input file input.rxt: /foo/foo.c 1.1 /foo/abc.h 1.4 Command line Cvs co @input.txt Or CVS co input.txt Thanks in advance Hamid ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: How does CVS Login Work?
WARNING: This E-MAIL is potentially in violation of your disclaimer (I am quoting the disclaimer portion only). The disclaimer is hereby rejected for the purpose of this reply and this e-mail message should be considered open and able to be forwarded to anyone and placed in any archive and used for any purpose. I am CCing your postmaster. You should inform your legal department that your disclaimer has been disclosed to an open e-mail list [EMAIL PROTECTED] [EMAIL PROTECTED] writes: [...a confidential e-mail message to [EMAIL PROTECTED] has been elided from this location of the e-mail. It is not possible for us to answer such a question with the restrictions given by your disclaimer...] Feel free to restate your question after you have ensured removal of the disclaimer. I personally will not answer it until the text of the message and any dialogue that follows its thread is allowed to be freely redistributed to anyone for any purpose. Here is a copy of the offending disclaimer: ** The information contained herein is confidential and is intended solely for the addresse(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. ** The above disclaimer information is being ignored for application to itself. You have transmitted your query to an open mailing list and the purpose of the list is to share rather than hoard information. You may NOT prohibit the spread of information posted to this list and it is very possible that your e-mail is now archived on a number of sites that are able to be searched which will violate your confidentiality agreement. There is nothing I can do to help you get those sites to remove your e-mail. If you do not cause that disclaimer to be removed, you will not ever get a response that does not include some kind of complaint like this one. -- Mark PS: The following information was posted recently by Greg A Woods concerning the use of disclaimers such as yours... I share it with you in the spirit of keeping this list open for the exchange of ideas and information. --- concerning disclaimers --- This e-mail puts you on notice that I will not be bound by your confidentiality notice and will feel free to review, disclose, distribute, archive, laugh at, be amused by, poke fun publicly at, and/or publish anything I get in e-mail, either directly or indirectly, and whether intended for me or not, without any further notice. If you don't feel comfortable with that, I suggest that you not send any e-mail, especially not to me or any mailing list I might subscribe to; or at least that you use strong digital encryption to ensure that your e-mail can't be read by anyone other than its intended recipient. There are many ways to do this, including using such things as PGP, Lotus Notes, S/Mime, and many other similar systems. I apologize to you if it was not your decision to add this notice to your e-mail. However, given the number of places that have legalized shrink wrap licenses and the similarity of this license to same, I feel like it is incumbent on me to put you on notice immediately regarding my rejection of your notice. Please forward it to whoever in your legal department or management chain you deem as appropriate. EULA - [ All rights to the preceeding communication are fully retained by the author, the non-exclusive right to read and/or reproduce the preceeding text is hereby licensed to the public, subject to the following conditions: (a) Scope of Use: No person may read the preceeding text without first agreeing to be bound by these conditions. Reading, perusing, scanning or otherwise viewing or percieving the preceeding text whether by visual, auditory, olfactory, gustatory or tactile manner constitutes agreement to these terms. (b) Fair Use of Material: license is granted for fair use of the preceeding material, including but not limited to reproduction in whole or in part, quoted or unquoted, so long at that use does not annoy, offend, irk, distress, disturb, bother, harry or otherwise taunt, tease, belittle, libel, slander, critisize, contradict, dispute, demean or cause to be so the author of the preceeding work. (c) Limitation of No Offense: No person reading or otherwise consuming in any way such as (but not limited to) those methods described in part (a) is permitted to be offended, annoyed, irked, distressed, disturbed, bothered, or harried by the preceeding text. If the preceding text would do so, the license for it's use is pre-emptorily
Re: How does CVS Login Work?
dont you think that you are going a bit overboard with this? 1) I personally do not control the disclaimer that is attached to my email ... 2) I work for a financial institution and I am not really sure which part of this disclaimer you have a problem with ... 3) If I am going to get this annoying email every time I post to the list I will not post to the list any more. Could you suggest where I can get CVS information and where I can lend what I know about CVS to others? 4) Arent you alienating a large group of people who work for large corporations by taking these actions? All I was asking was how CVS login works because I am having a problem with it. Sorry to offend if I have offended. Tom Mark D. Baushke [EMAIL PROTECTED]To: [EMAIL PROTECTED] Sent by: cc: [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED] Subject: Re: How does CVS Login Work? 06/19/2003 01:05 PM WARNING: This E-MAIL is potentially in violation of your disclaimer (I am quoting the disclaimer portion only). The disclaimer is hereby rejected for the purpose of this reply and this e-mail message should be considered open and able to be forwarded to anyone and placed in any archive and used for any purpose. I am CCing your postmaster. You should inform your legal department that your disclaimer has been disclosed to an open e-mail list [EMAIL PROTECTED] [EMAIL PROTECTED] writes: [...a confidential e-mail message to [EMAIL PROTECTED] has been elided from this location of the e-mail. It is not possible for us to answer such a question with the restrictions given by your disclaimer...] Feel free to restate your question after you have ensured removal of the disclaimer. I personally will not answer it until the text of the message and any dialogue that follows its thread is allowed to be freely redistributed to anyone for any purpose. Here is a copy of the offending disclaimer: ** The information contained herein is confidential and is intended solely for the addresse(s). It shall not be construed as a recommendation to buy or sell any security. Any unauthorized access, use, reproduction, disclosure or dissemination is prohibited. Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates shall assume any legal liability or responsibility for any incorrect, misleading or altered information contained herein. ** The above disclaimer information is being ignored for application to itself. You have transmitted your query to an open mailing list and the purpose of the list is to share rather than hoard information. You may NOT prohibit the spread of information posted to this list and it is very possible that your e-mail is now archived on a number of sites that are able to be searched which will violate your confidentiality agreement. There is nothing I can do to help you get those sites to remove your e-mail. If you do not cause that disclaimer to be removed, you will not ever get a response that does not include some kind of complaint like this one. -- Mark PS: The following information was posted recently by Greg A Woods concerning the use of disclaimers such as yours... I share it with you in the spirit of keeping this list open for the exchange of ideas and information. --- concerning disclaimers --- This e-mail puts you on notice that I will not be bound by your confidentiality notice and will feel free to review, disclose, distribute, archive, laugh at, be amused by, poke fun publicly at, and/or publish anything I get in e-mail, either directly or indirectly, and whether intended for me or not, without any further notice. If you don't feel comfortable with that, I suggest that you not send any e-mail, especially not to me or any mailing list I
Re: How does CVS Login Work?
[EMAIL PROTECTED] wrote: dont you think that you are going a bit overboard with this? 1) I personally do not control the disclaimer that is attached to my email ... At the risk of sustaining this thread beyond a reasonable lifespan, I would point out that no disclaimer was added to your response, which eludes to an element of control, perhaps implicit. I'll leave it to the archives for the proof, so I don't burn more bandwidth on this topic than is reasonable. -Matt ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
branches off of branches
hey, Is there a way to make a branch off another branch, what I'm envisioning is the following: --- / dev / --- / test / -- head where dev can be merged into test (and test only), and test can be merged into head (and head only). The idea is that you don't need to touch the head branch in order to do merges. I know you could directly merge head with test with something like: cvs update -j test -j dev but it then behooves you to remember when you've done the damn merge.. Argh! Overall, cvs's branching ability leaves much to be desired. I'd use MetaCVS, except I need to have the functionality available on solaris Ed (ps - also wrt MetaCVS... why isn't there a sourceforge project for it?) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: branches off of branches
Peschko, Edward writes: Is there a way to make a branch off another branch Of course -- just create a branch in a working directory that's already on a branch. (Or use the -r option of [r]tag along with -b to specify a root revision for the branch.) where dev can be merged into test (and test only), and test can be merged into head (and head only). You can always merge anything to anything. (Whether the merge actually makes sense or not is a different issue. In the above scenario, merging as you suggest is certainly the most sensible way to do it.) but it then behooves you to remember when you've done the damn merge.. It always behooves you to remember (typically with tags) what you've merged, unless you intend to merge the branch exactly once and then abandon it. -Larry Jones I'm writing you a message in code. How do you spell nincompoop? -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: branches off of branches
On Thu, 19 Jun 2003, Peschko, Edward wrote: but it then behooves you to remember when you've done the damn merge.. Argh! Overall, cvs's branching ability leaves much to be desired. I'd use MetaCVS, except I need to have the functionality available on solaris What issues have you run into trying to get Meta-CVS on Solaris? There exists a website ``www.solaris4u.dk'' which hosts categorized lists of software that apparently run on Solaris. Meta-CVS and other version control systems are stuck under the ``search engines'' category. http://www.solaris4you.dk/searchenginesSS.html The table suggests that the program was at least built on Solaris 2.8 and 2.9, SPARC and X86. Maybe the site's maintainer has binaries. I don't use Solaris, but I'd be happy to incorporate patches, if any, that are needed to get it running, and host the binary tarballs too. (ps - also wrt MetaCVS... why isn't there a sourceforge project for it?) The conditions are not right. So far, I have received very few patches for Meta-CVS. Every ChangeLog entry has my name on it! So there isn't a development team that needs a central repository. Read-only repository access for the masses would make sense if it was such a widely used, busy and buggy program that it was mandatory for thousands of people to get the latest codebase several times a day in hopes that the latest and greatest will solve their problems. A mailing list would be needed for similar reasons. The Meta-CVS-related traffic that I receive in my personal mailbox is so small that it doesn't require its own list. The odd time two people have the same ideas or problems, so I may put them in touch. A better question is: why isn't there actual working source code for 90% of the Sourceforge projects? :) ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: branches off of branches
makes sense or not is a different issue. In the above scenario, merging as you suggest is certainly the most sensible way to do it.) but it then behooves you to remember when you've done the damn merge.. It always behooves you to remember (typically with tags) what you've merged, unless you intend to merge the branch exactly once and then abandon it. yes, but I want *cvs* to remember it. If I say: cvs update -j TEST from head, then I'd like to have all further updates from test go from the point of where I last updated. Or, at least have the option of doing this via a command line argument: cvs update -j TEST -m (for mnemonic) Likewise.. cvs update -j TEST -j DEV -m means migrate changes from TEST to DEV, and remember the migration. Then, if, inside head: cvs update -j TEST -m this would migrate the TEST changes into head... on a cvs update -j DEV -m it would remember that the DEV changes have already been put into test... etc. etc. In short, it'd be cool if merges could remember their merging, and if there was some sort of repository of the changes that have been merged. It'd save one hell of a lot of tracking down conflicts. If this was true, I wouldn't have to worry about branching off of branches, or what not. As far as I can see, merges would all 'snap to'. Or am I missing something? Ed ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
