Mail Archives: cygwin/2000/08/01/01:37:20
As a new cvs package is being trialed, can someone confirm the following is
indeed correct.
For me, I have found that cvs + Cygwin1.dll has been broken for some time
although on the surface it look like it functions ok. (confused)
Firstly, I do use cvs all the time (only for anon cvs -z4 -q update -dP).
However, because of the problems I have experienced, I mainly use the CD
version of Cygwin, for cvs updates, which works correctly for me.
Now for my problem..........
If I do a cvs update with a "post CD Cygwin" (from 1.1.0 I think it
started) I get a huge amount of data being uploaded to the cvs server before
it downloads the code updates. It does do the update correctly but it takes
forever - It looks like it uploads the whole repository first.
Now if I use the CD version, only a small amount of data is uploaded to the
cvs server before it downloads the code updates, which is what I think
should happen, and the whole update is done reasonable quickly.
I have tested different versions of cvs but it always seems to be related to
the cygwin.dll version used. Just dropping a new cygwin1.dll into the CD
version cygwin causes the incorrect behaviour to occur.
Anyway, my aim is to just confirm whether or not it is isolated to my
setup.
Trevor
----- Original Message -----
From: "Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
To: <cygwin-apps AT sourceware DOT cygnus DOT com>
Sent: Monday, 31 July 2000 7:49
Subject: cvs package available for test
> CVS is the 'concurrent versioning system'. This is the initial port of
> cvs to cygwin's new packaging scheme. I've had cvs-1.10 on cygutils for
> some time but it didn't follow the package layout rules established here
> on cygwin-apps. This version is updated to cvs-1.10.8, and is
> dynamically linked to libgdbm.dll.
>
> The package is now available for testing at
> ftp://sourceware.cygnus.com/pub/cygwin/private/cygwin-extras-392/
>
> cvs-1.10.8-1.tar.gz
> cvs-1.10.8-1-src.tar.gz
>
> gdbm-1.8.0-1 must be installed.
>
> NOTES:
>
> o cygwin-specific doc /usr/doc/Cygwin/cvs-1.10.8.README
> o generic docs in /usr/doc/cvs-1.10.8/*
> o source archive already has the cygwin-specific patch applied
>
> o cygwin-specific README and PATCH are stored in the source archive,
> under <top>/CYGWIN-PATCHES/* (although the patch has already been
> applied to the archive itself).
>
> I ran the 'make check' tests, and of the many hundreds of tests, it
> failed only the following:
> - join-readonly-conflict
> - modules3
> - modules4
> - errmsg1
> - binfiles3
> - rcs3
> There were several other subtests that failed with a 'Signal 11' error
> (!!!) during the mega-test, but re-running those tests individually
> succeeded.
>
> I didn't run the following four tests, because they require a remote
> repository to which you have write access:
> - pserver
> - server
> - server2
> - client
>
> To run the tests individually, don't type 'make check'. Instead, cd to
> <top>/src and type:
> '/bin/sh ./sanity.sh `pwd`/cvs list-of-tests-to-run'
>
> You can find the list of all tests inside sanity.sh starting at line
> 592.
>
> This list of failures may be scary, but it's no worse than the older
> cygwin port of cvs-1.10. I'd appreciate any reports of success or
> failure using this version.
>
> BTW, cvs installs into /usr/bin, so if you've got an older version in
> /usr/local/bin make sure you're using the right version.
>
> --Chuck
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -