Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 To: cygwin AT cygwin DOT com From: Alejandro Lopez-Valencia Subject: Re: Pserver on cygwin corrupts binary files Date: Sun, 15 Feb 2004 08:58:37 -0500 Lines: 18 Message-ID: References: <001d01c3f368$60dcfe70$6500a8c0 AT Ray> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet AT sea DOT gmane DOT org X-Gmane-NNTP-Posting-Host: 200.93.154.69 X-Newsreader: Forte Agent 2.0/32.640 On Sat, 14 Feb 2004 20:06:47 -0600, Chuck Irvine wrote in <001d01c3f368$60dcfe70$6500a8c0 AT Ray>: >I'm using a cvs pserver on cygwin and I find that when I pull (checkout, >update, etc) binary file from the repository they come out corrupted, >i.e. can't be opened with jar, etc. Using the cvs command locally works >fine. If I'm not mistaken, I've used used a cvs pserver previously >without this problem. Does any have any idea what my problem might be? I >specify dos line endings when I set up Cygwin, if that makes any >difference. Yup. You didn't read the CVS manual. Particularly what sticky tags are, and the reason of being of a certain CVSROOT/cvswrappers file in the repository. Furthermore, using textmode mounts in cygwin main filesystem structure is asking for trouble. -- 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/