[cvsnt] Why is cvswrapper being interpreted as an improper commit response?

Anne Bonham abonham at gnx.com
Tue Aug 10 00:51:41 BST 2004


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


This problem could be either the server (CVSNT 2.0.12 on solaris 8) or our
client, but I have posted to CVSgui list and haven't gotten a response.

I want to encourage our users to upgrade their WinCVS clients from 1.2 to
1.3.17 and I'm testing 1.3.17 with our implementation before doing so.

So far, it appears that most everything is working fine but I notice on
updates or commits, I get this funny output (along with a healthy status 0)
Ultimately, the operation succeeds...

cvs commit: warning: unrecognized response `# This file affects
handling of files based on their names.' from cvs server
cvs commit: warning: unrecognized response `#' from cvs server
cvs commit: warning: unrecognized response `# The -m option specifies
whether CVS attempts to merge files.' from cvs server
cvs commit: warning: unrecognized response `#' from cvs server
cvs commit: warning: unrecognized response `# The -k option specifies
keyword expansion (e.g. -kb for binary).' from cvs server
cvs commit: warning: unrecognized response `#' from cvs server
cvs commit: warning: unrecognized response `# Format of wrapper file
($CVSROOT/CVSROOT/cvswrappers or .cvswrappers)' from cvs server
cvs commit: warning: unrecognized response `#' from cvs server
cvs commit: warning: unrecognized response `# wildcard [option value]
[option value]...' from cvs server
cvs commit: warning: unrecognized response `#' from cvs server
cvs commit: warning: unrecognized response `# where option is one
of' from cvs server
cvs commit: warning: unrecognized response `# -m
update methodology value: MERGE or COPY' from cvs server
cvs commit: warning: unrecognized response `# -k
expansion mode value: b, o, kkv, &c' from cvs server
cvs commit: warning: unrecognized response `#' from cvs server
cvs commit: warning: unrecognized response `# and value is a single-
quote delimited value.' from cvs server
cvs commit: warning: unrecognized response `# For example:' from cvs
server
cvs commit: warning: unrecognized response `*.gif -k 'b'' from cvs
server
cvs commit: warning: unrecognized response `*.jpg -k 'b'' from cvs
server

WinCVS or CVSNT seems to be reading each line of the cvswrapper file on the
server but is confusing it for server responses.

Any ideas on resolving this? It doesn't appear to be causing any real harm,
but I'd like to clean this up (or at least be able to explain it) before
encouraging users to upgrade.

Again, users on WinCVS 1.2 do NOT see this unwanted response.

I do intend to upgrade our server soon, but was hoping to upgrade clients
first - maybe this isn't a good idea?

Anne


-----------------------------------------
Anne Bonham | Release Manager
abonham at gnx.com
GlobalNetXchange, LLC
San Francisco | CA | 94104
-----------------------------------------




More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook