diff options
Diffstat (limited to 'tags/i')
79 files changed, 824 insertions, 0 deletions
diff --git a/tags/i/icon-size-and-directory-name-mismatch.tag b/tags/i/icon-size-and-directory-name-mismatch.tag new file mode 100644 index 0000000..2865a35 --- /dev/null +++ b/tags/i/icon-size-and-directory-name-mismatch.tag @@ -0,0 +1,6 @@ +Tag: icon-size-and-directory-name-mismatch +Severity: warning +Check: desktop/icons +Explanation: The icon has a size that differs from the size specified by the name + of the directory under which it was installed. The icon was probably + mistakenly installed into the wrong directory. diff --git a/tags/i/illegal-multi-arch-value.tag b/tags/i/illegal-multi-arch-value.tag new file mode 100644 index 0000000..0911275 --- /dev/null +++ b/tags/i/illegal-multi-arch-value.tag @@ -0,0 +1,7 @@ +Tag: illegal-multi-arch-value +Severity: error +Check: fields/multi-arch +Explanation: The package is architecture all and has the Multi-Arch same value. + . + This combination is not allowed by the Multi-Arch specification. +See-Also: https://wiki.ubuntu.com/MultiarchSpec diff --git a/tags/i/illegal-runtime-test-name.tag b/tags/i/illegal-runtime-test-name.tag new file mode 100644 index 0000000..315a84d --- /dev/null +++ b/tags/i/illegal-runtime-test-name.tag @@ -0,0 +1,7 @@ +Tag: illegal-runtime-test-name +Severity: warning +Check: testsuite +Explanation: Runtime test names in debian/tests/control are only allowed to + contain decimal digits, lowercase ASCII letters, plus or minus signs, + dots or slashes. +See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff --git a/tags/i/illegal-variable.tag b/tags/i/illegal-variable.tag new file mode 100644 index 0000000..74dd973 --- /dev/null +++ b/tags/i/illegal-variable.tag @@ -0,0 +1,21 @@ +Tag: illegal-variable +Severity: error +Check: debian/variables +Explanation: With debhelper compatibility level >= 13 (and also + <code>dh-exec</code> before it) several files in the + <code>./debian</code> folder support the expansion of variables. + Unfortunately, people sometimes confuse the + <code>DEB_BUILD_*</code> + variables with the similarly-named + <code>DEB_HOST_*</code> variables. + . + Some conditions are difficult to detect but it is never correct + to use <code>DEB_BUILD_MULTIARCH</code> in + <code>debian/*.install</code> or in + <code>debian/*.links</code>. + . + Please use <code>DEB_HOST_MULTIARCH</code> instead + of <code>DEB_BUILD_MULTIARCH</code>. +See-Also: + https://wiki.debian.org/Multiarch/Implementation#Recipes_for_converting_packages, + Bug#983219 diff --git a/tags/i/image-file-has-conflicting-name.tag b/tags/i/image-file-has-conflicting-name.tag new file mode 100644 index 0000000..092e590 --- /dev/null +++ b/tags/i/image-file-has-conflicting-name.tag @@ -0,0 +1,6 @@ +Tag: image-file-has-conflicting-name +Severity: info +Check: images/filenames +Explanation: An image file in this package has a name that is + usually associated with another image format. +See-Also: Bug#717818 diff --git a/tags/i/image-file-has-unexpected-name.tag b/tags/i/image-file-has-unexpected-name.tag new file mode 100644 index 0000000..0bbfc2b --- /dev/null +++ b/tags/i/image-file-has-unexpected-name.tag @@ -0,0 +1,6 @@ +Tag: image-file-has-unexpected-name +Severity: pedantic +Check: images/filenames +Explanation: An image file in this package has a name not generally + associated with its format. +See-Also: Bug#717818 diff --git a/tags/i/image-file-in-usr-lib.tag b/tags/i/image-file-in-usr-lib.tag new file mode 100644 index 0000000..666bb56 --- /dev/null +++ b/tags/i/image-file-in-usr-lib.tag @@ -0,0 +1,6 @@ +Tag: image-file-in-usr-lib +Severity: pedantic +Check: images +Explanation: This package installs a pixmap or a bitmap within <code>/usr/lib</code>. + According to the Filesystem Hierarchy Standard, architecture-independent + files should be placed within <code>/usr/share</code> instead. diff --git a/tags/i/improbable-bug-number-in-closes.tag b/tags/i/improbable-bug-number-in-closes.tag new file mode 100644 index 0000000..26f5a04 --- /dev/null +++ b/tags/i/improbable-bug-number-in-closes.tag @@ -0,0 +1,6 @@ +Tag: improbable-bug-number-in-closes +Severity: warning +Check: debian/changelog +Explanation: The most recent changelog closes a low-numbered bug number. + While this is distantly possible, it's more likely a typo or a + placeholder value that mistakenly wasn't filled in. diff --git a/tags/i/incompatible-java-bytecode-format.tag b/tags/i/incompatible-java-bytecode-format.tag new file mode 100644 index 0000000..aea1761 --- /dev/null +++ b/tags/i/incompatible-java-bytecode-format.tag @@ -0,0 +1,7 @@ +Tag: incompatible-java-bytecode-format +Severity: warning +Check: languages/java +Explanation: The package contains Java class files with a minimum requirement on the + listed Java version. This Java version is not supported by the default JVM + in Debian and is therefore likely to be a mistake. +See-Also: Bug#673276 diff --git a/tags/i/incomplete-creative-commons-license.tag b/tags/i/incomplete-creative-commons-license.tag new file mode 100644 index 0000000..86be15b --- /dev/null +++ b/tags/i/incomplete-creative-commons-license.tag @@ -0,0 +1,23 @@ +Tag: incomplete-creative-commons-license +Severity: warning +Check: debian/copyright/dep5 +Explanation: The package appears to be licensed under a Creative Commons + license but only includes the human-readable summary in the + debian/copyright file which is not the actual licence. The Creative + Commons webpages contains the following disclaimer: + . + This deed highlights only some of the key features and terms of the + actual license. It is not a license and has no legal value. You should + carefully review all of the terms and conditions of the actual license + before using the licensed material. + . + Creative Commons is not a law firm and does not provide legal + services. Distributing, displaying, or linking to this deed or the + license that it summarizes does not create a lawyer-client or any + other relationship. + . + Please use the full, plain-text version of the license text which may + be found here: + . + https://creativecommons.org/2014/01/07/plaintext-versions-of-creative-commons-4-0-licenses/ +See-Also: Bug#903470, Bug#795402 diff --git a/tags/i/inconsistent-appstream-metadata-license.tag b/tags/i/inconsistent-appstream-metadata-license.tag new file mode 100644 index 0000000..03680a9 --- /dev/null +++ b/tags/i/inconsistent-appstream-metadata-license.tag @@ -0,0 +1,10 @@ +Tag: inconsistent-appstream-metadata-license +Severity: warning +Check: debian/copyright/dep5 +Explanation: The specified AppStream metadata file specifies a + <code>metadata_license</code> field but this does not match + its entry (possibly via the <code>Files: *</code> stanza) in + <code>debian/copyright</code>. +See-Also: https://wiki.debian.org/AppStream/Guidelines, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/, + https://www.freedesktop.org/software/appstream/docs/chap-Metadata.html#tag-metadata_license diff --git a/tags/i/inconsistent-maintainer.tag b/tags/i/inconsistent-maintainer.tag new file mode 100644 index 0000000..ea85a19 --- /dev/null +++ b/tags/i/inconsistent-maintainer.tag @@ -0,0 +1,10 @@ +Tag: inconsistent-maintainer +Severity: error +Check: fields/maintainer +Explanation: The Maintainer address in a group of related processables is + inconsistent as indicated. + . + This sometimes happens when environmental variables like <code>DEBEMAIL</code> + are set to different values when building sources and changes separately. + Please use the same maintainer everywhere. +See-Also: Bug#546525, https://wiki.ubuntu.com/DebianMaintainerField, Ubuntu Bug#1862787 diff --git a/tags/i/incorrect-libdir-in-la-file.tag b/tags/i/incorrect-libdir-in-la-file.tag new file mode 100644 index 0000000..a09daa9 --- /dev/null +++ b/tags/i/incorrect-libdir-in-la-file.tag @@ -0,0 +1,8 @@ +Tag: incorrect-libdir-in-la-file +Severity: error +Check: build-systems/libtool/la-file +Explanation: The given .la file points to a libdir other than the path where it is + installed. This can be caused by resetting <code>prefix</code> at make install + time instead of using <code>DESTDIR</code>. The incorrect path will cause + packages linking to this library using libtool to build incorrectly (adding + incorrect paths to RPATH, for example). diff --git a/tags/i/incorrect-locale-code.tag b/tags/i/incorrect-locale-code.tag new file mode 100644 index 0000000..f4cdb53 --- /dev/null +++ b/tags/i/incorrect-locale-code.tag @@ -0,0 +1,15 @@ +Tag: incorrect-locale-code +Severity: warning +Check: files/locales +Explanation: The package appears to ship locales for a language but uses an + incorrect locale code as a subdirectory of <code>/usr/share/locale</code>. + This usually results in users of the intended target language not + finding the locale. The language codes used in the locale directories + are those from the ISO 639-1 and ISO 639-2 standards, not those + usually used as TLDs (which are from the ISO 3166 standard). + . + When both standards define a language code for a given language, the + ISO 639-1 code should be used (i.e. the two lettered code). + . + Lintian only knows about some commonly-mistaken set of incorrect + locale codes. diff --git a/tags/i/incorrect-naming-of-pkcs11-module.tag b/tags/i/incorrect-naming-of-pkcs11-module.tag new file mode 100644 index 0000000..4e5477f --- /dev/null +++ b/tags/i/incorrect-naming-of-pkcs11-module.tag @@ -0,0 +1,11 @@ +Tag: incorrect-naming-of-pkcs11-module +Severity: error +Check: files/p11-kit +Explanation: This package ships a PKCS#11 module configuration file under + <code>/usr/share/p11-kit/modules</code>, but its naming doesn't conform + to what <code>p11-kit</code> expects. Files in that directory should + respect the following convention, case insensitive: + [a-z0-9][a-z0-9_.-]*.module + . + p11-kit currently warns on every file that does not follow the + convention and may ignore them in the future. diff --git a/tags/i/incorrect-packaging-filename.tag b/tags/i/incorrect-packaging-filename.tag new file mode 100644 index 0000000..6a1045b --- /dev/null +++ b/tags/i/incorrect-packaging-filename.tag @@ -0,0 +1,16 @@ +Tag: incorrect-packaging-filename +Severity: warning +Check: debian/filenames +Explanation: Some packaging files obtain different names when they are copied + from source to installation packages. Debhelper sometimes adds *.Debian + extensions to NEWS, README and TODO files. That can be confusing. + . + Debhelper's behavior also depends on the filename. + . + This source package contains a file that debhelper will not find. The + file will not be included in your installation packages. Important + information, such as incompatibilties on upgrades, may not reach your + users. + . + Please rename the file as indicated. +See-Also: Bug#429510, Bug#946126, Bug#946041 diff --git a/tags/i/incorrect-path-for-interpreter.tag b/tags/i/incorrect-path-for-interpreter.tag new file mode 100644 index 0000000..4425dff --- /dev/null +++ b/tags/i/incorrect-path-for-interpreter.tag @@ -0,0 +1,13 @@ +Tag: incorrect-path-for-interpreter +Severity: warning +Check: scripts +Explanation: The interpreter you used is installed at another location on Debian + systems. + . + Whilst the script may work, it is in violation of Debian Policy. This + may have been caused by usrmerge. + . + Note that, as a particular exception, Debian Policy § 10.4 states that + Perl scripts should use <code>/usr/bin/perl</code> directly and not + <code>/usr/bin/env</code>, etc. +See-Also: debian-policy 10.4, https://wiki.debian.org/UsrMerge diff --git a/tags/i/info-document-has-wrong-extension.tag b/tags/i/info-document-has-wrong-extension.tag new file mode 100644 index 0000000..f0f6eda --- /dev/null +++ b/tags/i/info-document-has-wrong-extension.tag @@ -0,0 +1,4 @@ +Tag: info-document-has-wrong-extension +Severity: warning +Check: documentation/texinfo +Explanation: The info document has an extension other than info*.gz. diff --git a/tags/i/info-document-missing-dir-entry.tag b/tags/i/info-document-missing-dir-entry.tag new file mode 100644 index 0000000..62115e3 --- /dev/null +++ b/tags/i/info-document-missing-dir-entry.tag @@ -0,0 +1,16 @@ +Tag: info-document-missing-dir-entry +Severity: error +Check: documentation/texinfo +Explanation: This info document has no directory entry. This is text between + START-INFO-DIR-ENTRY and END-INFO-DIR-ENTRY lines which is copied into + the <code>dir</code> file in <code>/usr/share/info</code> by + <code>install-info</code>. The best solution is to add lines like: + . + @dircategory Software development + @direntry + * foo: (foo). Foo creator and editor + @end direntry + . + to the texinfo source so that the generated info file will contain an + appropriate entry. You will have to ensure that the build process builds + new info files rather than using ones built by upstream. diff --git a/tags/i/info-document-missing-dir-section.tag b/tags/i/info-document-missing-dir-section.tag new file mode 100644 index 0000000..3d7eb88 --- /dev/null +++ b/tags/i/info-document-missing-dir-section.tag @@ -0,0 +1,13 @@ +Tag: info-document-missing-dir-section +Severity: error +Check: documentation/texinfo +Explanation: This info document has no INFO-DIR-SECTION line. + <code>install-info</code> will be unable to determine the section into which + this info page should be put. The best solution is to add a line like: + . + @dircategory Software development + . + to the texinfo source so that the generated info file will contain a + section. See <code>/usr/share/info/dir</code> for sections to choose from. + You will have to ensure that the build process builds new info files + rather than using ones built by upstream. diff --git a/tags/i/info-document-missing-image-file.tag b/tags/i/info-document-missing-image-file.tag new file mode 100644 index 0000000..469a67a --- /dev/null +++ b/tags/i/info-document-missing-image-file.tag @@ -0,0 +1,19 @@ +Tag: info-document-missing-image-file +Severity: warning +Check: documentation/texinfo +Explanation: This info document contains an "[image]" but the image file it + specifies is missing. Texinfo <code>@image{}</code> becomes + . + [image src="filename.png"] + . + in the <code>.info</code>. Emacs 22 and up info + mode can display this in a GUI if filename.png is in + <code>/usr/share/info</code> or if the src gives a path to the file + elsewhere. + . + If you put an image file in <code>/usr/share/info</code> then please name + it like the document so as to avoid name clashes. Eg. foo.info might + call an image foo-example1.png. If upstream does not do this already + then it may be easier to <code>sed</code> the <code>src=""</code> to a path + elsewhere, perhaps to share with an HTML rendition under say + <code>/usr/share/doc/foo/html/</code>. diff --git a/tags/i/info-document-not-compressed-with-gzip.tag b/tags/i/info-document-not-compressed-with-gzip.tag new file mode 100644 index 0000000..e06929c --- /dev/null +++ b/tags/i/info-document-not-compressed-with-gzip.tag @@ -0,0 +1,7 @@ +Tag: info-document-not-compressed-with-gzip +Severity: error +Check: documentation/texinfo +Explanation: Info documents should be compressed with <code>gzip -9n</code>. This + file ends in <code>.gz</code> but doesn't appear to be a gzip-compressed + file. +See-Also: debian-policy 12.2 diff --git a/tags/i/info-document-not-compressed-with-max-compression.tag b/tags/i/info-document-not-compressed-with-max-compression.tag new file mode 100644 index 0000000..7326198 --- /dev/null +++ b/tags/i/info-document-not-compressed-with-max-compression.tag @@ -0,0 +1,6 @@ +Tag: info-document-not-compressed-with-max-compression +Severity: error +Check: documentation/texinfo +Explanation: Info documents should be compressed with <code>gzip -9n</code>. This + file is compressed with gzip, but without using maximum compression. +See-Also: debian-policy 12.2 diff --git a/tags/i/info-document-not-compressed.tag b/tags/i/info-document-not-compressed.tag new file mode 100644 index 0000000..bc1f982 --- /dev/null +++ b/tags/i/info-document-not-compressed.tag @@ -0,0 +1,5 @@ +Tag: info-document-not-compressed +Severity: error +Check: documentation/texinfo +Explanation: Info documents should be compressed with <code>gzip -9n</code>. +See-Also: debian-policy 12.2 diff --git a/tags/i/init-d-script-stops-in-s-runlevel.tag b/tags/i/init-d-script-stops-in-s-runlevel.tag new file mode 100644 index 0000000..5f6dd27 --- /dev/null +++ b/tags/i/init-d-script-stops-in-s-runlevel.tag @@ -0,0 +1,8 @@ +Tag: init-d-script-stops-in-s-runlevel +Severity: warning +Check: init-d +Explanation: This <code>/etc/init.d</code> script specifies the S runlevel in + Default-Stop in its LSB keyword section. The S runlevel is not a real + runlevel and is only used during boot. There is no way to switch to it + and hence no use for stop scripts for it, so S should be removed from + Default-Stop. diff --git a/tags/i/init-script-is-not-a-file.tag b/tags/i/init-script-is-not-a-file.tag new file mode 100644 index 0000000..20cd1bf --- /dev/null +++ b/tags/i/init-script-is-not-a-file.tag @@ -0,0 +1,5 @@ +Tag: init-script-is-not-a-file +Severity: error +Check: systemd +Explanation: The package contains an init script that is not a regular file or + resolvable symlink. diff --git a/tags/i/init.d-script-contains-skeleton-template-content.tag b/tags/i/init.d-script-contains-skeleton-template-content.tag new file mode 100644 index 0000000..bc06f66 --- /dev/null +++ b/tags/i/init.d-script-contains-skeleton-template-content.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-contains-skeleton-template-content +Severity: error +Check: init-d +Explanation: The given init script appears to contain content from the + <code>/etc/init.d/skeleton</code> example. + . + Please double-check the script and/or replace it with content suitable to + this binary package. diff --git a/tags/i/init.d-script-depends-on-all-virtual-facility.tag b/tags/i/init.d-script-depends-on-all-virtual-facility.tag new file mode 100644 index 0000000..6b7e304 --- /dev/null +++ b/tags/i/init.d-script-depends-on-all-virtual-facility.tag @@ -0,0 +1,9 @@ +Tag: init.d-script-depends-on-all-virtual-facility +Severity: error +Check: init-d +Explanation: The given init script declares a dependency on the virtual + facility "$all". This virtual facility is reserved for very special + cases, that work specifically with init system. + . + Regular services should not use this facility. +See-Also: https://wiki.debian.org/LSBInitScripts diff --git a/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag b/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag new file mode 100644 index 0000000..de3ff7c --- /dev/null +++ b/tags/i/init.d-script-depends-on-unknown-virtual-facility.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-depends-on-unknown-virtual-facility +Severity: error +Check: init-d +Explanation: The given init script declares a dependency on a virtual facility + that is not known to be provided by any init.d script in the archive. + If the dependency cannot be satisfied upon the package's + installation, insserv will refuse the activation of the init.d script. +See-Also: https://wiki.debian.org/LSBInitScripts diff --git a/tags/i/init.d-script-does-not-implement-required-option.tag b/tags/i/init.d-script-does-not-implement-required-option.tag new file mode 100644 index 0000000..0d1653e --- /dev/null +++ b/tags/i/init.d-script-does-not-implement-required-option.tag @@ -0,0 +1,6 @@ +Tag: init.d-script-does-not-implement-required-option +Severity: error +Check: init-d +See-Also: debian-policy 9.3.2 +Explanation: The <code>/etc/init.d</code> scripts have to support the following + command line arguments: start, stop, restart, force-reload. diff --git a/tags/i/init.d-script-does-not-implement-status-option.tag b/tags/i/init.d-script-does-not-implement-status-option.tag new file mode 100644 index 0000000..a693edd --- /dev/null +++ b/tags/i/init.d-script-does-not-implement-status-option.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-does-not-implement-status-option +Severity: info +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: The specified <code>/etc/init.d</code> script does not implement the + <code>status</code> option. This is actually required by LSB, often + requested by users and will be required by the Debian Policy in + the future. diff --git a/tags/i/init.d-script-does-not-provide-itself.tag b/tags/i/init.d-script-does-not-provide-itself.tag new file mode 100644 index 0000000..e9bc72a --- /dev/null +++ b/tags/i/init.d-script-does-not-provide-itself.tag @@ -0,0 +1,9 @@ +Tag: init.d-script-does-not-provide-itself +Severity: info +Check: init-d +Explanation: This <code>/etc/init.d</code> script indicates it provides one or + more facilities, but none of the provided facilities match the name of + the init script. In certain cases, it may be necessary to not follow + that convention, but normally init scripts should always provide a + facility matching the name of the init script. +See-Also: https://wiki.debian.org/LSBInitScripts diff --git a/tags/i/init.d-script-does-not-source-init-functions.tag b/tags/i/init.d-script-does-not-source-init-functions.tag new file mode 100644 index 0000000..9b7a823 --- /dev/null +++ b/tags/i/init.d-script-does-not-source-init-functions.tag @@ -0,0 +1,11 @@ +Tag: init.d-script-does-not-source-init-functions +Severity: warning +Check: systemd +Explanation: The <code>/etc/init.d</code> script does not source + <code>/lib/lsb/init-functions</code>. The <code>systemd</code> package provides + <code>/lib/lsb/init-functions.d/40-systemd</code> to redirect + <code>/etc/init.d/$script</code> calls to systemctl. + . + Please add a line like this to your <code>/etc/init.d</code> script: + . + . /lib/lsb/init-functions diff --git a/tags/i/init.d-script-has-bad-lsb-line.tag b/tags/i/init.d-script-has-bad-lsb-line.tag new file mode 100644 index 0000000..e2bab8e --- /dev/null +++ b/tags/i/init.d-script-has-bad-lsb-line.tag @@ -0,0 +1,10 @@ +Tag: init.d-script-has-bad-lsb-line +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: This line in the LSB keyword section of an <code>/etc/init.d</code> + script doesn't match the required formatting of that section. Note that + keyword settings must start with <code>#</code>, a single space, the keyword, + a colon, and some whitespace, followed by the value (if any). Only the + Description keyword allows continuation lines, and continuation lines + must begin with <code>#</code> and either a tab or two or more spaces. diff --git a/tags/i/init.d-script-has-bad-start-runlevel.tag b/tags/i/init.d-script-has-bad-start-runlevel.tag new file mode 100644 index 0000000..8f7652f --- /dev/null +++ b/tags/i/init.d-script-has-bad-start-runlevel.tag @@ -0,0 +1,7 @@ +Tag: init.d-script-has-bad-start-runlevel +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: The given runlevel specified in the Default-Start keyword of the LSB + keyword section of this <code>/etc/init.d</code> script isn't one of the + recognized standard runlevels (S, 0, 1, 2, 3, 4, 5, and 6). diff --git a/tags/i/init.d-script-has-bad-stop-runlevel.tag b/tags/i/init.d-script-has-bad-stop-runlevel.tag new file mode 100644 index 0000000..9fec931 --- /dev/null +++ b/tags/i/init.d-script-has-bad-stop-runlevel.tag @@ -0,0 +1,7 @@ +Tag: init.d-script-has-bad-stop-runlevel +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: The given runlevel specified in the Default-Stop keyword of the LSB + keyword section of this <code>/etc/init.d</code> script isn't one of the + recognized standard runlevels (0, 1, 2, 3, 4, 5, and 6). diff --git a/tags/i/init.d-script-has-conflicting-start-stop.tag b/tags/i/init.d-script-has-conflicting-start-stop.tag new file mode 100644 index 0000000..6d027b5 --- /dev/null +++ b/tags/i/init.d-script-has-conflicting-start-stop.tag @@ -0,0 +1,9 @@ +Tag: init.d-script-has-conflicting-start-stop +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: The given runlevel was included in both the Default-Start and + Default-Stop keywords of the LSB keyword section of this + <code>/etc/init.d</code> script. Since it doesn't make sense to both start + and stop a service in the same runlevel, there is probably an error in + one or the other of these keywords. diff --git a/tags/i/init.d-script-has-duplicate-lsb-keyword.tag b/tags/i/init.d-script-has-duplicate-lsb-keyword.tag new file mode 100644 index 0000000..3006758 --- /dev/null +++ b/tags/i/init.d-script-has-duplicate-lsb-keyword.tag @@ -0,0 +1,7 @@ +Tag: init.d-script-has-duplicate-lsb-keyword +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: The given keyword was set twice in the LSB keyword section in this + <code>/etc/init.d</code> script. This is probably a mistake; the behavior of + setting the same keyword twice is undefined. diff --git a/tags/i/init.d-script-has-duplicate-lsb-section.tag b/tags/i/init.d-script-has-duplicate-lsb-section.tag new file mode 100644 index 0000000..4e32eb3 --- /dev/null +++ b/tags/i/init.d-script-has-duplicate-lsb-section.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-has-duplicate-lsb-section +Severity: error +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: This <code>/etc/init.d</code> script has more than one LSB keyword + section. These sections start with <code>### BEGIN INIT INFO</code> and end + with <code>### END INIT INFO</code>. There should be only one such section + per init script. diff --git a/tags/i/init.d-script-has-unknown-lsb-keyword.tag b/tags/i/init.d-script-has-unknown-lsb-keyword.tag new file mode 100644 index 0000000..f743f17 --- /dev/null +++ b/tags/i/init.d-script-has-unknown-lsb-keyword.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-has-unknown-lsb-keyword +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: The given keyword was set in the LSB keyword section in this + <code>/etc/init.d</code> script but isn't one of the known LSB keywords and + doesn't begin with <code>X-</code>. One of the standard keywords may have + been misspelled. diff --git a/tags/i/init.d-script-has-unterminated-lsb-section.tag b/tags/i/init.d-script-has-unterminated-lsb-section.tag new file mode 100644 index 0000000..7e2d22b --- /dev/null +++ b/tags/i/init.d-script-has-unterminated-lsb-section.tag @@ -0,0 +1,11 @@ +Tag: init.d-script-has-unterminated-lsb-section +Severity: error +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: This <code>/etc/init.d</code> script has an LSB keyword section starting + with <code>### BEGIN INIT INFO</code> but either has no matching <code>### END + INIT INFO</code> or has lines between those two markers that are not + comments. The line number given is the first line that doesn't look like + part of an LSB keyword section. There must be an end marker after all + the keyword settings and there must not be any lines between those + markers that do not begin with <code>#</code>. diff --git a/tags/i/init.d-script-missing-dependency-on-local_fs.tag b/tags/i/init.d-script-missing-dependency-on-local_fs.tag new file mode 100644 index 0000000..eb3c34b --- /dev/null +++ b/tags/i/init.d-script-missing-dependency-on-local_fs.tag @@ -0,0 +1,12 @@ +Tag: init.d-script-missing-dependency-on-local_fs +Severity: error +Check: init-d +Explanation: The given init script seems to refer to <code>/var</code>, possibly + using a file from there. Without a dependency on <code>$local_fs</code> in + Required-Start or Required-Stop, as appropriate, the init script might be + run before <code>/var</code> is mounted or after it's unmounted. + . + Using Should-Start or Should-Stop to declare the dependency is + conceptually incorrect since the $local_fs facility is always + available. Required-Start or Required-Stop should be used instead. +See-Also: https://wiki.debian.org/LSBInitScripts diff --git a/tags/i/init.d-script-missing-lsb-keyword.tag b/tags/i/init.d-script-missing-lsb-keyword.tag new file mode 100644 index 0000000..bef14ef --- /dev/null +++ b/tags/i/init.d-script-missing-lsb-keyword.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-missing-lsb-keyword +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: This <code>/etc/init.d</code> script has an LSB keyword section, but it + is missing the given required LSB keyword. If the value of this keyword + should be empty, please still include it in the LSB keyword section with + an empty value. diff --git a/tags/i/init.d-script-missing-lsb-section.tag b/tags/i/init.d-script-missing-lsb-section.tag new file mode 100644 index 0000000..0fe9111 --- /dev/null +++ b/tags/i/init.d-script-missing-lsb-section.tag @@ -0,0 +1,9 @@ +Tag: init.d-script-missing-lsb-section +Severity: warning +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: This <code>/etc/init.d</code> script does not have an LSB keyword + section (or the <code>### BEGIN INIT INFO</code> tag is incorrect). This + section provides description and runlevel information in a standard + format and provides dependency information that can be used to + parallelize the boot process. Please consider adding it. diff --git a/tags/i/init.d-script-missing-lsb-short-description.tag b/tags/i/init.d-script-missing-lsb-short-description.tag new file mode 100644 index 0000000..a1bbd81 --- /dev/null +++ b/tags/i/init.d-script-missing-lsb-short-description.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-missing-lsb-short-description +Severity: info +Check: init-d +See-Also: https://wiki.debian.org/LSBInitScripts +Explanation: This <code>/etc/init.d</code> script has an LSB keyword section, but it + is missing a Short-Description LSB keyword. This field isn't directly + used currently, but adding it is still a good idea for documentation + purposes. diff --git a/tags/i/init.d-script-missing-start.tag b/tags/i/init.d-script-missing-start.tag new file mode 100644 index 0000000..518c96d --- /dev/null +++ b/tags/i/init.d-script-missing-start.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-missing-start +Severity: warning +Check: init-d +Explanation: The given <code>/etc/init.d</code> script indicates it should be + started at one of the runlevels 2-5 but not at all of them. This is a + mistake. The system administrators should be given the opportunity to + customize the runlevels at their will. +See-Also: debian-policy 9.3.3.1 diff --git a/tags/i/init.d-script-not-included-in-package.tag b/tags/i/init.d-script-not-included-in-package.tag new file mode 100644 index 0000000..79af697 --- /dev/null +++ b/tags/i/init.d-script-not-included-in-package.tag @@ -0,0 +1,5 @@ +Tag: init.d-script-not-included-in-package +Severity: error +Check: init-d +Explanation: The <code>/etc/init.d</code> script is registered in the + <code>postinst</code> script, but is not included in the package. diff --git a/tags/i/init.d-script-not-marked-as-conffile.tag b/tags/i/init.d-script-not-marked-as-conffile.tag new file mode 100644 index 0000000..3d5a5d3 --- /dev/null +++ b/tags/i/init.d-script-not-marked-as-conffile.tag @@ -0,0 +1,8 @@ +Tag: init.d-script-not-marked-as-conffile +Severity: warning +Check: init-d +See-Also: debian-policy 9.3.2 +Explanation: <code>/etc/init.d</code> scripts should be marked as conffiles. + . + This is usually an error, but the Policy allows for managing these files + manually in maintainer scripts and Lintian cannot reliably detect that. diff --git a/tags/i/init.d-script-possible-missing-stop.tag b/tags/i/init.d-script-possible-missing-stop.tag new file mode 100644 index 0000000..ee1a2da --- /dev/null +++ b/tags/i/init.d-script-possible-missing-stop.tag @@ -0,0 +1,15 @@ +Tag: init.d-script-possible-missing-stop +Severity: warning +Check: init-d +Explanation: The given <code>/etc/init.d</code> script indicates it should be + stopped at one of the runlevels 0, 1, or 6 but not at all of them. + This is usually a mistake. Normally, facilities that need to be stopped + at any of those runlevels need to be stopped at all of them. + . + For example, if it is safe for the facility provided by this init script + to be stopped by <code>sendsigs</code> at runlevels 0 and 6, there should be + no reason to special case runlevel 1, where <code>killprocs</code> would + stop it. If the facility needs special shutdown handling when rebooting + the system (runlevel 6), it probably needs the same handling when + halting the system (runlevel 0) or switching to single-user mode + (runlevel 1). diff --git a/tags/i/init.d-script-provides-virtual-facility.tag b/tags/i/init.d-script-provides-virtual-facility.tag new file mode 100644 index 0000000..89c10f6 --- /dev/null +++ b/tags/i/init.d-script-provides-virtual-facility.tag @@ -0,0 +1,16 @@ +Tag: init.d-script-provides-virtual-facility +Severity: warning +Check: init-d +Explanation: This <code>/etc/init.d</code> script indicates in its LSB headers that + it provides a virtual facility, denoted by the dollar sign in front of + the name. + . + This is not the correct way to provide a virtual facility. Instead, the + package should include a file in <code>/etc/insserv.conf.d</code>, usually + named after the package, containing: + . + $virtual_facility_name +init-script-name + . + to declare that the named init script provides the named virtual + facility. +See-Also: https://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities diff --git a/tags/i/init.d-script-should-always-start-service.tag b/tags/i/init.d-script-should-always-start-service.tag new file mode 100644 index 0000000..c26c24a --- /dev/null +++ b/tags/i/init.d-script-should-always-start-service.tag @@ -0,0 +1,19 @@ +Tag: init.d-script-should-always-start-service +Severity: error +Check: init-d +Explanation: The specified file under <code>/etc/default/</code> includes a line + such as <code>ENABLED=</code>, <code>DISABLED=</code>, <code>RUN=</code>, etc. + . + This is an older practice used so that the package's init script would + not start the service until the local system administrator changed this + value. + . + However, this hides from the underlying init system whether or not the + daemon should actually be started leading to confusing behavior + including <code>service package start</code> returning success without the + service actually starting. + . + Please remove this mechanism and disable enabling the daemon on install + via <code>dh_installinit --no-enable</code> or move to automatically + starting it. +See-Also: debian-policy 9.3.3.1, update-rc.d(8), dh_installinit(1) diff --git a/tags/i/init.d-script-sourcing-without-test.tag b/tags/i/init.d-script-sourcing-without-test.tag new file mode 100644 index 0000000..8998372 --- /dev/null +++ b/tags/i/init.d-script-sourcing-without-test.tag @@ -0,0 +1,11 @@ +Tag: init.d-script-sourcing-without-test +Severity: error +Check: init-d +Explanation: The given <code>/etc/init.d</code> script seems to be sourcing an + <code>/etc/default/</code> file without checking for its existence first. + Files in <code>/etc/default/</code> can be deleted by the administrator at + any time, and init scripts are required to handle the situation + gracefully. For example: + . + [ -r /etc/default/foo ] && . /etc/default/foo +See-Also: debian-policy 9.3.2 diff --git a/tags/i/init.d-script-starts-in-stop-runlevel.tag b/tags/i/init.d-script-starts-in-stop-runlevel.tag new file mode 100644 index 0000000..9943d1b --- /dev/null +++ b/tags/i/init.d-script-starts-in-stop-runlevel.tag @@ -0,0 +1,9 @@ +Tag: init.d-script-starts-in-stop-runlevel +Severity: error +Check: init-d +Explanation: This <code>/etc/init.d</code> script specifies the 0 or 6 runlevels in + Default-Start in its LSB keyword section. The 0 and 6 runlevels are + meant to only stop services, not to start them. Even if the init script + is doing something that isn't exactly stopping a service, the run-level + should be listed in Default-Stop, not Default-Start, and the script + should perform those actions when passed the <code>stop</code> argument. diff --git a/tags/i/init.d-script-uses-usr-interpreter.tag b/tags/i/init.d-script-uses-usr-interpreter.tag new file mode 100644 index 0000000..203c765 --- /dev/null +++ b/tags/i/init.d-script-uses-usr-interpreter.tag @@ -0,0 +1,15 @@ +Tag: init.d-script-uses-usr-interpreter +Severity: warning +Check: init-d +Explanation: The given <code>/etc/init.d</code> script specifies an interpreter in + its shebang located under <code>/usr</code>. + . + It indicates that the init script may be using a non-essential + interpreter. Since init scripts are configuration files, they may be + left on the system after their package has been removed but not purged. + At that point, the package dependencies are not guaranteed to exist and + the interpreter may therefore not be available. + . + It's generally best to write init scripts using <code>/bin/sh</code> or + <code>/bin/bash</code> where possible, since they are guaranteed to always be + available. diff --git a/tags/i/initial-upload-closes-no-bugs.tag b/tags/i/initial-upload-closes-no-bugs.tag new file mode 100644 index 0000000..4651ddc --- /dev/null +++ b/tags/i/initial-upload-closes-no-bugs.tag @@ -0,0 +1,12 @@ +Tag: initial-upload-closes-no-bugs +Severity: warning +Check: debian/changelog +Renamed-From: new-package-should-close-itp-bug +Explanation: This package appears to be the first packaging of a new upstream + software package (there is only one changelog entry and the Debian + revision is 1), but it does not close any bugs. The initial upload of a + new package should close the corresponding ITP bug for that package. + . + This warning can be ignored if the package is not intended for Debian or + if it is a split of an existing Debian package. +See-Also: developer-reference 5.1 diff --git a/tags/i/insecure-copyright-format-uri.tag b/tags/i/insecure-copyright-format-uri.tag new file mode 100644 index 0000000..0f19843 --- /dev/null +++ b/tags/i/insecure-copyright-format-uri.tag @@ -0,0 +1,11 @@ +Tag: insecure-copyright-format-uri +Severity: pedantic +Check: debian/copyright/dep5 +Explanation: Format URI of the machine-readable copyright file uses the plain HTTP + unencrypted transport protocol. Since policy version 4.0.0, using HTTPS is preferred. + . + Please use + <code>https://www.debian.org/doc/packaging-manuals/copyright-format/*version*/</code> + as the format URI instead. +See-Also: + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff --git a/tags/i/install-info-used-in-maintainer-script.tag b/tags/i/install-info-used-in-maintainer-script.tag new file mode 100644 index 0000000..8151360 --- /dev/null +++ b/tags/i/install-info-used-in-maintainer-script.tag @@ -0,0 +1,10 @@ +Tag: install-info-used-in-maintainer-script +Severity: error +Check: scripts +Explanation: This script apparently runs <code>install-info</code>. Updating the + <code>/usr/share/info/dir</code> file is now handled automatically by + triggers, so running <code>install-info</code> from maintainer scripts is no + longer necessary. + . + If debhelper generated the maintainer script fragment, rebuilding the + package with debhelper 7.2.17 or later will fix this problem. diff --git a/tags/i/installable-field-mirrors-source.tag b/tags/i/installable-field-mirrors-source.tag new file mode 100644 index 0000000..f91ceeb --- /dev/null +++ b/tags/i/installable-field-mirrors-source.tag @@ -0,0 +1,11 @@ +Tag: installable-field-mirrors-source +Severity: info +Check: debian/control/field/redundant +Renamed-From: + binary-control-field-duplicates-source +Explanation: The named field for an installation package in + <code>debian/control</code> has the same value as the one inherited + from the source paragraph. + . + In the interest of shorter and clearer files, you may wish to take advantage + of the inheritance rules. This field is redundant. diff --git a/tags/i/interpreter-in-usr-local.tag b/tags/i/interpreter-in-usr-local.tag new file mode 100644 index 0000000..8caceae --- /dev/null +++ b/tags/i/interpreter-in-usr-local.tag @@ -0,0 +1,6 @@ +Tag: interpreter-in-usr-local +Severity: error +Check: scripts +Explanation: This package contains a script that looks for an interpreter in a + directory in /usr/local. Since Debian does not install anything in + /usr/local, this is the wrong place to look. diff --git a/tags/i/interpreter-not-absolute.tag b/tags/i/interpreter-not-absolute.tag new file mode 100644 index 0000000..7e62d1e --- /dev/null +++ b/tags/i/interpreter-not-absolute.tag @@ -0,0 +1,6 @@ +Tag: interpreter-not-absolute +Severity: warning +Check: scripts +Explanation: This script uses a relative path to locate its interpreter. + This path will be taken relative to the caller's current directory, not + the script's, so it is not likely to be what was intended. diff --git a/tags/i/intra-source-package-circular-dependency.tag b/tags/i/intra-source-package-circular-dependency.tag new file mode 100644 index 0000000..e1d5ad4 --- /dev/null +++ b/tags/i/intra-source-package-circular-dependency.tag @@ -0,0 +1,14 @@ +Tag: intra-source-package-circular-dependency +Severity: warning +Check: group-checks +Explanation: The listed packages from the same source circularly depend + (or pre-depend) on each other. This makes it difficult for tools + to properly handle install/upgrade sequences. Furthermore this + complicates automated removal of unused packages. + . + If possible, consider removing or reducing one of the depends. + . + Note: This check is limited to packages created from the same + source package. Full circular dependencies between binaries from + different source packages is beyond the scope of Lintian. +See-Also: debian-policy 7.2 diff --git a/tags/i/invalid-arch-string-in-source-relation.tag b/tags/i/invalid-arch-string-in-source-relation.tag new file mode 100644 index 0000000..db8cc03 --- /dev/null +++ b/tags/i/invalid-arch-string-in-source-relation.tag @@ -0,0 +1,9 @@ +Tag: invalid-arch-string-in-source-relation +Severity: error +Check: fields/package-relations +See-Also: debian-policy 5.6.8 +Explanation: The architecture string in the source relation includes an unknown + architecture. This may be a typo, or it may be an architecture that dpkg + doesn't know about yet. A common problem is incorrectly separating + architectures with a comma, such as <code>[i386, m68k]</code>. Architectures + are separated by spaces; this should instead be <code>[i386 m68k]</code>. diff --git a/tags/i/invalid-date-in-debian-changelog.tag b/tags/i/invalid-date-in-debian-changelog.tag new file mode 100644 index 0000000..0c6de55 --- /dev/null +++ b/tags/i/invalid-date-in-debian-changelog.tag @@ -0,0 +1,16 @@ +Tag: invalid-date-in-debian-changelog +Severity: error +Check: debian/changelog +Explanation: The date format in the latest changelog entry file appears to be invalid. + . + Dates should use the following format (compatible and with the same semantics + of RFC 2822 and RFC 5322): + . + day-of-week, dd month yyyy hh:mm:ss +zzzz + . + To avoid problems like this, consider using a tool like dch(1) or + date(1) to generate the date. Example: + . + $ date -R -ud '2013-11-05 23:59:59' + Tue, 05 Nov 2013 23:59:59 +0000 +See-Also: debian-policy 4.4 diff --git a/tags/i/invalid-escape-sequence-in-dep5-copyright.tag b/tags/i/invalid-escape-sequence-in-dep5-copyright.tag new file mode 100644 index 0000000..347cdb1 --- /dev/null +++ b/tags/i/invalid-escape-sequence-in-dep5-copyright.tag @@ -0,0 +1,9 @@ +Tag: invalid-escape-sequence-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Explanation: The only allowed escape sequences are "\*", "\?" and "\\" (without + quotes) to produce a literal star, question mark and backslash, respectively. + Without the escaping backslash, the star and question mark take the role of + globbing operators similar to shell globs which is why they have to be + escaped. No other escapable characters than "*", "?" and "\" exist. diff --git a/tags/i/invalid-field-for-derivative.tag b/tags/i/invalid-field-for-derivative.tag new file mode 100644 index 0000000..89d59c7 --- /dev/null +++ b/tags/i/invalid-field-for-derivative.tag @@ -0,0 +1,17 @@ +Tag: invalid-field-for-derivative +Severity: error +Check: fields/derivatives +Explanation: The specified field in <code>debian/control</code> does not match the + required format for this Debian derivative. + . + Derivative distributions of Debian may enforce additional restrictions + on such fields for many reasons including ensuring that: + . + - Debian maintainers are not contacted for forked or packages that + are otherwise modified by the derivative. + - The original maintainer is still credited for their work (eg. in a + <code>XSBC-Original-Maintainer</code> field). + - References to revision control systems (eg. <code>Vcs-Git</code>) are + pointing to the correct, updated location. + - Fields that become misleading in the context of a derivative are + removed. diff --git a/tags/i/invalid-override-restriction.tag b/tags/i/invalid-override-restriction.tag new file mode 100644 index 0000000..26ea506 --- /dev/null +++ b/tags/i/invalid-override-restriction.tag @@ -0,0 +1,8 @@ +Tag: invalid-override-restriction +Severity: error +Show-Always: yes +Check: debian/lintian-overrides/restricted +Explanation: The architecture restriction in the given <code>override</code> + line is invalid for the reason indicated. +See-Also: + lintian-manual 2.4.1 diff --git a/tags/i/invalid-po-file.tag b/tags/i/invalid-po-file.tag new file mode 100644 index 0000000..69e8117 --- /dev/null +++ b/tags/i/invalid-po-file.tag @@ -0,0 +1,6 @@ +Tag: invalid-po-file +Severity: warning +Check: debian/po-debconf +Explanation: Errors were found in the listed PO file that will cause its content + to be discarded. Run <code>msgfmt</code> on the file to see the error + messages. diff --git a/tags/i/invalid-potfiles-in.tag b/tags/i/invalid-potfiles-in.tag new file mode 100644 index 0000000..5f6bb1c --- /dev/null +++ b/tags/i/invalid-potfiles-in.tag @@ -0,0 +1,11 @@ +Tag: invalid-potfiles-in +Severity: warning +Check: debian/po-debconf +Explanation: Errors were found in the <code>debian/po/POTFILES.in</code> file. + . + Please make sure that all strings marked for translation are in uniform + encoding (say UTF-8) then prepend the following line to POTFILES.in and + rerun intltool-update. + . + [encoding: UTF-8] +See-Also: Bug#849912, Bug#883653 diff --git a/tags/i/invalid-profile-name-in-build-profiles-field.tag b/tags/i/invalid-profile-name-in-build-profiles-field.tag new file mode 100644 index 0000000..e14ce77 --- /dev/null +++ b/tags/i/invalid-profile-name-in-build-profiles-field.tag @@ -0,0 +1,28 @@ +Tag: invalid-profile-name-in-build-profiles-field +Severity: error +Check: debian/control/field/build-profiles +Explanation: The restriction formula in the <code>Build-Profiles</code> field + includes an unknown build profile. The only allowed build profiles are: + . + - <code>cross</code> + - <code>nobiarch</code> + - <code>nocheck</code> + - <code>nocil</code> + - <code>nodoc</code> + - <code>nogolang</code> + - <code>noguile</code> + - <code>noinsttest</code> + - <code>nojava</code> + - <code>nolua</code> + - <code>noocaml</code> + - <code>noperl</code> + - <code>nopython</code> + - <code>noruby</code> + - <code>noudeb</code> + - <code>nowasm</code> + - <code>nowindows</code> + - <code>stage1</code> + - <code>stage2</code> + - <code>pkg.*srcpkg*.*anything*</code> +See-Also: + https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff --git a/tags/i/invalid-profile-name-in-source-relation.tag b/tags/i/invalid-profile-name-in-source-relation.tag new file mode 100644 index 0000000..613d130 --- /dev/null +++ b/tags/i/invalid-profile-name-in-source-relation.tag @@ -0,0 +1,26 @@ +Tag: invalid-profile-name-in-source-relation +Severity: error +Check: fields/package-relations +Explanation: The restriction formula in the source relation includes an unknown build + profile. The only allowed build profiles are + "cross", + "nobiarch", + "nocheck", + "nocil", + "nodoc", + "nogolang", + "noguile", + "noinsttest", + "nojava", + "nolua", + "noocaml", + "noperl", + "nopython", + "noruby", + "noudeb", + "nowasm", + "nowindows", + "stage1", + "stage2" + and "pkg.*srcpkg*.*anything*". +See-Also: https://wiki.debian.org/BuildProfileSpec#Registered_profile_names diff --git a/tags/i/invalid-restriction-formula-in-build-profiles-field.tag b/tags/i/invalid-restriction-formula-in-build-profiles-field.tag new file mode 100644 index 0000000..8375d87 --- /dev/null +++ b/tags/i/invalid-restriction-formula-in-build-profiles-field.tag @@ -0,0 +1,8 @@ +Tag: invalid-restriction-formula-in-build-profiles-field +Severity: error +Check: debian/control/field/build-profiles +Explanation: The restriction formula in the <code>Build-Profiles</code> field + must be in the same format as the restriction formula in the + <code>Build-Depends</code> field (with angle brackets). +See-Also: + https://wiki.debian.org/BuildProfileSpec#The_Build-Profiles_field diff --git a/tags/i/invalid-short-name-in-dep5-copyright.tag b/tags/i/invalid-short-name-in-dep5-copyright.tag new file mode 100644 index 0000000..f9b5ec3 --- /dev/null +++ b/tags/i/invalid-short-name-in-dep5-copyright.tag @@ -0,0 +1,6 @@ +Tag: invalid-short-name-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Explanation: The “License” field contains a short name observed to be a + misspelling of one of the standard short names. diff --git a/tags/i/invalid-standards-version.tag b/tags/i/invalid-standards-version.tag new file mode 100644 index 0000000..5051291 --- /dev/null +++ b/tags/i/invalid-standards-version.tag @@ -0,0 +1,6 @@ +Tag: invalid-standards-version +Severity: error +Check: fields/standards-version +Explanation: The source package refers to a Standards-Version which never + existed. Please update your package to latest Policy and set this + control field appropriately. diff --git a/tags/i/invalid-systemd-documentation.tag b/tags/i/invalid-systemd-documentation.tag new file mode 100644 index 0000000..a4d126c --- /dev/null +++ b/tags/i/invalid-systemd-documentation.tag @@ -0,0 +1,25 @@ +Tag: invalid-systemd-documentation +Severity: info +Check: systemd +Explanation: The named systemd service file contains a <code>Documentation</code> + field that is not a URI. + . + The field should contain a space-separated list of URIs referencing documentation + for the unit or its configuration. Accepted are only URIs of the types + <code>http://</code>, <code>https://</code>, <code>file:</code>, <code>info:</code>, + <code>man:</code>. + . + For more information about the syntax of these URIs, see <code>uri(7)</code>. The URIs + should be listed in order of relevance, starting with the most relevant. It is a good + idea to first reference documentation that explains what the unit's purpose is, + followed by how it is configured, followed by any other related documentation. + . + The <code>Documentation</code> key may be specified more than once, in which case the + specified list of URIs is merged. If the empty string is assigned to this option, the + list is reset and prior assignments have no effect. + . + Documentation for systemd service files can be automatically viewed using + <code>systemctl help servicename</code> if this field is present. +See-Also: + systemd.unit(5), + uri(7) diff --git a/tags/i/invalid-template-id-in-symbols-file.tag b/tags/i/invalid-template-id-in-symbols-file.tag new file mode 100644 index 0000000..577ebd5 --- /dev/null +++ b/tags/i/invalid-template-id-in-symbols-file.tag @@ -0,0 +1,9 @@ +Tag: invalid-template-id-in-symbols-file +Severity: error +Check: debian/shlibs +Explanation: The symbol definition refers to an alternative dependency template + which is not defined for the library containing the symbol. + . + The first alternative dependency template for a library the id number + of 1, with the ids of subsequent alternative templates increasing in + sequence. diff --git a/tags/i/invalid-value-in-built-using-field.tag b/tags/i/invalid-value-in-built-using-field.tag new file mode 100644 index 0000000..c8fab8f --- /dev/null +++ b/tags/i/invalid-value-in-built-using-field.tag @@ -0,0 +1,11 @@ +Tag: invalid-value-in-built-using-field +Severity: error +Check: fields/built-using +Explanation: The Built-Using field contains invalid fields. + . + The Built-Using field must consist of simple <code>source (= + version)</code> clauses. Notably, it must use a strictly equal in the + relation. + . + Only first issue is shown. +See-Also: debian-policy 7.8 diff --git a/tags/i/invalid-version-number-for-derivative.tag b/tags/i/invalid-version-number-for-derivative.tag new file mode 100644 index 0000000..ebea535 --- /dev/null +++ b/tags/i/invalid-version-number-for-derivative.tag @@ -0,0 +1,9 @@ +Tag: invalid-version-number-for-derivative +Severity: error +Check: fields/version/derivative +Explanation: The version does not comply with the format required for that Debian + derivative. + . + Derivative distributions may enforce additional restrictions on version strings + in order to ensure that packages modified specifically for that derivative can + be so identified. diff --git a/tags/i/invalid-versioned-provides.tag b/tags/i/invalid-versioned-provides.tag new file mode 100644 index 0000000..fd79895 --- /dev/null +++ b/tags/i/invalid-versioned-provides.tag @@ -0,0 +1,8 @@ +Tag: invalid-versioned-provides +Severity: error +Check: fields/package-relations +See-Also: debian-policy 7.1, Bug#761219 +Explanation: The package declares a provides relation with an invalid version + operator (e.g. ">="). + . + If a provides is versioned, it must use "=". diff --git a/tags/i/isdefault-flag-is-deprecated.tag b/tags/i/isdefault-flag-is-deprecated.tag new file mode 100644 index 0000000..a53f0bf --- /dev/null +++ b/tags/i/isdefault-flag-is-deprecated.tag @@ -0,0 +1,12 @@ +Tag: isdefault-flag-is-deprecated +Severity: warning +Check: debian/debconf +Explanation: The "isdefault" flag on debconf questions is deprecated as of debconf + 0.5.00, and has been replaced by "seen" with the inverse meaning. From + debconf 0.5 onwards there should be very few reasons to use isdefault/seen + anyway, as backing up works much better now. See + /usr/share/doc/debconf-doc/changelog.gz for more information. + . + The misuse of isdefault often leads to questions being asked twice in one + installation run, or, worse, on every upgrade. Please test your package + carefully to make sure this does not happen. |