Originally Posted by daemonfowl
How fast do mirror servers sync to main server for -current ?
A better question would be:
"How do I verify that the update I just did has all recent code changes?"
The reason is that the developers may be checking in multiple
files, & did I just happen to do a code update while they were in the middle of checking in lots of changes?
The solution is to watch the source-changes@
mailing lists for activity. Most posts to these mailing lists are CVS check-in messages which will list the affected filename(s). This can be cross-referenced back to information found in CVSWeb to find the CVS version number of the file. This, in turn, can be verified on the local filesystem. As an example, at the time of composing this message, the following was the most recent check-in found in source-changes@
The steps required to verify that this file has been downloaded is:
- Perform a code update through whatever is the chosen method -- AnonCVS or CVSync.
- The CVSWeb page summarizing umidivar.h can be found at the following:
Note that the most recent check-in is version 1.14.
- If the following output is seen:
The most recent change has not been downloaded. The chosen mirror is not up to date.
$ grep umidivar.h /usr/src/sys/dev/usb/CVS/Entries
/umidivar.h/1.13/Sat Aug 25 18:26:04 2012//
If files are not synchronized, wait an hour, & repeat the same process until the local version matches the information found in CVS. Be sure to check the mailing lists again as more files may have been checked in during the interim.