Discussion:
Stuck with commitinfo while setting up CVSspam
Shah, Kunal
2009-04-22 23:05:29 UTC
Permalink
Hello,

Need help !

I have been trying to install CVSspam for our project and stuck in checking in commitinfo file.

Below are the lines that I added in commitinfo file.

---------------------------------------------------------------------------------------
^cobra $CVSROOT/CVSROOT/record_lastdir.rb

# always allow commits to CVSROOT
^CVSROOT /bin/cat>/dev/null

# Invoke CVSspam lastdir script,
DEFAULT ...
---------------------------------------------------------------------------------------


Error that I get while checking in commitinfo file.

---------------------------------------------------------------------------------------
cvs commit: cannot find pre-commit filter `/bin/cat>/dev/null': No such file or directory
cvs commit: Pre-commit check failed
---------------------------------------------------------------------------------------

Now I'm not able to make any changes in commitinfo and probably in CVSROOT directory.

Appreciate your help on this.


Thanks,

Kunal
Todd Denniston
2009-04-23 22:28:38 UTC
Permalink
Post by Shah, Kunal
Hello,
Need help !
I have been trying to install CVSspam for our project and stuck in checking in commitinfo file.
Below are the lines that I added in commitinfo file.
---------------------------------------------------------------------------------------
^cobra $CVSROOT/CVSROOT/record_lastdir.rb
# always allow commits to CVSROOT
^CVSROOT /bin/cat>/dev/null
# Invoke CVSspam lastdir script,
DEFAULT ...
---------------------------------------------------------------------------------------
Error that I get while checking in commitinfo file.
---------------------------------------------------------------------------------------
cvs commit: cannot find pre-commit filter `/bin/cat>/dev/null': No such file or directory
cvs commit: Pre-commit check failed
---------------------------------------------------------------------------------------
`cvs -ver` reports what?
which OS and distribution is your server on?
I think you need a space or two, like:
^CVSROOT /bin/cat >/dev/null
or
^CVSROOT /bin/cat > /dev/null

BTW after you fix that ... not sure if cat will return at all considering that
it is not going to get any user input nor file input.
was this line for other than testing?
I would suggest /bin/true and /bin/false.
Post by Shah, Kunal
Now I'm not able to make any changes in commitinfo and probably in CVSROOT directory.
One of those rare instances where you actually have to use vi IN the repository.
i.e. you have to vi the commitinfo IN the repository.
and then from your checked out CVSROOT commit the same thing back in.
Post by Shah, Kunal
Appreciate your help on this.
Thanks,
Kunal
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
Mark D. Baushke
2009-04-23 23:08:11 UTC
Permalink
Post by Todd Denniston
I would suggest /bin/true and /bin/false.
One should consume all of the input or you will get odd broken pipe
error messages.

Other than that, I agree with the rest of your message.

-- Mark
Shah, Kunal
2009-04-24 00:35:52 UTC
Permalink
Thanks Todd.

That was helpful. I was able to modify commitinfo.


Kunal


-----Original Message-----
From: Todd Denniston [mailto:***@ssa.crane.navy.mil]
Sent: Thursday, April 23, 2009 3:29 PM
To: Shah, Kunal
Cc: info-***@nongnu.org
Subject: Re: Stuck with commitinfo while setting up CVSspam
Post by Shah, Kunal
Hello,
Need help !
I have been trying to install CVSspam for our project and stuck in checking in commitinfo file.
Below are the lines that I added in commitinfo file.
---------------------------------------------------------------------------------------
^cobra $CVSROOT/CVSROOT/record_lastdir.rb
# always allow commits to CVSROOT
^CVSROOT /bin/cat>/dev/null
# Invoke CVSspam lastdir script,
DEFAULT ...
---------------------------------------------------------------------------------------
Error that I get while checking in commitinfo file.
---------------------------------------------------------------------------------------
cvs commit: cannot find pre-commit filter `/bin/cat>/dev/null': No such file or directory
cvs commit: Pre-commit check failed
---------------------------------------------------------------------------------------
`cvs -ver` reports what?
which OS and distribution is your server on?
I think you need a space or two, like:
^CVSROOT /bin/cat >/dev/null
or
^CVSROOT /bin/cat > /dev/null

BTW after you fix that ... not sure if cat will return at all considering that
it is not going to get any user input nor file input.
was this line for other than testing?
I would suggest /bin/true and /bin/false.
Post by Shah, Kunal
Now I'm not able to make any changes in commitinfo and probably in CVSROOT directory.
One of those rare instances where you actually have to use vi IN the repository.
i.e. you have to vi the commitinfo IN the repository.
and then from your checked out CVSROOT commit the same thing back in.
Post by Shah, Kunal
Appreciate your help on this.
Thanks,
Kunal
--
Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter
Mohan, Inder
2009-04-24 20:46:07 UTC
Permalink
Hi All,



I am very new to CVS I am creating a test branch for myself. It created
successfully but when I am trying to see it through rlog command it
shows me following output with different revisions



[***@emac ~]$ cvs rlog -h -l test|grep -I test_1_2_3

cvs rlog: Logging config

test_1_2_3: 1.1.0.248

test_1_2_3: 1.3.0.248

test_1_2_3: 1.1.0.248



And why it is showing me revision number 1.1.0.248 two times.



Thanks,

Inder Mohan



P Please do not print this email unless it is absolutely necessary.
Spread environmental awareness.


If you are not the intended recipient of this e-mail message, please notify the sender
and delete all copies immediately. The sender believes this message and any attachments
were sent free of any virus, worm, Trojan horse, and other forms of malicious code.
This message and its attachments could have been infected during transmission. The
recipient opens any attachments at the recipient's own risk, and in so doing, the
recipient accepts full responsibility for such actions and agrees to take protective
and remedial action relating to any malicious code. Travelport is not liable for any
loss or damage arising from this message or its attachments.
Jim Hyslop
2009-04-25 16:45:07 UTC
Permalink
Post by Mohan, Inder
I am very new to CVS I am creating a test branch for myself. It created
successfully but when I am trying to see it through rlog command it
shows me following output with different revisions
[...]
Post by Mohan, Inder
And why it is showing me revision number 1.1.0.248 two times.
The short answer is: until you are an expert at CVS, do not attempt to
interpret the meaning of the numbers in a revision. CVS manages them,
and has done so quite well for many years.

The long answer (which will help you become more expert at CVS :=) is:
you are looking at the revision numbers assigned to different files. If
you modify the grep expression to look for the file name as well, you
will see the files to which the revision numbers apply.

Revision numbers for any given file are completely independent of
revision numbers for any other file. So it is entirely possible - and
safe - for two files to have the same revision number.

Sections 4 and 5 of the manual,
http://ximbiot.com/cvs/manual/cvs-1.11.23/cvs.html give a nicely
detailed explanation of how revision numbering works.

On a slight tangent - when creating a branch, always create a symbolic
tag for the base of the branch, then create the branch based on the
symbolic tag. That way you will always have a way of finding the branch
point (and believe me, one day you *will* need to know the branch point).

- --
Jim Hyslop
Dreampossible: Better software. Simply. http://www.dreampossible.ca
Consulting * Mentoring * Training in
C/C++ * OOD * SW Development & Practices * Version Management

Loading...