[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: problem commiting over ssh
From: |
Doug Munsinger |
Subject: |
Re: problem commiting over ssh |
Date: |
Thu, 05 Apr 2001 09:08:06 -0400 |
Much thanks. This pointed me in the right direction -
I have verified that a stock CVS 1.11 repository works just fine - it is
the OLD repository
with has these issues either because the scripts were customized to add
undocumented functionality or
just more entomology.
I added a .cvsrc file with "cvs -s MSG=NULL" in it - this eliminated the
user variable error specifically and added more of the same but different,
so this is on the right track.
--doug
At 06:03 PM 4/4/2001 -0700, you wrote:
Doug Musinger wrote:
>~
>"/tmp/cvsU8Y8FX" 19L, 528C written
>cvs server commitinfo16 no such user variable ${=MSG}
>cvs server commitinfo17 no such user variable ${=MSG}
>cvs server commitinfo18 no such user variable ${=MSG}
>cvs server commitinfo19 no such user variable ${=MSG}
>cvs server commitinfo20 no such user variable ${=MSG}
>cvs server commitinfo21 no such user variable ${=MSG}
>cvs server commitinfo22 no such user variable ${=MSG}
>cvs server commitinfo23 no such user variable ${=MSG}
>cvs server commitinfo24 no such user variable ${=MSG}
>cvs server Pre-commit check failed
>cvs [server aborted] correct above errors first!
>cvs commit saving log message in /tmp/cvs7p8hYX
>address@hidden doc]$
It looks like your commitinfo script(s) is/are failing. Maybe because
there's a bug in it. Who wrote the script?
The "commitinfo" file is used to control pre-commit checks. It
specifies a filter program to run for specific directories. A
non-zero exit of the filter program will cause the commit to be
aborted.
This explains why you can do everything but commit.
--
Stephen Rasku E-mail: address@hidden
Senior Software Engineer Web: http://www.pop-star.net/
TGI Technologies
Doug Munsinger
egenera, Inc.
address@hidden
165 Forest Street, Marlboro, MA 01752
Tel: 508-786-9444 ext. 2612