Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <39AEFB42.66A7EDB2@ece.gatech.edu> Date: Thu, 31 Aug 2000 20:41:38 -0400 From: "Charles S. Wilson" X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Richard =?iso-8859-1?Q?H=F6fter?= CC: cygwin AT sources DOT redhat DOT com Subject: Re: cvs package available for test References: <39AE768E DOT E5D65099 AT ece DOT gatech DOT edu> <7601 DOT 967737334 AT www14 DOT gmx DOT net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Ahhh.....the light dawns. Okay, now I'm assumming that all failures that you see are when you are using the "official" cvs package's cvs server, correct? You may want to apply more than just Andy's pserverd patch; the following reference includes not only that, but also various other fixes: 1) Andy Piper's and Jim Kingdon's patch to tunnel CVS through an HTTP proxy server; 2) Mike Sutton --allow-list pserver option patch (allows repository roots to be specified in a file). 3) Andy Piper's pserverd patch (but also: Andy has provided a number of other changes that allow CVS to compile under Cygwin.) http://www.cvshome.org/cyclic/cvs/dev-win-ttaylor.txt I have not used or tested the patch referenced here. Since it is against cvs-1.10.5, it may not apply cleanly against 1.10.8, or some parts of it may have already been absorbed into the main 1.10.8 code. YMMV. BTW, the users allowed to access the cvs server must appear both in /repository/CVSROOT/passwd and in /etc/passwd --Chuck Richard Höfter wrote: > > Charles Wilson wrote: > > Okay, linux/cvs-1.10.7 client ---> andy's cygwin/cvs-??? server works. > > But we've already established that cygwin/cvs client ---> andy's > > cygwin/cvs-??? server fails. > > Ah, kind of misunderstanding: Andy's server works quite fine! > You can connect to it with cygwin CVS or Linux CVS. > > But Andy's server is pretty old, therefore my question to get > cygwin CVS server running. > > > However, cygwin/cvs client ---> external unixy/cvs server works. > > > > Also, you state that linux/cvs client ---> "official" cygwin/cvs server > > fails. Well, it's not surprising that the "official" cygwin/cvs server > > doesn't work; I made no effort to build or test it. If someone would > > like to reconcile Andy's server patches to the current release, I'll > > consider adding it --- AFTER we figure out why andy's server doesn't > > work! > > Again a misunderstanding: Andy's server works fine, I just took it as a > working reference programm for my tests with cygwin CVS. > > > > > So, the only conclusions I can draw are: > > 1) "official" cygwin/cvs server broken -- not surprising; let's drop > > this topic for now > > 2) some weird interaction between "official" cygwin/cvs client and > > Andy's cygwin/cvs server when running on the same machine (e.g. access > > thru 'localhost'). > > No, there is nothing weird. It works! > > > > > Can you try using the "official" cygwin/cvs client on a second machine, > > and connect to Andy's cygwin/cvs server running on the first machine? > > (I'm not sure why localhost would break wrt external TCP communication, > > but I'm just trying to rule out all possibilities). > > > > Well, this works quite fine, too. > > Cheers, > Richard. > > -- > Sent through GMX FreeMail - http://www.gmx.net -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com