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

[Git][lintian/lintian][master] Fix typos in tag descriptions.



Title: GitLab

Felix Lechner pushed to branch master at lintian / lintian

Commits:

2 changed files:

Changes:

  • tags/c/circular-installation-prerequisite.tag
    ... ... @@ -3,11 +3,11 @@ Severity: warning
    3 3
     Check: debian/control/prerequisite/circular
    
    4 4
     Renamed-From:
    
    5 5
      package-depends-on-itself
    
    6
    -Explanation: The package is its own installation prerquisite in the relevant
    
    7
    - <code>debian/control</code> stanza.
    
    6
    +Explanation: The installable declares itself as its own installation prerequisite
    
    7
    + in the relevant <code>debian/control</code> stanza.
    
    8 8
      .
    
    9 9
      Current versions of <code>dpkg-gencontrol</code> will silently ignore the
    
    10
    - prerequisite, but this may still indicate an oversight, like a misspelling
    
    11
    - or having unintentionally cut and pasted an incorrect package name.
    
    10
    + prerequisite, but it may still indicate an oversight. It could be a misspelling
    
    11
    + or having cut and pasted an incorrect package name.
    
    12 12
     See-Also:
    
    13 13
      debian-policy 7.2

  • tags/t/test-leaves-python-version-untested.tag
    ... ... @@ -2,10 +2,10 @@ Tag: test-leaves-python-version-untested
    2 2
     Severity: warning
    
    3 3
     Check: testsuite
    
    4 4
     Explanation: The named autopkgtest declares <code>python3-all</code> or an equivalent
    
    5
    - as a runtime prerquisite but the test script does not query the installed Python
    
    5
    + as a runtime prerequisite but the test script does not query the supported Python
    
    6 6
      versions with <code>py3versions --supported</code>.
    
    7 7
      .
    
    8 8
      The test may pass with the standard Python version but could fail in the future with
    
    9 9
      a Python version that is already available now.
    
    10 10
      .
    
    11
    - It is best to run tests for all available Python versions.
    11
    + It is best to run tests for all Python versions supported by the target system.


  • Reply to: