cvs pserver issue with new cygwin packages

[Larry Hall (Cygwin)]

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.
>>>
>>> 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?


The answer to these questions is to try the snapshot.  Simply keep a
copy of 1.5.18 in case you find something that makes you want to step
back for now.  But if you really need this to work for 1.5.20, you're
not going to be sure yourself unless you can verify that it fixes the
problem you see and doesn't cause others.  If you wait for 1.5.20 to
try this out and you find a problem, it's possible that you'll need to
wait until 1.5.21 to see a resolution to that issue.  Getting involved
earlier means you get the opportunity to provide important feedback at
a time when it will do the most good and benefit you the most.  If you
don't want to be stuck at 1.5.18 with no way out, this is your best
opportunity to secure your future and answer all your own questions.
Try it.  It doesn't hurt. ;-)


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