Louis-Philippe VĂ©ronneau pushed to branch master at lintian / lintian


Commits:
43279978 by Nicolas Peugnet at 2024-10-31T18:52:11+00:00
Fix clearly invalid Markdown tag descriptions

Some descriptions contained clearly invalid Markdown, which caused
rendering bugs in Lintian SSG, but also in the HTML output of
lintian-explain-tags.

The text, JSON and HTML format output of lintian-explain-tags have
been checked.

See-also: 
https://salsa.debian.org/lintian/lintian-ssg/-/blob/106ab1c22f37a05342524bf31787a0e756a43b87/TODO.md#lintian-tag-sources

- - - - -
e7e2d023 by Nicolas Peugnet at 2024-10-31T18:52:11+00:00
Fix some more invalid <code> tags in literal blocks

- - - - -


8 changed files:

- tags/d/desktop-entry-file-has-crs.tag
- tags/d/dfsg-version-with-period.tag
- tags/e/empty-rust-library-declares-provides.tag
- tags/g/groff-message.tag
- tags/m/missing-built-using-field-for-golang-package.tag
- tags/p/pipe-symbol-used-as-license-disjunction.tag
- tags/r/relative-library-search-path.tag
- tags/w/whitespace-after-continuation-character.tag


Changes:

=====================================
tags/d/desktop-entry-file-has-crs.tag
=====================================
@@ -9,6 +9,6 @@ Explanation: The desktop entry file has lines ending in 
carriage-return and line
  .
  You can run the following command to remove any <code>CR</code> character in 
a file:
  .
-      <code>sed -i 's/\r//g' path/to/file</code>
+     sed -i 's/\r//g' path/to/file
 See-Also:
  https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s03.html


=====================================
tags/d/dfsg-version-with-period.tag
=====================================
@@ -10,4 +10,4 @@ Explanation: The version contains the string 
<code>.dfsg</code>.
  It is better to use <code>+dfsg</code> instead. The plus sign <code>+</code> 
sorts
  before <code>.</code>, so the sorting that is usually desired can take place:
  .
-   <code>1.2</code> &lt; <code>1.2+dfsg</code> &lt; <code>1.2.1</code>
+ <code>1.2</code> &lt; <code>1.2+dfsg</code> &lt; <code>1.2.1</code>


=====================================
tags/e/empty-rust-library-declares-provides.tag
=====================================
@@ -14,8 +14,8 @@ Explanation: For some time, Rust libraries used empty 
installation packages
  .
  You can see some examples here:
  .
-     - https://sources.debian.org/src/rust-dbus/0.9.0-2/debian/control/
-     - https://sources.debian.org/src/rust-x11rb/0.7.0-1/debian/control/
+  - https://sources.debian.org/src/rust-dbus/0.9.0-2/debian/control/
+  - https://sources.debian.org/src/rust-x11rb/0.7.0-1/debian/control/
  .
  The decision to burden the Rust packaging team with that extra step was
  made after weighing all possible alternatives.


=====================================
tags/g/groff-message.tag
=====================================
@@ -34,6 +34,6 @@ Explanation: A manual page provoked warnings or errors from 
the <code>man</code>
  .
  You can see the warnings yourself by running the command used by Lintian:
  .
-     <code>LC&lowbar;ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \
-         man --warnings -E UTF-8 -l -Tutf8 -Z &lt;file&gt; &gt;/dev/null</code>
+     LC&lowbar;ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \
+         man --warnings -E UTF-8 -l -Tutf8 -Z &lt;file&gt; &gt;/dev/null
 See-Also: groff_man(7), groff_mdoc(7)


=====================================
tags/m/missing-built-using-field-for-golang-package.tag
=====================================
@@ -11,4 +11,4 @@ Explanation: The stanza for a Golang installation package in 
the
  .
  Please add the following line to the relevant stanza:
  .
-  <code>Built-Using: ${misc:Built-Using}</code>
+     Built-Using: ${misc:Built-Using}


=====================================
tags/p/pipe-symbol-used-as-license-disjunction.tag
=====================================
@@ -1,7 +1,7 @@
 Tag: pipe-symbol-used-as-license-disjunction
 Severity: warning
 Check: debian/copyright/dep5
-Explanation: A vertical bar &vert (also known as a pipe symbol) does not stand 
for
+Explanation: A vertical bar &vert; (also known as a pipe symbol) does not 
stand for
  a logical OR relationship in <code>debian/copyright</code>.
  .
  To describe dual licensing, please use the word "or" between license


=====================================
tags/r/relative-library-search-path.tag
=====================================
@@ -18,9 +18,11 @@ Explanation: The binary or shared library sets RPATH or 
RUNPATH. This
  .
  To fix this problem, look for link lines like:
  .
-     <code>gcc test.o -o test -Wl,--rpath,/usr/local/lib</code>
+     gcc test.o -o test -Wl,--rpath,/usr/local/lib
+ .
  or
-     <code>gcc test.o -o test -R/usr/local/lib</code>
+ .
+     gcc test.o -o test -R/usr/local/lib
  .
  and remove the <code>-Wl,--rpath</code> or <code>-R</code> argument.
  .


=====================================
tags/w/whitespace-after-continuation-character.tag
=====================================
@@ -2,7 +2,7 @@ Tag: whitespace-after-continuation-character
 Severity: error
 Check: menu-format
 Explanation: The menu item is split up over two or more continuation lines, but
- there is additional whitespace after the backslash (<code>\</code>) that
+ there is additional whitespace after the backslash (<code>&bsol;</code>) that
  indicates where lines should be joined together.
  .
  There is no guarantee that such additional whitespace is handled correctly.



View it on GitLab: 
https://salsa.debian.org/lintian/lintian/-/compare/5f8186aaaad6585baaf072f7f82ef71b7e915be8...e7e2d02310fefad08f2b6939ed185a073ce76005

-- 
View it on GitLab: 
https://salsa.debian.org/lintian/lintian/-/compare/5f8186aaaad6585baaf072f7f82ef71b7e915be8...e7e2d02310fefad08f2b6939ed185a073ce76005
You're receiving this email because of your account on salsa.debian.org.


Reply via email to