Have you ever heard about commitcheck binary ?
Hi, there. I have a question about some binary i.e. "commitcheck" which isn't included in CVS source. A senior of mine has installed CVS, and added some binary "commitcheck" to patch a bug. But he's not, here. So I cannot ask him why he added the file, "commitcheck". Now, I've upgraded to CVS 1.10, but I have no idea about deleting the file "commitcheck". I'm not sure... it'll work properly, without "commitcheck". Do you know why the "commitcheck" binary was/is needed, and can be deleted or not ? "commitcheck" is included in the $CVSROOT/commitinfo file to run as "DEFAULT". I mean the commitinfo file has the line of "DEFAULT /usera/cad/gnu/bin/commitcheck". Regards... nana.
Recursiveness not achievable in CVSClient
Hi Im working with the development of CVSClient in java on Linux. My query is how to do recursive add or import of directories That is when you do above operations, How to create subdirectories to module in the repository. if i import a directory, only one directory gets imported to repository.Its subdirectory are not getting imported.So how to create subdirectory in the module in repository. Please help me Thanks and Regards Praveen.C Get free email and a permanent address at http://www.netaddress.com/?N=1
Re: Recursiveness not achievable in CVSClient
This should not happen. When you do the import it should import all the files and dirs below that directory. Try checking a reference to see what the options are for the import command. I can't recall off the top of my head, but there may be an -r option for recursive. Also be sure you have the module name listed in the /CVSROOT/modules file before doing the import. Michael Amorose Author FireUtils for Macintosh Author Sound Core for Macintosh FireWire Watch Webmaster http://www.fireutils.com http://www.soundcore.com http://www.michael-amorose.com/firewire - At 2:47 PM -0700 7/31/00, Praveen.C wrote: Hi Im working with the development of CVSClient in java on Linux. My query is how to do recursive add or import of directories That is when you do above operations, How to create subdirectories to module in the repository. if i import a directory, only one directory gets imported to repository.Its subdirectory are not getting imported.So how to create subdirectory in the module in repository. Please help me Thanks and Regards Praveen.C Get free email and a permanent address at http://www.netaddress.com/?N=1
Re: latest patches posted to SourceForge RCVS
I've cc'd the mailing list 'cos part of my response may be important to others. The patches I've posted are incremental meaning that you'll have to apply each of the preceding ones before the one you really need. Of course, this means that you may get more than you wanted. You might want to manually apply the patches (probably in an ad hoc manner) so that you get only the things you want. If you've been following the mailing list, I've come to the decision that this patch is very BAD. Conceivably, many client users may wind up with the same client username. This could be disastrous if this patch were used in such an environment. I plan to remove this patch once I have some time. A kludge to this problem may be to make the client hostname as part of the username that's logged by CVS. I haven't thought of the consequences of such a patch though (it may be more disastrous than the existing patch). The real solution would be to have CVS maintain its own user identities and have pluggable authentication support. From what I think I know, nserver-cvs may be headed in this direction. I haven't looked much into this yet, though. I've enclosed our client.c, but it's probably dependent on other patches I've made. However, I have warned you of the consequences of using this patch. Noel Enc (See attached file: client.c) [EMAIL PROTECTED] on 2000.07.31 10:11:59 To: [EMAIL PROTECTED] cc: Subject: Re: latest patches posted to SourceForge RCVS Hi Noel, On Wed, Jul 19 2000, Norbert Gruener wrote: On Wed, Jul 19 2000, Norbert Gruener wrote: I am especially interested in your patches "logging of client username instead of server username". Were can I get this patch ? finally I have found it. Thank you very much for your help. I have installed the above mentioned patch, but it is not working for me. The problem is that I am not sure, if I have patched the client.c file properly. Would it be possible for you to supply me with a patched version of the "client.c" source file ? Thank you very much in advance. Cheers, Norbert -- +---+ | Norbert E. Gruener http://www.MPA-Garching.MPG.DE/~nog/ | | Max-Planck-Institut [EMAIL PROTECTED]| | fuer Astrophysik PGP encrypted mail preferred | | PGPprint(RSA): 66 64 C0 D0 6F 1A 16 02 C2 C6 37 83 3A 5F 88 9B | | PGPprint(DH): EBBF 02ED 1B91 39C3 5FB9 4D2F 9478 E224 334C 34CD | | PGPprint(DSS): A3F0 BDFA EAC0 128D A6C5 B11D 6EEC 0A88 47CD A77D | +---+ client.c
file permission problem
hi, i posted this question one week ago. the problem: i add a file to a existing project. 1. ´cvs add README´ (this is only a example :-)) ok i got the messages "file added - make commit" 2. ok i commit. ´cvs co README´ . cvs create the file, but with the permissions - (correct: nothing for anyone) after creation cvs is not able to write into this file - and the reult is "permission denied" without the ability to add new files to the repository, cvs isn´t usable for us. you understand my devil english? bernd email: [EMAIL PROTECTED] and [EMAIL PROTECTED]
Re: Have you ever heard about commitcheck binary ?
[EMAIL PROTECTED] wrote: Hi, there. I have a question about some binary i.e. "commitcheck" which isn't included in CVS source. A senior of mine has installed CVS, and added some binary "commitcheck" to patch a bug. But he's not, here. So I cannot ask him why he added the file, "commitcheck". Now, I've upgraded to CVS 1.10, but I have no idea about deleting the file "commitcheck". I'm not sure... it'll work properly, without "commitcheck". Do you know why the "commitcheck" binary was/is needed, and can be deleted or not ? "commitcheck" is included in the $CVSROOT/commitinfo file to run as "DEFAULT". I mean the commitinfo file has the line of "DEFAULT /usera/cad/gnu/bin/commitcheck". I doubt that it would work without that executable. It won't with 1.10.8. You either have to keep the commitcheck file or remove the lines that refer to it in the commitinfo file. I would recommend that you keep the binary unless it is preventing checkins and you can't determine why. -- Stephen Rasku E-mail: [EMAIL PROTECTED] Senior Software EngineerWeb:http://www.tgivan.com/ TGI Technologieshttp://www.pop-star.net/
RE: Checking branch for commit
From: Laird Nelson [mailto:[EMAIL PROTECTED]] Marc Poinot wrote: On the server side ? Yes; even in a pserver or rsh context. If your script is being called [] semantics I can't recall at the moment). Here's an example: /ScopeTypes.java/1.1/Wed Jul 12 22:21:05 2000// Perhaps more pertinent to your question, if the file is on a branch named tagname, the line in ./CVS/Entries will look like: /ScopeTypes.java/1.1/Wed Jul 12 22:21:05 2000//Ttagname Cheers, Jerry
Re: file permission problem
[EMAIL PROTECTED] on 2000.07.31 11:19:09 i add a file to a existing project. 1. ´cvs add README´ (this is only a example :-)) ok i got the messages "file added - make commit" 2. ok i commit. ´cvs co README´ . cvs create the file, but with the permissions - (correct: nothing for anyone) after creation cvs is not able to write into this file - and the reult is "permission denied" I'm assuming you meant 'cvs ci README'. This (ie the permissions) are NOT correct. How do you expect to see what's inside the file if you don't have read permissions? How do you expect to be able to write to the file if you don't have write permissions? Furthermore, the permissions for the archive file will probably be incorrect as well, meaning that you won't be able to checkout the file. you understand my devil english? Perhaps not. Noel This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Co. Incorporated, its subsidiaries and affiliates.
RE: Checking branch for commit
On Friday, July 28, 2000 9:45 PM, Marc Poinot [SMTP:[EMAIL PROTECTED]] wrote: I have to check the commited branch, but the commitinfo actually gives nothing else but the file name. The loginfo has more infos, but it cannot make the commit fail. Thus, I have modified the src/commit.c file with these three lines: Sorry if this is late, but there was a patch posted at one time to pass version information to commitinfo. This would allow you to determine that the commit was occuring on the branch. I can't find or remember the patch :(! *** Chris CameronOpen Telecommunications NZ Ltd Senior Solution Architect [EMAIL PROTECTED] P.O.Box 10-388 +64 4 495 8403 (DDI) The Terrace fax: +64 4 495 8419 Wellington cell: +64 21 650 680New Zealand Life, don't talk to me about life (Marvin - HHGTTG)
WinCVS Macros
I realize that this is a CVS mailing list and not a WinCVS list, but I have a WinCVS question that I am going to ask anyway. Does anyone know how to create macros to run under WinCVS? It's my understanding that you can create macros for some functions, but I can't find any documentation on how to do this. Have I misunderstood something? Thanks in advance. Sheldon Samuels Panja V: 800-952-6995/972-644-3048 F: 972-644-1291 e-mail: [EMAIL PROTECTED] "Enjoy Change! Savor the Adventure and the Taste of the New Cheese!" from "Who Moved the Cheese" by Spencer Johnson
Re: file permission problem
[EMAIL PROTECTED] writes: i add a file to a existing project. 1. ´cvs add README´ (this is only a example :-)) ok i got the messages "file added - make commit" 2. ok i commit. ´cvs co README´ . cvs create the file, but with the permissions - (correct: nothing for anyone) after creation cvs is not able to write into this file - and the reult is "permission denied" In your previous message, you said you were using the "file_perm-patch"; what is this and where did you get it? It may well be the source of your problems. What are the permissions on the file before you commit it? What are the permissions on the file in the repository? It sure looks like *someone's* umask is set to 777 -- perhaps the cvs server's? You might want to try the current version of CVS (1.10.8) from www.cvshome.org without any patches. If that works, then you can start applying patches if you want -- when it breaks, you'll know what to blame. -Larry Jones It's hard to be religious when certain people are never incinerated by bolts of lightning. -- Calvin
cvs commit ../include/foo.h
I used to be able to commit like this: cvs commit -m"foo changes" foo.c ../include/foo.h After upgrading to CVS 1.10.8, I get this error: protocol error: '..' has too many .. If I pass the full pathname of the file (e.g., "$HOME/cvs/foo/include/foo.h"), I get absolute pathname '/home/hal/cvs/foo/include' illegal for server This worked in 1.10.1. Is this a bug, or was it incorporated to fix some other condition? If so, what was the reason? Thanks! :)hal mahaffey
Re: cvs commit ../include/foo.h
Hello! I used to be able to commit like this: cvs commit -m"foo changes" foo.c ../include/foo.h After upgrading to CVS 1.10.8, I get this error: protocol error: '..' has too many .. This worked in 1.10.1. Is this a bug, or was it incorporated to fix some other condition? If so, what was the reason? I believe this was a quick fix to close a security hole. Instead of checking that the target directory is still under the allowed root, CVS just forbids using ".." for some (not fot all) commands. Regards, Pavel Roskin
Re: cvs commit ../include/foo.h
[EMAIL PROTECTED] writes: After upgrading to CVS 1.10.8, I get this error: protocol error: '..' has too many .. I think this is a bug -- the client is supposed to tell the server how many levels of .. it expects to send and the server compensates, but when the code was rearranged to support multiple repositories the code to send the information was moved so that it happens too late in the process. If I pass the full pathname of the file (e.g., "$HOME/cvs/foo/include/foo.h"), I get absolute pathname '/home/hal/cvs/foo/include' illegal for server This is intentional. -Larry Jones I obey the letter of the law, if not the spirit. -- Calvin
extended watch
Hi there I have for a long time wanted to get more info in my "cvs watch add" mails. The notification that others have made a commit is too little for me. I want the log-message in my mail. I have tried to make the log.pl contrib-script work but it seems that I either don't pull the right trigger or do a bad configuration. I did alter my $CVSROOT/CVSROOT/loginfo with lines user1 /usr/lib/cvs/contrib/log %s -f CVSROOT/commitlog -m user1email user2 /usr/lib/cvs/contrib/log %s -f CVSROOT/commitlog -m user2email ... however I don't get any email's from this - only from the "cvs watch add FILENAME" commands. Is the intention that the log.pl script is trigged by "cvs watch add" or are the two mechanisms disconnected. Well I don't get any email's... Any clues are valuable too me ;-)) -- Peter Toft, Ph.D. [[EMAIL PROTECTED]] http://www.sslug.dk/~pto "You don't win a battle by asking, `Will we win?' You win it by doing your best to win" - Richard M Stallman Visit http://petition.eurolinux.org ---
CVS-Tree
Hi, Is there any tool/script around that would display the version tree in a format as follows : 1.1- Main | 1.2 | 1.3 - Release | 1.4 | 1.5 - Release 2.0 / \ / \ / \ (1.5.2) (1.5.4) - Release 2.0-Patch1 / \ 1.5.2.11.5.4.1 | | 1.5.2.21.5.4.2 | | (etc) (...) | 1.5.4.37 - Release 2.0-Patch1.1 / / (1.5.4.37.2) --- (this is also a branch number) / / 1.5.4.37.2.1 | 1.5.4.37.2.2 | 1.5.4.37.2.3 Thanks Rohit
