X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Nicholas Thayer Subject: Re: cvs pserver issue with new cygwin packages Date: Wed, 10 May 2006 15:17:56 -0600 Lines: 42 Message-ID: References: <20060510185230 DOT GA9473 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) In-Reply-To: <20060510185230.GA9473@trixie.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Christopher Faylor wrote: > On Wed, May 10, 2006 at 06:41:23PM +0000, Michael Lemke wrote: > >>Igor Peshansky cs.nyu.edu> writes: >> >>>On Wed, 10 May 2006, Nicholas Thayer wrote: >>> >>>>After upgrading to the latest cygwin packages (coreutils, findutils, >>>>cygwin), the cvs pserver fails for updates and checkouts. [snip] $ cvs >>>>co test cannot mkdir /tmp/cvs-serv3172/. No such file or directory >>> >>>This was a bug in Cygwin 1.5.19, which returned the wrong error code >>>for creating this directory, and CVS didn't know to ignore it. Try a >>>snapshot. >> >>I've been wondering when we'll see the fix for that in a non-snapshot >>release. I've been waiting for it since 1.5.19 came out (many months >>ago). Sure, I could use a snapshot but I'd rather use something not in >>a state of flux. How hard would it be to make a 1.5.19-5 with that >>fix? > > > Not going to happen. Help the community. Use a snapshot. > > Either that or suffer silently. Those are your options. > > cgf > I don't necessarily _mind_ using a snapshot, but on this particular system stability is quite important. My concern is that the 1.5.18 cygwin package does work, and if other programs break as a result of running an unstable snapshot, then the problems have simply migrated from one area to another. Can you say with certainty that this particular problem has been fixed in the updated cygwin snapshot? Have others posted issues with cvs-cygwin integration on the 1.5.19 branch? Regards, Nicholas -- 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/