Adding upstream version 2.117.0.upstream/2.117.0upstream

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

29 files changed, 294 insertions, 0 deletions

diff --git a/tags/t/tab-in-license-text.tag b/tags/t/tab-in-license-text.tag
new file mode 100644
index 0000000..0fb0129
--- /dev/null
+++ b/tags/t/tab-in-license-text.tag
@@ -0,0 +1,9 @@
+Tag: tab-in-license-text
+Severity: warning
+Check: debian/copyright/dep5
+Explanation: A long license text in <code>debian/copyright</code> contains
+ a tab character. It often occurs when a license text is copied
+ from another source, and not reformatted.
+ .
+ DEP-5 disallows the use of tab characters in the license text.
+ Please remove it.
diff --git a/tags/t/tclsh-script-but-no-tclsh-dep.tag b/tags/t/tclsh-script-but-no-tclsh-dep.tag
new file mode 100644
index 0000000..0b15b3b
--- /dev/null
+++ b/tags/t/tclsh-script-but-no-tclsh-dep.tag
@@ -0,0 +1,9 @@
+Tag: tclsh-script-but-no-tclsh-dep
+Severity: error
+Check: scripts
+Explanation: Packages that include tclsh scripts must depend on the virtual
+ package tclsh or, if they require a specific version of tcl, that
+ version of tcl.
+ .
+ In some cases a weaker relationship, such as Suggests or Recommends, will
+ be more appropriate.
diff --git a/tags/t/team-upload-has-incorrect-version-number.tag b/tags/t/team-upload-has-incorrect-version-number.tag
new file mode 100644
index 0000000..154b3e8
--- /dev/null
+++ b/tags/t/team-upload-has-incorrect-version-number.tag
@@ -0,0 +1,7 @@
+Tag: team-upload-has-incorrect-version-number
+Severity: warning
+Check: nmu
+Explanation: A team upload (uploading a package from the same team without adding
+ oneself as maintainer or uploader) is a maintainer upload: it should not
+ get a NMU revision number. Team uploads are recognized by the string
+ "team upload" on the first line of the changelog file.
diff --git a/tags/t/template-uses-unsplit-choices.tag b/tags/t/template-uses-unsplit-choices.tag
new file mode 100644
index 0000000..be97f71
--- /dev/null
+++ b/tags/t/template-uses-unsplit-choices.tag
@@ -0,0 +1,15 @@
+Tag: template-uses-unsplit-choices
+Severity: warning
+Check: debian/debconf
+Explanation: The use of &lowbar;Choices in templates is deprecated.
+ A &lowbar;Choices field must be translated as a single string.
+ .
+ Using &lowbar;&lowbar;Choices allows each choice to be translated separately, easing
+ translation and is therefore recommended.
+ .
+ Instead of simply replacing all occurrences of "&lowbar;Choices" by "&lowbar;&lowbar;Choices",
+ apply the method described in po-debconf(7) under "SPLITTING CHOICES
+ LIST", to avoid breaking existing translations.
+ .
+ If in doubt, please ask for help on the debian-i18n mailing list.
+See-Also: po-debconf(7)
diff --git a/tags/t/temporary-debhelper-file.tag b/tags/t/temporary-debhelper-file.tag
new file mode 100644
index 0000000..3cbc5a3
--- /dev/null
+++ b/tags/t/temporary-debhelper-file.tag
@@ -0,0 +1,10 @@
+Tag: temporary-debhelper-file
+Severity: error
+Check: debhelper/temporary
+Explanation: The named file is a temporary Debhelper file.
+ .
+ The file should have been removed by <code>dh&lowbar;clean</code>. Sometimes
+ that happens when an installable package was renamed or removed before the
+ build directory was cleaned up.
+See-Also:
+ dh_clean(1)
diff --git a/tags/t/test-leaves-python-version-untested.tag b/tags/t/test-leaves-python-version-untested.tag
new file mode 100644
index 0000000..3075cd7
--- /dev/null
+++ b/tags/t/test-leaves-python-version-untested.tag
@@ -0,0 +1,11 @@
+Tag: test-leaves-python-version-untested
+Severity: warning
+Check: testsuite
+Explanation: The named autopkgtest declares <code>python3-all</code> or an equivalent
+ as a runtime prerequisite but the test script does not query the supported Python
+ versions with <code>py3versions --supported</code>.
+ .
+ The test may pass with the standard Python version but could fail in the future with
+ a Python version that is already available now.
+ .
+ It is best to run tests for all Python versions supported by the target system.
diff --git a/tags/t/testsuite-dependency-has-unparsable-elements.tag b/tags/t/testsuite-dependency-has-unparsable-elements.tag
new file mode 100644
index 0000000..4a2705d
--- /dev/null
+++ b/tags/t/testsuite-dependency-has-unparsable-elements.tag
@@ -0,0 +1,11 @@
+Tag: testsuite-dependency-has-unparsable-elements
+Severity: warning
+Check: testsuite
+Explanation: Lintian cannot parse the Depends field for the given autopkgtest.
+ .
+ Please double check that dependency the syntax is correct.
+ .
+ Note that Lintian has a whitelist of known "special" dependencies
+ permitted by autopkgtest (e.g. @builddeps@). Lintian does not accept
+ these as a part of an OR-clause.
+See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst
diff --git a/tags/t/third-party-package-in-python-dir.tag b/tags/t/third-party-package-in-python-dir.tag
new file mode 100644
index 0000000..a93aee5
--- /dev/null
+++ b/tags/t/third-party-package-in-python-dir.tag
@@ -0,0 +1,10 @@
+Tag: third-party-package-in-python-dir
+Severity: warning
+Check: languages/python
+Explanation: Third-party Python packages should install their files in
+ <code>/usr/lib/python*VERSION*/site-packages</code> for Python versions
+ before 2.6 and <code>/usr/lib/python*VERSION*/dist-packages</code>
+ for Python 2.6 and later. All other directories in
+ <code>/usr/lib/python*VERSION*</code> are for use by the core python
+ packages.
+See-Also: python-policy 2.5
diff --git a/tags/t/timewarp-standards-version.tag b/tags/t/timewarp-standards-version.tag
new file mode 100644
index 0000000..8cf5108
--- /dev/null
+++ b/tags/t/timewarp-standards-version.tag
@@ -0,0 +1,7 @@
+Tag: timewarp-standards-version
+Severity: warning
+Check: fields/standards-version
+Explanation: The source package refers to a Standards-Version that was released
+ after the date of the most recent <code>debian/changelog</code> entry.
+ Perhaps you forgot to update the timestamp in <code>debian/changelog</code>
+ before building the package?
diff --git a/tags/t/too-long-extended-description-in-templates.tag b/tags/t/too-long-extended-description-in-templates.tag
new file mode 100644
index 0000000..cb6da92
--- /dev/null
+++ b/tags/t/too-long-extended-description-in-templates.tag
@@ -0,0 +1,7 @@
+Tag: too-long-extended-description-in-templates
+Severity: warning
+Check: debian/debconf
+Explanation: Some debconf interfaces cannot deal very well with descriptions of
+ more than about 20 lines, so try to keep the extended description below
+ this limit.
+See-Also: developer-reference 6.5.3.2
diff --git a/tags/t/too-long-short-description-in-templates.tag b/tags/t/too-long-short-description-in-templates.tag
new file mode 100644
index 0000000..4046f2f
--- /dev/null
+++ b/tags/t/too-long-short-description-in-templates.tag
@@ -0,0 +1,8 @@
+Tag: too-long-short-description-in-templates
+Severity: warning
+Check: debian/debconf
+Explanation: The short description should be kept short (50 characters or so) so
+ that it may be accommodated by most debconf interfaces. Keeping it short
+ also helps translators, as usually translations tend to end up being
+ longer than the original.
+See-Also: developer-reference 6.5.3.2
diff --git a/tags/t/too-many-architectures.tag b/tags/t/too-many-architectures.tag
new file mode 100644
index 0000000..7d8d2fe
--- /dev/null
+++ b/tags/t/too-many-architectures.tag
@@ -0,0 +1,6 @@
+Tag: too-many-architectures
+Severity: error
+Check: fields/architecture
+Explanation: A binary package should list exactly one architecture (the one it is
+ compiled for), or the special value "all" if it is architecture-independent.
+See-Also: debian-policy 5.6.8
diff --git a/tags/t/too-many-contacts.tag b/tags/t/too-many-contacts.tag
new file mode 100644
index 0000000..e34df76
--- /dev/null
+++ b/tags/t/too-many-contacts.tag
@@ -0,0 +1,7 @@
+Tag: too-many-contacts
+Severity: error
+Check: fields/mail-address
+Explanation: The named field identifying a contact person lists too many people.
+See-Also: debian-policy 5.6.2,
+ debian-policy 5.6.3,
+ debian-policy 5.6.4
diff --git a/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag b/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag
new file mode 100644
index 0000000..d8a884c
--- /dev/null
+++ b/tags/t/trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir.tag
@@ -0,0 +1,7 @@
+Tag: trailing-slash-for-dpkg-maintscript-helper-symlink_to_dir
+Severity: error
+Check: scripts
+Explanation: The maintainer script seems to call dpkg-maintscript-helper
+ symlink&lowbar;to&lowbar;dir with a trailing slash for pathname. This renders the
+ package uninstallable.
+See-Also: dpkg-maintscript-helper(1)
diff --git a/tags/t/trailing-whitespace.tag b/tags/t/trailing-whitespace.tag
new file mode 100644
index 0000000..1040168
--- /dev/null
+++ b/tags/t/trailing-whitespace.tag
@@ -0,0 +1,27 @@
+Tag: trailing-whitespace
+Severity: pedantic
+Check: debian/trailing-whitespace
+Renamed-From: file-contains-trailing-whitespace
+Explanation: This file contains lines with trailing whitespace characters.
+ .
+ Whilst often harmless and unsightly, such extra whitespaces can also
+ cause tools to interpret the whitespace characters literally. The
+ tool <code>diff(1)</code> does not like them, either. They are best
+ avoided.
+ .
+ Some of these problems can be hard to track down.
+ .
+ Whitespace at the end of lines may be removed with the following:
+ .
+  $ sed -i -e 's@[[:space:]]&ast;$@@g' debian/control debian/changelog
+ .
+ If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup).
+ .
+ However, if you wish to only remove trailing spaces and leave trailing tabs
+ (eg. for Makefiles), you can use the following code snippet:
+ .
+  $ sed -i -e 's@[ ]&ast;$@@g' debian/rules
+ .
+ To remove empty lines from the end of a file, you can use:
+ .
+  $ sed -i -e :a -e '/^\n&ast;$/{$d;N;};/\n$/ba' debian/rules
diff --git a/tags/t/transitional-package-not-oldlibs-optional.tag b/tags/t/transitional-package-not-oldlibs-optional.tag
new file mode 100644
index 0000000..d66a5b4
--- /dev/null
+++ b/tags/t/transitional-package-not-oldlibs-optional.tag
@@ -0,0 +1,13 @@
+Tag: transitional-package-not-oldlibs-optional
+Severity: warning
+Check: fields/section
+Renamed-From:
+ transitional-package-should-be-oldlibs-extra
+ transitional-package-should-be-oldlibs-optional
+Explanation: The package appears to be a transitional package, but it is not
+ priority optional and in the oldlibs section.
+ .
+ Using oldlibs/optional assists package managers in handling the
+ transition package correctly.
+See-Also: Bug#645438,
+ developer-reference 6.8.7
diff --git a/tags/t/translated-default-field.tag b/tags/t/translated-default-field.tag
new file mode 100644
index 0000000..9e9f325
--- /dev/null
+++ b/tags/t/translated-default-field.tag
@@ -0,0 +1,20 @@
+Tag: translated-default-field
+Severity: warning
+Check: debian/po-debconf
+Explanation: You should not mark as translatable "Default:" or "DefaultChoice:"
+ fields, unless explicitly needed (e.g. default country, default language,
+ etc.). If this Default field really should be translated, you should
+ explain translators how they should translate it by using comments or
+ brackets. For example:
+ .
+   # Translators: Default language name, but not translated
+   &lowbar;Default: English
+ .
+ Or:
+ .
+   &lowbar;Default: English[ Default language name, but not translated]
+ .
+ Note that in the first case, Lintian ignores the comment unless it
+ explicitly references translators and it is appears directly before
+ the field in question.
+See-Also: po-debconf(7), Bug#637881
diff --git a/tags/t/trimmed-deb822-field.tag b/tags/t/trimmed-deb822-field.tag
new file mode 100644
index 0000000..787d529
--- /dev/null
+++ b/tags/t/trimmed-deb822-field.tag
@@ -0,0 +1,6 @@
+Tag: trimmed-deb822-field
+Severity: classification
+Check: fields/deb822
+Explanation: The raw but trimmed contents of the named field in the given
+ Deb822 file. The number indicates the section from the top,
+ starting at 1.
diff --git a/tags/t/trimmed-field.tag b/tags/t/trimmed-field.tag
new file mode 100644
index 0000000..168cc3c
--- /dev/null
+++ b/tags/t/trimmed-field.tag
@@ -0,0 +1,5 @@
+Tag: trimmed-field
+Severity: classification
+Check: fields/trimmed
+Explanation: These are the raw but trimmed contents of the named field in
+ the package's primary control file.
diff --git a/tags/t/triplet-dir-and-architecture-mismatch.tag b/tags/t/triplet-dir-and-architecture-mismatch.tag
new file mode 100644
index 0000000..e1ac3d8
--- /dev/null
+++ b/tags/t/triplet-dir-and-architecture-mismatch.tag
@@ -0,0 +1,9 @@
+Tag: triplet-dir-and-architecture-mismatch
+Severity: error
+Check: files/architecture
+See-Also: debian-policy 9.1.1
+Explanation: This package contains a directory under <code>/lib</code> or
+ <code>/usr/lib</code> which doesn't match the proper triplet for the
+ binary package's architecture. This is very likely to be a mistake
+ when indicating the underlying build system where the files should be
+ installed.
diff --git a/tags/t/truetype-font-prohibits-installable-embedding.tag b/tags/t/truetype-font-prohibits-installable-embedding.tag
new file mode 100644
index 0000000..32def69
--- /dev/null
+++ b/tags/t/truetype-font-prohibits-installable-embedding.tag
@@ -0,0 +1,7 @@
+Tag: truetype-font-prohibits-installable-embedding
+Severity: warning
+Check: fonts/truetype
+Explanation: This package installs a TrueType font with restrictive license
+ terms. The font does not permit installable embedding, as defined by
+ the TrueType standard.
+See-Also: https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6OS2.html
diff --git a/tags/t/truetype-font-wrong-filename.tag b/tags/t/truetype-font-wrong-filename.tag
new file mode 100644
index 0000000..dca4250
--- /dev/null
+++ b/tags/t/truetype-font-wrong-filename.tag
@@ -0,0 +1,5 @@
+Tag: truetype-font-wrong-filename
+Severity: warning
+Check: fonts/truetype
+Explanation: This package installs a TrueType font with an extension other than
+ <code>.ttf</code>. The check is insensitive to case.
diff --git a/tags/t/typelib-in-arch-all-package.tag b/tags/t/typelib-in-arch-all-package.tag
new file mode 100644
index 0000000..b621eba
--- /dev/null
+++ b/tags/t/typelib-in-arch-all-package.tag
@@ -0,0 +1,8 @@
+Tag: typelib-in-arch-all-package
+Severity: error
+Check: desktop/gnome/gir
+Explanation: GObject-Introspection compiled typelibs
+ (<code>Foo-23.typelib</code>) are architecture-specific. They must ship in
+ architecture-dependent packages.
+See-Also:
+ /usr/share/doc/gobject-introspection/policy.txt
diff --git a/tags/t/typelib-missing-gir-depends.tag b/tags/t/typelib-missing-gir-depends.tag
new file mode 100644
index 0000000..fe17927
--- /dev/null
+++ b/tags/t/typelib-missing-gir-depends.tag
@@ -0,0 +1,9 @@
+Tag: typelib-missing-gir-depends
+Severity: warning
+Check: desktop/gnome/gir
+Explanation: GObject-Introspection compiled typelibs
+ (<code>Foo-23.typelib</code>) can depend on other typelibs. To generate
+ appropriate dependencies in the binary package, they must specify
+ <code>Depends: ${gir:Depends}</code> in the <code>control</code> file.
+See-Also:
+ /usr/share/doc/gobject-introspection/policy.txt
diff --git a/tags/t/typelib-not-in-multiarch-directory.tag b/tags/t/typelib-not-in-multiarch-directory.tag
new file mode 100644
index 0000000..f9939ce
--- /dev/null
+++ b/tags/t/typelib-not-in-multiarch-directory.tag
@@ -0,0 +1,6 @@
+Tag: typelib-not-in-multiarch-directory
+Severity: warning
+Check: desktop/gnome/gir
+Explanation: Public GObject-Introspection binary typelibs
+ (<code>Foo-23.typelib</code>) should be installed in the multi-arch
+ directory <code>/usr/lib/MULTIARCH-TUPLE/girepository-1.0</code>.
diff --git a/tags/t/typelib-package-name-does-not-match.tag b/tags/t/typelib-package-name-does-not-match.tag
new file mode 100644
index 0000000..bdde8d6
--- /dev/null
+++ b/tags/t/typelib-package-name-does-not-match.tag
@@ -0,0 +1,18 @@
+Tag: typelib-package-name-does-not-match
+Severity: warning
+Check: desktop/gnome/gir
+Explanation: GObject-Introspection binary typelibs (<code>Foo-23.typelib</code>)
+ should normally be made available in a package named gir1.2-foo-23.
+ .
+ If multiple typelibs are shipped in the same package, then that package
+ should have versioned <code>Provides</code> for the names that would have been
+ used for separate packages. This arrangement should only be used if the
+ included typelibs' versions are expected to remain the same at all times.
+ .
+ For example, <code>gir1.2-gtk-3.0</code> is named for the <code>Gtk-3.0</code>
+ typelib, but also contains the <code>Gdk-3.0</code> and <code>GdkX11-3.0</code>
+ typelibs. It should have versioned <code>Provides</code> entries for
+ <code>gir1.2-gdk-3.0 (= ${binary:Version})</code>
+ and <code>gir1.2-gdkx11-3.0 (= ${binary:Version})</code> to indicate this.
+See-Also:
+ /usr/share/doc/gobject-introspection/policy.txt
diff --git a/tags/t/typelib-section-not-introspection.tag b/tags/t/typelib-section-not-introspection.tag
new file mode 100644
index 0000000..aed2b22
--- /dev/null
+++ b/tags/t/typelib-section-not-introspection.tag
@@ -0,0 +1,10 @@
+Tag: typelib-section-not-introspection
+Severity: warning
+Check: desktop/gnome/gir
+Explanation: GObject-Introspection compiled typelibs (<code>Foo-23.typelib</code>)
+ should be made available in a GObject-Introspection package
+ in the <code>introspection</code> section of the archive.
+ .
+ Normally, it would named <code>gir1.2-foo-23</code>.
+See-Also:
+ /usr/share/doc/gobject-introspection/policy.txt
diff --git a/tags/t/typo-in-debhelper-override-target.tag b/tags/t/typo-in-debhelper-override-target.tag
new file mode 100644
index 0000000..09cd141
--- /dev/null
+++ b/tags/t/typo-in-debhelper-override-target.tag
@@ -0,0 +1,13 @@
+Tag: typo-in-debhelper-override-target
+Severity: warning
+Check: debhelper
+Explanation: The listed target in debian/rules is a likely misspelling or it is
+ missing an underscore ("&lowbar;") between the <code>override&lowbar;dh</code>,
+ <code>execute&lowbar;after&lowbar;dh</code> etc. and the command name.
+ .
+ This can result in (for example) a <code>override&lowbar;dh&lowbar;foo</code>-style target
+ silently not being executed by <code>make</code>.
+ .
+ Implementation detail: The typo is detected by using "Levenshtein
+ edit distance" so if the typo involve several characters Lintian may
+ not detect it.
diff --git a/tags/t/typo-in-manual-page.tag b/tags/t/typo-in-manual-page.tag
new file mode 100644
index 0000000..ef3d391
--- /dev/null
+++ b/tags/t/typo-in-manual-page.tag
@@ -0,0 +1,14 @@
+Tag: typo-in-manual-page
+Severity: info
+Check: documentation/manual
+Renamed-From: spelling-error-in-manpage
+Explanation: Lintian found a spelling error in a manual page. Lintian has a list
+ of common misspellings that it looks for. It does not have a
+ dictionary like a spelling checker does.
+ .
+ If the string containing the spelling error is translated with the help
+ of gettext (with the help of po4a, for example) or a similar tool,
+ please fix the error in the translations as well as the English text to
+ avoid making the translations fuzzy. With gettext, for example, this
+ means you should also fix the spelling mistake in the corresponding
+ msgids in the &ast;.po files.