X-Spam-Check-By: sourceware.org
Message-ID: <004701c655bf$6ede1340$84017ece@jabelxp>
From: "Jay Abel" <jabel AT flex DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Re: cvs 1.11.17 in command line server mode, OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005, problem with binary files
Date: Sat, 1 Apr 2006 09:06:45 -1000
MIME-Version: 1.0
Content-Type: text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Questions answered below:

>> $ cvs commit -m 'update wrappers'

> Did a message with the revision number appeared at this point?

Yes:

 [jabel AT jabelxp][cvstemp/CVSROOT] % cvs commit -m 'try again'
 Checking in cvswrappers;
 /home/spring2006/CVSROOT/cvswrappers,v  <--  cvswrappers
 new revision: 1.3; previous revision: 1.2
 done
 cvs commit: Rebuilding administrative file database
 [jabel AT jabelxp][cvstemp/CVSROOT] %

> If you run cvs through ssh the repository has to belong (or at least has 
> to be
writable) by the user (and/or group) that is logging in.  The same goes for
CVSROOT on the repository (the history log changes).  Since you don't show 
any
user id on your example that means the user you are logged as has to exist 
and
have the required privileges on jayabel.com (and on the other non-cygwin
machines you used).

Yes, I have the same login name on both the unix machine and the local 
machine, in the one case where I don't I use a Hosts entry in the 
.ssh/config file.  I have write access to the repository in all cases.

You were right to point out the 'I' message, I rarely use the import 
command, so perhaps I should have chosen a different example.

Now this may interest you.  I currently have the lines:

cvs -q -z5
update -Pd

And when I take a way the compression option:

cvs -q
update -Pd

I get the following:

[jabel AT jabelxp][jabel/cvstemp] % cd CVSROOT
[jabel AT jabelxp][cvstemp/CVSROOT] % vi cvswrappers
[jabel AT jabelxp][cvstemp/CVSROOT] % cvs up
unrecognized request `anged loginfo'
[jabel AT jabelxp][cvstemp/CVSROOT] %

Now, forgive me for grasping at straws here, but doesn't that look like a 
message was truncated or that perhaps some data was lost, or that perhaps a 
random piece of the file was sent instead?  In any case, all I have to do is 
turn compression back on, and:

[jabel AT jabelxp][cvstemp/CVSROOT] % cvs up
M cvswrappers
[jabel AT jabelxp][cvstemp/CVSROOT] %

and:

cvs commit -m 'try again'
Checking in cvswrappers;
/home/spring2006/CVSROOT/cvswrappers,v  <--  cvswrappers
new revision: 1.4; previous revision: 1.3
done
cvs commit: Rebuilding administrative file database

The earlier example was given with -z5 on, so it's not a simple matter of 
the communication link working when -z5 is on, and not working otherwise. 
More likely, there is another factor which depends on the specific stream.

Let's agree going forward that you'll stipulate I have read the faq, googled 
the problem, and that a real problem exists.  I'll stipulate I shouldn't 
have offered any explanation, and I was obviously (foolishly) wrong to ask 
about the 'I' option.  Of course those directories are ignored, that's what 
I want to happen.  But the problem does exist.  Sometimes CVS client and 
server running on the same machine can connect and complete the transaction. 
Sometimes they can't.  It appears that the problem is dependent on the 
specific characters sent (file contents affect it, compression affects it) 
and not on any design weaknes, per se, of the protocol, connection, or 
machine setup.

Jay Abel 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/