[lintian] 01/01: Clarify that new-package-should-not-package-python2-module triggers when there is a single changelog entry as well as providing general guidance where upstream have not ported to Python 3 yet.
This is an automated email from the git hooks/post-receive script.
lamby pushed a commit to branch master
in repository lintian.
commit dff0d388f2ada26aeb80356528549885d9990f84
Author: Chris Lamb <lamby@debian.org>
Date: Sun Dec 10 16:56:16 2017 +0000
Clarify that new-package-should-not-package-python2-module triggers when there is a single changelog entry as well as providing general guidance where upstream have not ported to Python 3 yet.
---
checks/python.desc | 23 +++++++++++++++++------
debian/changelog | 4 ++++
2 files changed, 21 insertions(+), 6 deletions(-)
diff --git a/checks/python.desc b/checks/python.desc
index 70a01b1..fa46519 100644
--- a/checks/python.desc
+++ b/checks/python.desc
@@ -8,14 +8,19 @@ Tag: new-package-should-not-package-python2-module
Severity: normal
Certainty: certain
Info: This package appears to be the initial packaging of a new upstream
- software package but it appears to package a module for Python 2.
+ software package (ie. it contains a single changelog entry) but it ships
+ a module for Python 2.
.
- The 2.x series of Python is due for deprecation and will not be maintained
- past 2020 so it is recommended that Python 2 modules are not packaged unless
- necessary such as directly requested by an end-user or required as part of a
- dependency chain.
+ Python 2 modules should not be packaged unless strictly necessary (such as
+ being explicitly requested by an end-user or required as part of a dependency
+ chain) as the 2.x series of Python is due for deprecation and will not be
+ maintained past 2020.
+ .
+ If upstream have not moved or have no intention to move to Python 3, please be
+ certain that Debian would benefit from the inclusion of this package before
+ uploading.
.
- This warning can be ignored if the package is not intended for Debian or
+ This warning can also be ignored if the package is not intended for Debian or
if it is a split of an existing Debian package.
Tag: python-foo-but-no-python3-foo
@@ -26,6 +31,9 @@ Info: This package appears to generate a Python 2 module without a
.
The 2.x series of Python is due for deprecation and will not be maintained
past 2020.
+ .
+ If upstream have not moved or have no intention to move to Python 3, please be
+ certain that Debian would benefit from the inclusion of this package.
Tag: build-depends-on-python-sphinx-only
Severity: normal
@@ -60,6 +68,9 @@ Info: The package specifies a dependency on Python 2.x which is due for
deprecation and will not be maintained past 2020.
.
Please port the package to use Python 3 instead.
+ .
+ If upstream have not moved or have no intention to move to Python 3, please be
+ certain that Debian would benefit from the inclusion of this package.
Tag: django-package-does-not-depend-on-django
Severity: normal
diff --git a/debian/changelog b/debian/changelog
index 82795c6..a2e2604 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -7,6 +7,10 @@ lintian (2.5.63) UNRELEASED; urgency=medium
ELF binaries in $PATH. Host architecture binaries are generally not
executable so such files are useless for cross builds.
(Closes: #794295)
+ * checks/python.pm:
+ + [CL] Clarify that new-package-should-not-package-python2-module
+ triggers when there is a single changelog entry as well as providing
+ general guidance where upstreams have not ported to Python 3 yet.
* commands/lintian.pm:
+ [CL] Correct parsing of "jobs=42" in lintianrc. If specified, it
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/lintian/lintian.git
Reply to: