I don't think it is a size issue. A tar.gz file is a binary file. I would verify that you added/imported this file using the -kb options to ignore keyword expansion on checkouts, etc. See http://ximbiot.com/cvs/manual/cvs-1.11.7/cvs_9.html#SEC80 for more information on binary files. Hope this answers, or at least assists, your issue.
Also, this is a CVS list, not a WinCVS or CVSNT list. So I am approaching your question from a CVS standpoint only. Enjoy, Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of slock Sent: Friday, March 17, 2006 1:37 PM To: [email protected] 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 [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
