[pkgsrc/trunk]: pkgsrc/doc doc/pkgsrc.*: regen

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

details:   https://anonhg.NetBSD.org/pkgsrc/rev/24d6cdaa0c11
branches:  trunk
changeset: 457336:24d6cdaa0c11
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Mon Aug 23 18:40:27 2021 +0000

description:
doc/pkgsrc.*: regen

diffstat:

 doc/pkgsrc.html |  4 ++--
 doc/pkgsrc.txt  |  4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diffs (41 lines):

diff -r 67040a09f69e -r 24d6cdaa0c11 doc/pkgsrc.html
--- a/doc/pkgsrc.html   Mon Aug 23 18:38:16 2021 +0000
+++ b/doc/pkgsrc.html   Mon Aug 23 18:40:27 2021 +0000
@@ -7785,7 +7785,7 @@
     problems due unrelated <code class="varname">PKGREVISION</code> bumps not
     related to security fixes. Lower bounds can be added too, using
     '&gt;' or '&gt;='. For example,
-    <span class="quote">&#8220;<span class="quote"><code class="literal">foo&gt;'=1&lt;1.2</code></span>&#8221;</span> would mark
+    <span class="quote">&#8220;<span class="quote"><code class="literal">foo&gt;=1&lt;1.2</code></span>&#8221;</span> would mark
     versions 1.0 (included) to 1.2 (excluded) of
     <span class="quote">&#8220;<span class="quote"><code class="literal">foo</code></span>&#8221;</span> as affected by the security
     issue.</p>
@@ -7793,7 +7793,7 @@
 <p>When fixing packages, please modify the upper bound of the
     corresponding entry. To continue the previous example, if a fix
     was backported to version 1.1nb2, change the previous pattern to
-    <span class="quote">&#8220;<span class="quote"><code class="literal">foo&gt;'=1&lt;1.1nb2</code></span>&#8221;</span>.</p>
+    <span class="quote">&#8220;<span class="quote"><code class="literal">foo&gt;=1&lt;1.1nb2</code></span>&#8221;</span>.</p>
 <p>To locally test a package version pattern against a
     <code class="varname">PKGNAME</code> you can use the <span class="command"><strong>pkg_admin
     pmatch</strong></span> command.</p>
diff -r 67040a09f69e -r 24d6cdaa0c11 doc/pkgsrc.txt
--- a/doc/pkgsrc.txt    Mon Aug 23 18:38:16 2021 +0000
+++ b/doc/pkgsrc.txt    Mon Aug 23 18:40:27 2021 +0000
@@ -6445,14 +6445,14 @@
 For the package version pattern please always use `<' to mark an upper bound
 (not `<='!). This will avoid possible problems due unrelated PKGREVISION bumps
 not related to security fixes. Lower bounds can be added too, using '>' or '>=
-'. For example, "foo>'=1<1.2" would mark versions 1.0 (included) to 1.2
+'. For example, "foo>=1<1.2" would mark versions 1.0 (included) to 1.2
 (excluded) of "foo" as affected by the security issue.
 
 Entries should always be added at the bottom of the file.
 
 When fixing packages, please modify the upper bound of the corresponding entry.
 To continue the previous example, if a fix was backported to version 1.1nb2,
-change the previous pattern to "foo>'=1<1.1nb2".
+change the previous pattern to "foo>=1<1.1nb2".
 
 To locally test a package version pattern against a PKGNAME you can use the 
 pkg_admin pmatch command.