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

[Git][lintian/lintian][master] Indent some text to turn them into literal blocks



Title: GitLab

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

Commits:

  • 3e860543
    by Nicolas Peugnet at 2024-10-31T18:53:10+00:00
    Indent some text to turn them into literal blocks
    

6 changed files:

Changes:

  • tags/c/changelog-is-dh_make-template.tag
    ... ... @@ -4,7 +4,7 @@ Check: debian/changelog
    4 4
     Explanation: The changelog file has an instruction left by dh_make, which has
    
    5 5
      not been removed. Example:
    
    6 6
      .
    
    7
    -   - Initial release (Closes: #nnnn)  <nnnn is the bug number of your ITP>
    
    7
    +     - Initial release (Closes: #nnnn)  <nnnn is the bug number of your ITP>
    
    8 8
      .
    
    9 9
      The "<... is the bug number ...>" part has not been removed from the
    
    10 10
      changelog.

  • tags/h/homepage-for-bioconductor-package-not-canonical.tag
    ... ... @@ -7,8 +7,8 @@ Explanation: The Homepage field for this package points to an uncanonical Biocon
    7 7
      release version (or devel if package is not in release yet). For example, the
    
    8 8
      link for the package "foo" should be:
    
    9 9
      .
    
    10
    - https://bioconductor.org/packages/foo/
    
    10
    +     https://bioconductor.org/packages/foo/
    
    11 11
      .
    
    12 12
      not:
    
    13 13
      .
    
    14
    - https://www.bioconductor.org/packages/(release|devel|*)/bioc/html/foo.html
    14
    +     https://www.bioconductor.org/packages/(release|devel|*)/bioc/html/foo.html

  • tags/h/homepage-github-url-ends-with-dot-git.tag
    ... ... @@ -5,8 +5,8 @@ Explanation: The Homepage field contains a GitHub URL that ends with .git
    5 5
      Please update to use the canonical URL, without .git at the end, for the
    
    6 6
      GitHub repository instead.
    
    7 7
      .
    
    8
    - https://github.com/foo/bar
    
    8
    +     https://github.com/foo/bar
    
    9 9
      .
    
    10 10
      not:
    
    11 11
      .
    
    12
    - https://github.com/foo/bar.git
    12
    +     https://github.com/foo/bar.git

  • tags/h/homepage-gitlab-url-ends-with-dot-git.tag
    ... ... @@ -5,8 +5,8 @@ Explanation: The Homepage field contains a GitLab URL that ends with .git
    5 5
      Please update to use the canonical URL, without .git at the end, for the
    
    6 6
      GitLab repository instead.
    
    7 7
      .
    
    8
    - https://gitlab.com/foo/bar
    
    8
    +     https://gitlab.com/foo/bar
    
    9 9
      .
    
    10 10
      not:
    
    11 11
      .
    
    12
    - https://gitlab.com/foo/bar.git
    12
    +     https://gitlab.com/foo/bar.git

  • tags/h/homepage-salsa-url-ends-with-dot-git.tag
    ... ... @@ -5,8 +5,8 @@ Explanation: The Homepage field contains a Salsa URL that ends with .git
    5 5
      Please update to use the canonical URL, without .git at the end, for the
    
    6 6
      Salsa repository instead.
    
    7 7
      .
    
    8
    - https://salsa.debian.org/foo/bar
    
    8
    +     https://salsa.debian.org/foo/bar
    
    9 9
      .
    
    10 10
      not:
    
    11 11
      .
    
    12
    - https://salsa.debian.org/foo/bar.git
    12
    +     https://salsa.debian.org/foo/bar.git

  • tags/u/unicode-trojan.tag
    ... ... @@ -27,7 +27,7 @@ Explanation: The named text file contains a Unicode codepoint that has been
    27 27
      .
    
    28 28
      You can also run a similar check in your shell with that command:
    
    29 29
      .
    
    30
    - <code>grep -r $'[\u061C\u200E\u200F\u202A\u202B\u202C\u202D\u202E\u2066\u2067\u2068\u2069]'</code>
    
    30
    +     grep -r $'[\u061C\u200E\u200F\u202A\u202B\u202C\u202D\u202E\u2066\u2067\u2068\u2069]'
    
    31 31
      .
    
    32 32
      The registered vulnerabilities are  CVE-2021-42694 ("Homoglyph") and
    
    33 33
      CVE-2021-42574 ("Bidirectional Attack").
    


  • Reply to: