Adding upstream version 2.117.0.upstream/2.117.0upstream

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

34 files changed, 302 insertions, 0 deletions

diff --git a/tags/f/FSSTND-dir-in-manual-page.tag b/tags/f/FSSTND-dir-in-manual-page.tag
new file mode 100644
index 0000000..67b08dd
--- /dev/null
+++ b/tags/f/FSSTND-dir-in-manual-page.tag
@@ -0,0 +1,10 @@
+Tag: FSSTND-dir-in-manual-page
+Severity: info
+Check: documentation/manual
+Explanation: The manual page references a directory that is specified
+ in the FSSTND but not in the FHS which is used by Debian.
+ This can be an indicator of a mismatch of the location of
+ files as installed for Debian and as described by the manual page.
+ .
+ If you have to change file locations to abide by Debian Policy
+ please also patch the manual page to mention these new locations.
diff --git a/tags/f/FSSTND-dir-in-usr.tag b/tags/f/FSSTND-dir-in-usr.tag
new file mode 100644
index 0000000..91e9e11
--- /dev/null
+++ b/tags/f/FSSTND-dir-in-usr.tag
@@ -0,0 +1,9 @@
+Tag: FSSTND-dir-in-usr
+Severity: error
+Check: files/hierarchy/standard
+Explanation: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
+ .
+ Instead, we use the Filesystem Hierarchy Standard (FHS).
+See-Also:
+ debian-policy 9.1.1,
+ filesystem-hierarchy
diff --git a/tags/f/FSSTND-dir-in-var.tag b/tags/f/FSSTND-dir-in-var.tag
new file mode 100644
index 0000000..aca3d42
--- /dev/null
+++ b/tags/f/FSSTND-dir-in-var.tag
@@ -0,0 +1,10 @@
+Tag: FSSTND-dir-in-var
+Severity: error
+Check: files/hierarchy/standard
+Explanation: As of policy version 3.0.0.0, Debian no longer follows the FSSTND.
+ .
+ Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is
+ used. You can find it in /usr/share/doc/debian-policy/fhs/ .
+See-Also:
+ debian-policy 9.1.1,
+ filesystem-hierarchy
diff --git a/tags/f/faulty-debian-qa-group-address.tag b/tags/f/faulty-debian-qa-group-address.tag
new file mode 100644
index 0000000..5883ec2
--- /dev/null
+++ b/tags/f/faulty-debian-qa-group-address.tag
@@ -0,0 +1,10 @@
+Tag: faulty-debian-qa-group-address
+Severity: error
+Check: fields/mail-address
+Renamed-From: wrong-debian-qa-address-set-as-maintainer
+Explanation: Orphaned packages should no longer have the address
+ <debian-qa@lists.debian.org> in the Maintainer field.
+ .
+ The correct Maintainer field for orphaned packages is
+ Debian QA Group <packages@qa.debian.org>.
+See-Also: developer-reference 5.9.4
diff --git a/tags/f/faulty-debian-qa-group-phrase.tag b/tags/f/faulty-debian-qa-group-phrase.tag
new file mode 100644
index 0000000..4406eee
--- /dev/null
+++ b/tags/f/faulty-debian-qa-group-phrase.tag
@@ -0,0 +1,6 @@
+Tag: faulty-debian-qa-group-phrase
+Severity: error
+Check: fields/mail-address
+Explanation: Orphaned packages should have "Debian QA Group
+ <packages@qa.debian.org>" in the maintainer field.
+See-Also: developer-reference 5.9.4
diff --git a/tags/f/field-too-long.tag b/tags/f/field-too-long.tag
new file mode 100644
index 0000000..45f943d
--- /dev/null
+++ b/tags/f/field-too-long.tag
@@ -0,0 +1,11 @@
+Tag: field-too-long
+Severity: error
+Check: fields/length
+Explanation: The length of the specified field is too long.
+ .
+ Overly-long fields not only can break some tools (e.g.
+ <code>reprepro(1)</code>) they can waste space as they are shipped to all
+ users.
+ .
+ Please reduce the number of characters.
+See-Also: Bug#942493
diff --git a/tags/f/file-contains-fixme-placeholder.tag b/tags/f/file-contains-fixme-placeholder.tag
new file mode 100644
index 0000000..ddc638a
--- /dev/null
+++ b/tags/f/file-contains-fixme-placeholder.tag
@@ -0,0 +1,9 @@
+Tag: file-contains-fixme-placeholder
+Severity: info
+Check: dh-make
+Explanation: This file appears to be incomplete or insufficiently modified as it
+ contains a "FIXME" placeholder text. These can often be generated by
+ package generation tools such as dh&lowbar;make or npm2deb.
+ .
+ Please double-check the file and replace the placeholder with the required
+ command or information.
diff --git a/tags/f/file-directly-in-usr-share-doc.tag b/tags/f/file-directly-in-usr-share-doc.tag
new file mode 100644
index 0000000..c11d863
--- /dev/null
+++ b/tags/f/file-directly-in-usr-share-doc.tag
@@ -0,0 +1,6 @@
+Tag: file-directly-in-usr-share-doc
+Severity: error
+Check: documentation
+Explanation: Documentation files have to be installed in
+ <code>/usr/share/doc/*pkg*</code>.
+See-Also: debian-policy 12.3
diff --git a/tags/f/file-directly-in-usr-share.tag b/tags/f/file-directly-in-usr-share.tag
new file mode 100644
index 0000000..c0822fb
--- /dev/null
+++ b/tags/f/file-directly-in-usr-share.tag
@@ -0,0 +1,8 @@
+Tag: file-directly-in-usr-share
+Severity: error
+Check: files/hierarchy/standard
+Explanation: Packages should not install files directly in <code>/usr/share</code>,
+ i.e., without a subdirectory.
+ .
+ You should either create a subdirectory <code>/usr/share/...</code> for your
+ package or place the file in <code>/usr/share/misc</code>.
diff --git a/tags/f/file-in-discouraged-x11-font-directory.tag b/tags/f/file-in-discouraged-x11-font-directory.tag
new file mode 100644
index 0000000..2b814a6
--- /dev/null
+++ b/tags/f/file-in-discouraged-x11-font-directory.tag
@@ -0,0 +1,10 @@
+Tag: file-in-discouraged-x11-font-directory
+Severity: warning
+Check: desktop/x11
+See-Also: debian-policy 11.8.5
+Explanation: For historical reasons, use of <code>PEX</code>, <code>CID</code>,
+ <code>Speedo</code>, and <code>cyrillic</code> subdirectories of
+ <code>/usr/share/fonts/X11</code> are permitted, but installation of files
+ into these directories is discouraged. Support for the first three font
+ types is deprecated or no longer available, and Cyrillic fonts should use
+ the normal font directories where possible.
diff --git a/tags/f/file-in-etc-not-marked-as-conffile.tag b/tags/f/file-in-etc-not-marked-as-conffile.tag
new file mode 100644
index 0000000..80d35fb
--- /dev/null
+++ b/tags/f/file-in-etc-not-marked-as-conffile.tag
@@ -0,0 +1,6 @@
+Tag: file-in-etc-not-marked-as-conffile
+Severity: error
+Check: conffiles
+See-Also: debian-policy 10.7
+Explanation: Files in <code>/etc</code> must be marked conffiles if they are included
+ in a package. Otherwise they should be created by maintainer scripts.
diff --git a/tags/f/file-in-etc-rc.d-marked-as-conffile.tag b/tags/f/file-in-etc-rc.d-marked-as-conffile.tag
new file mode 100644
index 0000000..63e8363
--- /dev/null
+++ b/tags/f/file-in-etc-rc.d-marked-as-conffile.tag
@@ -0,0 +1,5 @@
+Tag: file-in-etc-rc.d-marked-as-conffile
+Severity: error
+Check: conffiles
+See-Also: debian-policy 9.3.3
+Explanation: The symbolic links in <code>/etc/rc?.d</code> may not be marked as conffiles.
diff --git a/tags/f/file-in-root-and-usr.tag b/tags/f/file-in-root-and-usr.tag
new file mode 100644
index 0000000..ecf4401
--- /dev/null
+++ b/tags/f/file-in-root-and-usr.tag
@@ -0,0 +1,12 @@
+Tag: file-in-root-and-usr
+Severity: error
+Check: usrmerge
+Explanation: The package ships two files with the same name installed both in
+ /{bin,sbin,lib&ast;}/ and /usr/{bin,sbin,lib&ast;}/.
+ This is incompatible with the merged /usr directories scheme.
+ .
+ Packages with conflicting files must remove one of them if possible or
+ make it a symlink to the other and manage the links in the maintainer
+ scripts.
+See-Also: https://wiki.debian.org/UsrMerge,
+     https://anonscm.debian.org/cgit/users/md/usrmerge.git/plain/debian/README.Debian
diff --git a/tags/f/file-in-unknown-x11-font-directory.tag b/tags/f/file-in-unknown-x11-font-directory.tag
new file mode 100644
index 0000000..0632c31
--- /dev/null
+++ b/tags/f/file-in-unknown-x11-font-directory.tag
@@ -0,0 +1,9 @@
+Tag: file-in-unknown-x11-font-directory
+Severity: error
+Check: desktop/x11
+See-Also: debian-policy 11.8.5
+Explanation: Subdirectories of <code>/usr/share/fonts/X11</code> other than
+ <code>100dpi</code>, <code>75dpi</code>, <code>misc</code>, <code>Type1</code>, and some
+ historic exceptions must be neither created nor used. (The directories
+ <code>encodings</code> and <code>util</code>, used by some X Window System
+ packages, are also permitted by Lintian.)
diff --git a/tags/f/file-in-unusual-dir.tag b/tags/f/file-in-unusual-dir.tag
new file mode 100644
index 0000000..74ee428
--- /dev/null
+++ b/tags/f/file-in-unusual-dir.tag
@@ -0,0 +1,5 @@
+Tag: file-in-unusual-dir
+Severity: warning
+Check: files/hierarchy/standard
+Explanation: This file or symbolic link is in a directory where files are not
+ normally installed by Debian packages.
diff --git a/tags/f/file-in-usr-lib-sgml.tag b/tags/f/file-in-usr-lib-sgml.tag
new file mode 100644
index 0000000..c741348
--- /dev/null
+++ b/tags/f/file-in-usr-lib-sgml.tag
@@ -0,0 +1,7 @@
+Tag: file-in-usr-lib-sgml
+Severity: warning
+Check: files/sgml
+See-Also: filesystem-hierarchy theusrhierarchy
+Explanation: This package installs a file in <code>/usr/lib/sgml</code>. This was
+ the old location for SGML catalogs and similar flies. All those files
+ should now go into <code>/usr/share/sgml</code>.
diff --git a/tags/f/file-in-usr-lib-site-python.tag b/tags/f/file-in-usr-lib-site-python.tag
new file mode 100644
index 0000000..549df64
--- /dev/null
+++ b/tags/f/file-in-usr-lib-site-python.tag
@@ -0,0 +1,9 @@
+Tag: file-in-usr-lib-site-python
+Severity: error
+Check: languages/python
+See-Also: python-policy 2.5
+Explanation: The directory /usr/lib/site-python has been deprecated as a
+ location for installing Python modules and may be dropped from Python's
+ module search path in a future version. Most likely this module is a
+ private module and should be packaged in a directory outside of Python's
+ default search path.
diff --git a/tags/f/file-in-usr-local.tag b/tags/f/file-in-usr-local.tag
new file mode 100644
index 0000000..8b08157
--- /dev/null
+++ b/tags/f/file-in-usr-local.tag
@@ -0,0 +1,6 @@
+Tag: file-in-usr-local
+Severity: error
+Check: files/hierarchy/standard
+Explanation: The package installs a file in <code>/usr/local/...</code> which is
+ not allowed.
+See-Also: debian-policy 9.1.2
diff --git a/tags/f/file-in-usr-marked-as-conffile.tag b/tags/f/file-in-usr-marked-as-conffile.tag
new file mode 100644
index 0000000..8d68d1c
--- /dev/null
+++ b/tags/f/file-in-usr-marked-as-conffile.tag
@@ -0,0 +1,8 @@
+Tag: file-in-usr-marked-as-conffile
+Severity: error
+Check: conffiles
+See-Also: debian-policy 10.7.2
+Explanation: All configuration files must reside in <code>/etc</code>. Files below
+ <code>/usr</code> may not be marked as conffiles since <code>/usr</code> might be
+ mounted read-only. The local system administrator would therefore not
+ have a chance to modify this configuration file.
diff --git a/tags/f/file-included-already.tag b/tags/f/file-included-already.tag
new file mode 100644
index 0000000..7ef8067
--- /dev/null
+++ b/tags/f/file-included-already.tag
@@ -0,0 +1,11 @@
+Tag: file-included-already
+Severity: error
+Check: debian/copyright/dep5
+Explanation: The Debian <code>copyright</code> notes included files with the
+ <code>Files-Included</code> field, but the given file would have been shipped
+ without it.
+ .
+ The wildcards in the field may be too broad. Please narrow the criteria for
+ files included in the field <code>Files-Included</code>.
+See-also:
+ https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
diff --git a/tags/f/file-missing-in-md5sums.tag b/tags/f/file-missing-in-md5sums.tag
new file mode 100644
index 0000000..c79efa0
--- /dev/null
+++ b/tags/f/file-missing-in-md5sums.tag
@@ -0,0 +1,9 @@
+Tag: file-missing-in-md5sums
+Severity: warning
+Check: md5sums
+Explanation: The package contains a file which isn't listed in the md5sums control
+ file.
+ .
+ Usually, this error occurs during the package build process if the
+ <code>debian/tmp/</code> directory is touched after <code>dh&lowbar;md5sums</code>
+ is run.
diff --git a/tags/f/file-name-contains-wildcard-character.tag b/tags/f/file-name-contains-wildcard-character.tag
new file mode 100644
index 0000000..9bb82a5
--- /dev/null
+++ b/tags/f/file-name-contains-wildcard-character.tag
@@ -0,0 +1,7 @@
+Tag: file-name-contains-wildcard-character
+Severity: warning
+Check: files/names
+Explanation: The file name contains shell wildcard characters.
+ .
+ These are most likely unexpanded wildcard characters from (for example)
+ <code>debian/&ast;.install</code> files, or it may have been installed by accident.
diff --git a/tags/f/file-name-ends-in-whitespace.tag b/tags/f/file-name-ends-in-whitespace.tag
new file mode 100644
index 0000000..ebf50ad
--- /dev/null
+++ b/tags/f/file-name-ends-in-whitespace.tag
@@ -0,0 +1,10 @@
+Tag: file-name-ends-in-whitespace
+Severity: warning
+Check: files/names
+Explanation: This package installs a file or directory whose name ends in
+ whitespace. This might be intentional but it's normally a mistake. If
+ it is intentional, add a Lintian override.
+ .
+ One possible cause is using Debhelper 5.0.57 or earlier to install a
+ <code>doc-base</code> file with a <code>Document</code> field that ends
+ in whitespace.
diff --git a/tags/f/file-name-in-PATH-is-not-ASCII.tag b/tags/f/file-name-in-PATH-is-not-ASCII.tag
new file mode 100644
index 0000000..d40a587
--- /dev/null
+++ b/tags/f/file-name-in-PATH-is-not-ASCII.tag
@@ -0,0 +1,8 @@
+Tag: file-name-in-PATH-is-not-ASCII
+Severity: error
+Check: files/names
+See-Also: debian-policy 10.10
+Explanation: The given file is in PATH but consists of non-ASCII characters.
+ .
+ Note that Lintian may be unable to display the filename accurately.
+ Unprintable characters may have been replaced.
diff --git a/tags/f/file-references-package-build-path.tag b/tags/f/file-references-package-build-path.tag
new file mode 100644
index 0000000..5e8c533
--- /dev/null
+++ b/tags/f/file-references-package-build-path.tag
@@ -0,0 +1,18 @@
+Tag: file-references-package-build-path
+Severity: info
+Check: files/contents
+Explanation: The listed file or maintainer script appears to reference
+ the build path used to build the package as specified in the
+ <code>Build-Path</code> field of the <code>.buildinfo</code> file.
+ .
+ This is likely to cause the package to be unreproducible, but it may
+ also indicate that the package will not work correctly outside of the
+ maintainer's own system.
+ .
+ Please note that this tag will not appear unless the
+ <code>.buildinfo</code> file contains a <code>Build-Path</code> field. That
+ field is optional. You may have to set
+ <code>DEB&lowbar;BUILD&lowbar;OPTIONS=buildinfo=+path</code> or use
+ <code>--buildinfo-option=--always-include-path</code> with
+ <code>dpkg-buildpackage</code> when building.
+See-Also: https://reproducible-builds.org/, https://wiki.debian.org/ReproducibleBuilds/BuildinfoFiles, dpkg-genbuildinfo(1)
diff --git a/tags/f/file-size-mismatch-in-changes-file.tag b/tags/f/file-size-mismatch-in-changes-file.tag
new file mode 100644
index 0000000..cbaf49a
--- /dev/null
+++ b/tags/f/file-size-mismatch-in-changes-file.tag
@@ -0,0 +1,6 @@
+Tag: file-size-mismatch-in-changes-file
+Severity: error
+Check: changes-file
+Explanation: The actual file size does not match what's listed in the
+ <code>.changes</code> file.
+See-Also: debian-policy 5.6.21, debian-policy 5.6.24
diff --git a/tags/f/file-without-copyright-information.tag b/tags/f/file-without-copyright-information.tag
new file mode 100644
index 0000000..5ac3b34
--- /dev/null
+++ b/tags/f/file-without-copyright-information.tag
@@ -0,0 +1,7 @@
+Tag: file-without-copyright-information
+Severity: warning
+Check: debian/copyright/dep5
+See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Explanation: The source tree contains a file which was not matched by any of
+ the <code>Files</code> paragraphs in debian/copyright. Either adjust existing
+ wildcards to match that file or add a new <code>Files</code> paragraph.
diff --git a/tags/f/files-excluded-without-copyright-format-1.0.tag b/tags/f/files-excluded-without-copyright-format-1.0.tag
new file mode 100644
index 0000000..a49b47a
--- /dev/null
+++ b/tags/f/files-excluded-without-copyright-format-1.0.tag
@@ -0,0 +1,15 @@
+Tag: files-excluded-without-copyright-format-1.0
+Severity: error
+Check: debian/copyright/dep5
+Explanation: The <code>Files-Excluded</code> field in <code>debian/copyright</code> is
+ used to exclude files from upstream source packages such as when they
+ violate the Debian Free Software Guidelines
+ .
+ However, this field will be ignored by uscan(1) if the <code>copyright</code>
+ file is not declared as following the <code>1.0</code> format.
+ .
+ Please ensure your <code>debian/copyright</code> file starts with the
+ following line:
+ .
+   Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+See-Also: uscan(1)
diff --git a/tags/f/font-in-non-font-package.tag b/tags/f/font-in-non-font-package.tag
new file mode 100644
index 0000000..7308ac3
--- /dev/null
+++ b/tags/f/font-in-non-font-package.tag
@@ -0,0 +1,11 @@
+Tag: font-in-non-font-package
+Severity: info
+Check: fonts
+Explanation: This package contains a &ast;.ttf, &ast;.otf, or &ast;.pfb file, file
+ extensions used by TrueType, OpenType, or Type 1 fonts, but the package
+ does not appear to be a dedicated font package. Dedicated font package
+ names should begin with <code>fonts-</code>. (Type 1 fonts are also allowed
+ in packages starting with <code>xfonts-</code>.) If the font is already
+ packaged, you should depend on that package instead. Otherwise, normally
+ the font should be packaged separately, since fonts are usually useful
+ outside of the package that embeds them.
diff --git a/tags/f/font-outside-font-dir.tag b/tags/f/font-outside-font-dir.tag
new file mode 100644
index 0000000..6df6def
--- /dev/null
+++ b/tags/f/font-outside-font-dir.tag
@@ -0,0 +1,6 @@
+Tag: font-outside-font-dir
+Severity: info
+Check: fonts
+Explanation: This package contains a TrueType, OpenType, or Type 1 fonts,
+ but the package does not install this file under <code>/usr/share/fonts/</code>.
+See-Also: https://wiki.debian.org/Fonts/PackagingPolicy
diff --git a/tags/f/font-package-not-multi-arch-foreign.tag b/tags/f/font-package-not-multi-arch-foreign.tag
new file mode 100644
index 0000000..eae3589
--- /dev/null
+++ b/tags/f/font-package-not-multi-arch-foreign.tag
@@ -0,0 +1,10 @@
+Tag: font-package-not-multi-arch-foreign
+Severity: warning
+Check: fields/multi-arch
+Explanation: This package is architecture all and hence requires a Multi-Arch
+ foreign value.
+ .
+ An Architecture: all package to satisfy the dependencies of a
+ foreign-architecture package, it must be marked Multi-Arch: foreign
+ or Multi-Arch: allowed.
+See-Also: https://wiki.ubuntu.com/MultiarchSpec#Dependencies_involving_Architecture:_all_packages
diff --git a/tags/f/forbidden-config-interpreter.tag b/tags/f/forbidden-config-interpreter.tag
new file mode 100644
index 0000000..e48ca3c
--- /dev/null
+++ b/tags/f/forbidden-config-interpreter.tag
@@ -0,0 +1,7 @@
+Tag: forbidden-config-interpreter
+Severity: error
+Check: scripts
+Explanation: This package contains a <code>config</code> script for pre-configuring
+ the package. During pre-configuration, however, only essential packages
+ are guaranteed to be installed, so you cannot use a non-essential
+ interpreter.
diff --git a/tags/f/forbidden-postrm-interpreter.tag b/tags/f/forbidden-postrm-interpreter.tag
new file mode 100644
index 0000000..622a75b
--- /dev/null
+++ b/tags/f/forbidden-postrm-interpreter.tag
@@ -0,0 +1,9 @@
+Tag: forbidden-postrm-interpreter
+Severity: error
+Check: scripts
+Explanation: This package contains a <code>postrm</code> maintainer script that uses
+ an interpreter that isn't essential. The <code>purge</code> action of
+ <code>postrm</code> can only rely on essential packages, which means the
+ interpreter used by <code>postrm</code> must be one of the essential ones
+ (<code>sh</code>, <code>bash</code>, or <code>perl</code>).
+See-Also: debian-policy 7.2
diff --git a/tags/f/format-3.0-but-debian-changes-patch.tag b/tags/f/format-3.0-but-debian-changes-patch.tag
new file mode 100644
index 0000000..40cc5a0
--- /dev/null
+++ b/tags/f/format-3.0-but-debian-changes-patch.tag
@@ -0,0 +1,12 @@
+Tag: format-3.0-but-debian-changes-patch
+Severity: warning
+Check: debian/patches/quilt
+Explanation: This package declares source format 3.0 (quilt), but the Debian
+ .debian.tar.gz file contains a debian-changes-VERSION patch, which represents
+ direct changes to files outside of the <code>debian</code> directory. This often
+ indicates accidental changes that weren't meant to be in the package or changes
+ that were supposed to be separated out into a patch.
+ .
+ If this is intentional, you may wish to consider adding
+ <code>single-debian-patch</code> to <code>debian/source/options</code>, and/or a patch
+ header to <code>debian/source/patch-header</code> explaining why this is done.