This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: cvs pserver issue with new cygwin packages
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 25 Jun 2006 17:14:18 -0400
- Subject: Re: cvs pserver issue with new cygwin packages
- References: <e3t8jn$v5e$1@sea.gmane.org> <Pine.GSO.4.63.0605101423200.8628@access1.cims.nyu.edu> <loom.20060510T203237-633@post.gmane.org> <20060510185230.GA9473@trixie.casa.cgf.cx> <e3tla6$fbk$1@sea.gmane.org> <44629207.8000203@cygwin.com> <loom.20060625T202400-862@post.gmane.org>
- Reply-to: cygwin at cygwin dot com
Michael Lemke wrote:
Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
Nicholas Thayer wrote:
Christopher Faylor wrote:
On Wed, May 10, 2006 at 06:41:23PM +0000, Michael Lemke wrote:
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.
Today I did try the latest snapshot (20060622) and it fixes the problem. With
1.5.19 it does not work. This was a fresh compile of cvs 1.12.12. So this is a
cygwin error after all. How much longer do we have to wait for a non-snapshot
fix? This has been broken for more than 5 months now.
Is this a rhetorical question. If not, the answer is - until it's ready.
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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/