X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Michael Lemke <lemkemch AT t-online DOT de>
Subject:	Re: cvs pserver issue with new cygwin packages
Date:	Wed, 10 May 2006 18:41:23 +0000 (UTC)
Lines:	26
Message-ID:	<loom.20060510T203237-633@post.gmane.org>
References:	<e3t8jn$v5e$1 AT sea DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0605101423200 DOT 8628 AT access1 DOT cims DOT nyu DOT edu>
Mime-Version:	1.0
User-Agent:	Loom/3.14 (http://gmane.org/)
X-IsSubscribed:	yes
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

Igor Peshansky <pechtcha <at> 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?  Judging from this mailing list I 
am surprised that cvs server is the only application bitten by this bug.

Michael





--
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/

- Raw text -