[cvsnt] CVS HEAD stuck?!?
arthur.barrett at march-hare.com
Thu Apr 19 13:45:22 BST 2007
Enable tracing on the server, then re-run the commit with -ttt (cvs -ttt
ci) and look for anything odd in the trace. Also do a "cvs rlog" on the
affected files to detect if the RCS file has become corrupt.
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org] On Behalf
Of Christian Hack
Sent: Thursday, 19 April 2007 7:52 PM
To: cvsnt at cvsnt.org
Subject: [cvsnt] CVS HEAD stuck?!?
We've been running CVSNT for a few years now with nary a problem
(excluding operator errors...). Server is currently running on Win2k3
and is version 2.5.01 build 1976 Travis. Not sure if that's old or new
or what but it's been working fine and if it ain't broke don't fix it.
Most users are running reasonably up to date TortoiseCVS for the client
on Windows XP.
Just today we are having some trouble. When we commit certain files
(only a few) it seems that the client end isn't updating in the CVS
A file called history.txt
Current revision is 1.301
I commit successfully and revision moves to 1.302 according to the
client commit output Server history.txt,v file all looks good and first
line says HEAD is now 1.302 However the client still thinks it's 1.301
for some reason (in CVS/Entries and in the $Id$ tag) If I commit again
the committed revision becomes 1.301.2.1 instead of 1.303 If I use the
revision graph feature of TortoiseCVS it shows the sandbox copy is 1.301
but shows 1.302 is there.
If I check out a completely brand new copy of the project I get 1.301
instead of the latest 1.302.
Any ideas? I couldn't really search since I don't really know what's
really going on or how to explain it.
cvsnt mailing list
cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt