Adding upstream version 2.117.0.upstream/2.117.0upstream

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 24 insertions, 0 deletions

diff --git a/tags/n/new-package-should-not-package-python2-module.tag b/tags/n/new-package-should-not-package-python2-module.tag
new file mode 100644
index 0000000..39fa255
--- /dev/null
+++ b/tags/n/new-package-should-not-package-python2-module.tag
@@ -0,0 +1,24 @@
+Tag: new-package-should-not-package-python2-module
+Severity: warning
+Check: languages/python
+Explanation: This package appears to be the initial packaging of a new upstream
+ software package (ie. it contains a single changelog entry). However, it
+ ships the specified module for Python 2.
+ .
+ Python 2.x 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 by upstream past 2020 and will likely be dropped
+ after the release of Debian <code>buster</code>.
+ .
+ If upstream have not yet moved to Python 3, please be certain that Debian
+ would benefit from the inclusion, continued maintenance burden and eventual
+ removal of this package before you upload.
+ .
+ This warning can be ignored if the package is not intended for Debian or
+ if it is a split of an existing Debian package. This warning can also be
+ ignored if viewed on https://lintian.debian.org/.
+ .
+ Please do not override this warning. Instead, add a justification to your
+ changelog entry. Lintian will detect your comment in the changelog. It ensures
+ that your rationale is preserved for posterity.