[src/trunk]: src More general advice about "cvs [update aborted]... No such file

[apb <apb%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/67f4e788f937
branches:  trunk
changeset: 330830:67f4e788f937
user:      apb <apb%NetBSD.org@localhost>
date:      Wed Jul 23 08:52:32 2014 +0000

description:
More general advice about "cvs [update aborted]... No such file
or directory".

Also invent a "Cause:" keyword for use in "Symptom:/Cause:/Fix" sections.

Also add a note near the top of the file saying that there are
several sections marked by "^^^".

diffstat:

 UPDATING |  15 ++++++++++++++-
 1 files changed, 14 insertions(+), 1 deletions(-)

diffs (33 lines):

diff -r 13f0eec5b1d7 -r 67f4e788f937 UPDATING
--- a/UPDATING  Wed Jul 23 08:37:03 2014 +0000
+++ b/UPDATING  Wed Jul 23 08:52:32 2014 +0000
@@ -1,4 +1,4 @@
-$NetBSD: UPDATING,v 1.256 2014/07/23 08:37:03 apb Exp $
+$NetBSD: UPDATING,v 1.257 2014/07/23 08:52:32 apb Exp $
 
 This file (UPDATING) is intended to be a brief reference to recent
 changes that might cause problems in the build process, and a guide for
@@ -11,6 +11,9 @@
 build.sh existed.  Nevertheless, the advice here may be useful for
 working around specific problems with build.sh.
 
+Sections are marked with "^^^^^".  After the section on "Recent changes"
+are several sections containing more general information.
+
 See also: BUILDING, build.sh, Makefile.
 
 Recent changes:
@@ -677,3 +680,13 @@
 Symptom:Update build fails in src/tools/gcc complaining that a variable
        (e.g. CPPFLAGS) has changed since the previous run.
 Fix:    Run "nbmake-${ARCH} clean" in src/tools/gcc or do a clean build.
+
+Symptom:cvs [update aborted]: cannot open directory /cvsroot/src/...:
+       No such file or directory.
+Cause: If a directory is created by mistake, then it is sometimes
+       deleted from the CVS repository using administrative commands
+       that bypass the normal cvs access controls.  If your cvs working tree
+       contains references to a directory that has been deleted on the
+       server in this way, then "cvs update" reports this error.
+Fix:   Recursively delete the affected directory from your working tree
+       and try the update again.