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

Bug#687141: lintian: [checks/scripts] python-script-but-no-python-dep: contradictory description.



Package: lintian
Version: 2.5.10.1
Severity: normal

Dear Lintian maintainers,

About the following tag:

E: python-script-but-no-python-dep
N:
N:   Packages with Python scripts should depend on the package python.
N:   Those with scripts that specify a specific version of Python must
N:   depend on that version of Python (exactly).
N:   
N:   For example, if a script in the package uses #!/usr/bin/python, the
N:   package needs a dependency on python. If a script uses
N:   #!/usr/bin/python2.6, the package needs a dependency on python2.6. A
N:   dependency on python (>= 2.6) is not correct, since later versions of
N:   Python may not provide the /usr/bin/python2.6 binary.
N:   
N:   If you are using debhelper, adding ${python:Depends} to the Depends
N:   field and ensuring dh_pysupport or dh_pycentral are run during the
N:   build should take care of adding the correct dependency.
N:   
N:   In some cases a weaker relationship, such as Suggests or Recommends,
N:   will be more appropriate.
N:   
N:   Severity: important, Certainty: certain
N:   
N:   Check: scripts, Type: binary

The description says: Severity: important, Certainty: certain, and the
tag is classified as an error, but on the other hand the description also
contains:

  In some cases a weaker relationship, such as Suggests or Recommends,
  will be more appropriate.

This creates confusion in team-maintained packages, as it is hard to
conclude from this description whether there is a problem or not.

How about either downgrading the importance, severity or certainty of
that tag, or change the check so that it also tolerates recommends or
suggests on python ?

Have a nice day,

-- 
Charles Plessy,
Tsurumi, Kanagawa, Japan


Reply to: