TortoiseCVS version 1.12.4
CVS client version: Concurrent Versions System (CVSNT) 2.5.05 (Gan) Build 3744
CVS server version: Concurrent Versions System (CVS) 1.11.23
SSH client version: TortoisePlink Release "0.56"
When I commit multiple files in my fairly large workspace ( more than 3000 files ) the top-level CVS/Entries directory gets overwritten with garbage. It looks like it contains partial contents from the CVS/Entries in a first directory that contains changes.
I was able to reproduce this bug on a cleanly checked out copy of my repository.
Also looks like size matters in this case, as I was not able to reproduce it on a small mock repository, only when I created a copy of my development workspace I was able to reproduce this bug.
To reproduce this bug I've added and removed files in the directory hierarchy deep underneath the root directory ( basically files in a java package structure ).
The end result of this bug is that when you are trying to update the sandbox, you get a conflict on every file in your repository. BTW, the commit does occur correctly.
As a workaround I am able to copy Entries.Old file over corrupted Entries and it seem to fix the problem
This issue is caused by CVSNT (the CVS client used by
TortoiseCVS), not by TortoiseCVS itself.
Please note that all communication with the CVS server and
all modifications of files in the sandbox is done by CVSNT, not
by TortoiseCVS.
Therefore, this issue cannot be fixed in TortoiseCVS; you need to
report the issue to the CVSNT maintainers using the mailing list
at http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt. When
doing this, be sure to include the version of CVSNT you are
using; you can see this in the About dialog of TortoiseCVS.
CVSNT does not want this bug on their system, but believe me it's real.
If you don't want to know what the "Entries" file is, I suggest you downgrade to TortoiseCVS 1.10.10.
To do this:
I guess this is one of the "ain't broken/don't fix it" lessons for me.
BTW, I agree with bullestock that it's not TortoiseCVS problem at all. It would be nice if the TortoiseCVS installation would have an option of not installing newer version of CVSNT client.
I think the bug you are describing a duplicate of 6021:
http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?tt=1&id=6021
It was first documented in October 2010, and resolved in February 2011 - before this TortoiseCVS bug report was filed. You wrote "CVSNT does not want this bug on their system" - but that is untrue. It's documented - it's also fixed.
Bug 6021 was introduced in the fix for bug 5836:
http://customer.march-hare.com/webtools/bugzilla/ttshow_bug.cgi?tt=1&id=5836
The fix for Bug 6021 is available in CVS Suite 2009-4095 as announced here:
http://www.twitter.com/CVSNT
and
http://www.facebook.com/pages/CVS/302315649701