[pkgsrc/trunk]: pkgsrc/doc/guide/files doc/guide: update for the type change ...

[rillig <rillig%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/e978f6b50317
branches:  trunk
changeset: 417132:e978f6b50317
user:      rillig <rillig%pkgsrc.org@localhost>
date:      Mon Nov 04 18:47:27 2019 +0000

description:
doc/guide: update for the type change of the variable BROKEN

diffstat:

 doc/guide/files/fixes.xml |  4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diffs (18 lines):

diff -r 8a10632acf7e -r e978f6b50317 doc/guide/files/fixes.xml
--- a/doc/guide/files/fixes.xml Mon Nov 04 18:44:38 2019 +0000
+++ b/doc/guide/files/fixes.xml Mon Nov 04 18:47:27 2019 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: fixes.xml,v 1.148 2019/05/20 18:14:24 leot Exp $ -->
+<!-- $NetBSD: fixes.xml,v 1.149 2019/11/04 18:47:27 rillig Exp $ -->
 
 <chapter id="fixes"> <?dbhtml filename="fixes.html"?>
 <title>Making your package work</title>
@@ -2042,7 +2042,7 @@
   immediately. In this case, one can plainly mark a package as broken.  For
   this, one just sets the variable <varname>BROKEN</varname> to the
   reason why the package is broken (similar to the
-  <varname>RESTRICTED</varname> variable).  A user trying to build
+  <varname>PKG_FAIL_REASON</varname> variable).  A user trying to build
   the package will immediately be shown this message, and the build
   will not be even tried.</para>
   <para><varname>BROKEN</varname> packages are removed from pkgsrc in irregular