Gerd Boerrigter <gerd.boerrigter(a)i2c-systems.com> writes:
PCL_CVS has a confusing behavior in our programming group. It
always
prints out a bunch of Parsing Errors in the *CVS* buffer. For
example, for a cvs-update I get:
,----
| PCL-CVS release v2_9_9
|
| Repository : :pserver:gboerrigter@cvs.i2c-systems.com:/cvs
| Working directory: /home/gboerrigter/workspace/dev-env/tools/
|
|
|
| Message: Parser Error: 'CVS server: Updating .'
| Message: Parser Error: 'CVS server: Updating togetherj'
| Message: Parser Error: 'CVS server: Updating togetherj/bin'
| Message: Parser Error: 'CVS server: Updating togetherj/config'
| Message: Parser Error: 'CVS server: Updating togetherj/doc'
| Message: Parser Error: 'CVS server: Updating togetherj/doc/images'
| Message: Parser Error: 'CVS server: Updating togetherj/gendoc'
| Message: Parser Error: 'CVS server: Updating xemacs'
| Modified xemacs/emacs-i2c.el
| Modified xemacs/init-1.el
| Unknown xemacs/semantic.cache
|
| --------------------- End ---------------------
| -- last cmd: cvs -f -z3 update --
`----
The Messages are very confusing, because they are not always at the
top, but mixed up with the files. This even happens with xemacs
-vanilla (the rest of this buffer is filled from that xemacs).
Any idea, why those messages are printed? Our server runs CVS 1.10.5.
I have experienced this too some times (with 21.1 and 21.4 ) using
'CVS_RSH=ssh', but only over "slower" connections (128kb/s) and
hitting cvs-status a couple of times made it go away. I have never
experienced this when using local (same computer or LAN) cvs
repository.
It could be nice if it was possible to set a cvs-debug variable to let
the cvs output go to a debug buffer to have a closer look at what
pcl_cvs receives.
relevant information:
XEmacs 21.1.14;
pcl-cvs v2_9_9 (pcl-cvs package version 1.49)
cvs-client side 1.11
XEmacs 21.4.4
pcl-cvs v2_9_9 (package version 1.55)
cvs-client side 1.11
cvs version (repository side) 1.10.7 (all cases)
I have not yet experienced it with the xemacs cvs repository yet, what
cvs version runs on that repository?
The problem is easily provoked on (256 kb/s)
':ext:jarlen@cvs.eicq.sourceforge.net:/cvsroot/eicq', Steve, can you
say what cvs version is installed there? The non-parseable output is
not always identical.
Jarl