Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com From: Jani Tiainen Subject: Re: strange problems with cvs Date: Wed, 01 Dec 2004 15:36:45 +0200 Lines: 37 Message-ID: References: <002201c4d793$837f5120$0100a8c0@pc07653> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 195.236.144.25 User-Agent: Mozilla Thunderbird 0.9 (Windows/20041118) In-Reply-To: <002201c4d793$837f5120$0100a8c0@pc07653> X-IsSubscribed: yes Nuno Lopes kirjoitti: > Hi, > > I use CVS with cygwin a long time ago, but after a recent updte it stoped > working. I'm using pserver auth and the cygwin is installed with *DOS* > line-endings. > > When I try to do something with cvs -1.11.17- (cvs up, cvs diff, etc..) it > simply returns: > ": no such repository" > > Normally if I close cygwin, run the setup again (without installing > anything) and opening cygwin again fixes the problem. > > If I do a fresh checkout, it will checkout the files with *unix* > file-endings, which isn't what I asked for.. > > Does anyone knows whats the problem here? I think it might be cause of the > release of the lastest dll version. (I update cygwin often..) Seems like you have encountered fancy EOL problem. To be safe use unix line-endings since CVS is pretty picky about those. And of course if you want to use DOS type line endings, use real win32 version of CVS. I've encountered numerous problems with CVS due the line-endings... Any decent text editor should be handle both CR+LF or LF/CR only line-endings and preserving existing ones... If yours doesn't it's time to upgrade... (Of course there might be problem in bin/textmode mounts) cygcheck output would do good here... -- Jani Tiainen -- 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/