RE: how to extract two versions of file for comparison
Original Message From: Dave Korn Sent: 14 July 2005 14:31 Original Message From: NoPlatitudes Sent: 14 July 2005 14:16 I am trying to get the difference between the latest working version of a file and a previous version. I need to use a third party tool to examine this difference (cvs's diff functionality won't do what I want here). I want the newest version to remain in my 'standard' working directory, and I'd like the old version to be extracted (for reference only; no edits needed) to another directory, like /temp off of my working directory. How can I do this? cvs update -C -r rev -p file.name /temp/file.name Correction: Don't use -C or you'll end up with a spurious 'locally modified ... moved to ...' message as the first line of /temp/file.name. Apologies for the confusion! cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
need help
Hi friends I am harish from India working as Jr.System Admin in a software development company. Actually i want to implement an version control software in my compnay. Could any one tell me from where i can download the cvs server client implement it becoz on the net it is having lots of ver on different sites. So PLZ I am requesting u to help me Always U R,s D.Harish__Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: problem with the Tortoise ssh -pw password option
On 13 Jul 2005 19:00:09 -0700, Ed [EMAIL PROTECTED] wrote: I know this is an insecure method, but I'm going crazy typing in my password every 2 seconds, and the pageant, puttygen, option keeps referring to Sourceforge example. The other examples I found didn't work for setting up public keys on the cvs server I'm using. but anyway So, it's bad when the 'lazy man's' alternative also craps out. My setup is: Tortoise 1.8.17 Tools ssh params -l %u %h -pw mycvspassword Try removing the -l %u %h. In winCVS the username and host is handled by the CVSROOT thingie. (e.g. :ext:[EMAIL PROTECTED]:/cvs/root). Mind you, I have not used Tortise so I don't know how it sets up the cvsroot. The reponse is an alert box: PuTTY Fatal Error Unable to authenticate Any ideas? Thanks, Ed Too lazy to do all this? There is an alternative solution, which is insecure as it keeps your password in plaintext on your machine. Go to TortoiseCVS Preferences - SSH - SSH parameters and set the value to -pw password. http://www.tortoisecvs.org/faq.shtml#sshkeys ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs --Russ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
how to extract two versions of file for comparison
I am trying to get the difference between the latest working version of a file and a previous version. I need to use a third party tool to examine this difference (cvs's diff functionality won't do what I want here). I want the newest version to remain in my 'standard' working directory, and I'd like the old version to be extracted (for reference only; no edits needed) to another directory, like /temp off of my working directory. How can I do this? Thanks... ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: how to extract two versions of file for comparison
try something like: cvs update -r [version] -p [filename] temp/[filename] On 14 Jul 2005 06:16:04 -0700, NoPlatitudes [EMAIL PROTECTED] wrote: I am trying to get the difference between the latest working version of a file and a previous version. I need to use a third party tool to examine this difference (cvs's diff functionality won't do what I want here). I want the newest version to remain in my 'standard' working directory, and I'd like the old version to be extracted (for reference only; no edits needed) to another directory, like /temp off of my working directory. How can I do this? Thanks... ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs -- Give me ambiguity, or give me something else. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: how to extract two versions of file for comparison
Many thanks... ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: how to extract two versions of file for comparison
Original Message From: NoPlatitudes Sent: 14 July 2005 14:16 I am trying to get the difference between the latest working version of a file and a previous version. I need to use a third party tool to examine this difference (cvs's diff functionality won't do what I want here). I want the newest version to remain in my 'standard' working directory, and I'd like the old version to be extracted (for reference only; no edits needed) to another directory, like /temp off of my working directory. How can I do this? cvs update -C -r rev -p file.name /temp/file.name cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Exact branching date?
Hi. I'm new to branching, I always used it just as tagging versions, never joining back with head... so pleas excuse me being naive :) I'd like to know if it's possible to know the exact date when a branching has been applied, without sticky dates, since I have none in my repository. I'd like to diff some versions with the head, but using diff files from the original branching date to the lates branched version, and then but it back on head... but I need the branching date! :) Thank you! PS. I know how to deal with diffing, tagging and basic things like date-based checkout... but this specific issue seems not covered in the faq... -- Sensei [EMAIL PROTECTED] cd /pub more beer ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs tag performance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hridyesh Pant [EMAIL PROTECTED] writes: Hi All, My cvs tag command is suddenly taking too much time while tagging a code of 2GB .It is affecting our performance. My system configuration after top command is as below 11:47am up 66 days, 19:24, 4 users, load average: 15.23, 13.82, 13.14 155 processes: 150 sleeping, 5 running, 0 zombie, 0 stopped CPU0 states: 41.0% user, 3.1% system, 0.0% nice, 54.1% idle CPU1 states: 100.0% user, 0.0% system, 0.0% nice, 0.0% idle CPU2 states: 28.0% user, 3.1% system, 0.0% nice, 68.0% idle CPU3 states: 75.0% user, 9.0% system, 0.0% nice, 15.1% idle Mem: 3946640K av, 3836128K used, 110512K free, 0K shrd, 73884K buff Swap: 6193120K av, 37112K used, 6156008K free 2637244K cached could any body help me what need to be done... Regards Hridyesh Not really. You need to see what kind of filesystem contention you are hitting. Remember that a tag operation will rewrite everyone of the ,v files in the list of files being tagged. Slow disk writes would impact it. However, the load of processes waiting to run (150 sleeping) would seem to indicate something else is the bottle neck unless every one of them are waiting for read or write locks in the repository. You may wish to look into using a memory filesystem on the box along with a LockDir directive in your CVSROOT/config file to point to it. Good luck, -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFC1nwq3x41pRYZE/gRAkn1AJ9f1EY3cgxQ9+m7YoloIgV+2DjpBgCfQj7J QelhfdWvGzogI60521YHJW4= =xpoR -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Exact branching date?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sensei [EMAIL PROTECTED] writes: Hi. I'm new to branching, I always used it just as tagging versions, never joining back with head... so pleas excuse me being naive :) I'd like to know if it's possible to know the exact date when a branching has been applied, without sticky dates, since I have none in my repository. You should be able to bracket the timeframe, but you will not be able to get it exactly. For the upper bound, the closest you can probably come would be the second immediately before the first commit to the branch. You would want to use one of the tools that plays with the 'cvs status' or 'cvs log' output to find the first commit to the branch (cvs2cl is a good choice). For the lower bound, you would want to take one second after the most recent commit to the parent branch prior to the upper bound time found in previous step. I'd like to diff some versions with the head, but using diff files from the original branching date to the lates branched version, and then but it back on head... but I need the branching date! :) For all practical purposes you should be able to use the upper bound timestamp. Something like this may be what you want cvs2cl.pl --no-ancestors --follow branch-name --tags --branches \ --revisions --chrono grep -B2 branch-name ChangeLog If I have misremembered the syntax, I am certain that some one else on the list will be able to help you. Good luck, -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFC1oI13x41pRYZE/gRApo6AJ9zqXNHVqB3B4bwrIc/LYfpCYhR5gCg5qIf ib/e0gF8/2ONr/ZU9xEl1io= =oIL3 -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
CVS Client on VMS 7.3-1 and SSH
I'm using ssh on VMS to connect to a Linux box that has Concurrent Versions System (CVS) 1.11.20 (client/server)[ The VMS side has Concurrent Versions System (CVS) 1.11.20 (client) When I do a connect, I get the following error $ cvs co smile cvs [checkout aborted]: can't set close-on-exec flag on 3: bad file number $ Can someone who has more insight into the CVS code point me to which files I may need to patch to get this connection to work? I may have to re-compile with debug options, then run under the debugger. Before I go to that depth, I though I'd see if anyone had any suggestions. Thanks, -Roger ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Any consequences over removing a subdir permanently?
Hi I know how to delete and commit files to the attic and on the next checkout do a -P to prune out empty dirs but I have not seen any documentation on how to remove empty dirs/subdirs permanently. Is this not recommended lest you have to retrieve dead files later? And CVS wouldn't know what structure to retrieve them to? Should I or not delete the empty dirs on the server side or too dangerous? We have many, and I mean many, empty dirs just sitting there! Thanks Steve ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Any consequences over removing a subdir permanently?
Thank you as always. Do you think though that deleting a dir and later retrieving a dead file would confuse the dead file where to implant itself? I have a dummy repository and I'm going to try this to find out the outcome. The subdirs I speak of are about 5 years old and don't think anyone would care. We have restructured our code so many times and we may soon port over to a completely clean repository without its history. So in our case it shouldn't matter but I see your point about NOT exercising this. Thanks. :) Original Message Follows From: Todd Denniston [EMAIL PROTECTED] To: S I [EMAIL PROTECTED] CC: info-cvs@gnu.org Subject: Re: Any consequences over removing a subdir permanently? Date: Thu, 14 Jul 2005 12:13:32 -0500 MIME-Version: 1.0 Received: from mail.ssa.crane.navy.mil ([164.227.42.3]) by mc7-f2.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 14 Jul 2005 10:13:35 -0700 Received: from ssa.crane.navy.mil ([EMAIL PROTECTED] [164.227.42.142]) by mail.ssa.crane.navy.mil with ESMTP id MAA27385; Thu, 14 Jul 2005 12:15:22 -0500 X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8= Organization: Code 6067, NSWC Crane X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.25glock1 i686) X-Accept-Language: en References: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 14 Jul 2005 17:13:35.0856 (UTC) FILETIME=[5E9AA700:01C58897] S I wrote: Hi I know how to delete and commit files to the attic and on the next checkout do a -P to prune out empty dirs but I have not seen any documentation on how to remove empty dirs/subdirs permanently. Is this not recommended lest you have to retrieve dead files later? And CVS wouldn't know what structure to retrieve them to? Should I or not delete the empty dirs on the server side or too dangerous? We have many, and I mean many, empty dirs just sitting there! Deleting anything permanently out of a version control system is _usually_ a _very_ BAD idea. However if your project management really desires it, keep your self sane with a good backup, and go directly into the repository and `rm -fr offensive_directory_structure`. The reason that cvs does not have a built-in command (that I am aware of) for doing this is that it is such a _very_ BAD idea. Got permission and a backup? Happy hunting. :) -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: CCASE data import into CVS
Mark Thank you for your promptly reply. Actually link you provided was very useful - I was going to checkout version from CCASE and checkin in CVS. With files access method, described in that link, I will be able to write script for CCASE part much faster. I do not think, that I will end with some universal script and probably it will be something very specific for my current configuration, but in case if I will find it useful for general migration I will surely post it to contrib directory. Thanks again for your support. With best regards Martynas -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark D. Baushke Sent: Tuesday, July 12, 2005 4:32 PM To: Buozis, Martynas Cc: info-cvs@gnu.org Subject: Re: CCASE data import into CVS -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buozis, Martynas [EMAIL PROTECTED] writes: Is it possible to import data from CCASE into CVS ? If yes - how ? Thanks. You should use a search engine to find prior art... something like this describes how you might go about writing one for yourself... http://lists.gnu.org/archive/html/info-cvs/2001-06/msg00134.html You should also consider looking for something that can export from ClearCase into RCS as it is a short step from there to using CVS. If you come up with a script, feel free to post it to bug-cvs@gnu.org for possible inclusion into the contrib directory. Good luck, -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFC09RL3x41pRYZE/gRAvQTAJ47rUWCpBSQgvZYbr7AYCTSSWyhEACdEnlg UYTLDEpkhu9yM4Uue57ZvXs= =lAGA -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Any consequences over removing a subdir permanently?
S I wrote: Thank you as always. Do you think though that deleting a dir and later retrieving a dead file would confuse the dead file where to implant itself? Well ... if you rm -fr'd the directory structure the file was in, you'll likely be confused yourself, because not only is there no dead file to retrieve but there is no attic. :) This is the reason it is _usually_ a _very_ BAD idea to remove things from the repository. Because when they are gone from the version control file system / database they are GONE, NOT COMING BACK, DESTROYED. I have a dummy repository and I'm going to try this to find out the outcome. That is good practice, keep it up. :) The subdirs I speak of are about 5 years old and don't think anyone would care. Be SURE, don't just think it. 8O We have restructured our code so many times and we may soon port over to a completely clean repository without its history. So in our case it shouldn't matter but I see your point about NOT exercising this. A middle ground might be: 1) tell everyone to commit all changes they have currently. 2) backup to cold storage media. 3) copy the CVS tree to a new location. 4) do a checkout from the new location and then do a `cvs watch on -R` against that checkout. 5) find and mark all the directories in the new copies location read only, and setup a lockdir for it so people can do readonly checkouts. (lock it down) 6) again backup to cold storage media. 7) remove the unused directories. This should leave you with a copy in the new location for people who need to know the ancient history, a copy to recover from if you hit enter on the rm in the wrong directory, and a smaller repo but with all the history since the each of the files were last restructured. Thanks. :) SNIP -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Any consequences over removing a subdir permanently?
Todd Denniston wrote: Clerity demands I respond to my own post. sorry. S I wrote: SNIP We have restructured our code so many times and we may soon port over to a completely clean repository without its history. So in our case it shouldn't matter but I see your point about NOT exercising this. A middle ground might be: 1) tell everyone to commit all changes they have currently. 2) backup to cold storage media. 3) copy the CVS tree to a new location. 4) do a checkout from the new location and then do a `cvs watch on -R` against that checkout. 5) find and mark all the directories in the new copies location read only, and setup a lockdir for it so people can do readonly checkouts. (lock it down) 6) again backup to cold storage media. SNIP 7) remove the unused directories, in the original (and still current) version of the repo, i.e., no one has to change their CVSROOT values. 8) if people still have sand boxes from before there may be some difficulty in doing updates and such, have them check that `cvs update -dP` command works with out error at a minimum. If your really sure just have them remove all their old sandboxes and start fresh. This should leave you with a copy in the new location for people who need to know the ancient history, a copy to recover from if you hit enter on the rm in the wrong directory, and a smaller repo but with all the history since the each of the files were last restructured. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs tag performance
run iostat -x 3 or equivalent to monitor the disk for contention. Look for stats like (see man iostat). On Linux : avgqu-sz The average queue length of the requests that were issue to the device. await The average time (in milliseconds) for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servic- ing them. svctm The average service time (in milliseconds) for I/O requests that were issued to the device. If you see large queue sizes and response times you know you may have a disk storm being generated when tag command modifies files. Since CVS doesn't do any concurrent tagging (like mutliple threads or processes operating on individual dirs etc) you will have to look at faster disk option. When you say it's suddenly taking too much time there must be other disk activity kicking in that's causing disk contention when tag command shows up. Regards, === Rahul Bhargava CTO, WANdisco http://www.wandisco.com/cvs ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
The reason i am using locks is because the files are XML, and as far as i know when CVS trys to merge XML it can result in invalid XML. I do however remember on previous uses of CVS the option to check stuff out as read only. However I cannot find that option now, this option was on the WinCvs client I am sure. Do i require to do some sort of configuration on the Cvs Server to allow the locking of files? I have read the above manual, well actually the manual for 1.11.17, as this is what I am using, it just seems to describe the difference between reserved and normal edits. I have been able to check out the repository but then had to manually tell it to unedit all the files, so they appeared as locked. Then when i commit a change to a file it just leaves it as editable, were in previous use of cvs it would go back to being uneditable, i.e read only. Does anyone know if i need to do something else that I may have not done. Thanks all for the extended help S. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs branch version
Hi, I used 'cvs tag' to add a file to a branch. I then used 'cvs commit -r... ' to check in a new version. It normally creates a subversion from the version initially tagged. For example, I tag file 'A' version 1.1 with release-patch. It creates a version 1.1.0.2 for the tag. When I check in a new version to the branch, it creates a version 1.1.2.1. But this time, I did not see any output from the command line after I entered the comments in vi. When I did a 'cvs log', I did not see any subversion created. Did you change the file before committing it? CVS will not create a new revision unless there are changes from the old one. If I do a 'cvs status' on the file, the sticky tag shows : Sticky Tag: release-patche (branch: 1.1.2) But I cannot see this revision with 'cvs log'. Can anyone explain what happened? Sure. You now have the file in your working area as branch 1.1.2, but since there is no change from the original version, the only revision is 1.1. This revision is on both the trunk and the branch right now. That's what it looks like to me. David H. Thornley| If you want my opinion, ask. [EMAIL PROTECTED] | If you don't, flee. http://www.thornley.net/~thornley/david/ | O- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
Liquidchild wrote: The reason i am using locks is because the files are XML, and as far as i know when CVS trys to merge XML it can result in invalid XML. I do however remember on previous uses of CVS the option to check stuff out as read only. However I cannot find that option now, this option was on the WinCvs client I am sure. I have not searched the net for problems with XML and CVS, but I thought XML was text, and as such should be reasonably merge-able by CVS ... that is unless your XML contains binary blobs like what MS Word kicks out. I assume then that you have either seen some problems yourself or read about it on line? Do i require to do some sort of configuration on the Cvs Server to allow the locking of files? I have read the above manual, well actually the manual for 1.11.17, as this is what I am using, it just seems to describe the difference between reserved and normal edits. In most situations, with reasonable developers, reserved edits and watch notification, can take the place of locking. i.e., you can do `cvs watch on *XML` [1] setup the notify administrative file and have the developers do `cvs watch add -a all file_they_work_on` then have them do `cvs edit filename` anytime they need to edit a file. Then here is the hard part, if they get a notification that another user has begun editing a file, they should contact that user and negotiate with them the time needed to finish their own edits. You might also want to look at the 1.12.x series, IIRC it has the advisory lock patch in it, and can stop the edit from working, if there is someone else editing the file, unless the developer knowingly bypasses the edit with an option. i.e., it is a stronger (extended) form of the 'cvs watch on` + `cvs edit` commands. I have been able to check out the repository but then had to manually tell it to unedit all the files, so they appeared as locked. Had you already done `cvs watch on` on the files? if you had then they should have come as read-only (locked). Then when i commit a change to a file it just leaves it as editable, were in previous use of cvs it would go back to being uneditable, i.e read only. Then I would expect you had not yet done a `cvs watch on` on those files, the manual indicates [2] : the cvs commit command, which checks in your changes and returns the watched files to their usual read-only state Does anyone know if i need to do something else that I may have not done. See above and below. :) Thanks all for the extended help S. [1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_10.html#SEC88 [2] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_10.html#SEC91 -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
MAKE MONEY
MAKE MONEY!!! MAKE THOUSANDS!!! WELL GUESS WHAT!!! Within seven days, I started getting money in the mail!! I was shocked!! I figured it would end soon, but the money just kept coming in. In my first week, I made about $25.00. By the end of the second week I had made a total of more than $1000.00!! In the third week I had more than $10,000.00 and it's still growing!! This is now my fourth week and I have made a total of $42,000.00 and it's still coming rapidly. It's certainly worth $6.00 and six stamps, and I have spent more than that on the lottery without ever winning!!! My fingers are sore from opening all the envelopes I are on first name basis with our local post office. (i bet they are now doin it too!!) Let me tell you how this works and most important, why it works.. also make sure you print this out NOW, so you can get the information off of it, as you will need it. I promise you that if you follow the directions exactly that you will start making more money than you thought possible by doing something so easy!! Suggestion: Read this entire message carefully!! (Print it out or download it) Follow the simple directions and watch the money come in!! It's easy. It's legal. And, your investment is only $6.00 (Plus postage) !!! You can use any currancy as people can always change it.. IMPORTANT: This is not a rip-off, it is decent; it's legal; and it is virtually no risk - it really works!! If all the following instructions are adhered to, you will receive extraordinary dividends. PLEASE NOTE: Please follow the directions EXACTLY, and $50,000 or more can be yours in 20 to 60 days. This program remains successful because of the honesty and integrity of the participants. Please continue its success by carefully adhering to the instructions. You will now become apart of the Mail Order business. You are in the business of developing Mailing Lists. Many large corporations are happy to pay big bucks for quality lists. However, the money made from the mailing lists is secondary to income which is made from people like you and me asking to be included in that list. Here are the four easy steps to success. STEP ONE: Get six separate pieces of paper and write the following on each piece of paper PLEASE PUT ME ON YOUR MAILING LIST. Now get 6 U.S. $1.00 bills and place ONE inside of EACH of the six pieces of paper so the bill will not be seen through the envelope (to prevent thievery). Next, place one paper in each of the six envelopes and seal them. You now should have six sealed envelopes, each with a piece of paper stating the above phrase, your name and address, and a $1.00 bill. What you are doing is creating a service. THIS IS ABSOLUTELY LEGAL! You are requesting a legitimate service and you are paying for it!! Like most of us I was a little skeptical and little worried about the legal aspects of it all. So I checked it out with the U.S. Post Office (1-800-238-5355) and they confirmed that it is indeed legal!! Mail the six envelopes to the following addresses: 1) R. Visser P.O. Box 274 Nobby Beach QLD, 4218 Australia 2) S. Phillips 77 Manly Drive Robina, QLD 4226 Australia 3) Chris Pittman 7651 Abigail Glen Dr. Charlotte, NC 28212 USA 4) D Larrinaga 609 n. tweedt #203 kennewick, WA 99336 USA 5) W Beagen 48 Brook St Methuen, Ma 01844 6) J.L. Herzfeld P.O.Box 26099 Saint Louis,MO 63136-0099 STEP TWO:Now take the #1 name off the list that you see above, move the other names up (six becomes 5, 5 becomes 4, and etc.) and add YOUR NAME as number 6 on the list. STEP THREE: Change anything you need to but try to keep this article as close to original as possible. Now post your amended article to at least 200 news groups. : (I think there are close to 24,000 groups) All you need is 200, but remember, the more you post, the more money you make!! This is perfectly legal!! If you have any doubts, refer to Title 18 Sec. 1302 1341 of the Postal Lottery laws. Keep a copy of these steps for yourself and whenever you need money, you can use it again, and again. PLEASE REMEMBER that this program remains successful because of the honesty and integrity of the participants and by their carefully adhering to directions. Look at it this way. If you were of integrity, the program will continue and the money that so many others have received will come your way. NOTE: You may want to retain every name and address sent to you, either on a computer or hard copy and keep the notes people send you. This VERIFIES that you are truly providing a service. (Also, it might be a good idea to wrap the $1 bill in dark paper to reduce the risk of mail theft). So, as each post is downloaded and the directions carefully followed, all members will be reimbursed for their participation as a List Developer with one dollar each. Your name will move up the list geometrically so that when your name reaches the #1 position you will be receiving thousands of dollars in CASH!!! What an opportunity for only $6.00 (
Re: How do I get a barebone stripped off list of files changedbetween 2 builds?
Ok that worked beautifully, thank you again. :)
Original Message Follows
From: Robert Clark [EMAIL PROTECTED]
To: info-cvs@gnu.org
Subject: Re: How do I get a barebone stripped off list of files
changedbetween 2 builds?
Date: Tue, 12 Jul 2005 16:40:05 -0400
MIME-Version: 1.0
Received: from lists.gnu.org ([199.232.76.165]) by mc9-f9.hotmail.com with
Microsoft SMTPSVC(6.0.3790.211); Tue, 12 Jul 2005 18:38:23 -0700
Received: from localhost ([127.0.0.1] helo=lists.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43)id 1DsWDl-0003BE-94for [EMAIL PROTECTED]; Tue, 12 Jul
2005 21:39:33 -0400
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)id
1DsS0u-00053P-Tgfor info-cvs@gnu.org; Tue, 12 Jul 2005 17:10:01 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)id
1DsS0r-000520-QOfor info-cvs@gnu.org; Tue, 12 Jul 2005 17:09:59 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)by lists.gnu.org
with esmtp (Exim 4.43) id 1DsS0q-000502-FOfor info-cvs@gnu.org; Tue, 12 Jul
2005 17:09:57 -0400
Received: from [12.106.87.68] (helo=irvbhxw02.prod.quest.corp)by
monty-python.gnu.org with esmtp (Exim 4.34) id 1DsRfn-0007kS-3Tfor
info-cvs@gnu.org; Tue, 12 Jul 2005 16:48:11 -0400
Received: from tormbxw01.prod.quest.corp ([10.4.100.91])
byirvbhxw02.prod.quest.corp with Microsoft SMTPSVC(6.0.3790.211); Tue, 12
Jul 2005 13:40:07 -0700
Received: from tor106065.prod.quest.corp ([10.4.114.58])
bytormbxw01.prod.quest.corp with Microsoft SMTPSVC(5.0.2195.6713);Tue, 12
Jul 2005 16:40:06 -0400
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
Organization: Quest Software Inc.
User-Agent: KMail/1.8.1
References: [EMAIL PROTECTED]
X-Face:
@wf=R`Gp1sqW$*(jmq~x\Y:on!638~obu4W34T^iIADeQK]lx2S`sg;`ecD/*g]^,q
KWA}}rUgp4Iha3^:~P$|P|2Ad=8JMx#IPDX/PNbK0}{gLmf^-_V4fiR)!ZAn[5w
|Aij./#K!jiw6zMOY}W/,[l(%0beg9'2_s5#x5v7QZ$Pn67lUsJSsDyIF|#:9Cy#D
i?~]{X:ma68Crle{V.REztwUaW^Y.qHk1)8i[n/[#/~oi$,g(:/)gt6Fm^GW!BBsD
+RPI3Xb~I6OH#2^==29GQ~5UAfE._cNv.V4{qdw2uBp
X-OriginalArrivalTime: 12 Jul 2005 20:40:06.0564
(UTC)FILETIME=[E3372640:01C58721]
X-BeenThere: info-cvs@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Announcements and discussions for the CVS version control
systeminfo-cvs.gnu.org
List-Unsubscribe:
http://lists.gnu.org/mailman/listinfo/info-cvs,mailto:[EMAIL PROTECTED]
List-Archive: http://lists.gnu.org/pipermail/info-cvs
List-Post: mailto:info-cvs@gnu.org
List-Help: mailto:[EMAIL PROTECTED]
List-Subscribe:
http://lists.gnu.org/mailman/listinfo/info-cvs,mailto:[EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
Return-Path: [EMAIL PROTECTED]
On Tuesday July 12, 2005 03:58 pm, S I [EMAIL PROTECTED] wrote:
I'm trying to get a stripped down list of files modified and
committed between 2 builds or a build and my working folder in CVS.
I would just like to see the path/filename only.
What I generally do is use the rdiff command with the -q and -s (for
shout output) options. Something like:
cvs -q rdiff -s -r TAG1 -r TAG2 module.
You can substitute any valid combination of -r and -D options to
restrict the output to the range you want. So in this case, your
example would be:
cvs -q rdiff -s -r HEAD -D yesterday your-module-name cvsHist1.txt
- Rob
--
Robert J. Clark
[EMAIL PROTECTED]
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
problem with the Tortoise ssh -pw password option
I know this is an insecure method, but I'm going crazy typing in my password every 2 seconds, and the pageant, puttygen, option keeps referring to Sourceforge example. The other examples I found didn't work for setting up public keys on the cvs server I'm using. but anyway So, it's bad when the 'lazy man's' alternative also craps out. My setup is: Tortoise 1.8.17 Tools ssh params -l %u %h -pw mycvspassword The reponse is an alert box: PuTTY Fatal Error Unable to authenticate Any ideas? Thanks, Ed Too lazy to do all this? There is an alternative solution, which is insecure as it keeps your password in plaintext on your machine. Go to TortoiseCVS Preferences - SSH - SSH parameters and set the value to -pw password. http://www.tortoisecvs.org/faq.shtml#sshkeys ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Annotate of Log output wrong
This is to continue the discussion of the thread with the same subject that started on Dec 7, 2004. The original discussion appeared to focus on the expansion of the $Log$ keyword both in the file and as output by the cvs annotate command (under version 1.11.17); but I think other keywords such as $Id$ have the same problem. I am running CVS version 1.11.6 on Solaris. After I committed a file that contains some keywords, (I did not perform a checkout or update after that,) the file in my working directory shows the following: $Id: compiler.c,v 1.3 2005/07/12 03:10:28 mingl Exp $ this is $Date: 2005/07/12 03:10:28 $ $Log: compiler.c,v $ Revision 1.3 2005/07/12 03:10:28 mingl this is my log ha ha ha Revision 1.2 2005/07/12 02:32:17 mingl third commit Revision 1.1.1.1 2005/07/07 00:05:26 mingl init import And I ran cvs annotate' which output: Annotations for compiler.c *** 1.3 (mingl12-Jul-05): $Id: compiler.c,v 1.2 2005/07/12 02:32:17 mingl Exp $ 1.3 (mingl12-Jul-05): this is $Date: 2005/07/12 02:32:17 $ 1.2 (mingl12-Jul-05): $Log: compiler.c,v $ 1.3 (mingl12-Jul-05): Revision 1.2 2005/07/12 02:32:17 mingl 1.3 (mingl12-Jul-05): third commit 1.3 (mingl12-Jul-05): 1.2 (mingl12-Jul-05): Revision 1.1.1.1 2005/07/07 00:05:26 mingl 1.2 (mingl12-Jul-05): init import From the leftmost column, it is obvious that the latest revision is 1.3; however, the keywords expand to only revision 1.2. 1. Todd Denniston states that If I Recall Correctly, $Log:$ is expanded on checkout, so the last (chronological) log entry seen in a Log in a sandbox has not yet been checked into CVS. Therefore, the repository knows nothing about it, and can not annotate what to it does not exist. (Larry Jones says similar thing: the $Log$ keyword (not command) is expanded by checkout/update.) I think the first half of the sentence is inaccurate: apparently the keywords are expanded (in the working file) upon commitment (check-in), i.e. no subsequent checkout is needed. (What Todd probably meant is: $Log$ is expanded in the ,v file on checkout. - But see my Points 2 and 3 below.) And I think check in and check out should not be confused. ci and co are two separate commands, aren't they? The keywords are expanded in the working file on checkin, not checkout. In fact, Section 12 of the cederqvist 1.11.20 manual states Embedded strings of the form $keyword$ ... in a file are replaced ... whenever you obtain a new revision of the file. The way I interpret the phase whenever you obtain a new revision of the file is in a working file that has a new revision number. So, when you commit, you obtain a new revision. You don't need to check out to obtain a new revision. Now, what annotate shows is another question. Section A.7.1 of cederqvist says [annotate] print[s] the head revision of the trunk, together with information on the last modification for each line. I will discuss that in Point 4. 2. Jim Hyslop says I just created a test file with the $Log$ keyword and examined the ,v file. The information in there supports what you (i.e. Todd) just said. Well, I looked at the ,v file, which has the folowing: 1.3 log @this is my log ha ha ha @ text @$Id: compiler.c,v 1.2 2005/07/12 02:32:17 mingl Exp $ this is $Date: 2005/07/12 02:32:17 $ this is a file $Log: compiler.c,v $ Revision 1.2 2005/07/12 02:32:17 mingl third commit Revision 1.1.1.1 2005/07/07 00:05:26 mingl init import This is really the last line I added on Monday @ So, indeed, the keywords are not expanded to reflect the latest modification. However, in Section 12 of cederqvist the word files refer to files in the working directory, not in the repository. Keyword substition in the ,v files is undefined in cederqvist. Hence, I don't think it is appropriate to look at the ,v files in the repository to understand the behavior of keyword substitution. It is confusing to talk about keyword expansion in the repository files. 3. Todd says the log entry not yet been checked into CVS. I think that is the implementation detail that users should not be concerned with. From users' perspective, all cederqvist in effect says is After a local file with a keyword is checked in, the keyword in that file is expanded to reflect the new revision information. Maybe Todd knows that the keyword is actually not expanded in the ,v file at the time of the check-in so the ,v file does not have the keyword expanded to reflect the new revision information. But I am hesistant to use some undocumented implementation details, rather than cederqvist, to explain the program behavior. 4. cederqvist says annotate should print the last modification on each line (Sec A.7.1). It does not say whether the modification is in respect to the local file or the ,v file. Neither does it say what modification means in
disable changes of local file
Got large data file in project that I've imported to the repository along with other files. I'd like this file to be kept in repository, but that local changes (this file is changend often locally, because of testing) do not change the copy in repository and that during an update from repository local copy doesn't change either. Now, I know that I can accomplish later trough putting this file name in .cvsignore file, but is there some more proper way and further how to accomplish first. Thanks. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Annotate of Log output wrong
As a comparison, cvs diff considers the source file modified for the keyword expansion. That is, $ cvs diff -r 1.3 -1.2 retrieving revision 1.3 retrieving revision 1.2 diff -r1.3 -r1.2 1,2c1,2 $Id: compiler.c,v 1.3 2005/07/12 03:10:28 mingl Exp $ this is $Date: 2005/07/12 03:10:28 $ --- $Id: compiler.c,v 1.2 2005/07/12 02:32:17 mingl Exp $ this is $Date: 2005/07/12 02:32:17 $ 5,7d4 Revision 1.3 2005/07/12 03:10:28 mingl this is my log ha ha ha In this case, the ,v file actually not modified explanation would not work. CVS does not really determine its behavior, as seen by teh user, on what the contents of the ,v file is. _ Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Inaccurate documentation re cvs tag
Sec 4.5 of 1.11.20 cederqvist says: running the cvs tag command without arguments causes CVS to select the revisions which are checked out in the current working directory. ... One potentially aspect of the fact that cvs tag operates on the repository is that you are tagging the checked-in revisions, which may differ from locally modified files ... I think it is somewhat confusing, especially to new users. At first it talks about a checked-out revision, then it talks about a checked-in revision. Well, I understand they mean the same, at least in some cases; but it is not quite accurate and probably confusing. 1. The problem with checked out is that it does not literally mean checked out. Suppose I check out a file with revision 1.1, modify it and commit it, so now I have revision 1.2 in my working directory. I run cvs tag. And 1.2 gets tagged. Literally 1.1 is the revision I checked out. I did not check out 1.2, unless commit implies check out - but I think it's better separate them; after all ci and co are two different commands. Also, stating that a checked-out version is tagged may give the wrong impression that the user (unnecessarily) needs to do a cvs co before tagging. 2. The problem with checked in is that there may not be any check-in (cvs ci). Suppose I check out a file for the first time and without modifying it, run cvs tag. The one and only one revision gets tagged; but there is never any check-in. Stating that a checked-in revision is tagged may give the wrong impression that the user (unnecessarily) needs to do a cvs ci before tagging. Anyone agrees or disagrees? Incidentally, the entry for tag in Appendix B (page 132) says Add a symbolic tag to checked out version. I think checked out need to be re-worded, and version probably should be revision. Finally there are a number of places in cederqvist that use the phase checked out. I am not sure all mean literally checked out. For example, Sec 1.3.4 says diff compare[s] the version (revision?) of driver.c that you checked out with your working copy. Again, suppose I check out a file with revision 1.1, modify it and commit it, so now I have revision 1.2 in my working directory. I run cvs diff. There is no difference. The comparison is NOT between 1.1 (the last revision I checked out (using cvs co)) and 1.2. I think the phase checked out should be used with care. Ming Kin Lai _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
CCASE data import into CVS
Hello Is it possible to import data from CCASE into CVS ? If yes - how ? Thanks. Martynas ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
How to share files between CVS projects?
Folks, Apologies if this question is a no-brainer. I have basic CVS knowledge but not more. I have 2 versions of source code. In each version only a very few files are different - about 5 in total out of a total of @950. What I want to do is to share the files that are not different to be shared between projects, and to maintain separate versions of the 5 differing files. In VSS I think one can do this by pinning the files. But I am not sure how to achieve this with CVS. TIA - Adam ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Inaccurate documentation re cvs tag
Ming Kin Lai wrote: Sec 4.5 of 1.11.20 cederqvist says: running the cvs tag command without arguments causes CVS to select the revisions which are checked out in the current working directory. ... One potentially aspect of the fact that cvs tag operates on the repository is that you are tagging the checked-in revisions, which may differ from locally modified files ... I think it is somewhat confusing, especially to new users. At first it talks about a checked-out revision, then it talks about a checked-in revision. Well, I understand they mean the same, at least in some cases; but it is not quite accurate and probably confusing. 1. The problem with checked out is that it does not literally mean checked out. Actually it does literally mean the version which was checked out, not what you currently have (i.e., not possible local mods). Suppose I check out a file with revision 1.1, modify it and commit it, so now I have revision 1.2 in my working directory. Well this commit does do essentially a checkout (actually update, which is why things like $Log:$ and $Id:$ get updated). I run cvs tag. And 1.2 gets tagged. Because you checked out (updated to) 1.2 by committing it. Literally 1.1 is the revision I checked out. I did not check out 1.2, unless commit implies check out - but I think it's better separate them; after all ci and co are two different commands. It was learned long ago that less confusion was created by cvs handling the immediate update, otherwise cvs would have a hard time being Concurrent Versions System, the command you imply are serial locking commands and CVS is a parallel merging system. Also, stating that a checked-out version is tagged may give the wrong impression that the user (unnecessarily) needs to do a cvs co before tagging. No the update makes it the checked out version, this is simply a misconception on your part. 2. The problem with checked in is that there may not be any check-in (cvs ci). Suppose I check out a file for the first time and without modifying it, run cvs tag. The one and only one revision gets tagged; but there is never any check-in. If you checked it out there was a check in, which created 1.1. Stating that a checked-in revision is tagged may give the wrong impression that the user (unnecessarily) needs to do a cvs ci before tagging. Anyone agrees or disagrees? Yes, see above. Incidentally, the entry for tag in Appendix B (page 132) says Add a symbolic tag to checked out version. I think checked out need to be re-worded, and version probably should be revision. In most cases people tag an entire baseline (which is also the better practice), which has a version, but also has many files which have revisions. It seems clear as written from here. Finally there are a number of places in cederqvist that use the phase checked out. I am not sure all mean literally checked out. For example, Sec 1.3.4 says diff compare[s] the version (revision?) of driver.c that you checked out with your working copy. Again, suppose I check out a file with revision 1.1, modify it and commit it, so now I have revision 1.2 in my working directory. I run cvs diff. There is no difference. The comparison is NOT between 1.1 (the last revision I checked out (using cvs co)) see above information about your misunderstanding because cvs commit does an update to get you synchronized with what is in the baseline after commit. and 1.2. I think the phase checked out should be used with care. It is, you simply have a little learning to do. Ming Kin Lai -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Annotate of Log output wrong
Ming Kin Lai wrote: This is to continue the discussion of the thread with the same subject that started on Dec 7, 2004. The original discussion appeared to focus on the expansion of the $Log$ keyword both in the file and as output by the cvs annotate command (under version 1.11.17); but I think other keywords such as $Id$ have the same problem. I am running CVS version 1.11.6 on Solaris. After I committed a file that contains some keywords, (I did not perform a checkout or update after that,) the file in my working directory shows the following: See my reply to your 'Inaccurate documentation re cvs tag'. commit does an update to keep things consistent between your sandbox and the repo when it gets done. BTW I think you should stop thinking of ci and co, which are RCS commands, and start thinking in terms of checkin and checkout which are CVS commands, and imply a bit more work. (although CVS will happily let you abbreviate checkin with ci and checkout with co, do not try to abbreviate the concepts.) SNIP Annotations for compiler.c *** 1.3 (mingl12-Jul-05): $Id: compiler.c,v 1.2 2005/07/12 02:32:17 mingl Exp $ 1.3 (mingl12-Jul-05): this is $Date: 2005/07/12 02:32:17 $ 1.2 (mingl12-Jul-05): $Log: compiler.c,v $ SNIP From the leftmost column, it is obvious that the latest revision is 1.3; however, the keywords expand to only revision 1.2. 1. Todd Denniston states that If I Recall Correctly, $Log:$ is expanded on checkout, so the last (chronological) log entry seen in a Log in a sandbox has not yet been checked into CVS. Therefore, the repository knows nothing about it, and can not annotate what to it does not exist. (Larry Jones says similar thing: the $Log$ keyword (not command) is expanded by checkout/update.) I think the first half of the sentence is inaccurate: apparently the keywords are expanded (in the working file) upon commitment (check-in), i.e. no subsequent checkout is needed. No you misinterpret the situation, because commit syncs your sandbox with the repository after it does the commit. (What Todd probably meant is: $Log$ is expanded in the ,v file on checkout. - But see my Points 2 and 3 below.) And I think check in and check out should not be confused. ci and co are two separate commands, aren't they? Yes and NO. co can be performed separate, but in a Concurrent situation, a ci must be followed with a co to have your sandbox in sync, CVS handles it for you. (some where around here I expect Larry, Derek or Greg to hit me with a clue stick.) The keywords are expanded in the working file on checkin, not checkout. In fact, Section 12 of the cederqvist 1.11.20 manual states Embedded strings of the form $keyword$ ... in a file are replaced ... whenever you obtain a new revision of the file. The way I interpret the phase whenever you obtain a new revision of the file is in a working file that has a new revision number. So, when you commit, you obtain a new revision. You don't need to check out to obtain a new revision. correct you obtain the new revision because commit updates your local directory to re-expand the RCS keywords. Now, what annotate shows is another question. Section A.7.1 of cederqvist says [annotate] print[s] the head revision of the trunk, together with information on the last modification for each line. I will discuss that in Point 4. SNIP 3. Todd says the log entry not yet been checked into CVS. I think that is the implementation detail that users should not be concerned with. From users' perspective, all cederqvist in effect says is After a local file with a keyword is checked in, the keyword in that file is expanded to reflect the new revision information. Maybe Todd knows that the keyword is actually not expanded in the ,v file at the time of the check-in so the ,v file does not have the keyword expanded to reflect the new revision information. But I am hesistant to use some undocumented implementation details, rather than cederqvist, to explain the program behavior. Actually, it is a known thing that the RCS keywords cause problems / misunderstandings and it is expected that if you really want to use them you will do enough reading and experimenting to understand their intricate problems in a concurrent environment, i.e., they were made to be used in RCS not CVS and their behavior because of the RCS history makes them act kind of badly under CVS. 4. cederqvist says annotate should print the last modification on each line (Sec A.7.1). It does not say whether the modification is in respect to the local file or the ,v file. partially agreed, the manual does indicate that it is printing the head revision of the trunk which implies the version from the repository. I am not certain (someone needs to test) if you are on a branch if annotate does the branch instead of the trunk. assuming annotate will show branch information if you
Re: CCASE data import into CVS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Buozis, Martynas [EMAIL PROTECTED] writes: Is it possible to import data from CCASE into CVS ? If yes - how ? Thanks. You should use a search engine to find prior art... something like this describes how you might go about writing one for yourself... http://lists.gnu.org/archive/html/info-cvs/2001-06/msg00134.html You should also consider looking for something that can export from ClearCase into RCS as it is a short step from there to using CVS. If you come up with a script, feel free to post it to bug-cvs@gnu.org for possible inclusion into the contrib directory. Good luck, -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFC09RL3x41pRYZE/gRAvQTAJ47rUWCpBSQgvZYbr7AYCTSSWyhEACdEnlg UYTLDEpkhu9yM4Uue57ZvXs= =lAGA -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: How to share files between CVS projects?
Search for modules and ampersand modules to combine different directories into one project, or keep the changes to one set of files on a branch. ~Matt -Original Message- From: [EMAIL PROTECTED] [mailto:info-cvs- [EMAIL PROTECTED] On Behalf Of Adam Lipscombe Sent: Tuesday, July 12, 2005 3:23 AM To: info-cvs@gnu.org Subject: How to share files between CVS projects? Folks, Apologies if this question is a no-brainer. I have basic CVS knowledge but not more. I have 2 versions of source code. In each version only a very few files are different - about 5 in total out of a total of @950. What I want to do is to share the files that are not different to be shared between projects, and to maintain separate versions of the 5 differing files. In VSS I think one can do this by pinning the files. But I am not sure how to achieve this with CVS. TIA - Adam ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Is it OK to post an EAP/beta invitation for a product thatintegrates with CVS?
I'd say sure, if it's just one post (text not HTML). And if the product is any good ;-) ~Matt -Original Message- From: [EMAIL PROTECTED] [mailto:info-cvs- [EMAIL PROTECTED] On Behalf Of Slavik Sent: Monday, July 11, 2005 11:54 PM To: info-cvs@gnu.org Subject: Is it OK to post an EAP/beta invitation for a product thatintegrates with CVS? Hello all, I was wondering if it is OK to post here an invitation to an early access AKA beta program for a product that integrates with CVS (a continuous integration/build management server)? Thanks, Slavik ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
We have seen similar problems with the SmartCVS zlib compression. In fact yesterday our QA found an issue with SmartCVS 4.0.5 whereby connection closes by server was causing java io exception in the Java zlib input stream handler in SmartCVS. With compression disabled all was well. Regards, Rahul Bhargava CTO, WANdisco http://www.wandisco.com/cvs ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How to share files between CVS projects?
Adam Lipscombe wrote: Folks, Apologies if this question is a no-brainer. I have basic CVS knowledge but not more. I have 2 versions of source code. In each version only a very few files are different - about 5 in total out of a total of @950. What I want to do is to share the files that are not different to be shared between projects, and to maintain separate versions of the 5 differing files. 1) If you mean that you have two projects that use the same source, however each has some files with specific mods in just a few of the files and only those changes can not share between the two, I would think what you would want is to branch (cvs tag -b tagname). the further choice would be, do you do development on the trunk in a generic manner and have two branches and update the branches only when the generic set has stabilized. or do you have one of the projects be the main one (on the trunk) and only update the other one on the branch when the main one stabilizes, i.e., Third Party Codeline[2]. I suggest look at the ACME project [1] for ideas. [1] http://www.cmcrossroads.com/bradapp/acme/ http://www.cmcrossroads.com/bradapp/acme/branching/ [2] http://www.cmcrossroads.com/bradapp/acme/branching/branch-structs.html#ThirdPartyLine 2) If on the other hand you have a situation where each project essentially use a library of other code and have completely different non common files, then having the non common in their own sub repositories and using ampersand modules would be a good idea. In VSS I think one can do this by pinning the files. But I am not sure how to achieve this with CVS. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
How do I get a barebone stripped off list of files changed between 2 builds?
Hi I'm trying to get a stripped down list of files modified and committed between 2 builds or a build and my working folder in CVS. I would just like to see the path/filename only. Compare it to a list received from the developers to verify we're in synch, do the build and deliver their corresponding .class files. Many of the CVS commands (log, tag, history, diff, etc) generate way more than I need. Do I need to write scripts that parse out what I need? Is there a cvs command to do this so I can avoid scripting? For instance I did the following command: cvs history -ac -D yesterday cvsHist1.txt And this is yet the closest I've got to what I needed. Thanks Steve ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
Liquidchild wrote: Guys Finally got it all working! woho! Great. Only question I have left is can you make files read only in smartCVS so that users have to select the file for editing first, to stop other users being able to edit the same file at the same time? Canonical answer: Why would you want to do that? Are you working with some strange binary format? Full answer: If you really think you wan to do that, read the manual section 10 Multiple developers[1], the answers you seek are there. [1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_10.html#SEC82 -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How do I get a barebone stripped off list of files changed between 2 builds?
On Tuesday July 12, 2005 03:58 pm, S I [EMAIL PROTECTED] wrote: I'm trying to get a stripped down list of files modified and committed between 2 builds or a build and my working folder in CVS. I would just like to see the path/filename only. What I generally do is use the rdiff command with the -q and -s (for shout output) options. Something like: cvs -q rdiff -s -r TAG1 -r TAG2 module. You can substitute any valid combination of -r and -D options to restrict the output to the range you want. So in this case, your example would be: cvs -q rdiff -s -r HEAD -D yesterday your-module-name cvsHist1.txt - Rob -- Robert J. Clark [EMAIL PROTECTED] ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How do I get a barebone stripped off list of files changed between2 builds?
S I wrote:
Hi
I'm trying to get a stripped down list of files modified and committed
between 2 builds or a build and my working folder in CVS. I would just like
to see the path/filename only. Compare it to a list received from the
developers to verify we're in synch, do the build and deliver their
corresponding .class files.
Many of the CVS commands (log, tag, history, diff, etc) generate way more
than I need. Do I need to write scripts that parse out what I need? Is
there a cvs command to do this so I can avoid scripting?
For instance I did the following command:
cvs history -ac -D yesterday cvsHist1.txt
And this is yet the closest I've got to what I needed.
I am usually happy with what cvs2cl gives me. I do however have a script
which does:
PREVIOUS_DATE=`ls -l --full-time $OUTFILE 2/dev/null| \
awk '{print $7 \ \ $8 \ \ $9 \ \ $10}'`
cvs his -calD $PREVIOUS_DATE |sort -rb -k 7,7 |\
sort -mub -k 7,7|sort -b -k 8,8 $TMP_FILE
the sorts get rid of redundant information to hopefully just show the last
change of each file.
$OUTFILE is a file that was created when the script was last ran, and well I
expect you know what $TMP_FILE is. It still has a lot of information in it,
but I find that info useful, I believe if you take $TMP_FILE and run it
through the following awk it will have just what you want:
cat $TMP_FILE|awk '{print $8 / $7 }'
as I indicated I only use it to see what has changed between runs, more of a
disaster recovery tool than anything (and yes I have _used it for that_),
now that I have cvs2cl and am using CVS vs SCCS.
Your biggest trick is either creating a file with the date you want, or
building up the $PREVIOUS_DATE string by hand.
Thanks
Steve
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Inaccurate documentation re cvs tag
Sec 4.5 of 1.11.20 cederqvist says: running the cvs tag command without arguments causes CVS to select the revisions which are checked out in the current working directory. ... One potentially aspect of the fact that cvs tag operates on the repository is that you are tagging the checked-in revisions, which may differ from locally modified files ... I think it is somewhat confusing, especially to new users. At first it talks about a checked-out revision, then it talks about a checked-in revision. Well, I understand they mean the same, at least in some cases; but it is not quite accurate and probably confusing. 1. The problem with checked out is that it does not literally mean checked out. Actually it does literally mean the version which was checked out, not what you currently have (i.e., not possible local mods). Apparently you and I have disagreement about what literally means means. Suppose I check out a file with revision 1.1, modify it and commit it, so now I have revision 1.2 in my working directory. Well this commit does do essentially a checkout (actually update, which is why things like $Log:$ and $Id:$ get updated). This makes it clear what you mean by literally means - to you, a commit essentially does a checkout, so a commit literally means a checkout. But to me, even though a commit essentially does a checkout, it is not a literally a checkout. Please note that there is nowhere in cederqvist that says a commit is essentially a checkout or a commit implies a checkout, etc (if you can find such, please show me). To an experienced user like you, that may be clear. But as I said, that may be confusing to a new user. A manual such as cederqvist is to make things clear. People should not need a yaer's experience using CVS to understand what cederqvist really means. I run cvs tag. And 1.2 gets tagged. Because you checked out (updated to) 1.2 by committing it. Again, I cannot find any place in cederqvist that says when the user commits a file, he in effect checks it out. And that's my point: cederqvist should mke this clear or use the word checked out with care. Literally 1.1 is the revision I checked out. I did not check out 1.2, unless commit implies check out - but I think it's better separate them; after all ci and co are two different commands. It was learned long ago that less confusion was created by cvs handling the immediate update, otherwise cvs would have a hard time being Concurrent Versions System, the command you imply are serial locking commands and CVS is a parallel merging system. I did not imply any command. What I mean is less confusion would be created by explaining what check out really mean, e.g. that would be implied by a commit. Also, stating that a checked-out version is tagged may give the wrong impression that the user (unnecessarily) needs to do a cvs co before tagging. No the update makes it the checked out version, this is simply a misconception on your part. I am pointing out a potential misconception because of the way checked out is used in cederqvist. 2. The problem with checked in is that there may not be any check-in (cvs ci). Suppose I check out a file for the first time and without modifying it, run cvs tag. The one and only one revision gets tagged; but there is never any check-in. If you checked it out there was a check in, which created 1.1. Not necessarily. I initially import the file and then check it out. There is no check-in. Well, I guess you would say something like an import essentially does a check-in or an import literally means a check-in. My take is that if that's what the CVS designers mean, fine, document it in cederqvist to avoid misunderstanding. A user should be not be left wondering whether xxx is essentially doing yyy. From this discussion it is quite apparent that you separate the _concept_ of checkin and checkout, respectively, from the actual command of cvs checkin (or cvs ci) and cvs checkout (or cvs ci), respectively. It appears, to you, the concept of checkout encompasses both the cvs checkout and cvs commit, for example. I am not arguing about the merit of this way of thinking. Look at the title of my post - inacurrate documentation. I am talking about the documentation. If you can find any place in cederqvist that explains that the concept of checkin encompasses cvs checkout and cvs commit, please show me. If you do not explain that to a new user, can you expect him to somehow figure it out himself? Yes, he will eventually. But why can't the documentation give him an easier time? cederqvist is not just a reference for experienced users, it also serves as a guide for first-time users. Stating that a checked-in revision is tagged may give the wrong impression that the user (unnecessarily) needs to do a cvs ci before tagging. Anyone agrees or disagrees? Yes, see above. Incidentally, the entry for
Re: How do I get a barebone stripped off list of files changed between 2 builds?
Hello, --- S I [EMAIL PROTECTED] wrote: Hi I'm trying to get a stripped down list of files modified and committed between 2 builds or a build and my working folder in CVS. I would just like to see the path/filename only. Compare it to a list received from the developers to verify we're in synch, do the build and deliver their corresponding .class files. Many of the CVS commands (log, tag, history, diff, etc) generate way more than I need. Do I need to write scripts that parse out what I need? Is there a cvs command to do this so I can avoid scripting? You can avoid this kind of scripting by using Parabuild for your build automation - it shows new changes in the build. The side effect is that you will never be out of sync... Slavik ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS Export
Liquidchild writes: When i run the cvs export command either through WinCVS or on the command line using [...] it exports the ecc module with the CVSROOT folders and CVS folders. Have you looked at the repository to see if someone managed to actually add those directories to it? -Larry Jones I've got to start listening to those quiet, nagging doubts. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking CVS
Jim Hyslop writes: If you want to lock all projects, then create an empty $CVSROOT/CVSROOT/writers file. I believe this will work for all access methods, not just pserver. You believe incorrectlly. The readers and writers files only affect pserver. -Larry Jones You should see me when I lose in real life! -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Error while checking out.
Sumit Dey writes: cvs [server aborted]: cannot write D:/CVSRepo/Project342/CVSROOT/val-tags: Permission denied Any help will be greatly appreciated. I don't see how the error message could be any clearer -- you need to change the permissions on your val-tags file so that anyone can write to it. See the manual: https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC13 -Larry Jones Even my FRIENDS don't do what I want. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
cvs branch version
Hi, I used 'cvs tag' to add a file to a branch. I then used 'cvs commit -r... ' to check in a new version. It normally creates a subversion from the version initially tagged. For example, I tag file 'A' version 1.1 with release-patch. It creates a version 1.1.0.2 for the tag. When I check in a new version to the branch, it creates a version 1.1.2.1. But this time, I did not see any output from the command line after I entered the comments in vi. When I did a 'cvs log', I did not see any subversion created. If I do a 'cvs status' on the file, the sticky tag shows : Sticky Tag: release-patche (branch: 1.1.2) But I cannot see this revision with 'cvs log'. Can anyone explain what happened? Thanks, Mei ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs branch version
ypi can use wincvs or other GUI front to help you. If you are not very familiar with the command line opition, and the operation. Enjoy. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: disable changes of local file
[EMAIL PROTECTED] wrote: Got large data file in project that I've imported to the repository along with other files. I'd like this file to be kept in repository, but that local changes (this file is changend often locally, because of testing) do not change the copy in repository and that during an update from repository local copy doesn't change either. Not easy. Anyone can commit new revisions. What you should do (should have done) is import the file under a different name, that makes it clear that it is a template for the tests. Developers would have to copy the template file to the correct filename before running their tests. Since the copied file is not in CVS, they can make any change they want. If it's early enough in the game, the path of least resistance is to rename the ,v file in the repository --but that breaks any checked out sandbox, so people should check out new ones and delete the old. Now, I know that I can accomplish later trough putting this file name in .cvsignore file, but is there some more proper way and further how to accomplish first. Actually, no. Files listed in CVS/Entries are never ignored. -- pa at panix dot com ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: How do I get a barebone stripped off list of files changed between
S I writes: I'm trying to get a stripped down list of files modified and committed between 2 builds or a build and my working folder in CVS. I would just like to see the path/filename only. Compare it to a list received from the developers to verify we're in synch, do the build and deliver their corresponding .class files. Take a look at rdiff -s. -Larry Jones Fortunately, that was our plan from the start. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Annotate of Log output wrong
Ming Kin Lai writes: The original discussion appeared to focus on the expansion of the $Log$ keyword both in the file and as output by the cvs annotate command (under version 1.11.17); but I think other keywords such as $Id$ have the same problem. They do. The bottom line is that keywords are expanded to their current values by the checkout/update process that is also part of the checkin process and some other processes (like diff). Annotate, on the other hand, annotates the RCS file as-is, without any further processing. Feel free to submit patches if you would like it to behave differently. -Larry Jones They can make me do it, but they can't make me do it with dignity. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Pbm updating sandbox
Hello, An user has put a new source in the repository. But other users can't even see the new source when updating their sandbox even which tkcvs. What can be the reason ? Thanks for your help. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Error while checking out.
Hi all, I am getting the following error message when I try to checkout using a tag. I can see the tag existing when I display the graph. "cvs [server aborted]: cannot write D:/CVSRepo/Project342/CVSROOT/val-tags: Permission denied" Any help will be greatly appreciated. Thanking you,With Best Regards,Sumit. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
CVS Export
When i run the cvs export command either through WinCVS or on the command line using cvs export -r DNOW ecc it exports the ecc module with the CVSROOT folders and CVS folders. Can anyone give me a hint, or preferably the answer as to what I am doing wrong! Thanks in advance guys S. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Pbm updating sandbox
Muriel Delaveau wrote: Hello, An user has put a new source in the repository. But other users can't even see the new source when updating their sandbox even which tkcvs. What can be the reason ? Thanks for your help. Assumption, the user who put the new source in the repository, did so by using `cvs add file` and `cvs commit file`, and there is a ,v for the file in the repository. Q1) is the new file in a new directory, or a directory that never had any thing in it before? Reason they don't see it: their sandbox has been optimized to work on what was known at the time of their checkout, i.e., don't waste time looking for things we did not find the first time. Fix, have every one else `cvs update -dP`. Q2) is the user who put the new source in the repository, working on a branch, or a different branch from the rest of the users (the trunk can be considered a branch for consideration of this question)? Reason they don't see it: branches exist for work separation and segregation of changes so one group will not affect another until they are ready to be affected. Fix, read the CVS manual on merging changes from branch to branch. (-j options to update or checkout, IIRC) -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking CVS
S I wrote: Hi everyone, I'm planning to lock cvs today getting ready for our release. I realize with certain version control software nowadays you don't have to lock the repo and the developers can continue with their work. However, we're imposing and enforcing a few days for freeze and to regroup. Our repository resides on a linux box with :pserver method access from WinXP CVS DOS and Tortoise clients. Could I just lock the repo by executing cvs admin -l or -L or do I have to download some perl module to accomplish this? I need to lock our CVS repository today. Three projects reside in the repository, is it possible to lock them selectively or would admin -l lock the entire repo? If you want to lock all projects, then create an empty $CVSROOT/CVSROOT/writers file. I believe this will work for all access methods, not just pserver. Unlocking the repository is a simple matter of deleting the file. See https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC36 for details. To selectively lock projects, have a look at the cvs_acls script. It's in the source code distribution (available from www.cvshome.org) in the contrib/ directory. -- Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking CVS
Thank you. I'm not sure what /bin/test represents? To be replaced with the
path to my proj?
Original Message Follows
From: Mark D. Baushke [EMAIL PROTECTED]
To: S I [EMAIL PROTECTED]
CC: info-cvs@gnu.org
Subject: Re: Locking CVS
Date: Mon, 11 Jul 2005 08:49:43 -0700
MIME-Version: 1.0
Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by
mc3-f23.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 11 Jul 2005
08:49:51 -0700
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])by
colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j6BFnn912917;Mon, 11
Jul 2005 08:49:49 -0700 (PDT)(envelope-from [EMAIL PROTECTED])
Received: from juniper.net (sapphire.juniper.net [172.17.28.108])by
merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j6BFnhj59521;Mon, 11 Jul
2005 08:49:43 -0700 (PDT)(envelope-from [EMAIL PROTECTED])
X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8=
References: [EMAIL PROTECTED]
X-Mailer: MH-E 7.84+cvs; nmh 1.0.4; GNU Emacs 21.3.1
X-Face:
#8D_6URD2G%vC.hzUdI#Y9szHj$'mGtUqd=rXy^L$-=G_-LmZ^5!Fszk:yXZp$k\nTF?
8Up0!v/%1Q[(d?ES0mQW8dRCXi18gK)luJu)loHk,}4{Vi`yX?p?crF5o:LL{6#eiO:(E:YMxLXULB
k|'a*EjN.BL+[J!PhJ*aX0n:5/
Mail-Followup-To: info-cvs info-cvs@gnu.org
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 11 Jul 2005 15:49:51.0677 (UTC)
FILETIME=[2CB886D0:01C58630]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
S I [EMAIL PROTECTED] writes:
Hi everyone,
I'm planning to lock cvs today getting ready for our release. I
realize with certain version control software nowadays you don't have
to lock the repo and the developers can continue with their work.
However, we're imposing and enforcing a few days for freeze and to
regroup.
Our repository resides on a linux box with :pserver method access from
WinXP CVS DOS and Tortoise clients. Could I just lock the repo by
executing cvs admin -l or -L or do I have to download some perl
module to accomplish this? I need to lock our CVS repository today.
Three projects reside in the repository, is it possible to lock them
selectively or would admin -l lock the entire repo?
admin -l will not really do what you want.
It would probably be simplest to add something to your CVSROOT/commitinfo
to do the job and fail whenever the :pserver: userid was used.
If you have an 'id' command that accepts the -u option, and for example
if the 'id -u' command printed 12345 as your userid, you could add
For cvs 1.11.x
ALL /bin/test `id -u` = 12345
For cvs 1.12.x you might want to use
ALL /bin/test `id -u` = 12345 : %r/%p %s
This should return a non-zero error code for anyone other than the user
with the uid 12345 which we would presume you would use your own userid
and that you would be accessing the repository outside of the :pserver:
method or have arranged for your :pserver: usage to use your real userid
rather than masking it with the system userid.
Other methods exist for just locking a single branch (such as the main
trunk) using something like the contrib/cvs_acls file that comes with
recent cvs distributions.
Good luck,
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFC0pUX3x41pRYZE/gRAidYAJ4q835ZSjjYD585MNFhbFjRMdibWwCeKjwT
HJNxXIpklSOnVL0LdeqU7DM=
=dQWC
-END PGP SIGNATURE-
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking CVS
All 3 projects are under /usr/local/cvs/proj1 thru 3. I just added a blank writers file. Will this do it until I do a final build, tag, and branch? Original Message Follows From: Todd Denniston [EMAIL PROTECTED] To: S I [EMAIL PROTECTED] CC: info-cvs@gnu.org Subject: Re: Locking CVS Date: Mon, 11 Jul 2005 11:01:21 -0500 MIME-Version: 1.0 Received: from mail.ssa.crane.navy.mil ([164.227.42.3]) by mc1-f12.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 11 Jul 2005 09:04:32 -0700 Received: from ssa.crane.navy.mil ([EMAIL PROTECTED] [164.227.42.142]) by mail.ssa.crane.navy.mil with ESMTP id LAA19518; Mon, 11 Jul 2005 11:03:05 -0500 X-Message-Info: JGTYoYF78jEHjJx36Oi8+Z3TmmkSEdPtfpLB7P/ybN8= Organization: Code 6067, NSWC Crane X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.25glock1 i686) X-Accept-Language: en References: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 11 Jul 2005 16:04:32.0380 (UTC) FILETIME=[39A923C0:01C58632] S I wrote: Hi everyone, I'm planning to lock cvs today getting ready for our release. I realize with certain version control software nowadays you don't have to lock the repo and the developers can continue with their work. However, we're imposing and enforcing a few days for freeze and to regroup. Another method would be to tag and then branch, decide whether the trunk or branch is where you will host the release, and use cvs_acls to lock down the trunk/branch for release work only. look at ACME [2] for ideas. Our repository resides on a linux box with :pserver method access from WinXP CVS DOS and Tortoise clients. Could I just lock the repo by executing cvs admin -l or -L or do I have to download some perl module to accomplish this? I need to lock our CVS repository today. Three projects reside in the repository, is it possible to lock them selectively or would admin -l lock the entire repo? There are a few ways I think you could go at it. If you don't even want anyone reading from the repo, you could temporarily remove it's allow-root option from [x]inetd.conf.(assumes the three projects have different roots in [x]inetd.conf) if you are ONLY accessing the repo via pserver, the reader / writer [1] files could do it for you.(assumes the three projects have different roots in [x]inetd.conf, OR that none of the developers work on multiple projects) if you want fine grain control, look at using cvs_acl, from the distribution contrib directory, as a commitinfo script. [1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC36 [2] http://www.cmcrossroads.com/bradapp/acme/ http://www.cmcrossroads.com/bradapp/acme/branching/ -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking CVS
S I wrote: Hi everyone, I'm planning to lock cvs today getting ready for our release. I realize with certain version control software nowadays you don't have to lock the repo and the developers can continue with their work. However, we're imposing and enforcing a few days for freeze and to regroup. Another method would be to tag and then branch, decide whether the trunk or branch is where you will host the release, and use cvs_acls to lock down the trunk/branch for release work only. look at ACME [2] for ideas. Our repository resides on a linux box with :pserver method access from WinXP CVS DOS and Tortoise clients. Could I just lock the repo by executing cvs admin -l or -L or do I have to download some perl module to accomplish this? I need to lock our CVS repository today. Three projects reside in the repository, is it possible to lock them selectively or would admin -l lock the entire repo? There are a few ways I think you could go at it. If you don't even want anyone reading from the repo, you could temporarily remove it's allow-root option from [x]inetd.conf.(assumes the three projects have different roots in [x]inetd.conf) if you are ONLY accessing the repo via pserver, the reader / writer [1] files could do it for you.(assumes the three projects have different roots in [x]inetd.conf, OR that none of the developers work on multiple projects) if you want fine grain control, look at using cvs_acl, from the distribution contrib directory, as a commitinfo script. [1] https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_2.html#SEC36 [2] http://www.cmcrossroads.com/bradapp/acme/ http://www.cmcrossroads.com/bradapp/acme/branching/ -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Locking CVS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 S I [EMAIL PROTECTED] writes: Thank you. I'm not sure what /bin/test represents? To be replaced with the path to my proj? It represents the /bin/test (see 'man test' on your GNU/Linux box for more details) command to compare the output of the `id -u` command with the numeric value of your own id. Otherwise you would never be able to undo the change to the CVSROOT/commitinfo script and it would be locked forever. The ALL means that all possible modules will run this test during the commit phase. The : command will accept any argument and always return true. This will stop any warnings that cvs 1.12.x might want to give you for using the older style format string defaults. As always, it is recommened that you run tests on a repository other than your main repository to be sure you understand how things work. -- Mark mdb wrote: For cvs 1.11.x ALL /bin/test `id -u` = 12345 For cvs 1.12.x you might want to use ALL /bin/test `id -u` = 12345 : %r/%p %s This should return a non-zero error code for anyone other than the user with the uid 12345 which we would presume you would use your own userid and that you would be accessing the repository outside of the :pserver: method or have arranged for your :pserver: usage to use your real userid rather than masking it with the system userid. Other methods exist for just locking a single branch (such as the main trunk) using something like the contrib/cvs_acls file that comes with recent cvs distributions. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFC0qIA3x41pRYZE/gRAssoAJ94aJt2/mY6gWHZ+jIrmFOUqHpOuACeITqT mY14iW+q1tps5zWsRGV10uU= =l6yd -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
cannot open /nonexistant/.cvsignore: Permission denied
Title: cannot open /nonexistant/.cvsignore: Permission denied Hello Colleagues, Its my second posting on the same issue. I am relatively new to CVS and I would really appreciate if somebody could help me to understand the root cause of the problem. I am using CVS version 1.11.17 for both client and server. My server is in Oregon. My client is in California. It runs on a PC under Windows XP using CYGWIN_NT-5.1 1.5.13(0.122/4/2) 2005-03-01 11:01. CVS works fine for me. However, every time I do a check in I get an additional error message: cvs server: cannot open /nonexistant/.cvsignore: Permission denied Every time I do a cvs update it works but every directory has an additional error message: cvs update: cannot open /nonexistant/.cvsignore: Permission denied I looked into my directories. File .cvsignore is present everywhere. Its permissions are writable for me. As an experiment I focused on one directory and made .cvsignore file writable for everybody. It did not help. I searched and have not found any directory with nonexistant name. I searched Internet and your archives. This message was not found. I would really appreciate if anybody knows where these messages come from and why. Thank you in advance. Boris ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Status of CVS on OpenVMS
In a message of Mon, 11 Jul 2005 16:34:04 +0200 Received on Mon, 11 Jul 2005 17:15:49 +0200 Andreas Lalloo [EMAIL PROTECTED] wrote to info-cvs@gnu.org Hello list! What is the status regarding support for OpenVMS on client side (pserver)? We are running a software shop where we have a range of old VMS systems where we basically build source (development mostly done on other platforms), with VMS versions ranging from 6.2 to 8.2 (alpha and itanium). We even run VAX hardware. For the newer platforms (7.1 and later) we've run a slightly modified version of 1.11.1p1. I am not sure what the modifications are, but I'm told some pipe functionality was modified to get it working on 6.X systems and those modifications were used on 7.x as well, even if they _might_ be unnecessary. I am curious if there are other users of CVS on OpenVMS, which versions they run and if I can get latest source for the 1.11 branch at least and compile them out-of-the-box on OpenVMS 7.X or later? I once managed to get a 1.12.5 running on 7.2-1. I'd like to send you a patch but I can't since cvshome discontinued pserver access. That was the only access method I could get to work. All the other rsh/ssh didn't work. I tried rsh with ucx's rsh and fish but to no avail. I quickly looked at what was necessary to change but it seemed rather complex to me. There is a small chance I sent a patch to this list - search the archives - but probably I didn't as it wasn't quite ready. It certainly has problems with filenames not supported on ODS-2 volumes although I didn't do a proper check on ODS-5. And cvs up always creates new versions, even in [.cvs]. So a lot of purge [...] is required. Michael ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cannot open /nonexistant/.cvsignore: Permission denied
Boris Landa wrote: Hello Colleagues, It's my second posting on the same issue. I am relatively new to CVS and I would really appreciate if somebody could help me to understand the root cause of the problem. I am using CVS version 1.11.17 for both client and server. My server is in Oregon. My client is in California. It runs on a PC under Windows XP using CYGWIN_NT-5.1 1.5.13(0.122/4/2) 2005-03-01 11:01. CVS works fine for me. However, every time I do a check in I get an additional error message: cvs server: cannot open /nonexistant/.cvsignore: Permission denied SNIP I searched and have not found any directory with nonexistant name. I searched Internet and your archives. This message was not found. Because of cygwin, you get a different message than is normally found. the canonical message is cvs server: cannot open /root/.cvsignore: Permission denied If you or someone else feels up to it, the manual should probably be updated to include cvs server: cannot open /nonexistant/.cvsignore: Permission denied in all the places you find the above message. And here is some reading on the subject. http://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=%2Froot%2F.cvsignore+and+jonessubmit=Search%21idxname=info-cvsmax=20result=normalsort=score Also in: https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_21.html#SEC188 a little ways down we see: cvs server: cannot open /root/.cvsignore: Permission denied cvs [server aborted]: can't chdir(/root): Permission denied See Trouble making a connection to a CVS server. - https://www.cvshome.org/docs/manual/cvs-1.11.20/cvs_21.html#SEC189 apparently then you probably haven't specified `-f' in `inetd.conf'. Hope this helps. I would really appreciate if anybody knows where these messages come from and why. Thank you in advance. Boris -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: migration of CVS repositery from one machine to another
One more query... do I need to create the repositery by cvs -d CVSROOT init or just by creating a folder and copying the files from existing repositery will do. On 7/6/05, Jim Hyslop [EMAIL PROTECTED] wrote: ravish agarwal wrote: Does that mean that by only copying the files of the repositery after installing the new version of CVS will do the needful. all the history-details will remain there.? also Is there any possilble version upgrade related issues. Please Help me out.As Todd Dennison wrote earlier in the thread, this is covered in themanual. Yes, that's all you need to do. There should be no other version upgrade issues.--Jim ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
newbie CVSROOT/passwd questions
Dear CVS users: I am a pretty newbie in cvs admin, could someone take a little time to guide me through the following problems: 1) In file CVSROOT/passwd, If I define: huaer:pswd:cvs where huaer is not a system userID. Now I want to communicate between the repository and sandbox with SSH, what info I should use in the -d CVSROOT? i.e. cvs -d :ext:cvs@server:/home/CVSROOT co cm If I use username:cvs, and its password to access to the repository, how can I know it is the user huaer instead of other people did this checkout??? I mean when we shall use these info in the CVSROOT/passwd?? 2) How to generate the second fieldpswd? Is there any command or softwares available under Linux? 3) what's the difference between pserver and SSH on using the file CVSROOT/passwd? Many thanks.. Huaer ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: how do I undo local changes
Hello, adding to what Jason and Rahul said: * On Fri, Jul 08, 2005 at 03:27:13PM -0700 MEENA SELVAM wrote: but in CVS I only find the cvs admin -o command to revert to older versions. But how can i simply undo the changes locally, without concerning about version? From your statement, I am not sure if you correctly understand the impliciations of the admin -o command. Thus, the following applies: WARNING: DON'T DO THIS! ;) There is almost never a reason to do a cvs admin -o, thus, be very careful unless you fully understand what that means. This command has NOTHING to do with what you want to achieve. Your task can be done by removing the file before doing an update, or using up -C (as Jason und Rahul said). Best regards, Spiro. -- Spiro R. Trikaliotis http://cbm4win.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: add new files to branch
Mei-Xing Zhao [EMAIL PROTECTED] wrote: Thanks. cvs tag works. But after running this cvs tag command, do I do a cvs add to add this file the the branch? It's already added. Just switch your sandbox to the branch, cvs update -r release-1-patch and you'll find that the file is now present. -- pa at panix dot com ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: error while installing CVS 1.11.20
I installed gcc and biasom Now, I am getting following error message:
usr/ccs/bin/ld: Warning At least one PA 2.0 object file add.o was detected. The linked output may not run on a PA 1.x system/usr/ccs/bin/ld: Unsatisfied sysmbols:GSS_C_NT_HOSTBASED_SERVICE (first referenced in
client.o) (data)collect2: ld returned 1 exit status.*** Error exit code 1
Stop
I got the same error when I tried with
$ ./configure --without-gssapi
$ make
$ make install
what could be reason of the problem.
regards
Ravish
On 7/6/05, Mark D. Baushke [EMAIL PROTECTED] wrote:
ravish agarwal [EMAIL PROTECTED] writes:
I am getting following error while installing CVS-1.11.20.On what operating system are you running?What compiler version are you using? # make No suffix list. make all-recursive
No suffix list. Making all in lib source='getpass.c' object='getpass.o' libtool=no \ DEPDIR=.deps depmode=hp /bin/sh ../depcomp \ cc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -g -c getpass.c
(Bundled) cc: warning 480: The -g option is available only with the C/ANSI C pro duct; ignored. (Bundled) cc: getpass.c, line 40: error 1705: Function prototypes are an ANSI
feature. *** Error exit code 1 Stop. *** Error exit code 1 Stop. *** Error exit code 1Please help me out. What is the possible cause of this error
regardsNote: You should consider getting a compiler that is able to deal withANSI C. Future releases of CVS (1.12.x) will give you many problemsotherwise as that release of CVS assumes a C89 capable standalone
compiler.Does the following patch fix your problem? -- MarkChangeLog entry:2005-07-06Mark D. Baushke[EMAIL PROTECTED] *
getpass.c (getpass): Add a KR style function definition.Index: getpass.c===RCS file: /cvs/ccvs/lib/getpass.c,vretrieving revision
1.1.2.4diff -u -p -u -p -r1.1.2.4 getpass.c--- getpass.c 2 Oct 2003 18:40:13 - 1.1.2.4+++ getpass.c 6 Jul 2005 15:31:55 -@@ -37,7 +37,12 @@#endif
char *+#if __STDC__getpass (const char *prompt)+#else+getpass (prompt)+const char *prompt;+#endif{FILE *in, *out;struct termios s, t;
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Smart CVS
Guys Finally got it all working! woho! Only question I have left is can you make files read only in smartCVS so that users have to select the file for editing first, to stop other users being able to edit the same file at the same time? Thanks for all the help! ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: CVS and SSH V2
Guys Finally got it all working! woho! Only question I have left is can you make files read only in smartCVS so that users have to select the file for editing first, to stop other users being able to edit the same file at the same time? Thanks for all the help! ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Guys Finally got it all working! woho! Only question I have left is can you make files read only in smartCVS so that users have to select the file for editing first, to stop other users being able to edit the same file at the same time? Thanks for all the help! ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
merging branch to HEAD when branch contains partly trunk changes already
Suppose the following situation. +-1.25.2 .. -- 1.25.2.2 -- 1.25.2.5 | ^ | |merge in 1.25 -- ... -- 1.27 -- ... -- 1.31 At 1.25 I created a branch. Later I merged the changes between 1.25 and 1.27 into the branch at 1.25.2.2 to have minor updates of the main trunk also in the branch. Now I want to merge the branch back into the trunk. I tried a straighforward merge of the tip of the branch with the tip of the trunk and get only minor conflicts. Am I just lucky with that? Normally I would expect all the changes between 1.25 and 1.27 to conflict, because they are in the branch but also already in the trunk. Or does CVS silently ignore changes which would not change anything in this case? (I am making sense?) Harald. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: merging branch to HEAD when branch contains partly trunk changes already
Herald, On 8 Jul 2005 03:46:00 -0700, HK [EMAIL PROTECTED] wrote: Suppose the following situation. +-1.25.2 .. -- 1.25.2.2 -- 1.25.2.5 | ^ | |merge in 1.25 -- ... -- 1.27 -- ... -- 1.31 At 1.25 I created a branch. Later I merged the changes between 1.25 and 1.27 into the branch at 1.25.2.2 to have minor updates of the main trunk also in the branch. Now I want to merge the branch back into the trunk. I tried a straighforward merge of the tip of the branch with the tip of the trunk and get only minor conflicts. Am I just lucky with that? Normally I would expect all the changes between 1.25 and 1.27 to conflict, because they are in the branch but also already in the trunk. Or does CVS silently ignore changes which would not change anything in this case? (I am making sense?) CVS considers a conflict as a block of text where it can not determine wheather the changes from either rev are correct. Any text that is the same will not cause a conflict. So your previously merged changes will not cause a conflict. Harald. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs --Russ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: error while installing CVS 1.11.20
On 7/8/05, ravish agarwal [EMAIL PROTECTED] wrote:
I installed gcc and biasom Now, I am getting following error message:
usr/ccs/bin/ld: Warning At least one PA 2.0 object file add.o was
detected. The linked output may not run on a PA 1.x system
/usr/ccs/bin/ld: Unsatisfied sysmbols:
GSS_C_NT_HOSTBASED_SERVICE (first referenced in client.o) (data)
collect2: ld returned 1 exit status.
*** Error exit code 1
Stop
See [1] and [2] below.
I got the same error when I tried with
$ ./configure --without-gssapi
$ make
$ make install
what could be reason of the problem.
regards
Ravish
On 7/6/05, Mark D. Baushke [EMAIL PROTECTED] wrote:
ravish agarwal [EMAIL PROTECTED] writes:
I am getting following error while installing CVS-1.11.20.
On what operating system are you running?
What compiler version are you using?
# make
No suffix list.
make all-recursive
No suffix list.
Making all in lib
source='getpass.c' object='getpass.o' libtool=no \
DEPDIR=.deps depmode=hp /bin/sh ../depcomp \
cc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -g -c getpass.c
(Bundled) cc: warning 480: The -g option is available only with the
C/ANSI C
pro
duct; ignored.
(Bundled) cc: getpass.c, line 40: error 1705: Function prototypes are
an
ANSI
feature.
*** Error exit code 1
Stop.
*** Error exit code 1
Stop.
*** Error exit code 1
Please help me out. What is the possible cause of this error
regards
Note: You should consider getting a compiler that is able to deal with
ANSI C. Future releases of CVS (1.12.x) will give you many problems
otherwise as that release of CVS assumes a C89 capable standalone
compiler.
Does the following patch fix your problem?
-- Mark
ChangeLog entry:
2005-07-06 Mark D. Baushke [EMAIL PROTECTED]
* getpass.c (getpass): Add a KR style function definition.
Index: getpass.c
===
RCS file: /cvs/ccvs/lib/getpass.c,v
retrieving revision 1.1.2.4
diff -u -p -u -p -r1.1.2.4 getpass.c
--- getpass.c 2 Oct 2003 18:40:13 - 1.1.2.4
+++ getpass.c 6 Jul 2005 15:31:55 -
@@ -37,7 +37,12 @@
#endif
char *
+#if __STDC__
getpass (const char *prompt)
+#else
+getpass (prompt)
+const char *prompt;
+#endif
{
FILE *in, *out;
struct termios s, t;
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
[1]
http://www.google.com/search?sourceid=mozclientie=utf-8oe=utf-8q=%3CWarning%3E+At+least+one+PA+2.0+object+file
[2] http://support.bb4.com/archive/199905/msg00210.html
--Russ
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Re:
___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Retrieving dead files from the Attic
___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Retrieving dead files from the Attic
See page 113 of the Repository Admin: cd into the folder where you need to retrieve the file and do c:cvs -Q update -p -r 1.1 foo.jpg foo.jpg c:dir (to verify) c:cvs add -kb foo.jpg c:cvs ci -m comment foo.jpg Original Message Follows From: Dennis W. Bulgrien [EMAIL PROTECTED] To: info-cvs@gnu.org Subject: Re: Retrieving dead files from the Attic Date: Fri, 8 Jul 2005 10:00:29 -0500 Received: from lists.gnu.org ([199.232.76.165]) by mc10-f16.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 8 Jul 2005 08:16:17 -0700 Received: from localhost ([127.0.0.1] helo=lists.gnu.org)by lists.gnu.org with esmtp (Exim 4.43)id 1Dqubp-py-HHfor [EMAIL PROTECTED]; Fri, 08 Jul 2005 11:17:45 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)id 1DquY6-0008AD-FQfor info-cvs@gnu.org; Fri, 08 Jul 2005 11:13:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)id 1DquY3-000894-JDfor info-cvs@gnu.org; Fri, 08 Jul 2005 11:13:53 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org)by lists.gnu.org with esmtp (Exim 4.43) id 1DquY3-00087M-2lfor info-cvs@gnu.org; Fri, 08 Jul 2005 11:13:51 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org)by monty-python.gnu.org with esmtp (TLS-1.0:RSA_AES_128_CBC_SHA:16)(Exim 4.34) id 1DqubV-0002l7-Fsfor info-cvs@gnu.org; Fri, 08 Jul 2005 11:17:25 -0400 Received: from root by ciao.gmane.org with local (Exim 4.43)id 1DquUW-0005YW-3Ffor info-cvs@gnu.org; Fri, 08 Jul 2005 17:10:12 +0200 Received: from saturn.vcsd.com ([64.238.237.215])by main.gmane.org with esmtp (Gmexim 0.1 (Debian))id 1AlnuQ-0007hv-00for info-cvs@gnu.org; Fri, 08 Jul 2005 17:10:12 +0200 Received: from dbulgrien by saturn.vcsd.com with local (Gmexim 0.1 (Debian))id 1AlnuQ-0007hv-00for info-cvs@gnu.org; Fri, 08 Jul 2005 17:10:12 +0200 X-Message-Info: JGTYoYF78jG1CpPzNfJmeEfSZiYehpSFfnKOeq8XphM= X-Injected-Via-Gmane: http://gmane.org/ Lines: 2 References: [EMAIL PROTECTED][EMAIL PROTECTED] X-Complaints-To: [EMAIL PROTECTED] X-Gmane-NNTP-Posting-Host: saturn.vcsd.com X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-BeenThere: info-cvs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Announcements and discussions for the CVS version control systeminfo-cvs.gnu.org List-Unsubscribe: http://lists.gnu.org/mailman/listinfo/info-cvs,mailto:[EMAIL PROTECTED] List-Archive: http://lists.gnu.org/pipermail/info-cvs List-Post: mailto:info-cvs@gnu.org List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://lists.gnu.org/mailman/listinfo/info-cvs,mailto:[EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] Return-Path: [EMAIL PROTECTED] X-OriginalArrivalTime: 08 Jul 2005 15:16:18.0034 (UTC) FILETIME=[FD41BD20:01C583CF] ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
how do I undo local changes
Hi, I checkedout a file from a repository for first time. i modified it. but i do not want my changes. now i want to do a cvs update to get others changes. but i will be asked for merging. i want to avoid that step. even i want to prevent automatic merging so i need to undo the changes. in systems like accurev, there is a purge command to discard the local changes. but in CVS I only find the cvs admin -o command to revert to older versions. But how can i simply undo the changes locally, without concerning about version? meena __ Discover Yahoo! Use Yahoo! to plan a weekend, have fun online and more. Check it out! http://discover.yahoo.com/ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: how do I undo local changes
You can do : 1. cvs up -C file You will see a msg similar to (Locally modified license.props moved to .#license.props.1.1) It will pull the latest from CVS tree and save the current changes in a .# file 2. rm file and pull again - cvs co/up Regards, Rahul Bhargava CTO, WANdisco http://www.wandisco.com/cvs ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
add new files to branch
Hi, I like to know how to add a file to an existing branch. Following is my env: o I have created branch tag release-1-patch from the main trunk base on tag release-1. o Then I have a file A checked in main trunk as v1.5 and the file is tagged as release-2 How do I add file A to the branch release-1-patch? I tried to use cvs rtag -b -r release-2 release-1-patch A It did not work. I guess this is not the right command. I was getting cvs rtag: cannot find module `browser.js' - ignored message. Can anyone help me with this? Thanks, Mei ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: how do I undo local changes
$ cvs -H up Usage: cvs.exe update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev] -A Reset any sticky tags/date/kopts. -P Prune empty directories. -C Overwrite locally modified files with clean repository copies. ( . . . ) -W spec Wrappers specification line. Looks like you want -C -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MEENA SELVAM Sent: Friday, July 08, 2005 6:27 PM To: info-cvs@gnu.org Subject: how do I undo local changes Hi, I checkedout a file from a repository for first time. i modified it. but i do not want my changes. now i want to do a cvs update to get others changes. but i will be asked for merging. i want to avoid that step. even i want to prevent automatic merging so i need to undo the changes. in systems like accurev, there is a purge command to discard the local changes. but in CVS I only find the cvs admin -o command to revert to older versions. But how can i simply undo the changes locally, without concerning about version? meena ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: merging branch to HEAD when branch contains partly trunk changes already
HK [EMAIL PROTECTED] wrote: Suppose the following situation. +-1.25.2 .. -- 1.25.2.2 -- 1.25.2.5 | ^ | |merge in 1.25 -- ... -- 1.27 -- ... -- 1.31 At 1.25 I created a branch. Later I merged the changes between 1.25 and 1.27 into the branch at 1.25.2.2 to have minor updates of the main trunk also in the branch. Now I want to merge the branch back into the trunk. If I remember correctly, the correct merge would be -j 1.27 -j 1.25.2.5 (or the equivalent with instead of hard revision numbers). I tried a straighforward merge of the tip of the branch with the tip of the trunk and get only minor conflicts. Yeah, sometimes that works. Other times I get bogus conflicts with the same text on both sides of the conflict. I just clean those up by hand. -- pa at panix dot com ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: add new files to branch
Mei-Xing Zhao [EMAIL PROTECTED] wrote: [ ... ] cvs rtag -b -r release-2 release-1-patch A Just use cvs tag instead of cvs rtag (and do it from a trunk sandbox where the A file is present). -- pa at panix dot com ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: add new files to branch
Pierre Asselin wrote: Mei-Xing Zhao [EMAIL PROTECTED] wrote: [ ... ] cvs rtag -b -r release-2 release-1-patch A Just use cvs tag instead of cvs rtag (and do it from a trunk sandbox where the A file is present). Thanks. cvs tag works. But after running this cvs tag command, do I do a cvs add to add this file to the branch? I am not sure if I run the cvs add command, will it add the file to the main trunk or to the branch? Thanks, Mei -- ~~ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ~~ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: add new files to branch
Thanks. cvs tag works. But after running this cvs tag command, do I do a cvs add to add this file the the branch? I am not sure if I run the cvs add command, will it add the file to the main trunk or in the branch? Thanks, Mei Pierre Asselin wrote: Mei-Xing Zhao [EMAIL PROTECTED] wrote: [ ... ] cvs rtag -b -r release-2 release-1-patch A Just use cvs tag instead of cvs rtag (and do it from a trunk sandbox where the A file is present). -- ~~ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ~~ ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: cvs error: received broken pipe signal
Thanks a lot for your reminding.
- host OS information for server: Redhat 9
- host OS information for client: Window 2000
- server version of cvs: cvs 1.11.6
- client version of cvs: wincvs 1.3
- nature of commitinfo, verifymsg, loginfo scripts being used (if any):
in the attachment
additional information: the error comes up after the commit is succeeded
and version number is changed.
and error does not always comes up every
time. but sometimes alternately or every three time.
Regards,
Winnie
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark D.
Baushke
Sent: Thursday, July 07, 2005 2:46 PM
To: Yu He
Cc: info-cvs@gnu.org; Peixiao Guo
Subject: Re: cvs error: received broken pipe signal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yu He [EMAIL PROTECTED] writes:
Hi all:
After commit,always receive the following error message,
cvs [server aborted]: received broken pipe signal
What's the reason?
Thanks a lot in advance!
You have provided insufficient information as to your configuration.
At a guess, you might not be reading all of the stdin being provided to
your cvs trigger scripts.
For better guesses, information like:
- host OS information for server
- host OS information for client
- server version of cvs
- client version of cvs
- nature of commitinfo, verifymsg, loginfo scripts being used (if any)
is desirable.
-- Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCzM+U3x41pRYZE/gRAuJCAKCqSqL/4wjCV3QoR45oAIuDgMyVsgCfQ/Wi
jXrtVnZZQE1vvlDu/87VN54=
=tfWn
-END PGP SIGNATURE-
#!/usr/local/ActiveTcl/bin/tclsh
lappend auto_path /usr/local/ActiveTcl/lib;
# commitCheck.tcl
#
set user [lindex $argv 0];
set repository [lindex $argv 1];
set fileList [lrange $argv 2 end];
puts Attempting commit:\n${argv}\nUser:$user Repos:$repository
Files:\n$fileList;
set checkoutAll 0;
switch $user {
heyu -
ldong {
puts Permission always granted to the mighty CVSAdmin!;
#Source cvsDb.tcl for history recording
#source [file join $env(CVSROOT) CVSROOT cvsDb.tcl];
puts Recording history;
#appendHist [list action COMMIT username $user repository $repository
comment Commit: $fileList] Y;
exit 0;
}
default {
puts Verifying permissions...;
}
}
if { [catch {
#Temporary controls until we can import actual scripts:
switch -regexp $repository {
^/cvsroot/database/oracle/gtss2 -
^/cvsroot/database/oracle/gtss2/* {
puts Commits to this repository currently disabled. Contact
administrator (4-2062) for more info.
exit 1;
}
}
switch -regexp $repository {
^/usr/local/cvsroot/project/dev {
switch $user {
id {
puts Permission Granted- Development Area;
puts Have a nice day.
}
default {
puts You don't have permission to commit to Development.;
exit 1;
}
}
}
^/usr/local/cvsroot/project/qa {
switch $user {
id -
id2 -
id3 {
puts Permission Granted- qa Area;
puts Have a nice day.
}
default {
puts You don't have permission to commit to qa.;
exit 1;
}
}
}
default {
switch $user {
default {
puts You don't have permission to commit to this project
(${repository}). Contact administrator.
exit 1;
}
}
}
}
} ret] } {
#Error!
puts CVS Server error. Email me with this info:$::errorInfo;
exit 1;
} else {
#Success!
#if {$checkoutAll == 1} {
# exec /cvsroot/CVSROOT/checkoutAll.tcl ;
#}
exit 0;
}
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs error: received broken pipe signal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yu He [EMAIL PROTECTED] writes: Hi all: After commit,always receive the following error message, cvs [server aborted]: received broken pipe signal What's the reason? Thanks a lot in advance! You have provided insufficient information as to your configuration. At a guess, you might not be reading all of the stdin being provided to your cvs trigger scripts. For better guesses, information like: - host OS information for server - host OS information for client - server version of cvs - client version of cvs - nature of commitinfo, verifymsg, loginfo scripts being used (if any) is desirable. -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFCzM+U3x41pRYZE/gRAuJCAKCqSqL/4wjCV3QoR45oAIuDgMyVsgCfQ/Wi jXrtVnZZQE1vvlDu/87VN54= =tfWn -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs error: received broken pipe signal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yu He [EMAIL PROTECTED] writes: Thanks a lot for your reminding. - host OS information for server: Redhat 9 - host OS information for client: Window 2000 - server version of cvs: cvs 1.11.6 - client version of cvs: wincvs 1.3 - nature of commitinfo, verifymsg, loginfo scripts being used (if any): in the attachment How is the attachment used? I am guessing it is only used from CVSROOT/commitinfo right? Is there anything in CVSROOT/loginfo ? additional information: the error comes up after the commit is succeeded and version number is changed. and error does not always comes up every time. but sometimes alternately or every three time. Ahh, this does not agree with your first problem statement where you said it always happened... Are you able to find anything in common with the times when it fails? -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFCzNdK3x41pRYZE/gRAltnAJ9iOe0I8ZJT9bC6pGq+0TNhwFhkXQCfTXyu VFeqwMKzQNKl4zP13Bau2B8= =VNoE -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
CVS ( Status of lock files in the repository)
Hi all, I would like have ascriptwhich will show me all the user names who have locked a particular file along with the filename , the timestamp and path of that file locked. Thanks in Advance. regards surya` Free antispam, antivirus and 1GB to save all your messages Only in Yahoo! Mail: http://in.mail.yahoo.com___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: cvs error: received broken pipe signal
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 These two lines need to dispose of stdin: Original: project1 (chgrp -Rf project1 /usr/local/cvsroot/project1) project2 (chgrp -Rf project2 /usr/local/cvsroot/project2) Revised: project1 (chgrp -Rf project1 /usr/local/cvsroot/project1; cat) /dev/null project2 (chgrp -Rf project2 /usr/local/cvsroot/project2; cat) /dev/null Enjoy! -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFCzN/e3x41pRYZE/gRAmr0AJ9s5/DMr7yEYugqRlp61oxQN8+5KACg0T9J 0064dezA7A87GjCC6NX3BV0= =gcll -END PGP SIGNATURE- ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
How can I administratively freeze a branch?
Greetings. I have a project which was branched some time ago and now the branch has been merged back to HEAD. No further changes must be made to the old "DEV2" branch, it is officially dead. Is there a way I can prevent developers from mistakenly committing to that branch (appart from deleting it)? Raúl Pedroche Novillo BPM TOM This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: How can I administratively freeze a branch?
Original Message From: [EMAIL PROTECTED] Sent: 07 July 2005 11:09 Greetings. I have a project which was branched some time ago and now the branch has been merged back to HEAD. No further changes must be made to the old DEV2 branch, it is officially dead. Is there a way I can prevent developers from mistakenly committing to that branch (appart from deleting it)? Why not just cvs rm all the files from it, so they no longer exist at the head of the branch? People would have to accidentally checkout old revisions before they could accidentally commit to it; that's pretty improbable I think. cheers, DaveK -- Can't think of a witty .sigline today ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
RE: How can I administratively freeze a branch?
Why not just cvs rm all the files from it, so they no longer exist at the head of the branch? People would have to accidentally checkout old revisions before they could accidentally commit to it; that's pretty improbable I think. The problem is that files from old branch still exist in HEAD (in fact, what we did was to commit the branched files to HEAD). This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Smart CVS
Guys, I posted on here recently with regards to using SSH and SmartCvs, I have (i think) made a little head way in this but when trying to get the modules to read from smartCVS checkout project option i am getting the following: An i/o error occured, details: Unknown Compression method I have no idea why I am getting this! I can get the cvs now to check out files on an older version of CVS 1.2 or something like that using putty and plink, but would rather be using smartCVS Thanks again guys p.s. would have posted this on the smartCVS form but my company firewall blocks it! S. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
pserver user id's
Hello. I have a repository configured and working with pserver. I want to restrict user's permissions on subdirectories in the repository. I don't want user A to see user B's projects and vice versa. In my $CVSROOT/CVSROOT/passwd file, I have something like: divap:YBGW948yOKKSA:cvsadm divap is a user on the system. The user id under which CVS runs is 'cvsadm'. In $CVSROOT, I have a subdirectory that looks like this: drwxrws--x 3 divapdhdev 512 Jul 06 17:16 divap/ This all works fine except that, the pserver user divap can read ALL the projects in all the other subdirectories because on the server, he is actually running as cvsadm (see the passwd file entry above). If I change the passwd file to look like this: divap:YBGW948yOKKSA:divap I get an error when I try to run a 'checkout' on a project in the divap directory that says: cvs [checkout aborted]: unrecognized auth response from cae1axp1: setgroups: Not owner I don't want everyone to run as the administrator account (cvsadm) and the docs seem to indicate that they can run as themselves (their shell accounts) but I get the above error. Any help would be GREATLY appreciated. Andrew ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Possible Spam: Re: CVS and SSH V2
Russ Sherk wrote: I think you can put the port into CVS_RSH. Here is mine on winXP using plink: Z:\echo %CVS_RSH% d:\Tools\plink.exe -ssh -pw xx Z:\echo %CVSROOT% :ext:[EMAIL PROTECTED]:/var/cvs --- Does this not work on linux? No. It's an implementation difference. The src/run.c piped_child function accepts an argv array as an argument on Linux and passes that argv directly to execvp. Since argv[0] holds the contents of $CVS_RSH, the system looks for a process names $CVS_RSH, spaces, arguments, and all. The windows-NT/run.c pipted_child function turns it's argv into a single string with space-delimited arguments which it then passes back to the Windows shell for parsing, so the contents of $CVS_RSH gets resplit on spaces. Regards, Derek ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: pserver user id's
foomonkey wrote: Hello. I have a repository configured and working with pserver. I want to restrict user's permissions on subdirectories in the repository. I don't want user A to see user B's projects and vice versa. In my $CVSROOT/CVSROOT/passwd file, I have something like: divap:YBGW948yOKKSA:cvsadm divap is a user on the system. The user id under which CVS runs is 'cvsadm'. In $CVSROOT, I have a subdirectory that looks like this: drwxrws--x 3 divapdhdev 512 Jul 06 17:16 divap/ This all works fine except that, the pserver user divap can read ALL the projects in all the other subdirectories because on the server, he is actually running as cvsadm (see the passwd file entry above). If I change the passwd file to look like this: divap:YBGW948yOKKSA:divap I get an error when I try to run a 'checkout' on a project in the divap directory that says: cvs [checkout aborted]: unrecognized auth response from cae1axp1: setgroups: Not owner I don't want everyone to run as the administrator account (cvsadm) and the docs seem to indicate that they can run as themselves (their shell accounts) but I get the above error. Any help would be GREATLY appreciated. Andrew Obviously divap does not have write access to the repository structure. In my pserver setup, the repository directories files are owned cvs:cvs, and my users run username:password:cvs. My admin users DON'T have the :cvs part at the end, but instead are members of the linux group cvsadmin, who are granted access automatically (I'm not sure if it's by pserver or by CVS itself). Note: I am told it is ill-advised to use admin accounts for regular use. To get back to the original requirement (restricting access on a per-project basis), I believe that CVS/pserver does not conveniently suppport the granularity of access you require. julian. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Problem with admin privileges
Todd Denniston wrote: CLIP The only reason I am using pserver is that it allows my users to have CVAS controlled access to the respositories without giving them dierct write access to them. If you can suggest another way of doing that, I'd be glad to use it. As Far As I Know, you are correct, but at best you are only protecting them from a fat fingering while in the repository and do not have malicious intent. The first rule of the repository for users should be that if you are not the admin you never execute any non cvs command against it. The first rule of the repository for admins is back it up appropriately, as hardware/network/software faults can damage the work. With these two rules, I believe you should have at least as good a set of protection as pserver would get you, because you don't have developers with malicious intent and who follow the rules :} Pretty much true: if it isn't, I've got worse problems :) As long as the developers are using only :ext: cvs commands against the repository, I believe you should still be able to meet your FAA requirements: FAA-regulated environment, and my CVS respository must be secure, in that nobody can impair the lifecycle data, and all accesses must be documented and controlled, i.e.e all accesses must be via the cvs server. but would be counting on the backups to prevent you from loosing any lifecycle data, which is what you would be back to if they were looking at you with strictness when there is a known hole in pserver. In final, Yes using pserver will probably make it easier to show up front that everything meets the requirements, but in the past it has been the bain of security with cvs. I belive you are in the middle ground between the restricted execution of CVS Mark D. Baushke told you about, and the trusting developers ground of :ext: on a system they can execute more than cvs on. I further belive that you are only mildly protected from what you worry about, using your method. Where as one of the restricted execution of CVS would probably allow much more of the FAA level security lock down and logging. if you want further reading I suggest searching the list's archive for Greg Woods AND pserver OR Greg Woods AND authentication AND|OR authorization. I think the horse is dead, so I'll stop beating. SNIP Well I think the horse has completed the track, and I think we've won the race, inasmuch as I have fat-finger protection, which is all I need: I am backing up, after all, as you suggest (and as insisted upon by our friends at the FAA, in fact), and the backup includes logs, so I'm meeting the obligation. There is rarely a perfect solution for special needs situations such as this, but I think I've got the closest practical solution, and as long as my local FAA officer is happy, then so am I. Todd, you obviously spent plenty of time thinking and writing. Thank you very much for your opinions, insight and help. julian. ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: pserver user id's
I believe my problem lies in that my inetd.conf specifies to run cvspserver under the cvsadm user account. When I have my $CVSROOT/CVSROOT/passwd file configured like, username:password:cvsadm, everything works great. With the exception that user A can see user B's projects and vice versa. This is because cvsadm owns the repository directory structure. The mode for it is 771. When I change the passwd file to username:password:username, this does not work. I get the previously mentioned error. My belief is that pserver is running as cvsadm but wants to run in the context of the user specified in passwd. I don't know that this is possible unless pserver is running as root. In a sandbox environment, I have changed pserver to run as root (in inetd.conf) and it works correctly. I may be missing something but that's the way things appear to me. Is there any danger in having pserver run as root? inetd.conf contains many other services running as root. I realize that ANY service running as root or otherwise introduces certain vulnerabilities. Thanks for any clarification anyone can provide. Andrew ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: pserver user id's
foomonkey writes: If I change the passwd file to look like this: divap:YBGW948yOKKSA:divap Note that you can just omit the third field entirely in that case. I get an error when I try to run a 'checkout' on a project in the divap directory that says: cvs [checkout aborted]: unrecognized auth response from cae1axp1: setgroups: Not owner Your [x]inetd must run cvs as root to be able to switch to another user. -Larry Jones I'm not a vegetarian! I'm a dessertarian. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
Re: pserver user id's
foomonkey writes: I may be missing something but that's the way things appear to me. Is there any danger in having pserver run as root? inetd.conf contains many other services running as root. I realize that ANY service running as root or otherwise introduces certain vulnerabilities. You've got it. Pserver runs as root just long enough to authenticate the user and then it switches to the actual user to run everything else so there's very little risk. -Larry Jones The game's called on account of sudden death. -- Calvin ___ Info-cvs mailing list Info-cvs@gnu.org http://lists.gnu.org/mailman/listinfo/info-cvs
