Mark E. Hamilton wrote:
Mathieu,
Mathieu Malaterre wrote:
cvs [commit aborted]: received broken pipe signal
As a temporary solution I commented out this faulty line, but
nothing changed, I still get the broken pipe signal message. Is there
any way to go back ? How do I track down this problem.
Well, then clearly the line you commented out was not the incorrect one.
In the past when we have seen this error it was caused by a faulty
filter in the loginfo file; ie, the filter program was not consuming all
of stdin.
According to Cederqvist:
All occurrences of the name 'ALL' appearing as a regular expression are
used in addition to the first matching regular expression or 'DEFAULT'.
So, I suspect that you've got another line that is matching your commit
that is not consuming all of stdin.
I think I have the problem. I change the line after cecking out the
CVSROOT dir from within my project:
$ cvs status loginfo
===================================================================
File: loginfo Status: Up-to-date
...
$ diff loginfo /var/lib/cvsd/FarSight/CVSROOT/loginfo
32c32
< #ALL mail -s %s [EMAIL PROTECTED]
---
> ALL mail -s %s [EMAIL PROTECTED]
How in the world could this happen ? How come cvs can tell me this is up
to date, but it isn't.
How does one rebuild the administrative database ?
Thanks
Mathieu
_______________________________________________
Info-cvs mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/info-cvs
