pkgsrc-Changes archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

CVS commit: pkgsrc/doc



Module Name:    pkgsrc
Committed By:   wiz
Date:           Mon Aug 23 18:40:27 UTC 2021

Modified Files:
        pkgsrc/doc: pkgsrc.html pkgsrc.txt

Log Message:
doc/pkgsrc.*: regen


To generate a diff of this commit:
cvs rdiff -u -r1.320 -r1.321 pkgsrc/doc/pkgsrc.html
cvs rdiff -u -r1.318 -r1.319 pkgsrc/doc/pkgsrc.txt

Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.

Modified files:

Index: pkgsrc/doc/pkgsrc.html
diff -u pkgsrc/doc/pkgsrc.html:1.320 pkgsrc/doc/pkgsrc.html:1.321
--- pkgsrc/doc/pkgsrc.html:1.320        Sun Aug 22 16:28:53 2021
+++ pkgsrc/doc/pkgsrc.html      Mon Aug 23 18:40:27 2021
@@ -7785,7 +7785,7 @@ CONFLICTS=      libXaw3d-[0-9]*
     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 @@ CONFLICTS=      libXaw3d-[0-9]*
 <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>

Index: pkgsrc/doc/pkgsrc.txt
diff -u pkgsrc/doc/pkgsrc.txt:1.318 pkgsrc/doc/pkgsrc.txt:1.319
--- pkgsrc/doc/pkgsrc.txt:1.318 Sun Aug 22 16:28:53 2021
+++ pkgsrc/doc/pkgsrc.txt       Mon Aug 23 18:40:27 2021
@@ -6445,14 +6445,14 @@ advisories/pkg-vulnerabilities. Entries 
 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.



Home | Main Index | Thread Index | Old Index