[gnome-love] Delays between CVS checkins and availability to vicious build scripts?

[George Karabin <gkarabin pobox com>]

I'm trying to build nautilus from CVS head, but appear to be getting 
(slightly) out of date files from the CVS server that the 
vicious-build-scripts sets up (/gnome/head/cvs/setvars.sh sets CVSROOT 
to use anoncvs4.gnome.org).

When I checkout nautilus, I am getting version 1.263 of the file (looked 
it up using 'cvs status', which tells me that that's the newest version 
checked in to the repository). However, when I look at the CVS checkins 
mailing list (or the CVS web interface), I can see that a change that I 
want went in on version 1.264, and that the file has since progressed to 
version 1.265. Forcing a cvs update doesn't have any effect, and I can't 
find any obvious CVS commands to force the issue.

Questions that occur to me include:
- How does a CVS checkin propagate to the slave servers?
- Is there some schedule that updates happen on, so I can figure out how 
long I have to wait for propagation to the CVS server I'm using?
- Is there another server that I could use that updates more frequently?
- Is there some other way for me to be able to get the newer version on 
demand (besides manually patching my local copy)?

By the way, here's the file that I'm looking at, on anoncvs4.gnome.org. 
I wouldn't be surprised if it updates by the time anyone looks at it, 
but right now the file appears to be 2 revisions out of date.

cvs status libnautilus-private/nautilus-file.c
===================================================================
File: nautilus-file.c      Status: Up-to-date

  Working revision:    1.263
  Repository revision:    1.263    
/cvs/gnome/nautilus/libnautilus-private/nautilus-file.c,v
  Sticky Tag:        (none)
  Sticky Date:        (none)
  Sticky Options:    (none)


Thanks,

- George