From: Andrew Tridgell <tridge@samba.anu.edu.au> To: lkcl@cb1.com Subject: Re: possible cvs update problems Message-Id: <19980513001034Z12641442-1176+16017@samba.anu.edu.au> Date: Wed, 13 May 1998 10:10:20 +1000
Luke,
just to explain a little ...
The anonymous cvs comes from a mirror of the repository, not the
repository itself (due to paranoid security concerns).
The mirror re-syncs whenever the CVSROOT/history file changes. So if
things get out of sync (which they shouldn't) then just do a cvs
update in the non-anonymous tree and this will change the history file
which will cause the next anonymous cvs access to do a total re-sync.
in this case I think the problems were at the client end, not on the
server. I just did a anonymous checkout myself and it compiled
cleanly.
Cheers, Andrew
PS: Problems can happen if you do a checkout at exactly the same time
as someone is doing a checkin. In that case all you can do is delete
the affected files and checkout again.