CVS commit problem

___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs

commit problem........

hi all, i'm using CVS for the first time. i'm using it as root on redhat 9.everything works fine, but when i try to commit changes i get a reply that root is not allowed to commitwhy is this so? another thingas a remedy to this, i tried to import a copy of the same project as a

Re: Commit Problem

Bill Smith writes: MIME-Version: 1.0 Content-Type: multipart/alternative; Please do not send MIME and/or HTML encrypted messages to the list. Plain text only, PLEASE! Additionally, I tried doing a cvs commit with cygwin cvs, I get /CVSROOTccess /var/cvs No such file or directory You

Re: Commit Problem

- Original Message - From: Mike Ayers [EMAIL PROTECTED] To: Bill Smith [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, December 05, 2002 3:51 PM Subject: Re: Commit Problem Please send only plain text messages to technical mailing lists. Thanks. New install. My mistake. I

Re: Commit Problem

Please send only plain text messages to technical mailing lists. Thanks. Bill Smith wrote: Below is a message I posted to the tortoise cvs mailing list. Additionally, I tried doing a cvs commit with cygwin cvs, I get /CVSROOTccess /var/cvs No such file or directory This is not a

Re: Commit Problem

Bill Smith wrote: - Original Message - From: Mike Ayers [EMAIL PROTECTED] Actually, yes it is a cut-and-paste, here it is again including the command line Here s the entire trace with the -t option $ cvs -t commit cvs commit: notice: main loop with CVSROOT=:ext:[EMAIL

commit problem

Hi CVS person, I have tried to commit a collection on files using the command: cvs commit -r2.0 and I get the error message: cvs commit: in directory fds: cvs [commit aborted]: there is no version here; do 'cvs checkout' first I have tried doing this after checking out the files. It seems to

Re: commit problem

In [EMAIL PROTECTED] Laurence Park [EMAIL PROTECTED] writes: I have tried to commit a collection on files using the command: cvs commit -r2.0 1) You can't use 2.0, it has to start at 2.1 . 2) Don't do that. Learn to use tags. and I get the error message: cvs commit: in directory fds: cvs

Re: CVS Commit Problem

Bob Goan writes: I'm trying to use CVS in my Sun Forte for Java environment, which is a PC running Windows 2000, networked to a LINUX Box, and I use SAMBA to mount the LINUX directories locally to my PC, including the CVSROOT directory. Using a network file system like SAMBA to access your

Re: cvs commit problem

It is a permission problem on the server side, though it isn't completely clear without more investigation what it is. If you don't mind a little nitty-gritty, you can figure out exactly what is happening by tracing your cvs pserver. What I do is open a second port on the server as follows (you

Re: cvs commit problem

Joss, Werner 3936 S-RD-MP2 writes: cannot create_adm_p /tmp/cvs-serv13750/CVI/MDAQ Permission denied cvs commit: saving log message in /tmp/cvsiIyJXt That frequently means that you're missing the CVSROOT/Emptydir directory. Try running cvs init as a user who's allowed to create files in

CVS Commit Problem

I'm trying to use CVS in my Sun Forte for Java environment, which is a PC running Windows 2000, networked to a LINUX Box, and I use SAMBA to mount the LINUX directories locally to my PC, including the CVSROOT directory. I have a cvs executable installed on my PC. I am using the built-in GUI

cvs commit problem

Hi all, I'm currently trying to get my cvs pserver running on redhat 7.2. I've managed to get it working partly by setting up xinetd as described in the faq-o-matic. so far, I can connect to cvs, also checkout modules, but if I try to commit changes, I get the following error: cannot

Commit Problem

I'm using wincvs , and y checkout my working copy of my project and get it ... *CVS exited normally with code 0* cvs checkout -P -r vuelto_multimoneda POS_Z After that, i modified a file, andwheni try to make a commit , get : cvs commit -m "Commit del archivo bat, federico-."

Re: Commit Problem

You get the error because you are trying to commit to the tag 'vuelto_multimoneda POS_Z'. If you need to modify seperately from the main trunk, you need to specify the tag as a branch cvs tag -b 'My_Tag'. If you trying to modify on the main trunk, don't run the second command cvs checkout -P -r

CVS Commit Problem

To whom it may concern, I seem to be having troubles committing files to the repository, whenever I commit a file, cvs complains that it cannot be done under the user root when infact I am logged an as a different user. I am using Tortoise CVS Client for Windows and a RedHat Linux 7.1 pserver.

Re: CVS Commit Problem

Todd Rosner - Syoni Communications Inc. writes: I seem to be having troubles committing files to the repository, whenever I commit a file, cvs complains that it cannot be done under the user root when infact I am logged an as a different user. I am using Tortoise CVS Client for Windows and

Re: CVS Commit Problem

Todd Rosner - Syoni Communications Inc. [EMAIL PROTECTED] on 06/28/2001 02:57:04 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Steven Rosenstein/FTCI) Subject: CVS Commit Problem To whom it may concern, I seem to be having troubles committing files

commit problem

Dear Sir, I am using WinCvs1.2 When I try to commit a file after modification, error occur with message like: cvs server: sticky tag `v1-0-0-0' for file `telcom/telcom_tags_pool.dat' is not a branch cvs [server aborted]: correct above errors first! *CVS exited normally with code 1*

Re: commit problem

[EMAIL PROTECTED] wrote: cvs server: sticky tag `v1-0-0-0' for file `telcom/telcom_tags_pool.dat' is not a branch cvs [server aborted]: correct above errors first! *CVS exited normally with code 1* Read the section of the manual on sticky tags, branches, and branching and merging.

Commit problem

Hi, When I do a commit on a particular file, I get this error response from my CVS server: -- snip -- Checking in system.class.inc; c:\cvs/Assurances/Classes/system.class.inc,v -- system.class.inc cvs [commit aborted]: end of file from server (consult above messages if any) -- snip -- This

Re: Commit problem

Alain Fontaine writes: Checking in system.class.inc; c:\cvs/Assurances/Classes/system.class.inc,v -- system.class.inc cvs [commit aborted]: end of file from server (consult above messages if any) Sounds like the server's crashing. I suggest trying the same thing on the server machine

cvs edit/commit problem

I'm experiencing a problem with cvs edit and commit. First of all, we have a watch on the entire repository and everyone has the CVSREAD variable set so that checkouts come as read only. This forces all developers to use "cvs edit" before editing a file. It is common practice, however, to just do

Re: cvs edit/commit problem

dit" stuff that hasn't really been checked in. Noel [EMAIL PROTECTED] on 2000.10.05 12:20:51 Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Noel L Yap) Subject: cvs edit/commit problem I'm experiencing a problem with cvs edit and commit. First of all, we have

Re: cvs edit/commit problem

On Thu, 5 Oct 2000, Richard J. Duncan wrote: Is this a know bug in CVS? Is there a known workaround? Maybe some No it is not a bug. If CVS did this it would be a bad idea for the same reason that the directive to automatically unedit the file you suggested would be a bad idea. The known

Re: cvs edit/commit problem

[EMAIL PROTECTED] on 2000.10.05 13:25:57 On Thu, 5 Oct 2000, Richard J. Duncan wrote: Is this a know bug in CVS? Is there a known workaround? Maybe some No it is not a bug. If CVS did this it would be a bad idea for the same reason that the directive to automatically unedit the file you

Re: cvs edit/commit problem

[EMAIL PROTECTED] on 2000.10.05 14:28:01 The purpose of "cvs edit" is to communicate to others that you intend to modify and commit a file. Therefore, unless you really do intend to modify and commit all files, "cvs edit *" is the wrong thing to do. Don't do that. Ok, then take this

RE: cvs edit/commit problem

[EMAIL PROTECTED] on 2000.10.05 14:28:01 Ok, then take this situation. I see a problem in this file. I want to edit it so I type "cvs edit file1" Then with further investigation I see the problem is really in file2, so I do "cvs edit file2" and then make my changes in file2. Then I am

Re: cvs edit/commit problem

Why does cvs unedit the file that was modified and not unedit the file that was not modified. Take this situation: I see problems in file1 and file2, so I "cvs edit file1 file2". I fix file1 and "cvs commit". Why should cvs unedit file2? I still want to make changes to file2. When I

Re: cvs edit/commit problem

"Richard J. Duncan" wrote: It seems arbitrary that it operates on only modified files, do people really like this. So far I have seen a lot of "it is right because it is the way it is," not "it is right because it seems the proper interface." I might argue the side for the existing

Re: cvs edit/commit problem

[EMAIL PROTECTED] on 2000.10.05 16:42:02 I would argue that in your situation you should type cvs commit file1 instead of cvs commit What if there were tons of files spread throughout the directory hierarchy? It seems arbitrary that it operates on only modified files, do people

commit problem

Hi, I must have seen this question being brought up recently, could someone forward me the solution/suggestions? Thanks a bunch! cvs commit -m "no message" CreateAccount.py (in directory C:\WINNT\Profiles\david.000\Personal\Projects\MyProj\) cvs server: [16:05:42] waiting for david's lock in

Re: commit problem

Hi, I found the answer (www.wincvs.org/howto/cvsdoc/cvs_21.html#Sec180). Thanks anyway. --Walter On Tue, 9 May 2000, Walter M. Yuan wrote: Hi, I must have seen this question being brought up recently, could someone forward me the solution/suggestions? Thanks a bunch! cvs commit -m