X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,TW_SV,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Message-ID: <4D593E24.6060208@cs.umass.edu> Date: Mon, 14 Feb 2011 09:37:24 -0500 From: Eliot Moss Reply-To: moss AT cs DOT umass DOT edu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: svn References: <4D540927 DOT 9030000 AT cs DOT umass DOT edu> <83vd0rmzd6 DOT fsf AT garydjones DOT name> <4D54506B DOT 7080702 AT acm DOT org> <4D5563A9 DOT 60607 AT acm DOT org> <4D5919A7 DOT 2090108 AT cs DOT umass DOT edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 2/14/2011 7:25 AM, Gary wrote: > Eliot Moss wrote: >> On 2/14/2011 3:11 AM, Gary wrote: >>> David Rothenberger wrote: >>>> If the files checked out in both directories are byte-for-byte >> identical >>>> (including binary files), I can't see how svn could be the culprit. >>> >>> If I can replace svn in the sequence with something else, for example >>> tortoise, and everything then works, then Cygwin/svn *is* the culprit. >> >> Not necessarily ... it could be the underlying ssh, if you are using >> svn over ssh, and it could be BLODA interfering with cygwin ... > > And yet not doing it with another client? It's not really very likely, > is it? In the fall of 2009 I was having a problem with rsync over ssh. Corinna and I got to the bottom of it: BLODA interfering with proper operation of socketpair. In the process, I found that if I disabled socketpair manually in the output of /.configure for building rsync, forcing it to use pipes instead, it worked fine. We have had occasional but persistent queries here about git over ssh, and you are reporting issues with svn and ssh. I am wondering if it has something to do with the sockets/pipes used to communicate between svn or git and the ssh subprocess. Best wishes -- EM -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple