RE: WinCVS/CVSNT choking on large tar.gz files during Import/Checkoutprocess

[Arthur Barrett]

Stpehen,

You are running both CVSNT client and CVSNT server - this list is only
for problems with CVS (not WinCVS at all which is different again).
WinCVS is "just" a GUI in front of the cvsnt client (look for cvs.exe in
the WinCVS directory, and check the properties) - so WinCVS will have
nothing to do with this problem.

Please upgrade the server and client to 2.5.03.2260 and if the problem
still occurs report it to the CVSNT newsgroup:
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
or
news://news.cvsnt.org/support.cvsnt

WinCVS by default ships a very very old CVSNT client with many known
bugs, and you haven't reported the server version either.  I vaguely
remember this bug from years ago.  Also note that if you are checking
out a 160Mb file you'll need at least three times that much memory
available (even more with -kB binary diffs).

Regards,



Arthur Barrett

-----Original Message-----
From: address@hidden
[mailto:address@hidden On
Behalf Of slock
Sent: Saturday, 18 March 2006 6:37 AM
To: address@hidden
Subject: WinCVS/CVSNT choking on large tar.gz files during
Import/Checkoutprocess


I just wanted to post an observation that I have made with WinCVS
2.0.2.4 (Build 4).

I have a large source tree (~1.5 GB) that I am trying to import using
WinCVS.  The source code resides on a Linux 2.4 machine, while my CVSNT
server is on a Windown Server 2003 box.

I have noticed that when I try to import a tar.gz file that is larger
than ~184 MB I cannot subsequently check that file out without receiving
an "Invalid Argument" error.  Due to this I have had to keep these large
tar-balls separate from CVS (not something that I am particularily happy
about).

Has anyone else observed this issue?  If so, is there a known solution?

Stephen

_______________________________________________
info-cvs mailing list
address@hidden http://lists.nongnu.org/mailman/listinfo/info-cvs