diff options
Diffstat (limited to 'tags/d')
245 files changed, 2655 insertions, 0 deletions
diff --git a/tags/d/data-tarball-compression-format.tag b/tags/d/data-tarball-compression-format.tag new file mode 100644 index 0000000..bd8c238 --- /dev/null +++ b/tags/d/data-tarball-compression-format.tag @@ -0,0 +1,4 @@ +Tag: data-tarball-compression-format +Severity: classification +Check: deb-format +Explanation: This is the compressor format used for the <code>data.tar</code> tarball. diff --git a/tags/d/dbg-package-missing-depends.tag b/tags/d/dbg-package-missing-depends.tag new file mode 100644 index 0000000..bd1a00e --- /dev/null +++ b/tags/d/dbg-package-missing-depends.tag @@ -0,0 +1,16 @@ +Tag: dbg-package-missing-depends +Severity: warning +Check: fields/package-relations +Explanation: The given binary package has a name of the form of "X-dbg", indicating it + contains detached debugging symbols for the package X. If so, it should + depend on the corresponding package, generally with (= ${binary:Version}) + since the debugging symbols are only useful with the binaries created by + the same build. + . + Note that the package being depended upon cannot be "Architecture: + all". + . + If this package provides debugging symbols for multiple other + packages, it should normally depend on all of those packages as + alternatives. In other words, <code>pkga (= ${binary:Version}) | pkgb (= + ${binary:Version})</code> and so forth. diff --git a/tags/d/dbus-policy-at-console.tag b/tags/d/dbus-policy-at-console.tag new file mode 100644 index 0000000..74f29d4 --- /dev/null +++ b/tags/d/dbus-policy-at-console.tag @@ -0,0 +1,28 @@ +Tag: dbus-policy-at-console +Severity: warning +Check: desktop/dbus +Explanation: The package contains D-Bus policy configuration that uses the + deprecated <code>at_console</code> condition to impose a different policy + for users who are "logged in at the console" according to + systemd-logind, ConsoleKit or similar APIs, such as: + . + <policy context="default"> + <deny send_destination="com.example.PowerManagementDaemon"/> + </policy> + <policy at_console="true"> + <allow send_destination="com.example.PowerManagementDaemon"/> + </policy> + . + The maintainers of D-Bus recommend that services should allow or deny + method calls according to broad categories that are not typically altered + by the system administrator (usually either "all users", or only root + and/or a specified system user). + . + If finer-grained authorization + is required, the service should accept the method call message, then call + out to PolicyKit to decide whether to honor the request. PolicyKit can + use system-administrator-configurable policies to make that decision, + including distinguishing between users who are "at the console" and + those who are not. +See-Also: + https://bugs.freedesktop.org/show_bug.cgi?id=39611 diff --git a/tags/d/dbus-policy-excessively-broad.tag b/tags/d/dbus-policy-excessively-broad.tag new file mode 100644 index 0000000..264a14f --- /dev/null +++ b/tags/d/dbus-policy-excessively-broad.tag @@ -0,0 +1,30 @@ +Tag: dbus-policy-excessively-broad +Severity: error +Check: desktop/dbus +Explanation: The package contains D-Bus policy configuration that + matches broad classes of messages. This will cause strange side-effects, + is almost certainly unintended, and is a probable security flaw. + . + For instance, + . + <policy user="daemon"> + <allow send_type="method_call"/> + <allow send_destination="com.example.Bees"/> + </policy> + . + in any system bus policy file would allow the <code>daemon</code> user to send + any method call to any service, including method calls which are meant to + be restricted to root-only for security, such as + <code>org.freedesktop.systemd1.Manager.StartTransientUnit</code>. (In addition, + it allows that user to send any message to the <code>com.example.Bees</code> + service.) + . + The intended policy for that particular example was probably more like + . + <policy user="daemon"> + <allow send_type="method_call" send_destination="com.example.Bees"/> + </policy> + . + which correctly allows method calls to that particular service only. +See-Also: + http://www.openwall.com/lists/oss-security/2015/01/27/25 diff --git a/tags/d/dbus-policy-in-etc.tag b/tags/d/dbus-policy-in-etc.tag new file mode 100644 index 0000000..b126f87 --- /dev/null +++ b/tags/d/dbus-policy-in-etc.tag @@ -0,0 +1,16 @@ +Tag: dbus-policy-in-etc +Severity: warning +Check: desktop/dbus +Explanation: The package contains D-Bus policy configuration and installs it + under <code>/etc/dbus-1/system.d</code> or + <code>/etc/dbus-1/session.d</code>. These directories are reserved for + local configuration, which overrides the default policies in + <code>/usr</code>. + . + The correct directory for system bus policy installed by packages is + <code>/usr/share/dbus-1/system.d</code>. + . + The correct directory for session bus policy installed by packages + (not usually needed) is <code>/usr/share/dbus-1/session.d</code>. +See-Also: + dbus-daemon(1) diff --git a/tags/d/dbus-policy-without-send-destination.tag b/tags/d/dbus-policy-without-send-destination.tag new file mode 100644 index 0000000..65b2345 --- /dev/null +++ b/tags/d/dbus-policy-without-send-destination.tag @@ -0,0 +1,37 @@ +Tag: dbus-policy-without-send-destination +Severity: warning +Check: desktop/dbus +Explanation: The package contains D-Bus policy configuration that uses + one of the <code>send_*</code> conditions, but does not specify a + <code>send_destination</code>, and is not specific to root. + . + Rules of the form + . + <allow send_interface="com.example.MyInterface"/> + . + allow messages with the given interface to be sent to *any* + service, not just the one installing the rule, which is rarely + what was intended. + . + Similarly, on the system bus, rules of the form + . + <deny send_interface="com.example.MyInterface"/> + . + are redundant with the system bus's default-deny policy, and have + unintended effects on other services. + . + This check ignores rules of the form + . + <policy user="root"> + <allow ... /> + </policy> + . + which are commonly used for the "agent" pattern seen in services like + BlueZ and NetworkManager: a root-privileged daemon calls out to + one or more per-user user interface agent processes with no specific + name, so <code>send_destination</code> is not easily applicable. + However, such rules should still be made as specific as possible to + avoid undesired side-effects. +See-Also: + https://bugs.freedesktop.org/show_bug.cgi?id=18961, + http://lists.freedesktop.org/archives/dbus/2008-February/009401.html diff --git a/tags/d/dbus-session-service-wrong-name.tag b/tags/d/dbus-session-service-wrong-name.tag new file mode 100644 index 0000000..d8b7d5c --- /dev/null +++ b/tags/d/dbus-session-service-wrong-name.tag @@ -0,0 +1,14 @@ +Tag: dbus-session-service-wrong-name +Severity: info +Check: desktop/dbus +Explanation: The package contains a D-Bus session service whose filename + does not match the <code>Name</code> field found in the file. + This makes it possible that two non-conflicting packages could + provide the same service name with the same search-path priority + (i.e. in the same directory). dbus-daemon will arbitrarily choose + one of them, which is unlikely to be the desired result. + . + Best-practice is that if you implement a session service whose well-known + name is <code>com.example.MyService1</code>, and it should be + service-activatable, you should achieve that by packaging + <code>/usr/share/dbus-1/services/com.example.MyService1.service</code>. diff --git a/tags/d/dbus-system-service-wrong-name.tag b/tags/d/dbus-system-service-wrong-name.tag new file mode 100644 index 0000000..eabc9dd --- /dev/null +++ b/tags/d/dbus-system-service-wrong-name.tag @@ -0,0 +1,13 @@ +Tag: dbus-system-service-wrong-name +Severity: error +Check: desktop/dbus +Explanation: The package contains a D-Bus system service whose filename + does not match the <code>Name</code> field found in the file. + This will not work, because dbus-daemon-launch-helper specifically + looks for that filename, in order to keep system-level activation + secure and predictable. + . + If you implement a session service whose well-known name is + <code>com.example.MyService1</code>, and it should be service-activatable, + you must provide + <code>/usr/share/dbus-1/system-services/com.example.MyService1.service</code>. diff --git a/tags/d/debconf-config-not-executable.tag b/tags/d/debconf-config-not-executable.tag new file mode 100644 index 0000000..1ec1e57 --- /dev/null +++ b/tags/d/debconf-config-not-executable.tag @@ -0,0 +1,5 @@ +Tag: debconf-config-not-executable +Severity: error +Check: debian/debconf +Explanation: The debconf "config" script in the package control area must be + executable. diff --git a/tags/d/debconf-is-not-a-registry.tag b/tags/d/debconf-is-not-a-registry.tag new file mode 100644 index 0000000..6fdbf4b --- /dev/null +++ b/tags/d/debconf-is-not-a-registry.tag @@ -0,0 +1,17 @@ +Tag: debconf-is-not-a-registry +Severity: warning +Check: debian/debconf +Explanation: In the Unix tradition, Debian packages should have human-readable and + human-editable configuration files. This package uses debconf commands + outside its maintainer scripts, which often indicates that it is taking + configuration information directly from the debconf database. Typically, + packages should use debconf-supplied information to generate + configuration files, and -- to avoid losing configuration information on + upgrades -- should parse these configuration files in the <code>config</code> + script if it is necessary to ask the user for changes. + . + Some standalone programs may legitimately use debconf to prompt the user + for questions. If you maintain a package containing such a program, + please install an override. Other exceptions to this check include + configuration scripts called from the package's post-installation script. +See-Also: developer-reference 6.5.1, debconf-devel(7) diff --git a/tags/d/debconf-translation-using-general-list.tag b/tags/d/debconf-translation-using-general-list.tag new file mode 100644 index 0000000..e3a5322 --- /dev/null +++ b/tags/d/debconf-translation-using-general-list.tag @@ -0,0 +1,11 @@ +Tag: debconf-translation-using-general-list +Severity: warning +Check: debian/po-debconf +Explanation: This debconf translation is using the general debconf-i18n list as + the address in the Language-Team field. + . + The intended purpose of the Language-Team field is to be an additional + contact for new translation requests in addition to the previous + translator (as recorded in Last-Translator). The field should therefore + point to a mailing list dedicated to the language of this PO file, not + the general list for translation discussions. diff --git a/tags/d/debhelper-autoscript-in-maintainer-scripts.tag b/tags/d/debhelper-autoscript-in-maintainer-scripts.tag new file mode 100644 index 0000000..c5c6f11 --- /dev/null +++ b/tags/d/debhelper-autoscript-in-maintainer-scripts.tag @@ -0,0 +1,5 @@ +Tag: debhelper-autoscript-in-maintainer-scripts +Severity: classification +Check: maintainer-scripts/generated +Explanation: The maintainer scripts of the package contain one or more + auto-generated shell snippets inserted by the listed debhelper tool. diff --git a/tags/d/debhelper-but-no-misc-depends.tag b/tags/d/debhelper-but-no-misc-depends.tag new file mode 100644 index 0000000..92df45a --- /dev/null +++ b/tags/d/debhelper-but-no-misc-depends.tag @@ -0,0 +1,10 @@ +Tag: debhelper-but-no-misc-depends +Severity: warning +Check: debhelper +See-Also: debhelper(7) +Explanation: The source package uses debhelper, but it does not include + ${misc:Depends} in the given binary package's debian/control entry. Any + debhelper command may add dependencies to ${misc:Depends} that are + required for the work that it does, so recommended best practice is to + always add ${misc:Depends} to the dependencies of each binary package if + debhelper is in use. diff --git a/tags/d/debhelper-compat-file-contains-multiple-levels.tag b/tags/d/debhelper-compat-file-contains-multiple-levels.tag new file mode 100644 index 0000000..bfcda33 --- /dev/null +++ b/tags/d/debhelper-compat-file-contains-multiple-levels.tag @@ -0,0 +1,11 @@ +Tag: debhelper-compat-file-contains-multiple-levels +Severity: error +Check: debhelper +See-Also: debhelper(7) +Explanation: The <code>debian/compat</code> file appears to contain multiple + compatibility levels. + . + This was likely due to the use of >> instead of > when + updating the level. + . + Please update the file to specify a single level. diff --git a/tags/d/debhelper-compat-file-is-empty.tag b/tags/d/debhelper-compat-file-is-empty.tag new file mode 100644 index 0000000..e88c99d --- /dev/null +++ b/tags/d/debhelper-compat-file-is-empty.tag @@ -0,0 +1,7 @@ +Tag: debhelper-compat-file-is-empty +Severity: error +Check: debhelper +See-Also: debhelper(7) +Explanation: The source package has an empty debian/compat file. This is an error, + the compat level of debhelper should be in there. Note that only the first + line of the file is relevant. diff --git a/tags/d/debhelper-compat-file-is-missing.tag b/tags/d/debhelper-compat-file-is-missing.tag new file mode 100644 index 0000000..f29c4e9 --- /dev/null +++ b/tags/d/debhelper-compat-file-is-missing.tag @@ -0,0 +1,14 @@ +Tag: debhelper-compat-file-is-missing +Severity: warning +Check: debhelper +Explanation: The package build-depends on debhelper but does not ship a compat + file. Packages not using an experimental or beta compatibility level + may alternatively Build-Depend on the debhelper-compat virtual package, + For example: + . + Build-Depends: debhelper-compat (= 13) + . + Please refer to the debhelper documentation on how to create the + compat file and the differences between each compat level. +See-Also: https://lists.debian.org/debian-devel-changes/2012/01/msg01335.html, + debhelper(7) diff --git a/tags/d/debhelper-compat-level.tag b/tags/d/debhelper-compat-level.tag new file mode 100644 index 0000000..b88b4a7 --- /dev/null +++ b/tags/d/debhelper-compat-level.tag @@ -0,0 +1,4 @@ +Tag: debhelper-compat-level +Severity: classification +Check: debhelper +Explanation: This is the debhelper compat level used specified by this package. diff --git a/tags/d/debhelper-compat-not-a-number.tag b/tags/d/debhelper-compat-not-a-number.tag new file mode 100644 index 0000000..c9cc85c --- /dev/null +++ b/tags/d/debhelper-compat-not-a-number.tag @@ -0,0 +1,6 @@ +Tag: debhelper-compat-not-a-number +Severity: error +Check: debhelper +See-Also: debhelper(7) +Explanation: The debhelper compatibility level specified in + <code>debian/compat</code> is not a number. diff --git a/tags/d/debhelper-compat-virtual-relation.tag b/tags/d/debhelper-compat-virtual-relation.tag new file mode 100644 index 0000000..3e22a7b --- /dev/null +++ b/tags/d/debhelper-compat-virtual-relation.tag @@ -0,0 +1,5 @@ +Tag: debhelper-compat-virtual-relation +Severity: classification +Check: debhelper +Explanation: This package is using the <code>debhelper-compat</code> virtual + package as a build-dependency. diff --git a/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag b/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag new file mode 100644 index 0000000..251dee9 --- /dev/null +++ b/tags/d/debhelper-tools-from-autotools-dev-are-deprecated.tag @@ -0,0 +1,19 @@ +Tag: debhelper-tools-from-autotools-dev-are-deprecated +Severity: warning +Check: debhelper +Explanation: The debhelper tools from autotools-dev has been replaced by the tool + <code>dh_update_autotools_config</code>, which was available in + debhelper (>= 9.20160114) + . + The <code>dh_update_autotools_config</code> is run + by default via the <code>dh</code> + command sequencer. If you are using <code>dh</code>, you can probably just remove + the uses of the tooling from autotools-dev without doing any further changes. + . + If you use the "classic" debhelper style, then please replace all + calls to <code>dh_autotools-dev_updateconfig</code> with + <code>dh_update_autotools_config</code>. The calls to + <code>dh_autotools-dev_restoreconfig</code> are replaced by + <code>dh_clean</code>, so they can most likely just be removed without + any further changes. +See-Also: Bug#878528 diff --git a/tags/d/debian-adds-arch-control-dir.tag b/tags/d/debian-adds-arch-control-dir.tag new file mode 100644 index 0000000..74f7324 --- /dev/null +++ b/tags/d/debian-adds-arch-control-dir.tag @@ -0,0 +1,14 @@ +Tag: debian-adds-arch-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-arch-control-dir +Explanation: The Debian diff or native package contains files in an {arch} or + .arch-ids directory or a directory starting with <code>,,</code> (used by baz + for debugging traces). These are usually artifacts of the revision + control system used by the Debian maintainer and not useful in a diff or + native package. <code>dpkg-source</code> will automatically exclude these if + it is passed <code>-I</code> or <code>-i</code> for native and non-native + packages respectively. +See-Also: + dpkg-source(1) diff --git a/tags/d/debian-adds-arch-inventory-file.tag b/tags/d/debian-adds-arch-inventory-file.tag new file mode 100644 index 0000000..328f76f --- /dev/null +++ b/tags/d/debian-adds-arch-inventory-file.tag @@ -0,0 +1,8 @@ +Tag: debian-adds-arch-inventory-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-arch-inventory-file +Explanation: The Debian diff or native package contains an + <code>.arch-inventory</code> file. This is Arch metadata that should + normally not be distributed. diff --git a/tags/d/debian-adds-bts-control-dir.tag b/tags/d/debian-adds-bts-control-dir.tag new file mode 100644 index 0000000..5ee0c1b --- /dev/null +++ b/tags/d/debian-adds-bts-control-dir.tag @@ -0,0 +1,12 @@ +Tag: debian-adds-bts-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-bts-control-dir +Explanation: The Debian diff or native package contains files in a directory + used by a bug tracking system, which are not useful in a diff or native + package. <code>dpkg-source</code> will automatically exclude these if it + is passed <code>-I</code> or <code>-i</code> for native and non-native packages + respectively. +See-Also: + dpkg-source(1) diff --git a/tags/d/debian-adds-bzr-control-dir.tag b/tags/d/debian-adds-bzr-control-dir.tag new file mode 100644 index 0000000..cecda2f --- /dev/null +++ b/tags/d/debian-adds-bzr-control-dir.tag @@ -0,0 +1,12 @@ +Tag: debian-adds-bzr-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-bzr-control-dir +Explanation: The Debian diff or native package contains files in a .bzr + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + <code>dpkg-source</code> will automatically exclude these if it is passed + <code>-I</code> or <code>-i</code> for native and non-native packages respectively. +See-Also: + dpkg-source(1) diff --git a/tags/d/debian-adds-cvs-conflict-copy.tag b/tags/d/debian-adds-cvs-conflict-copy.tag new file mode 100644 index 0000000..c2d5e76 --- /dev/null +++ b/tags/d/debian-adds-cvs-conflict-copy.tag @@ -0,0 +1,10 @@ +Tag: debian-adds-cvs-conflict-copy +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-cvs-conflict-copy +Explanation: The Debian diff or native package contains a CVS conflict copy. + These have file names like <code>.#file.version</code> and are generated by + CVS when a conflict was detected when merging local changes with updates + from a source repository. They're useful only while resolving the + conflict and should not be included in the package. diff --git a/tags/d/debian-adds-cvs-control-dir.tag b/tags/d/debian-adds-cvs-control-dir.tag new file mode 100644 index 0000000..29311eb --- /dev/null +++ b/tags/d/debian-adds-cvs-control-dir.tag @@ -0,0 +1,11 @@ +Tag: debian-adds-cvs-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-cvs-control-dir +Explanation: The Debian diff or native package contains files in a CVS directory. + These are usually artifacts of the revision control system used by the + Debian maintainer and not useful in a diff or native package. + <code>dpkg-source</code> will automatically exclude these if it is passed + <code>-I</code> or <code>-i</code> for native and non-native packages respectively. +See-Also: dpkg-source(1) diff --git a/tags/d/debian-adds-editor-backup-file.tag b/tags/d/debian-adds-editor-backup-file.tag new file mode 100644 index 0000000..7cefaf5 --- /dev/null +++ b/tags/d/debian-adds-editor-backup-file.tag @@ -0,0 +1,11 @@ +Tag: debian-adds-editor-backup-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-editor-backup-file +Explanation: The Debian diff or native package contains a file ending in + <code>~</code> or of the form <code>.xxx.swp</code>, which is normally either an + Emacs or vim backup file or a backup file created by programs such as + <code>autoheader</code> or <code>debconf-updatepo</code>. This usually causes no + harm, but it's messy and bloats the size of the Debian diff to no useful + purpose. diff --git a/tags/d/debian-adds-git-control-dir.tag b/tags/d/debian-adds-git-control-dir.tag new file mode 100644 index 0000000..2469e4a --- /dev/null +++ b/tags/d/debian-adds-git-control-dir.tag @@ -0,0 +1,12 @@ +Tag: debian-adds-git-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-git-control-dir +Explanation: The Debian diff or native package contains files in a .git + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + <code>dpkg-source</code> will automatically exclude these if it is passed + <code>-I</code> or <code>-i</code> for native and non-native packages respectively. +See-Also: + dpkg-source(1) diff --git a/tags/d/debian-adds-hg-control-dir.tag b/tags/d/debian-adds-hg-control-dir.tag new file mode 100644 index 0000000..8329d6a --- /dev/null +++ b/tags/d/debian-adds-hg-control-dir.tag @@ -0,0 +1,12 @@ +Tag: debian-adds-hg-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-hg-control-dir +Explanation: The Debian diff or native package contains files in a .hg + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + <code>dpkg-source</code> will automatically exclude these if it is passed + <code>-I</code> or <code>-i</code> for native and non-native packages respectively. +See-Also: + dpkg-source(1) diff --git a/tags/d/debian-adds-hg-tags-file.tag b/tags/d/debian-adds-hg-tags-file.tag new file mode 100644 index 0000000..84eac9c --- /dev/null +++ b/tags/d/debian-adds-hg-tags-file.tag @@ -0,0 +1,9 @@ +Tag: debian-adds-hg-tags-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-hg-tags-file +Explanation: The Debian diff or native package contains an <code>.hgtags</code> + file. This file is Mercurial metadata that should normally not be + distributed. It stores hashes of tagged commits in a Mercurial + repository and isn't therefore useful without the repository. diff --git a/tags/d/debian-adds-patch-failure-file.tag b/tags/d/debian-adds-patch-failure-file.tag new file mode 100644 index 0000000..134c6ff --- /dev/null +++ b/tags/d/debian-adds-patch-failure-file.tag @@ -0,0 +1,10 @@ +Tag: debian-adds-patch-failure-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-patch-failure-file +Explanation: The Debian diff or native package contains a file that looks like + the files left behind by the <code>patch</code> utility when it cannot + completely apply a diff. This may be left over from a patch applied by + the maintainer. Normally such files should not be included in the + package. diff --git a/tags/d/debian-adds-quilt-control-dir.tag b/tags/d/debian-adds-quilt-control-dir.tag new file mode 100644 index 0000000..3134c4f --- /dev/null +++ b/tags/d/debian-adds-quilt-control-dir.tag @@ -0,0 +1,12 @@ +Tag: debian-adds-quilt-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-quilt-control-dir +Explanation: The Debian diff or native package contains files in a directory + used by quilt, which are not useful in a diff or native package. + <code>dpkg-source</code> will automatically exclude these if it is passed + <code>-I</code> or <code>-i</code> for native and non-native packages + respectively. +See-Also: + dpkg-source(1) diff --git a/tags/d/debian-adds-svk-commit-file.tag b/tags/d/debian-adds-svk-commit-file.tag new file mode 100644 index 0000000..59175ed --- /dev/null +++ b/tags/d/debian-adds-svk-commit-file.tag @@ -0,0 +1,8 @@ +Tag: debian-adds-svk-commit-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-svk-commit-file +Explanation: The Debian diff or native package contains an + <code>svk-commitNNN.tmp</code>, almost certainly a left-over from a failed + svk commit by the Debian package maintainer. diff --git a/tags/d/debian-adds-svn-commit-file.tag b/tags/d/debian-adds-svn-commit-file.tag new file mode 100644 index 0000000..56db3ef --- /dev/null +++ b/tags/d/debian-adds-svn-commit-file.tag @@ -0,0 +1,8 @@ +Tag: debian-adds-svn-commit-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-svn-commit-file +Explanation: The Debian diff or native package contains an + <code>svn-commit(.NNN).tmp</code>, almost certainly a left-over from a failed + Subversion commit by the Debian package maintainer. diff --git a/tags/d/debian-adds-svn-conflict-file.tag b/tags/d/debian-adds-svn-conflict-file.tag new file mode 100644 index 0000000..fc170c2 --- /dev/null +++ b/tags/d/debian-adds-svn-conflict-file.tag @@ -0,0 +1,10 @@ +Tag: debian-adds-svn-conflict-file +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-svn-conflict-file +Explanation: The Debian diff or native package contains a file that looks like a + Subversion conflict file. These are generated by Subversion when a + conflict was detected while merging local changes with updates from a + source repository. Use <code>svn resolved</code> to remove them and clear + the Subversion conflict state after you have resolved the conflict. diff --git a/tags/d/debian-adds-svn-control-dir.tag b/tags/d/debian-adds-svn-control-dir.tag new file mode 100644 index 0000000..5c9c73f --- /dev/null +++ b/tags/d/debian-adds-svn-control-dir.tag @@ -0,0 +1,11 @@ +Tag: debian-adds-svn-control-dir +Severity: warning +Check: files/artifact +Renamed-From: + diff-contains-svn-control-dir +Explanation: The Debian diff or native package contains files in an .svn + directory. These are usually artifacts of the revision control system + used by the Debian maintainer and not useful in a diff or native package. + <code>dpkg-source</code> will automatically exclude these if it is passed + <code>-I</code> or <code>-i</code> for native and non-native packages respectively. +See-Also: dpkg-source(1) diff --git a/tags/d/debian-build-system.tag b/tags/d/debian-build-system.tag new file mode 100644 index 0000000..70282ea --- /dev/null +++ b/tags/d/debian-build-system.tag @@ -0,0 +1,5 @@ +Tag: debian-build-system +Severity: classification +Check: debhelper +Explanation: This is the build system that Lintian believes the package is + using. diff --git a/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag b/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag new file mode 100644 index 0000000..4b2030e --- /dev/null +++ b/tags/d/debian-changelog-file-contains-obsolete-user-emacs-settings.tag @@ -0,0 +1,8 @@ +Tag: debian-changelog-file-contains-obsolete-user-emacs-settings +Severity: warning +Check: debian/changelog +Explanation: The add-log-mailing-address variable is no longer honored in + debian-changelog-mode, and should not appear in packages' changelog + files. Instead, put something like this in your ~/.emacs: + . + (setq debian-changelog-mailing-address "userid@debian.org") diff --git a/tags/d/debian-changelog-file-is-a-symlink.tag b/tags/d/debian-changelog-file-is-a-symlink.tag new file mode 100644 index 0000000..a9ec71b --- /dev/null +++ b/tags/d/debian-changelog-file-is-a-symlink.tag @@ -0,0 +1,13 @@ +Tag: debian-changelog-file-is-a-symlink +Severity: warning +Check: debian/changelog +Explanation: The Debian changelog file is a symlink to a file in a different + directory or not found in this package. Please don't do this. It makes + package checking and manipulation unnecessarily difficult. Because it was + a symlink, the Debian changelog file was not checked for other + problems. (Symlinks to another file in /usr/share/doc/*pkg* or a + subdirectory thereof are fine and should not trigger this warning.) + . + To refer to the changelog, copyright, and other documentation files of + another package that this one depends on, please symlink the entire + /usr/share/doc/*pkg* directory rather than individual files. diff --git a/tags/d/debian-changelog-file-missing-or-wrong-name.tag b/tags/d/debian-changelog-file-missing-or-wrong-name.tag new file mode 100644 index 0000000..4584e0a --- /dev/null +++ b/tags/d/debian-changelog-file-missing-or-wrong-name.tag @@ -0,0 +1,11 @@ +Tag: debian-changelog-file-missing-or-wrong-name +Severity: error +Check: debian/changelog +Explanation: Each Debian package (which provides a /usr/share/doc/*pkg* + directory) must install a Debian changelog file in + /usr/share/doc/*pkg*/changelog.Debian.gz + . + A common error is to name the Debian changelog like an upstream changelog + (/usr/share/doc/*pkg*/changelog.gz); therefore, Lintian will apply + further checks to such a file if it exists even after issuing this error. +See-Also: debian-policy 12.7 diff --git a/tags/d/debian-changelog-has-wrong-day-of-week.tag b/tags/d/debian-changelog-has-wrong-day-of-week.tag new file mode 100644 index 0000000..8df5e05 --- /dev/null +++ b/tags/d/debian-changelog-has-wrong-day-of-week.tag @@ -0,0 +1,13 @@ +Tag: debian-changelog-has-wrong-day-of-week +Severity: warning +Check: debian/changelog +Explanation: The date in the changelog entry is not consistent with the actual + day of that week. Either the date is wrong or the day of week is wrong. + . + 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 +Renamed-From: + debian-changelog-has-wrong-weekday diff --git a/tags/d/debian-changelog-line-too-long.tag b/tags/d/debian-changelog-line-too-long.tag new file mode 100644 index 0000000..04670c3 --- /dev/null +++ b/tags/d/debian-changelog-line-too-long.tag @@ -0,0 +1,7 @@ +Tag: debian-changelog-line-too-long +Severity: warning +Check: debian/changelog +Explanation: The given line of the latest changelog entry is over 80 columns. + Such changelog entries may look poor in terminal windows and mail + messages and be annoying to read. Please wrap changelog entries at 80 + columns or less where possible. diff --git a/tags/d/debian-changelog-line-too-short.tag b/tags/d/debian-changelog-line-too-short.tag new file mode 100644 index 0000000..79f191a --- /dev/null +++ b/tags/d/debian-changelog-line-too-short.tag @@ -0,0 +1,21 @@ +Tag: debian-changelog-line-too-short +Severity: pedantic +Check: debian/changelog +Explanation: The given line of the latest changelog entry appears to contain a + very terse entry. + . + This can make it hard for others to understand the changelog entry. + Please keep in mind that: + . + - It is not uncommon that people read changelog entries that are more + than a decade old to understand why a change was made or why a + package works in a specific way. + - Many users will read the changelog via + <code>apt-listchanges(1)</code> + - The information in <code>debian/changelog</code> is permanent. + . + Examples for entries that are too short include "dh 11" or simply + "R³" - these could be expanded to, for example: + . + - Switch to debhelper compat 11. + - Set Rules-Requires-Root: no. diff --git a/tags/d/debian-control-file-is-a-symlink.tag b/tags/d/debian-control-file-is-a-symlink.tag new file mode 100644 index 0000000..79304c4 --- /dev/null +++ b/tags/d/debian-control-file-is-a-symlink.tag @@ -0,0 +1,11 @@ +Tag: debian-control-file-is-a-symlink +Severity: warning +Check: debian/control/link +Explanation: The <code>debian/control</code> file is a symbolic link. + . + It is not recommended to use anything other than plain files for the required + source files. Using links makes it harder to check and manipulate sources + automatically. + . + If the file must be available under multiple names, please make + <code>debian/control</code> the real file and let the other names point to it. diff --git a/tags/d/debian-control-has-dbgsym-package.tag b/tags/d/debian-control-has-dbgsym-package.tag new file mode 100644 index 0000000..5ecb70e --- /dev/null +++ b/tags/d/debian-control-has-dbgsym-package.tag @@ -0,0 +1,10 @@ +Tag: debian-control-has-dbgsym-package +Severity: error +Check: debug/automatic +Explanation: The <code>debian/control</code> file declares a <code>-dbgsym</code> + package. Those are now generated automatically. + . + Please remove the declaration and rely on the automatic process. +See-Also: + Bug#858117, + https://wiki.debian.org/DebugPackage diff --git a/tags/d/debian-control-has-empty-field.tag b/tags/d/debian-control-has-empty-field.tag new file mode 100644 index 0000000..a1f9634 --- /dev/null +++ b/tags/d/debian-control-has-empty-field.tag @@ -0,0 +1,8 @@ +Tag: debian-control-has-empty-field +Severity: info +Check: debian/control/field/empty +Explanation: The field on this line of <code>debian/control</code> is empty. + It is permitted in the syntax of Debian control files, but the field is + ignored. + . + Please consider removing the empty field. diff --git a/tags/d/debian-control-has-obsolete-dbg-package.tag b/tags/d/debian-control-has-obsolete-dbg-package.tag new file mode 100644 index 0000000..0949c2a --- /dev/null +++ b/tags/d/debian-control-has-obsolete-dbg-package.tag @@ -0,0 +1,14 @@ +Tag: debian-control-has-obsolete-dbg-package +Severity: info +Check: debug/obsolete +Explanation: The <code>debian/control</code> file declares a + <code>-dbg</code> package. + . + Debug packages are now generated automatically. It reduces the space requirements + for archive mirrors for regular operations. + . + Please drop the <code>-dbg</code> package the <code>debian/control</code> file. + Do not change it to a dummy package that depends on the <code>-dbgsym</code> + package. +See-Also: + https://wiki.debian.org/AutomaticDebugPackages diff --git a/tags/d/debian-control-has-unusual-field-spacing.tag b/tags/d/debian-control-has-unusual-field-spacing.tag new file mode 100644 index 0000000..5158baf --- /dev/null +++ b/tags/d/debian-control-has-unusual-field-spacing.tag @@ -0,0 +1,10 @@ +Tag: debian-control-has-unusual-field-spacing +Severity: pedantic +Check: debian/control/field/spacing +Explanation: A field in the <code>debian/control</code> file has an unusual + amount of whitespace after the colon. + . + The syntax for Deb822 files permits any kind of space, but according to Policy + there is a convention to use a single space after the colon. +See-Also: + debian-policy 5.1 diff --git a/tags/d/debian-control-repeats-field-name-in-value.tag b/tags/d/debian-control-repeats-field-name-in-value.tag new file mode 100644 index 0000000..af206fe --- /dev/null +++ b/tags/d/debian-control-repeats-field-name-in-value.tag @@ -0,0 +1,9 @@ +Tag: debian-control-repeats-field-name-in-value +Severity: warning +Check: debian/control/field/doubled-up +Explanation: The field on this line of <code>debian/control</code> repeats + the field name in the value of the field. As an example: + . + Maintainer: Maintainer: Some Name <maintainer@mail.example.com> +See-Also: + debian-policy 5.1 diff --git a/tags/d/debian-copyright-is-symlink.tag b/tags/d/debian-copyright-is-symlink.tag new file mode 100644 index 0000000..c0c9e6d --- /dev/null +++ b/tags/d/debian-copyright-is-symlink.tag @@ -0,0 +1,7 @@ +Tag: debian-copyright-is-symlink +Severity: warning +Check: debian/copyright +Explanation: The file <code>debian/copyright</code> is a symlink instead of a regular + file. This makes package checking and manipulation more difficult. + . + This problem may have prevented Lintian from performing other checks. diff --git a/tags/d/debian-files-list-in-source.tag b/tags/d/debian-files-list-in-source.tag new file mode 100644 index 0000000..063c574 --- /dev/null +++ b/tags/d/debian-files-list-in-source.tag @@ -0,0 +1,9 @@ +Tag: debian-files-list-in-source +Severity: error +Check: debian/files +Explanation: Leaving <code>debian/files</code> causes problems for the autobuilders, + since that file will likely include the list of .deb files for another + architecture, which will cause dpkg-buildpackage run by the buildd to fail. + . + The clean rule for the package should remove this file. +See-Also: debian-policy 4.12 diff --git a/tags/d/debian-news-entry-has-strange-distribution.tag b/tags/d/debian-news-entry-has-strange-distribution.tag new file mode 100644 index 0000000..552e89c --- /dev/null +++ b/tags/d/debian-news-entry-has-strange-distribution.tag @@ -0,0 +1,8 @@ +Tag: debian-news-entry-has-strange-distribution +Severity: warning +Check: debian/changelog +Explanation: The latest entry in NEWS.Debian has an unusual distribution name. + This field is ignored by the archive software, so its value doesn't truly + matter, but it may be confusing to users reading the entry if the + distribution doesn't match the distribution for the same entry in the + Debian changelog file. diff --git a/tags/d/debian-news-entry-has-unknown-version.tag b/tags/d/debian-news-entry-has-unknown-version.tag new file mode 100644 index 0000000..c84fdcb --- /dev/null +++ b/tags/d/debian-news-entry-has-unknown-version.tag @@ -0,0 +1,8 @@ +Tag: debian-news-entry-has-unknown-version +Severity: warning +Check: debian/changelog +Explanation: The version number of the most recent <code>NEWS.Debian</code> entry + does not match any of the version numbers in the changelog file for this + package. This usually means the version in <code>NEWS.Debian</code> needs to + be updated to match a change to package version that happened after the + <code>NEWS.Debian</code> entry was written. diff --git a/tags/d/debian-news-entry-uses-asterisk.tag b/tags/d/debian-news-entry-uses-asterisk.tag new file mode 100644 index 0000000..ce882b0 --- /dev/null +++ b/tags/d/debian-news-entry-uses-asterisk.tag @@ -0,0 +1,8 @@ +Tag: debian-news-entry-uses-asterisk +Severity: info +Check: debian/changelog +Explanation: The latest entry in NEWS.Debian appears to use asterisks to present + changes in a bulleted list, similar to the normal changelog syntax. The + Debian Developer's Reference recommends using regular paragraphs in + NEWS.Debian rather than a bulleted list. +See-Also: developer-reference 6.3.4 diff --git a/tags/d/debian-news-file-not-compressed.tag b/tags/d/debian-news-file-not-compressed.tag new file mode 100644 index 0000000..8e2bc67 --- /dev/null +++ b/tags/d/debian-news-file-not-compressed.tag @@ -0,0 +1,6 @@ +Tag: debian-news-file-not-compressed +Severity: warning +Check: debian/changelog +Explanation: NEWS.Debian files should be compressed using "gzip -9". The file + must always have the same name. +See-Also: developer-reference 6.3.4 diff --git a/tags/d/debian-pycompat-is-obsolete.tag b/tags/d/debian-pycompat-is-obsolete.tag new file mode 100644 index 0000000..394495e --- /dev/null +++ b/tags/d/debian-pycompat-is-obsolete.tag @@ -0,0 +1,6 @@ +# Imported from lintian4python (python/helpers) +Tag: debian-pycompat-is-obsolete +Severity: info +Check: languages/python/obsolete +Explanation: The file <code>debian/pycompat</code> is not used by any modern + Python helper. It should be safe to remove the file. diff --git a/tags/d/debian-pyversions-is-obsolete.tag b/tags/d/debian-pyversions-is-obsolete.tag new file mode 100644 index 0000000..0efdebd --- /dev/null +++ b/tags/d/debian-pyversions-is-obsolete.tag @@ -0,0 +1,8 @@ +Tag: debian-pyversions-is-obsolete +Severity: info +Check: languages/python/obsolete +Explanation: This package contains a <code>debian/pyversions</code> file. Since + dh_python2 it has been recommended to use the + <code>X-Python3-Version</code> field in <code>debian/control</code> instead. +See-Also: https://wiki.debian.org/Python/TransitionToDHPython2, + https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-specifying_versions diff --git a/tags/d/debian-revision-is-zero.tag b/tags/d/debian-revision-is-zero.tag new file mode 100644 index 0000000..1a4ac6d --- /dev/null +++ b/tags/d/debian-revision-is-zero.tag @@ -0,0 +1,10 @@ +Tag: debian-revision-is-zero +Severity: error +Check: fields/version +Renamed-From: debian-revision-should-not-be-zero +Explanation: The Debian version part (the part after the -) should start with one, + not with zero. This is to ensure that a correctly-done Maintainer Upload will + always have a higher version number than a Non-Maintainer upload: a NMU could + have been prepared which introduces this upstream version with + Debian-revision -0.1 +See-Also: developer-reference 5.11.2 diff --git a/tags/d/debian-revision-not-well-formed.tag b/tags/d/debian-revision-not-well-formed.tag new file mode 100644 index 0000000..a583890 --- /dev/null +++ b/tags/d/debian-revision-not-well-formed.tag @@ -0,0 +1,7 @@ +Tag: debian-revision-not-well-formed +Severity: warning +Check: fields/version +Explanation: The Debian version part (the part after the -) should consist of one + or two dot-separated parts: one for a regular maintainer release or two + for a source-NMU. +See-Also: developer-reference 5.11.2, debian-policy 5.6.12 diff --git a/tags/d/debian-rules-calls-debhelper-in-odd-order.tag b/tags/d/debian-rules-calls-debhelper-in-odd-order.tag new file mode 100644 index 0000000..a768c7e --- /dev/null +++ b/tags/d/debian-rules-calls-debhelper-in-odd-order.tag @@ -0,0 +1,10 @@ +Tag: debian-rules-calls-debhelper-in-odd-order +Severity: warning +Check: debian/rules +Explanation: One of the targets in the <code>debian/rules</code> file for this + package calls debhelper programs in an odd order. Normally, + dh_makeshlibs should be run before dh_shlibdeps or dh_installdeb, and + dh_shlibdeps should be run before dh_gencontrol. dh_builddeb should be + the last debhelper action when building the package, after any of the + other programs mentioned. Calling these programs in the wrong order may + cause incorrect or missing package files and metadata. diff --git a/tags/d/debian-rules-calls-pwd.tag b/tags/d/debian-rules-calls-pwd.tag new file mode 100644 index 0000000..c27c79b --- /dev/null +++ b/tags/d/debian-rules-calls-pwd.tag @@ -0,0 +1,13 @@ +Tag: debian-rules-calls-pwd +Severity: warning +Check: debian/rules +Renamed-From: debian-rules-should-not-use-pwd +Explanation: The <code>debian/rules</code> file for this package appears to use the + variable $(PWD) to refer to the current directory. This variable is not + set by GNU make and therefore will have whatever value it has in the + environment, which may not be the actual current directory. Some ways of + building Debian packages (such as through sudo) will clear the PWD + environment variable. + . + Instead of $(PWD), use $(CURDIR), which is set by GNU make, ignores the + environment, and is guaranteed to always be set. diff --git a/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag b/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag new file mode 100644 index 0000000..c00865f --- /dev/null +++ b/tags/d/debian-rules-contains-unnecessary-get-orig-source-target.tag @@ -0,0 +1,15 @@ +Tag: debian-rules-contains-unnecessary-get-orig-source-target +Severity: info +Check: debian/rules +Explanation: This package's <code>debian/rules</code> file contains a + <code>get-orig-source</code> target that appears to be unnecessary. For + example, the package might simply contain a single call to uscan(1). + . + Such calls are not ideal; maintainers should be able to call uscan with + their own choice of options and they additionally encourage the + proliferation of boilerplate code across the archive. + . + Since Debian Policy 4.1.4, packages are encouraged to migrate to uscan + and a <code>Files-Excluded</code> header in the <code>debian/copyright</code> + file. +See-Also: uscan(1) diff --git a/tags/d/debian-rules-ignores-make-clean-error.tag b/tags/d/debian-rules-ignores-make-clean-error.tag new file mode 100644 index 0000000..b4bc8c4 --- /dev/null +++ b/tags/d/debian-rules-ignores-make-clean-error.tag @@ -0,0 +1,19 @@ +Tag: debian-rules-ignores-make-clean-error +Severity: warning +Check: debian/rules +Explanation: A rule in the <code>debian/rules</code> file for this package calls the + package's clean or distclean target with a line like: + . + -$(MAKE) distclean + or + $(MAKE) -i distclean + . + The leading "-" or the option -i tells make to ignore all errors. + Normally this is done for packages using Autoconf since Makefile may not + exist. However, this line ignores all other error messages, not just + the missing Makefile error. It's better to use: + . + [ ! -f Makefile ] || $(MAKE) distclean + . + so that other error messages from the clean or distclean rule will still + be caught (or just remove the "-" if the package uses a static makefile). diff --git a/tags/d/debian-rules-is-dh_make-template.tag b/tags/d/debian-rules-is-dh_make-template.tag new file mode 100644 index 0000000..ca95319 --- /dev/null +++ b/tags/d/debian-rules-is-dh_make-template.tag @@ -0,0 +1,7 @@ +Tag: debian-rules-is-dh_make-template +Severity: error +Check: debian/rules +Explanation: The debian/rules file appears to be an unmodified or insufficiently + modified copy of the dh_make template. + . + Please double-check the rules file. diff --git a/tags/d/debian-rules-is-symlink.tag b/tags/d/debian-rules-is-symlink.tag new file mode 100644 index 0000000..509b435 --- /dev/null +++ b/tags/d/debian-rules-is-symlink.tag @@ -0,0 +1,11 @@ +Tag: debian-rules-is-symlink +Severity: warning +Check: debian/rules +Explanation: The file <code>debian/rules</code> is a symlink instead of a regular + file. This is unnecessary and makes package checking and manipulation + more difficult. If the rules file should be available in the source + package under multiple names, make <code>debian/rules</code> the real + file and the other names symlinks to it. + . + This problem may have prevented Lintian from performing other checks, + leading to undetected changelog errors. diff --git a/tags/d/debian-rules-missing-recommended-target.tag b/tags/d/debian-rules-missing-recommended-target.tag new file mode 100644 index 0000000..fcb50b8 --- /dev/null +++ b/tags/d/debian-rules-missing-recommended-target.tag @@ -0,0 +1,10 @@ +Tag: debian-rules-missing-recommended-target +Severity: warning +Check: debian/rules +Explanation: The <code>debian/rules</code> file for this package does not + provide all recommended targets. + . + There are currently no recommended targets. Please contact the Lintian + maintainers when you encounter this tag. +See-Also: + debian-policy 4.9 diff --git a/tags/d/debian-rules-missing-required-target.tag b/tags/d/debian-rules-missing-required-target.tag new file mode 100644 index 0000000..7e3c671 --- /dev/null +++ b/tags/d/debian-rules-missing-required-target.tag @@ -0,0 +1,33 @@ +Tag: debian-rules-missing-required-target +Severity: error +Check: debian/rules +Explanation: The <code>debian/rules</code> file does not provide all required + targets. Both <code>build-arch</code> and <code>build-indep</code> must be + provided even if they do nothing. + . + For sources that do not currently split the building of architecture dependent + and independent installables, the following rules will fall back on the + <code>build</code> target: + . + build-arch: build + build-indep: build + . + Some say that the following form is recommended: + . + build: build-arch build-indep + build-arch: build-stamp + build-indep: build-stamp + build-stamp: + build here + . + As a modern alternative, you may wish to use the <code>dh</code> sequencer + instead. Your sources will no longer be affected by this issue. + . + Policy now requires those targets. Please add them to avoid rejection. + . + In your next upload, please also close the bug from the mass bug filing you + received. Details are described in the message to <code>debian-devel</code> + cited below. +See-Also: + debian-policy 4.9, + https://lists.debian.org/debian-devel/2021/11/msg00052.html diff --git a/tags/d/debian-rules-not-a-makefile.tag b/tags/d/debian-rules-not-a-makefile.tag new file mode 100644 index 0000000..8264890 --- /dev/null +++ b/tags/d/debian-rules-not-a-makefile.tag @@ -0,0 +1,8 @@ +Tag: debian-rules-not-a-makefile +Severity: error +Check: debian/rules +See-Also: debian-policy 4.9 +Explanation: The <code>debian/rules</code> file for this package does not appear to + be a makefile or does not start with the required line. + <code>debian/rules</code> must be a valid makefile and must have + "<code>#!/usr/bin/make -f</code>" as its first line. diff --git a/tags/d/debian-rules-not-executable.tag b/tags/d/debian-rules-not-executable.tag new file mode 100644 index 0000000..ceb1f9c --- /dev/null +++ b/tags/d/debian-rules-not-executable.tag @@ -0,0 +1,7 @@ +Tag: debian-rules-not-executable +Severity: pedantic +See-Also: debian-policy 4.9 +Check: debian/rules +Explanation: The <code>debian/rules</code> file for this package does not appear to + be marked as executable and should be changed via <code>chmod +x</code> or + similar. diff --git a/tags/d/debian-rules-parses-dpkg-parsechangelog.tag b/tags/d/debian-rules-parses-dpkg-parsechangelog.tag new file mode 100644 index 0000000..4b5a0bd --- /dev/null +++ b/tags/d/debian-rules-parses-dpkg-parsechangelog.tag @@ -0,0 +1,12 @@ +Tag: debian-rules-parses-dpkg-parsechangelog +Severity: info +Check: debian/rules +Explanation: The rules file appears to be parsing the output of dpkg-parsechangelog to + determine the current package version name, version, or timestamp, etc. + . + Since dpkg 1.16.1, this could be replaced by including the + /usr/share/dpkg/pkg-info.mk Makefile library and using the + DEB_{SOURCE,VERSION} or SOURCE_DATE_EPOCH variables. + . + Using this library is not only cleaner and more efficient, it handles many + corner-cases such as binNMUs, epoch versions, etc. diff --git a/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag b/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag new file mode 100644 index 0000000..7682838 --- /dev/null +++ b/tags/d/debian-rules-passes-version-info-to-dh_shlibdeps.tag @@ -0,0 +1,10 @@ +Tag: debian-rules-passes-version-info-to-dh_shlibdeps +Severity: warning +Check: debian/rules +Explanation: The <code>debian/rules</code> file for this package has a call to + <code>dh_shlibdeps(1)</code> with the <code>--version-info</code> or + <code>-V</code> option. + . + However, this has no effect on <code>dh_shlibdeps</code>; you probably + wanted to pass this option to <code>dh_makeshlibs(1)</code> instead. +See-Also: dh_shlibdeps(1), dh_makeshlibs(1) diff --git a/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag b/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag new file mode 100644 index 0000000..381527e --- /dev/null +++ b/tags/d/debian-rules-sets-DEB_BUILD_OPTIONS.tag @@ -0,0 +1,8 @@ +Tag: debian-rules-sets-DEB_BUILD_OPTIONS +Severity: warning +Check: debian/rules +See-Also: dpkg-buildflags(1) +Explanation: The <code>debian/rules</code> file sets the DEB_BUILD_OPTIONS variable, + which will override any user-specified build profile. + . + Please replace with DEB_BUILD_MAINT_OPTIONS. diff --git a/tags/d/debian-rules-sets-DH_COMPAT.tag b/tags/d/debian-rules-sets-DH_COMPAT.tag new file mode 100644 index 0000000..21e79f0 --- /dev/null +++ b/tags/d/debian-rules-sets-DH_COMPAT.tag @@ -0,0 +1,8 @@ +Tag: debian-rules-sets-DH_COMPAT +Severity: warning +Check: debian/rules +See-Also: debhelper(7) +Explanation: As of debhelper version 4, the DH_COMPAT environment variable is + only to be used for temporarily overriding <code>debian/compat</code>. Any + line in <code>debian/rules</code> that sets it globally should be deleted and + a separate <code>debian/compat</code> file created if needed. diff --git a/tags/d/debian-rules-sets-dpkg-architecture-variable.tag b/tags/d/debian-rules-sets-dpkg-architecture-variable.tag new file mode 100644 index 0000000..b95718a --- /dev/null +++ b/tags/d/debian-rules-sets-dpkg-architecture-variable.tag @@ -0,0 +1,16 @@ +Tag: debian-rules-sets-dpkg-architecture-variable +Severity: warning +Check: debian/rules +See-Also: dpkg-architecture(1) +Explanation: The <code>debian/rules</code> file sets one or more + <code>dpkg-architecture</code> variables such as <code>DEB_BUILD_ARCH</code>. + . + These variables are pre-initialized in the environment when running under + <code>dpkg-buildpackage</code> - avoiding these assignments can reduce package + build time. + . + Please use: + . + include /usr/share/dpkg/architecture.mk + . + instead, or replace the assignment operator with <code>?=</code>. diff --git a/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag b/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag new file mode 100644 index 0000000..390cc70 --- /dev/null +++ b/tags/d/debian-rules-should-not-set-CFLAGS-from-noopt.tag @@ -0,0 +1,9 @@ +Tag: debian-rules-should-not-set-CFLAGS-from-noopt +Severity: warning +Check: debian/rules +See-Also: dpkg-buildflags(1) +Explanation: The <code>debian/rules</code> file for this package appears to set + <code>CFLAGS</code> if the value of <code>DEB_BUILD_OPTIONS</code> contains + <code>noopt</code>. + . + This has been obsoleted in favour of <code>dpkg-buildflags</code>. diff --git a/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag b/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag new file mode 100644 index 0000000..d757fd2 --- /dev/null +++ b/tags/d/debian-rules-should-not-use-DH_EXTRA_ADDONS.tag @@ -0,0 +1,7 @@ +Tag: debian-rules-should-not-use-DH_EXTRA_ADDONS +Severity: warning +Check: debian/rules +Explanation: The DH_EXTRA_ADDONS variable is designed for local or downstream build + use and not for use in debian/rules + . + dh(1)'s <code>--with</code> should be used instead. diff --git a/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag b/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag new file mode 100644 index 0000000..9147ffe --- /dev/null +++ b/tags/d/debian-rules-should-not-use-sanitize-all-buildflag.tag @@ -0,0 +1,17 @@ +Tag: debian-rules-should-not-use-sanitize-all-buildflag +Severity: error +Check: debian/rules +Explanation: This package's <code>debian/rules</code> file contains a + <code>DEB_BUILD_MAINT_OPTIONS</code> assignment that enables the + <code>sanitize=+all</code> build flag. + . + This option instructs the compiler to enable options designed to + protect the binary against memory corruptions, memory leaks, use after + free, threading data races, and undefined behavior bugs. + . + However, this options should not be used for production Debian binaries + as they can reduce reliability for conformant code, reduce security or + even functionality. + . + Please remove the reference to <code>sanitize=+all</code>. +See-Also: dpkg-buildflags(1), Bug#895811 diff --git a/tags/d/debian-rules-updates-control-automatically.tag b/tags/d/debian-rules-updates-control-automatically.tag new file mode 100644 index 0000000..5a0c228 --- /dev/null +++ b/tags/d/debian-rules-updates-control-automatically.tag @@ -0,0 +1,9 @@ +Tag: debian-rules-updates-control-automatically +Severity: error +Check: debian/rules +Renamed-From: debian-rules-should-not-automatically-update-control +Explanation: DEB_AUTO_UPDATE_DEBIAN_CONTROL + appears to be set to <code>yes</code> in + the <code>debian/rules</code> file. This activates a feature of CDBS which + may not be used in packages uploaded to the Debian archive. +See-Also: https://ftp-master.debian.org/REJECT-FAQ.html diff --git a/tags/d/debian-rules-uses-as-needed-linker-flag.tag b/tags/d/debian-rules-uses-as-needed-linker-flag.tag new file mode 100644 index 0000000..f40e73d --- /dev/null +++ b/tags/d/debian-rules-uses-as-needed-linker-flag.tag @@ -0,0 +1,15 @@ +Tag: debian-rules-uses-as-needed-linker-flag +Severity: pedantic +Experimental: yes +Check: debian/rules +Explanation: The <code>debian/rules</code> file for this package uses the + <code>-Wl,--as-needed</code> linker flag. + . + The bullseye toolchain defaults to linking with <code>--as-needed</code> and + therefore it should no longer be necessary to inject this into the + build process. + . + However, it is not safe to make this change if the package will target + the buster distribution such as via backports to the buster-bpo / + stable-bpo distribution or, during the bookworm cycle itself, the + oldstable-bpo distribution. diff --git a/tags/d/debian-rules-uses-deb-build-opts.tag b/tags/d/debian-rules-uses-deb-build-opts.tag new file mode 100644 index 0000000..0457fb3 --- /dev/null +++ b/tags/d/debian-rules-uses-deb-build-opts.tag @@ -0,0 +1,7 @@ +Tag: debian-rules-uses-deb-build-opts +Severity: warning +Check: debian/rules +Renamed-From: debian-rules-should-not-use-DEB_BUILD_OPTS +Explanation: The standard environment variable for build options is + DEB_BUILD_OPTIONS. Usually, referring to DEB_BUILD_OPTS is a mistake and + DEB_BUILD_OPTIONS was intended instead. diff --git a/tags/d/debian-rules-uses-deprecated-makefile.tag b/tags/d/debian-rules-uses-deprecated-makefile.tag new file mode 100644 index 0000000..c02c0d9 --- /dev/null +++ b/tags/d/debian-rules-uses-deprecated-makefile.tag @@ -0,0 +1,6 @@ +Tag: debian-rules-uses-deprecated-makefile +Severity: warning +Check: debian/rules +Explanation: The <code>debian/rules</code> file for this package appears to + include a Makefile that has been deprecated. Please refer to the + documentation of the providing package for a replacement (if any). diff --git a/tags/d/debian-rules-uses-deprecated-systemd-override.tag b/tags/d/debian-rules-uses-deprecated-systemd-override.tag new file mode 100644 index 0000000..f0f6d31 --- /dev/null +++ b/tags/d/debian-rules-uses-deprecated-systemd-override.tag @@ -0,0 +1,14 @@ +Tag: debian-rules-uses-deprecated-systemd-override +Severity: error +Check: debhelper +Explanation: The <code>debian/rules</code> file for this package has an + <code>override_dh_systemd_enable</code> or + <code>override_dh_systemd_start</code> + target but the package uses debhelper compatibility level 11. + . + The <code>dh_systemd_{enable,start}</code> commands were deprecated in this + compat level and are no longer called. This is likely to cause your + package to not function as intended. + . + Please replace these with calls to <code>dh_installsystemd</code>. +See-Also: debhelper(7) diff --git a/tags/d/debian-rules-uses-installed-python-versions.tag b/tags/d/debian-rules-uses-installed-python-versions.tag new file mode 100644 index 0000000..c25e559 --- /dev/null +++ b/tags/d/debian-rules-uses-installed-python-versions.tag @@ -0,0 +1,17 @@ +Tag: debian-rules-uses-installed-python-versions +Severity: warning +Check: debian/rules +Explanation: The package appears to use <code>py3versions -i</code> to determine + the "installed" Python versions. + . + However, this can cause issues if a Python transition is in progress + as the <code>-minimal</code> variant of the previous version + (eg. <code>python3.X-minimal</code>) remains installed in many environments. + This variant then provides enough of an interpreter to count as being + "installed" but not enough for the tests themselves to succeed in most + cases. This then prevents the overall transition from taking place. + . + Please replace this will a call to all "supported" packages instead + (eg. <code>py3versions -s</code> and ensure <code>python3-all</code> is listed + in the build dependencies. +See-Also: https://lists.debian.org/debian-devel/2020/03/msg00280.html diff --git a/tags/d/debian-rules-uses-special-shell-variable.tag b/tags/d/debian-rules-uses-special-shell-variable.tag new file mode 100644 index 0000000..f59f0ed --- /dev/null +++ b/tags/d/debian-rules-uses-special-shell-variable.tag @@ -0,0 +1,20 @@ +Tag: debian-rules-uses-special-shell-variable +Severity: warning +Check: debian/rules +Renamed-From: + debian-rules-should-not-use-underscore-variable +Explanation: The rules file use the make variable $(_). + . + According to Policy 4.9, 'invoking either of <code>make -f debian/rules + <...></code> or <code>./debian/rules + <args...></code>' must result in identical behavior'. + The <code>$_</code> variable is an easy way to violate that rule + unwittingly. + . + If the <code>rules</code> file uses <code>$(dir $(_))</code> to + discover the directory containing the source package (for example, in order + to implement the <code>get-orig-source</code> target) please replace it + with <code>$(dir $(firstword $(MAKEFILE_LIST)))</code>. +See-Also: + debian-policy 4.9, + https://stackoverflow.com/a/27628164 diff --git a/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag b/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag new file mode 100644 index 0000000..51385af --- /dev/null +++ b/tags/d/debian-rules-uses-supported-python-versions-without-python-all-build-depends.tag @@ -0,0 +1,12 @@ +Tag: debian-rules-uses-supported-python-versions-without-python-all-build-depends +Severity: warning +Check: debian/rules +Explanation: The package appears to use <code>py3versions -s</code> to determine + the "supported" Python versions without specifying <code>python3-all</code> + as a build-dependency. + . + With only the default version of Python installed, the package may + build and test successfully but subsequently fail at runtime when + another, non-default, Python version is present. + . + Please add <code>python3-all</code> as a build-dependency. diff --git a/tags/d/debian-rules-uses-unnecessary-dh-argument.tag b/tags/d/debian-rules-uses-unnecessary-dh-argument.tag new file mode 100644 index 0000000..d82f9d2 --- /dev/null +++ b/tags/d/debian-rules-uses-unnecessary-dh-argument.tag @@ -0,0 +1,9 @@ +Tag: debian-rules-uses-unnecessary-dh-argument +Severity: warning +Check: debhelper +Explanation: The <code>debian/rules</code> file passes the specified argument to + <code>dh $@</code> but it is enabled by default from the mentioned debhelper + compatibility level onwards. + . + Please remove the argument from the call to <code>dh(1)</code>. +See-Also: debhelper(7), dh(1) diff --git a/tags/d/debian-rules-uses-wrong-environment-variable.tag b/tags/d/debian-rules-uses-wrong-environment-variable.tag new file mode 100644 index 0000000..41f2013 --- /dev/null +++ b/tags/d/debian-rules-uses-wrong-environment-variable.tag @@ -0,0 +1,13 @@ +Tag: debian-rules-uses-wrong-environment-variable +Severity: warning +Check: debian/rules +Renamed-From: debian-rules-should-not-use-or-modify-user-only-variable +See-Also: Bug#631786 +Explanation: The rules file appears to be reading or modifying a variable not + intended for use by package maintainers. + . + The special variables <code>DEB_*FLAGS_{SET,APPEND}</code> can be used by + users who want to re-compile Debian packages with special (or + non-standard) build flags. + . + Please use the <code>DEB_*FLAGS_MAINT_{SET,APPEND}</code> flags instead. diff --git a/tags/d/debian-tests-control-autodep8-is-obsolete.tag b/tags/d/debian-tests-control-autodep8-is-obsolete.tag new file mode 100644 index 0000000..0c03030 --- /dev/null +++ b/tags/d/debian-tests-control-autodep8-is-obsolete.tag @@ -0,0 +1,21 @@ +Tag: debian-tests-control-autodep8-is-obsolete +Severity: warning +Check: testsuite +See-Also: autodep8(1) +Explanation: The specified autopkgtest control file is considered obsolete. + . + Before autodep8 version 0.17 and autopkgtest version 5.7 if a + maintainer wished to add tests to the set of tests generated + by autodep8 they provided those tests in a file named + <code>debian/tests/control.autodep8</code>. + . + It is now preferred to declare the additional tests in the regular + <code>debian/tests/control</code> file so that <code>dpkg-source</code> can + pick up the test dependencies. + . + When configured to run autodep8 tests, autopkgtest will run the + additional tests and the autodep8 tests when <code>debian/control</code> + has the proper <code>Testsuite: autopkgtest-*</code> in the source + headers. + . + Please merge the specified file into <code>debian/tests/control</code>. diff --git a/tags/d/debian-upstream-obsolete-path.tag b/tags/d/debian-upstream-obsolete-path.tag new file mode 100644 index 0000000..1995444 --- /dev/null +++ b/tags/d/debian-upstream-obsolete-path.tag @@ -0,0 +1,15 @@ +Tag: debian-upstream-obsolete-path +Severity: error +Check: debian/upstream/metadata +Explanation: Upstream metadata is stored under an obsolete path. + . + Upstream MEtadata GAthered with YAml (UMEGAYA) is an effort to collect + meta-information about upstream projects from any source package + with a publicly accessible VCS via a file called + <code>debian/upstream/metadata</code>. + . + Older versions of this specification used + <code>debian/upstream-metadata.yaml</code> or <code>debian/upstream</code> + as meta-information storage file. + . + You should move any such file to <code>debian/upstream/metadata</code>. diff --git a/tags/d/debian-watch-contains-dh_make-template.tag b/tags/d/debian-watch-contains-dh_make-template.tag new file mode 100644 index 0000000..049c34a --- /dev/null +++ b/tags/d/debian-watch-contains-dh_make-template.tag @@ -0,0 +1,5 @@ +Tag: debian-watch-contains-dh_make-template +Severity: info +Check: debian/watch +Explanation: The watch file contains a standard template included by dh_make. + Please remove them once you have implemented the watch file. diff --git a/tags/d/debian-watch-could-verify-download.tag b/tags/d/debian-watch-could-verify-download.tag new file mode 100644 index 0000000..a48cd57 --- /dev/null +++ b/tags/d/debian-watch-could-verify-download.tag @@ -0,0 +1,9 @@ +Tag: debian-watch-could-verify-download +Severity: warning +Check: debian/watch +See-Also: uscan(1) +Explanation: One or more upstream signing keys are present in the Debian package + but are not being used. + . + Please enable the cryptographic verification of downloads with the + "pgpsigurlmangle" option in your watch file or remove the key. diff --git a/tags/d/debian-watch-does-not-check-openpgp-signature.tag b/tags/d/debian-watch-does-not-check-openpgp-signature.tag new file mode 100644 index 0000000..367b522 --- /dev/null +++ b/tags/d/debian-watch-does-not-check-openpgp-signature.tag @@ -0,0 +1,21 @@ +Tag: debian-watch-does-not-check-openpgp-signature +Severity: pedantic +Check: debian/watch +Experimental: yes +See-Also: uscan(1) +Explanation: This watch file does not specify a means to verify the upstream + tarball using a cryptographic signature. + . + If upstream distributions provides such signatures, please use the + <code>pgpsigurlmangle</code> options in this watch file's <code>opts=</code> to + generate the URL of an upstream OpenPGP signature. This signature is + automatically downloaded and verified against a keyring stored in + <code>debian/upstream/signing-key.asc</code> + . + Of course, not all upstreams provide such signatures but you could + request them as a way of verifying that no third party has modified the + code after its release (projects such as phpmyadmin, unrealircd, and + proftpd have suffered from this kind of attack). +Renamed-From: + debian-watch-does-not-check-gpg-signature + debian-watch-may-check-gpg-signature diff --git a/tags/d/debian-watch-file-in-native-package.tag b/tags/d/debian-watch-file-in-native-package.tag new file mode 100644 index 0000000..977742b --- /dev/null +++ b/tags/d/debian-watch-file-in-native-package.tag @@ -0,0 +1,8 @@ +Tag: debian-watch-file-in-native-package +Severity: warning +Check: debian/watch +See-Also: https://wiki.debian.org/DEHS +Explanation: The package ships a watch file although it is a Debian native + package. DEHS does not process watch files in native packages based on + the reasoning that native packages do not have upstreams to check for new + releases. diff --git a/tags/d/debian-watch-file-is-missing.tag b/tags/d/debian-watch-file-is-missing.tag new file mode 100644 index 0000000..cc1987d --- /dev/null +++ b/tags/d/debian-watch-file-is-missing.tag @@ -0,0 +1,16 @@ +Tag: debian-watch-file-is-missing +Severity: info +Check: debian/watch +See-Also: debian-policy 4.11, uscan(1) +Explanation: This source package is not Debian-native but it does not have a + <code>debian/watch</code> file. This file is used for automatic detection of + new upstream versions by the Debian External Health Status project and + other project infrastructure. If this package is maintained upstream, + please consider adding a <code>debian/watch</code> file to detect new + releases. + . + If the package is not maintained upstream or if upstream uses a + distribution mechanism that cannot be meaningfully monitored by uscan + and the Debian External Health Status project, please consider adding a + <code>debian/watch</code> file containing only comments documenting the + situation. diff --git a/tags/d/debian-watch-file-pubkey-file-is-missing.tag b/tags/d/debian-watch-file-pubkey-file-is-missing.tag new file mode 100644 index 0000000..d12d3b0 --- /dev/null +++ b/tags/d/debian-watch-file-pubkey-file-is-missing.tag @@ -0,0 +1,10 @@ +Tag: debian-watch-file-pubkey-file-is-missing +Severity: error +Check: debian/watch +See-Also: uscan(1) +Explanation: This watch file verifies a cryptographic signature but + the upstream public key is missing. + . + Please add upstream public keys in either + debian/upstream/signing-key.asc or + debian/upstream/signing-key.pgp. diff --git a/tags/d/debian-watch-file-specifies-old-upstream-version.tag b/tags/d/debian-watch-file-specifies-old-upstream-version.tag new file mode 100644 index 0000000..05e4715 --- /dev/null +++ b/tags/d/debian-watch-file-specifies-old-upstream-version.tag @@ -0,0 +1,10 @@ +Tag: debian-watch-file-specifies-old-upstream-version +Severity: warning +Check: debian/watch +Explanation: The watch file specifies an upstream version number which matches + the upstream portion of an old <code>debian/changelog</code> entry, and the + current <code>debian/changelog</code> entry specifies a newer upstream + version. The version number in the watch file is very likely to be + incorrect and probably should be replaced with the current expected + upstream version. Otherwise, DEHS and similar projects will think the + package is out of date even when it may not be. diff --git a/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag b/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag new file mode 100644 index 0000000..cbdbb32 --- /dev/null +++ b/tags/d/debian-watch-file-specifies-wrong-upstream-version.tag @@ -0,0 +1,10 @@ +Tag: debian-watch-file-specifies-wrong-upstream-version +Severity: warning +Check: debian/watch +See-Also: uscan(1) +Explanation: The watch file specifies an upstream version which exactly matches + the version of a <code>debian/changelog</code> entry, this is not a + native package, and no version mangling is being done. The version + field in a watch file should specify the expected upstream version, not + the version of the Debian package. Any epochs and Debian revisions + should be removed first or mangled away. diff --git a/tags/d/debian-watch-file-standard.tag b/tags/d/debian-watch-file-standard.tag new file mode 100644 index 0000000..2b9f387 --- /dev/null +++ b/tags/d/debian-watch-file-standard.tag @@ -0,0 +1,6 @@ +Tag: debian-watch-file-standard +Severity: classification +Check: debian/watch/standard +Explanation: The watch file uses this version standard. The currently known + watch file versions are 2, 3 and 4. Version 1 means it was undeclared. +See-Also: uscan(1) diff --git a/tags/d/debian-watch-file-uses-deprecated-githubredir.tag b/tags/d/debian-watch-file-uses-deprecated-githubredir.tag new file mode 100644 index 0000000..02235cb --- /dev/null +++ b/tags/d/debian-watch-file-uses-deprecated-githubredir.tag @@ -0,0 +1,12 @@ +Tag: debian-watch-file-uses-deprecated-githubredir +Severity: error +Check: debian/watch +See-Also: https://lists.debian.org/debian-devel-announce/2014/10/msg00000.html +Explanation: The watch file specifies a githubredir.debian.net URL, which is deprecated + Instead, use direct links to the tags page: + . + version=3 + https://github.com/<user>/<project>/tags .*/(.*)\.tar\.gz + . + replacing <code><user></code> and <code><project></code> with the Github + username and project respectively. diff --git a/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag b/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag new file mode 100644 index 0000000..5e4c894 --- /dev/null +++ b/tags/d/debian-watch-file-uses-deprecated-sf-redirector-method.tag @@ -0,0 +1,7 @@ +Tag: debian-watch-file-uses-deprecated-sf-redirector-method +Severity: warning +Check: debian/watch +Explanation: The watch file seems to be passing arguments to the redirector + other than a path. Calling the SourceForge redirector with parameters like + <code>project</code> prevents uscan from generating working URIs to the files + and thus has been deprecated and is no longer supported by the redirector. diff --git a/tags/d/debian-watch-lacks-sourceforge-redirector.tag b/tags/d/debian-watch-lacks-sourceforge-redirector.tag new file mode 100644 index 0000000..55545c1 --- /dev/null +++ b/tags/d/debian-watch-lacks-sourceforge-redirector.tag @@ -0,0 +1,16 @@ +Tag: debian-watch-lacks-sourceforge-redirector +Severity: warning +Check: debian/watch +Renamed-From: debian-watch-file-should-use-sf-redirector +See-Also: uscan(1) +Explanation: The watch file specifies a SourceForge page or download server + directly. This is not recommended; SourceForge changes their download + servers and website periodically, requiring watch files to be modified + every time. Instead, use the qa.debian.org redirector by using the magic + URL: + . + http://sf.net/<project>/<tar-name>-(.+)\.tar\.gz + . + replacing <code><project></code> with the name of the SourceForge + project and <code><tar-name></code> with the name of the tarball + distributed within that project. Adjust the filename regex as necessary. diff --git a/tags/d/debian-watch-line-invalid.tag b/tags/d/debian-watch-line-invalid.tag new file mode 100644 index 0000000..82f2eae --- /dev/null +++ b/tags/d/debian-watch-line-invalid.tag @@ -0,0 +1,6 @@ +Tag: debian-watch-line-invalid +Severity: warning +Check: debian/watch +See-Also: uscan(1) +Explanation: The indicated line in the <code>debian/watch</code> file in this + package does not have a regnized format. diff --git a/tags/d/debian-watch-mangles-debian-version-improperly.tag b/tags/d/debian-watch-mangles-debian-version-improperly.tag new file mode 100644 index 0000000..734bda2 --- /dev/null +++ b/tags/d/debian-watch-mangles-debian-version-improperly.tag @@ -0,0 +1,12 @@ +Tag: debian-watch-mangles-debian-version-improperly +Severity: info +Check: debian/watch +Renamed-From: debian-watch-file-should-dversionmangle-not-uversionmangle +See-Also: https://wiki.debian.org/DEHS +Explanation: The version of this package contains <code>dfsg</code>, <code>ds</code>, + or <code>debian</code>, but a misleading upstream version mangling occurs in + the <code>debian/watch</code> file. Since the <code>dfsg</code> string is not + part of the upstream version and its addition is Debian-specific, the + <code>debian/watch</code> file should use the dversionmangle option to + remove, instead of adding in uversionmangle, the <code>dfsg</code> before + comparing version numbers. diff --git a/tags/d/debian-watch-mangles-upstream-version-improperly.tag b/tags/d/debian-watch-mangles-upstream-version-improperly.tag new file mode 100644 index 0000000..aea470d --- /dev/null +++ b/tags/d/debian-watch-mangles-upstream-version-improperly.tag @@ -0,0 +1,10 @@ +Tag: debian-watch-mangles-upstream-version-improperly +Severity: info +Check: debian/watch +Renamed-From: debian-watch-file-should-uversionmangle-not-dversionmangle +See-Also: https://wiki.debian.org/DEHS +Explanation: The version of this package contains <code>alpha</code>, <code>beta</code>, + or <code>rc</code>, but a misleading Debian version mangling occurs in + the <code>debian/watch</code> file. You should use the uversionmangle + option instead of dversionmangle so that the prerelease is sorted by + uscan before a possible future final release. diff --git a/tags/d/debian-watch-not-mangling-version.tag b/tags/d/debian-watch-not-mangling-version.tag new file mode 100644 index 0000000..b436a3a --- /dev/null +++ b/tags/d/debian-watch-not-mangling-version.tag @@ -0,0 +1,13 @@ +Tag: debian-watch-not-mangling-version +Severity: warning +Check: debian/watch +Renamed-From: debian-watch-file-should-mangle-version +See-Also: uscan(1), https://wiki.debian.org/DEHS +Explanation: The version of this package contains <code>dfsg</code>, <code>ds</code>, + or <code>debian</code>, which normally indicates that the upstream source + has been repackaged to comply with the Debian Free Software Guidelines + (or similar reason), but there is no version mangling in the + <code>debian/watch</code> file. Since the <code>dfsg</code> string is not + part of the upstream version, the <code>debian/watch</code> file should + use the dversionmangle option to remove the <code>dfsg</code> before + version number comparison. diff --git a/tags/d/debian-watch-upstream-component.tag b/tags/d/debian-watch-upstream-component.tag new file mode 100644 index 0000000..41c09f0 --- /dev/null +++ b/tags/d/debian-watch-upstream-component.tag @@ -0,0 +1,5 @@ +Tag: debian-watch-upstream-component +Severity: classification +Check: debian/watch +See-Also: uscan(1) +Explanation: Component embedded in debian/watch diff --git a/tags/d/debian-watch-uses-insecure-uri.tag b/tags/d/debian-watch-uses-insecure-uri.tag new file mode 100644 index 0000000..2eb935a --- /dev/null +++ b/tags/d/debian-watch-uses-insecure-uri.tag @@ -0,0 +1,9 @@ +Tag: debian-watch-uses-insecure-uri +Severity: info +Check: debian/watch +Explanation: The watch file uses an unencrypted transport protocol for the + URI such as http:// or ftp://. It is recommended to use a secure + transport such as HTTPS for anonymous read-only access. + . + Upstream may already provide a HTTPS variant of the URI. If not, + please contact them and ask them to consider adding one. diff --git a/tags/d/debug-file-with-no-debug-symbols.tag b/tags/d/debug-file-with-no-debug-symbols.tag new file mode 100644 index 0000000..cdd4aa2 --- /dev/null +++ b/tags/d/debug-file-with-no-debug-symbols.tag @@ -0,0 +1,12 @@ +Tag: debug-file-with-no-debug-symbols +Severity: warning +Check: binaries/debug-symbols/detached +Explanation: The binary is installed as a detached "debug symbols" ELF file, + but it does not appear to have debug information associated with it. + . + A common cause is not passing <code>-g</code> to GCC when compiling. + . + Implementation detail: Lintian checks for the ".debug_line" and the + ".debug_str" sections. If either of these are present, the binary + is assumed to contain debug information. +See-Also: Bug#668437 diff --git a/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag b/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag new file mode 100644 index 0000000..7a2fddc --- /dev/null +++ b/tags/d/debug-package-for-multi-arch-same-pkg-not-coinstallable.tag @@ -0,0 +1,19 @@ +Tag: debug-package-for-multi-arch-same-pkg-not-coinstallable +Severity: info +Check: group-checks +Explanation: The debug package appear to be containing debug symbols for a + "Multi-Arch: same" package, but the debug package itself is not + "Multi-Arch: same". If so, it is not possible to have the debug + symbols for all architecture variants of the binaries available + at the same time. + . + Making a debug package co-installable with itself is very trivial, + when installing the debug symbols beneath: + <code>/usr/lib/debug/.build-id/<XX>/<rest-id>.debug</code> + . + dh_strip does this in debhelper compat 9. Otherwise, the expected + location of the debug symbols of a given ELF binary can be determined + by using: + . + readelf -n <binary-elf> | \ + perl -ne 'print if s,^\s*Build ID:\s*(\S\S)(\S+),/usr/lib/debug/.build-id/$1/$2.debug,' diff --git a/tags/d/debug-suffix-not-dbg.tag b/tags/d/debug-suffix-not-dbg.tag new file mode 100644 index 0000000..35eefcc --- /dev/null +++ b/tags/d/debug-suffix-not-dbg.tag @@ -0,0 +1,11 @@ +Tag: debug-suffix-not-dbg +Severity: warning +Check: files/debug +Renamed-From: + debug-package-should-be-named-dbg +Explanation: This package provides at least one file in <code>/usr/lib/debug</code>, + which is intended for detached debugging symbols, but the package name + does not end in "-dbg". Detached debugging symbols should be put into a + separate package, Priority: extra, with a package name ending in "-dbg". +See-Also: + developer-reference 6.8.9 diff --git a/tags/d/debug-symbol-migration-possibly-complete.tag b/tags/d/debug-symbol-migration-possibly-complete.tag new file mode 100644 index 0000000..e71c5f9 --- /dev/null +++ b/tags/d/debug-symbol-migration-possibly-complete.tag @@ -0,0 +1,18 @@ +Tag: debug-symbol-migration-possibly-complete +Severity: pedantic +Check: debian/rules +Explanation: The <code>debian/rules</code> file for this package has a call to + <code>dh_strip(1)</code> with the specified <code>--dbgsym-migration</code> or + <code>--ddeb-migration</code> argument. + . + Such arguments are used to migrate packages to use automatic debug + symbols, which first became available in December 2015. + . + If this command was added to the <code>debian/rules</code> that was + included in the current stable release of Debian then it can possibly + be removed. + . + However, if the command was added later (and/or the package was not + included in stretch) please wait until it has been included in a stable + release before removing it. +See-Also: dh_strip(1), https://wiki.debian.org/AutomaticDebugPackages diff --git a/tags/d/debug-symbols-directly-in-usr-lib-debug.tag b/tags/d/debug-symbols-directly-in-usr-lib-debug.tag new file mode 100644 index 0000000..4d57931 --- /dev/null +++ b/tags/d/debug-symbols-directly-in-usr-lib-debug.tag @@ -0,0 +1,11 @@ +Tag: debug-symbols-directly-in-usr-lib-debug +Severity: error +Check: binaries/debug-symbols/detached +Explanation: The given debugging symbols-only object is installed directly in + <code>/usr/lib/debug</code>, although it should be installed in a + subdirectory. For example, debug symbols of a binary in + <code>/usr/bin</code> should be placed in <code>/usr/lib/debug/usr/bin</code>. + gdb, when looking for debugging symbols, prepends <code>/usr/lib/debug</code> + to whatever path it finds in the .gnu_debuglink section, which when using + dh_strip(1) is either the path to your binary/library or a build-id based + path. diff --git a/tags/d/debug-symbols-not-detached.tag b/tags/d/debug-symbols-not-detached.tag new file mode 100644 index 0000000..64b2238 --- /dev/null +++ b/tags/d/debug-symbols-not-detached.tag @@ -0,0 +1,21 @@ +Tag: debug-symbols-not-detached +Severity: warning +Check: binaries/debug-symbols/detached +Renamed-From: + debug-file-should-use-detached-symbols +Explanation: This file is in a location generally used for detached debugging + symbols, but it appears to contain a complete copy of the executable or + library instead of only the debugging symbols. + . + Files in subdirectories of <code>/usr/lib/debug</code> mirroring the main file + system should contain only debugging information generated by <code>objcopy + --only-keep-debug</code>. Binaries or shared objects built with extra + debugging should be installed directly in <code>/usr/lib/debug</code> or in + subdirectories corresponding to the package, not in the directories that + mirror the main file system. + . + If you are using dh_strip with the --dbg-package flag, don't also install + the library in <code>/usr/lib/debug</code>. dh_strip does all the work for + you. +See-Also: + developer-reference 6.8.9 diff --git a/tags/d/declare-python-versions-for-test.tag b/tags/d/declare-python-versions-for-test.tag new file mode 100644 index 0000000..a488a2f --- /dev/null +++ b/tags/d/declare-python-versions-for-test.tag @@ -0,0 +1,25 @@ +Tag: declare-python-versions-for-test +Severity: warning +Check: testsuite +Renamed-from: + declare-requested-python-versions-for-test +Explanation: The specified test attempts to query the Python versions + <em>requested</em> by your sources with the command + <code>py3versions --requested</code> but your sources do not declare + any versions with the field <code>X-Python3-Version</code>. + . + Please choose between two suggested remedies: + . + In most circumstances, it is probably best to replace the argument + <code>--requested</code> with <code>--supported</code>. That will + exercise the test with all available Python versions. + . + Should your installable require only specific Python versions, please add + the field <code>X-Python3-Version</code> with the appropriate information + to the source stanza in the <code>debian/control</code> file. + . + No redirection of the output, as in <code>2 > /dev/null</code>, is + needed in either case. +See-Also: + py3versions(1), + Bug#1001677 diff --git a/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag b/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag new file mode 100644 index 0000000..40e7f0e --- /dev/null +++ b/tags/d/declares-possibly-conflicting-debhelper-compat-versions.tag @@ -0,0 +1,8 @@ +Tag: declares-possibly-conflicting-debhelper-compat-versions +Severity: error +Check: debhelper +See-Also: debhelper(7) +Explanation: The source package declares the debhelper compatibility version + both in the <code>debian/compat</code> file and in the <code>debian/rules</code> + file or in <code>debian/control</code>. If these ever get out of + synchronisation, the package may not build as expected. diff --git a/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag b/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag new file mode 100644 index 0000000..da73bf4 --- /dev/null +++ b/tags/d/default-mta-dependency-does-not-specify-mail-transport-agent.tag @@ -0,0 +1,12 @@ +Tag: default-mta-dependency-does-not-specify-mail-transport-agent +Severity: warning +Check: fields/package-relations +Explanation: This package has a relationship with the default-mta virtual + package but does not specify the mail-transport-agent as an + alternative. + . + default-mta and mail-transport-agent should only ever be in a set of + alternatives together, with default-mta listed first. + . + Please add a "or" dependency on mail-transport-agent after + default-mta. diff --git a/tags/d/default-mta-dependency-not-listed-first.tag b/tags/d/default-mta-dependency-not-listed-first.tag new file mode 100644 index 0000000..cc3e62d --- /dev/null +++ b/tags/d/default-mta-dependency-not-listed-first.tag @@ -0,0 +1,13 @@ +Tag: default-mta-dependency-not-listed-first +Severity: warning +Check: fields/package-relations +Explanation: This package has a relationship with the mail-transport-agent + or default-mta packages but does not specify the default-mta as an + first option. + . + default-mta and mail-transport-agent should only ever be in a set of + alternatives together, with default-mta listed in the primary + position. + . + Please rearrange the dependencies such that default-mta is listed + first. diff --git a/tags/d/dep5-copyright-license-name-not-unique.tag b/tags/d/dep5-copyright-license-name-not-unique.tag new file mode 100644 index 0000000..f9a25e9 --- /dev/null +++ b/tags/d/dep5-copyright-license-name-not-unique.tag @@ -0,0 +1,26 @@ +Tag: dep5-copyright-license-name-not-unique +Severity: warning +Check: debian/copyright/dep5 +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Explanation: This paragraph defines an already defined license. + . + According to the specification, short license names are required to be + unique within a single copyright file. + . + This tag could be raised by something like this: + . + Files: filea ... + Copyright: 2009, ... + License: LGPL-2.1 + This program is free software; + ... + . + Files: fileb ... + Copyright: 2009, ... + License: LGPL-2.1 + This program is free software; + ... + . + In this case, you redefine LGPL-2.1 license. You should use + a stand-alone paragraph or merge the two files (using a single + paragraph). diff --git a/tags/d/dep5-file-paragraph-references-header-paragraph.tag b/tags/d/dep5-file-paragraph-references-header-paragraph.tag new file mode 100644 index 0000000..fd87ac4 --- /dev/null +++ b/tags/d/dep5-file-paragraph-references-header-paragraph.tag @@ -0,0 +1,11 @@ +Tag: dep5-file-paragraph-references-header-paragraph +Severity: warning +Check: debian/copyright/dep5 +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Explanation: The Files paragraph uses a reference to a license which is + only defined in the Header paragraph. The copyright specification + requires that the Files paragraph either contains the full license + itself or references a "stand-alone" License paragraph, and not the + Header paragraph. +Renamed-From: + dep5-file-paragraph-reference-header-paragraph diff --git a/tags/d/dependency-is-not-multi-archified.tag b/tags/d/dependency-is-not-multi-archified.tag new file mode 100644 index 0000000..05f9400 --- /dev/null +++ b/tags/d/dependency-is-not-multi-archified.tag @@ -0,0 +1,6 @@ +Tag: dependency-is-not-multi-archified +Severity: warning +Check: group-checks +Explanation: The package is Multi-Arch "same", but it depends on a package that + is neither Multi-Arch "same" nor "foreign". +See-Also: https://wiki.ubuntu.com/MultiarchSpec diff --git a/tags/d/dependency-on-python-version-marked-for-end-of-life.tag b/tags/d/dependency-on-python-version-marked-for-end-of-life.tag new file mode 100644 index 0000000..32cb06e --- /dev/null +++ b/tags/d/dependency-on-python-version-marked-for-end-of-life.tag @@ -0,0 +1,17 @@ +Tag: dependency-on-python-version-marked-for-end-of-life +Severity: pedantic +Check: languages/python +Experimental: yes +See-Also: https://wiki.debian.org/Python/Python3Port, +https://www.python.org/dev/peps/pep-0373/, Bug#897213 +Explanation: The package specifies a dependency on Python 2.x which is due for + deprecation and will not be maintained upstream past 2020 and will + likely be dropped after the release of Debian "buster". + . + You should not make any changes to your package based on this presence + of this tag. + . + However, please override this tag with a suitably-commented override if + it is known that this package will not be migrated to Python 3.x for one + reason or another. This is so that developers may ignore the package + when looking for software that needs to be ported. diff --git a/tags/d/depends-exclusively-on-makedev.tag b/tags/d/depends-exclusively-on-makedev.tag new file mode 100644 index 0000000..0d755ed --- /dev/null +++ b/tags/d/depends-exclusively-on-makedev.tag @@ -0,0 +1,8 @@ +Tag: depends-exclusively-on-makedev +Severity: warning +Check: fields/package-relations +Explanation: This package depends on makedev without a udev alternative. This + probably means that it doesn't have udev rules and relies on makedev to + create devices, which won't work if udev is installed and running. + Alternatively, it may mean that there are udev rules, but udev was not + added as an alternative to the makedev dependency. diff --git a/tags/d/depends-on-essential-package-without-using-version.tag b/tags/d/depends-on-essential-package-without-using-version.tag new file mode 100644 index 0000000..b1f6dbb --- /dev/null +++ b/tags/d/depends-on-essential-package-without-using-version.tag @@ -0,0 +1,10 @@ +Tag: depends-on-essential-package-without-using-version +Severity: error +Check: fields/package-relations +See-Also: debian-policy 3.5 +Explanation: The package declares a depends on an essential package, e.g. dpkg, + without using a versioned depends. Packages do not need to depend on + essential packages; essential means that they will always be present. + The only reason to list an explicit dependency on an essential package + is if you need a particular version of that package, in which case the + version should be given in the dependency. diff --git a/tags/d/depends-on-libdb1-compat.tag b/tags/d/depends-on-libdb1-compat.tag new file mode 100644 index 0000000..95760ec --- /dev/null +++ b/tags/d/depends-on-libdb1-compat.tag @@ -0,0 +1,7 @@ +Tag: depends-on-libdb1-compat +Severity: error +Check: fields/package-relations +Explanation: The package seems to declare a relation on libdb1-compat. + This library exists for compatibility with applications built against + glibc 2.0 or 2.1. There is intentionally no corresponding development + package. Do not link new applications against this library! diff --git a/tags/d/depends-on-metapackage.tag b/tags/d/depends-on-metapackage.tag new file mode 100644 index 0000000..247c77d --- /dev/null +++ b/tags/d/depends-on-metapackage.tag @@ -0,0 +1,9 @@ +Tag: depends-on-metapackage +Severity: error +Check: fields/package-relations +Explanation: This package is one of the packages that Lintian believes is a + metapackage: a package that exists for the convenience of users or + installers to install a set of related packages. Packages that are not + themselves metapackages must not depend on metapackages, since this may + prevent the user from removing portions of the package set they don't + need. diff --git a/tags/d/depends-on-misc-pre-depends.tag b/tags/d/depends-on-misc-pre-depends.tag new file mode 100644 index 0000000..23e631d --- /dev/null +++ b/tags/d/depends-on-misc-pre-depends.tag @@ -0,0 +1,7 @@ +Tag: depends-on-misc-pre-depends +Severity: warning +Check: substvars/misc/pre-depends +Explanation: The <code>Depends</code> field contains the substitution variable + <code>${misc:Pre-Depends}</code>. + . + The variable should be in listed in the <code>Pre-Depends</code> field instead. diff --git a/tags/d/depends-on-obsolete-package.tag b/tags/d/depends-on-obsolete-package.tag new file mode 100644 index 0000000..9ce542a --- /dev/null +++ b/tags/d/depends-on-obsolete-package.tag @@ -0,0 +1,6 @@ +Tag: depends-on-obsolete-package +Severity: error +Check: fields/package-relations +Explanation: The package depends on a package that has been superseded. + If the superseded package is part of an ORed group, it should not be + the first package in the group. diff --git a/tags/d/depends-on-old-emacs.tag b/tags/d/depends-on-old-emacs.tag new file mode 100644 index 0000000..c26629e --- /dev/null +++ b/tags/d/depends-on-old-emacs.tag @@ -0,0 +1,11 @@ +Tag: depends-on-old-emacs +Severity: warning +Check: fields/package-relations +Explanation: The package lists an old version of Emacs as its first dependency. + It should probably be updated to support the current version of Emacs + in the archive and then list that version first in the list of Emacs + flavors it supports. + . + If the package intentionally only supports older versions of Emacs (if, + for example, it was included with later versions of Emacs), add a Lintian + override. diff --git a/tags/d/depends-on-packaging-dev.tag b/tags/d/depends-on-packaging-dev.tag new file mode 100644 index 0000000..b14e955 --- /dev/null +++ b/tags/d/depends-on-packaging-dev.tag @@ -0,0 +1,5 @@ +Tag: depends-on-packaging-dev +Explanation: You depend/recommend/build-depend on packaging-dev, which is + only a metapackage to install common packages needed for packaging. +Severity: warning +Check: fields/package-relations diff --git a/tags/d/depends-on-python-minimal.tag b/tags/d/depends-on-python-minimal.tag new file mode 100644 index 0000000..4620825 --- /dev/null +++ b/tags/d/depends-on-python-minimal.tag @@ -0,0 +1,8 @@ +Tag: depends-on-python-minimal +Severity: error +Check: fields/package-relations +Explanation: The python-minimal package (and versioned variants thereof) exists + only to possibly become an Essential package. Depending on it is always + an error since it should never be installed without python. If it + becomes Essential, there is no need to depend on it, and until then, + packages that require Python must depend on python. diff --git a/tags/d/depends-on-python2-and-python3.tag b/tags/d/depends-on-python2-and-python3.tag new file mode 100644 index 0000000..dadbac9 --- /dev/null +++ b/tags/d/depends-on-python2-and-python3.tag @@ -0,0 +1,8 @@ +Tag: depends-on-python2-and-python3 +Severity: info +Check: languages/python +Explanation: The specified package has a relation to both the Python 2 and + Python 3 interpreters. It may be that the package has only been + partially migrated to Python 3 from Python 2.x. + . + Please check the contents and/or dependencies of this package. diff --git a/tags/d/depends-on-specific-java-doc-package.tag b/tags/d/depends-on-specific-java-doc-package.tag new file mode 100644 index 0000000..6d2948a --- /dev/null +++ b/tags/d/depends-on-specific-java-doc-package.tag @@ -0,0 +1,6 @@ +Tag: depends-on-specific-java-doc-package +Severity: warning +Check: fields/package-relations +Explanation: The package should use default-jdk-doc instead of classpath-doc + or openjdk-X-doc to ease transitions when the providing doc package + is replaced (e.g. openjdk-6-doc being replaced by openjdk-7-doc). diff --git a/tags/d/deprecated-configure-filename.tag b/tags/d/deprecated-configure-filename.tag new file mode 100644 index 0000000..86c35dd --- /dev/null +++ b/tags/d/deprecated-configure-filename.tag @@ -0,0 +1,8 @@ +Tag: deprecated-configure-filename +Severity: info +Check: build-systems/automake +Explanation: The use of 'configure.in' with automake is deprecated and will + not be supported in future versions of automake. Please consider + (helping upstream) migrating to 'configure.ac' instead. +See-Also: https://lists.gnu.org/archive/html/automake/2013-05/msg00049.html +Experimental: yes diff --git a/tags/d/description-contains-dh-make-perl-template.tag b/tags/d/description-contains-dh-make-perl-template.tag new file mode 100644 index 0000000..ec865fc --- /dev/null +++ b/tags/d/description-contains-dh-make-perl-template.tag @@ -0,0 +1,7 @@ +Tag: description-contains-dh-make-perl-template +Severity: warning +Check: fields/description +Explanation: The extended description contains the statement that it was + automagically extracted by dh-make-perl. Please check the description + for correctness and usefulness and remove the dh-make-perl statement + to signal that you have done so. diff --git a/tags/d/description-contains-homepage.tag b/tags/d/description-contains-homepage.tag new file mode 100644 index 0000000..39e000d --- /dev/null +++ b/tags/d/description-contains-homepage.tag @@ -0,0 +1,9 @@ +Tag: description-contains-homepage +Severity: warning +Check: fields/description +Explanation: The extended description contains a "Homepage" pseudo-field + following the old Developer's Reference recommendation. As of 1.14.6, + dpkg now supports Homepage as a regular field in + <code>debian/control</code>. This pseudo-field should be moved from the + extended description to the fields for the relevant source or binary + packages. diff --git a/tags/d/description-contains-invalid-control-statement.tag b/tags/d/description-contains-invalid-control-statement.tag new file mode 100644 index 0000000..f95afb6 --- /dev/null +++ b/tags/d/description-contains-invalid-control-statement.tag @@ -0,0 +1,14 @@ +Tag: description-contains-invalid-control-statement +Severity: error +Check: fields/description +Explanation: The description contains an invalid control statement. + . + A control statement is a line starting with a dot (.). The only + control statement is defined by the policy is a single dot denoting + an empty line. + . + The "empty-line" control statement does not permit any characters + following it on the same line. Therefore, the line must consist + entirely of a space followed by a dot. +See-Also: + debian-policy 5.6.13 diff --git a/tags/d/description-contains-tabs.tag b/tags/d/description-contains-tabs.tag new file mode 100644 index 0000000..8fa9c7d --- /dev/null +++ b/tags/d/description-contains-tabs.tag @@ -0,0 +1,5 @@ +Tag: description-contains-tabs +Severity: error +Check: fields/description +Explanation: The package "Description:" must not contain tab characters. +See-Also: debian-policy 5.6.13 diff --git a/tags/d/description-is-debmake-template.tag b/tags/d/description-is-debmake-template.tag new file mode 100644 index 0000000..fe8e797 --- /dev/null +++ b/tags/d/description-is-debmake-template.tag @@ -0,0 +1,5 @@ +Tag: description-is-debmake-template +Severity: error +Check: fields/description +Explanation: The synopsis or the extended description just says "Missing", + which is a template provided by debmake. diff --git a/tags/d/description-is-dh_make-template.tag b/tags/d/description-is-dh_make-template.tag new file mode 100644 index 0000000..338dbf5 --- /dev/null +++ b/tags/d/description-is-dh_make-template.tag @@ -0,0 +1,5 @@ +Tag: description-is-dh_make-template +Severity: error +Check: fields/description +Explanation: The synopsis or the extended description has not been changed + from the template provided by dh_make. diff --git a/tags/d/description-is-pkg-name.tag b/tags/d/description-is-pkg-name.tag new file mode 100644 index 0000000..f3aac2a --- /dev/null +++ b/tags/d/description-is-pkg-name.tag @@ -0,0 +1,6 @@ +Tag: description-is-pkg-name +Severity: error +Check: fields/description +See-Also: developer-reference 6.2.2 +Explanation: The description is the same as the package name. + A better description should be provided for the user. diff --git a/tags/d/description-mentions-planned-features.tag b/tags/d/description-mentions-planned-features.tag new file mode 100644 index 0000000..200f368 --- /dev/null +++ b/tags/d/description-mentions-planned-features.tag @@ -0,0 +1,11 @@ +Tag: description-mentions-planned-features +Severity: info +Check: fields/description +Explanation: This package appears to mention planned or upcoming features of + the software. + . + Package descriptions should not mention features that are not yet implemented + as they waste the time of people searching for particular keywords. They are + also liable to become outdated quickly. + . + Please remove such statements from the package description. diff --git a/tags/d/description-possibly-contains-homepage.tag b/tags/d/description-possibly-contains-homepage.tag new file mode 100644 index 0000000..535a3c1 --- /dev/null +++ b/tags/d/description-possibly-contains-homepage.tag @@ -0,0 +1,7 @@ +Tag: description-possibly-contains-homepage +Severity: info +Check: fields/description +Explanation: This package has no Homepage field but has a URL in the description + and wording that might indicate this is the package Homepage. If it is, + add a Homepage control field containing it rather than mentioning it in + the package description. diff --git a/tags/d/description-starts-with-leading-spaces.tag b/tags/d/description-starts-with-leading-spaces.tag new file mode 100644 index 0000000..afd5f46 --- /dev/null +++ b/tags/d/description-starts-with-leading-spaces.tag @@ -0,0 +1,7 @@ +Tag: description-starts-with-leading-spaces +Severity: warning +Check: fields/description +Explanation: The package's extended "Description:" paragraph starts with more than + one leading space. Usually, leading spaces are used to switch "verbatim + display" on (i.e., lines are not wrapped) so this might be a bug in the + package. diff --git a/tags/d/description-starts-with-package-name.tag b/tags/d/description-starts-with-package-name.tag new file mode 100644 index 0000000..8d2fd54 --- /dev/null +++ b/tags/d/description-starts-with-package-name.tag @@ -0,0 +1,7 @@ +Tag: description-starts-with-package-name +Severity: error +Check: fields/description +Explanation: The first line of the "Description:" should not start with the + package name. For example, the package <code>foo</code> should not + have a description like this: "foo is a program that...". +See-Also: debian-policy 3.4.1 diff --git a/tags/d/description-synopsis-is-duplicated.tag b/tags/d/description-synopsis-is-duplicated.tag new file mode 100644 index 0000000..de97cb2 --- /dev/null +++ b/tags/d/description-synopsis-is-duplicated.tag @@ -0,0 +1,7 @@ +Tag: description-synopsis-is-duplicated +Severity: error +Check: fields/description +Explanation: The first line of the extended Description: should not repeat the + synopsis exactly. This indicates that either the synopsis is badly formed + or that the extended description has been wrongly copied and pasted. +See-Also: debian-policy 3.4.2 diff --git a/tags/d/description-synopsis-is-empty.tag b/tags/d/description-synopsis-is-empty.tag new file mode 100644 index 0000000..1f42d5f --- /dev/null +++ b/tags/d/description-synopsis-is-empty.tag @@ -0,0 +1,5 @@ +Tag: description-synopsis-is-empty +Severity: error +Check: fields/description +Explanation: The first line in the "Description:" is empty. +See-Also: debian-policy 3.4 diff --git a/tags/d/description-synopsis-starts-with-article.tag b/tags/d/description-synopsis-starts-with-article.tag new file mode 100644 index 0000000..c660c17 --- /dev/null +++ b/tags/d/description-synopsis-starts-with-article.tag @@ -0,0 +1,10 @@ +Tag: description-synopsis-starts-with-article +Severity: warning +Check: fields/description +Explanation: The first line of the "Description:" should omit any initial indefinite + or definite article: "a", "an", or "the". A good heuristic is that it should + be possible to substitute the package <code>name</code> and <code>synopsis</code> + into this formula: + . + The package <code>name</code> provides {a,an,the,some} <code>synopsis</code>. +See-Also: developer-reference 6.2.2 diff --git a/tags/d/description-too-short.tag b/tags/d/description-too-short.tag new file mode 100644 index 0000000..625df3b --- /dev/null +++ b/tags/d/description-too-short.tag @@ -0,0 +1,6 @@ +Tag: description-too-short +Severity: error +Check: fields/description +See-Also: developer-reference 6.2.2 +Explanation: The description contains only a single word. It is likely that the + description won't be very clear for the user. diff --git a/tags/d/desktop-command-not-in-package.tag b/tags/d/desktop-command-not-in-package.tag new file mode 100644 index 0000000..96110be --- /dev/null +++ b/tags/d/desktop-command-not-in-package.tag @@ -0,0 +1,11 @@ +Tag: desktop-command-not-in-package +Severity: warning +Check: menu-format +Explanation: The desktop entry specifies a <code>Command</code> that does not + match any of the executables shipped in the package. + . + This condition is often caused by a typo, or the desktop file was not updated + after the installed path of the executable was modified. + . + Packages should ship executables that are used as commands in <code>desktop</code> + files. diff --git a/tags/d/desktop-contains-deprecated-key.tag b/tags/d/desktop-contains-deprecated-key.tag new file mode 100644 index 0000000..5d57d1a --- /dev/null +++ b/tags/d/desktop-contains-deprecated-key.tag @@ -0,0 +1,13 @@ +Tag: desktop-contains-deprecated-key +Severity: warning +Check: menu-format +Explanation: The key on this line of the desktop entry was deprecated in the + FreeDesktop specification. + . + If that key is <code>KDE Desktop Entry</code>, the fix for this condition is + usually to change it to <code>Desktop Entry</code>. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff --git a/tags/d/desktop-entry-contains-deprecated-key.tag b/tags/d/desktop-entry-contains-deprecated-key.tag new file mode 100644 index 0000000..5094056 --- /dev/null +++ b/tags/d/desktop-entry-contains-deprecated-key.tag @@ -0,0 +1,10 @@ +Tag: desktop-entry-contains-deprecated-key +Severity: warning +Check: menu-format +Explanation: The key on this line of the Desktop entry was deprecated by the + FreeDesktop specification. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful for checking the syntax of Desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff --git a/tags/d/desktop-entry-contains-encoding-key.tag b/tags/d/desktop-entry-contains-encoding-key.tag new file mode 100644 index 0000000..a4e8183 --- /dev/null +++ b/tags/d/desktop-entry-contains-encoding-key.tag @@ -0,0 +1,12 @@ +Tag: desktop-entry-contains-encoding-key +Severity: info +Check: menu-format +Explanation: The <code>Encoding</code> key is deprecated in the FreeDesktop + standard. Instead, all strings must now be encoded in UTF-8. This desktop entry + specifies an <code>Encoding</code> of <code>UTF-8</code>. It is harmless but can + be dropped. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful for checking the syntax of desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/apc.html diff --git a/tags/d/desktop-entry-contains-unknown-key.tag b/tags/d/desktop-entry-contains-unknown-key.tag new file mode 100644 index 0000000..01d0aa7 --- /dev/null +++ b/tags/d/desktop-entry-contains-unknown-key.tag @@ -0,0 +1,13 @@ +Tag: desktop-entry-contains-unknown-key +Severity: warning +Check: menu-format +Explanation: The key on this line of the <code>desktop</code> entry is not listed + as being defined by the FreeDesktop specification. It is also not one of the legacy + KDE keywords and does not begin with <code>X-</code>. + . + The key may have been misspelled. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of <code>desktop</code> entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff --git a/tags/d/desktop-entry-file-has-crs.tag b/tags/d/desktop-entry-file-has-crs.tag new file mode 100644 index 0000000..e865b76 --- /dev/null +++ b/tags/d/desktop-entry-file-has-crs.tag @@ -0,0 +1,14 @@ +Tag: desktop-entry-file-has-crs +Severity: warning +Check: menu-format +Explanation: The desktop entry file has lines ending in carriage-return and line-feed + instead of just a line-feed. The Desktop Entry Specification says that lines should + end with line-feed alone. + . + Some software may mistake the carriage-return as a part of the field value. + . + You can run the following command to remove any <code>CR</code> character in a file: + . + <code>sed -i 's/\r//g' path/to/file</code> +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s03.html diff --git a/tags/d/desktop-entry-invalid-category.tag b/tags/d/desktop-entry-invalid-category.tag new file mode 100644 index 0000000..869576e --- /dev/null +++ b/tags/d/desktop-entry-invalid-category.tag @@ -0,0 +1,15 @@ +Tag: desktop-entry-invalid-category +Severity: warning +Check: menu-format +Explanation: This <code>desktop</code> entry shows a category that is not + among the registered "main" or "additional" categories in the FreeDesktop + specification. + . + The values are case-sensitive. Whitespace is only allowed just before and + after the equals sign in the <code>Category</code> key, and nowhere else. + . + The <code>desktop-file-validate</code> tool in the + <code>desktop-file-utils</code> package is useful when checking the syntax + of desktop entries. +See-Also: + https://specifications.freedesktop.org/menu-spec/latest/apa.html diff --git a/tags/d/desktop-entry-lacks-icon-entry.tag b/tags/d/desktop-entry-lacks-icon-entry.tag new file mode 100644 index 0000000..80d134c --- /dev/null +++ b/tags/d/desktop-entry-lacks-icon-entry.tag @@ -0,0 +1,17 @@ +Tag: desktop-entry-lacks-icon-entry +Severity: info +Check: menu-format +Explanation: This <code>.desktop</code> file does not contain an <code>Icon</code> + entry. + . + The <code>Icon</code> field should contain the name of the icon file, without the + extension, that is displayed. The different icon themes are searched to locate it. + For absolute paths, the name given will be used. The icon should be sufficiently + unique so that the user can recognize the application. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful for checking the syntax of desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, + https://specifications.freedesktop.org/icon-theme-spec/icon-theme-spec-latest.html, + Bug#854132 diff --git a/tags/d/desktop-entry-lacks-keywords-entry.tag b/tags/d/desktop-entry-lacks-keywords-entry.tag new file mode 100644 index 0000000..52d200e --- /dev/null +++ b/tags/d/desktop-entry-lacks-keywords-entry.tag @@ -0,0 +1,18 @@ +Tag: desktop-entry-lacks-keywords-entry +Severity: info +Check: menu-format +Explanation: This <code>.desktop</code> file is either missing a <code>Keywords</code> + entry, or it does not contain keywords above and beyond those already present in the + <code>Name</code> or <code>GenericName</code> entries. + . + The <code>Keywords</code> field is intended to show keywords relevant for a + <code>.desktop</code> file. + . + Desktop files are organized in key-value pairs and are similar to INI files. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html, + Bug#693918, + https://wiki.gnome.org/Initiatives/GnomeGoals/DesktopFileKeywords diff --git a/tags/d/desktop-entry-lacks-main-category.tag b/tags/d/desktop-entry-lacks-main-category.tag new file mode 100644 index 0000000..8729486 --- /dev/null +++ b/tags/d/desktop-entry-lacks-main-category.tag @@ -0,0 +1,11 @@ +Tag: desktop-entry-lacks-main-category +Severity: warning +Check: menu-format +Explanation: The categories for this <code>desktop</code> entry do not contain any + "main" categories, but only "additional" ones. Additional categories should only + be used on conjunction with one or more main categories. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of <code>desktop</code> entries. +See-Also: + https://specifications.freedesktop.org/menu-spec/latest/apa.html diff --git a/tags/d/desktop-entry-limited-to-environments.tag b/tags/d/desktop-entry-limited-to-environments.tag new file mode 100644 index 0000000..f13a3a6 --- /dev/null +++ b/tags/d/desktop-entry-limited-to-environments.tag @@ -0,0 +1,14 @@ +Tag: desktop-entry-limited-to-environments +Severity: info +Check: menu-format +Explanation: This desktop entry limits the environments in which it is shown + via the <code>OnlyShowIn</code> field but lists multiple environments therein. + . + The condition often indicates that a desktop file was written under the + assumption that only GNOME, KDE, or Xfce are being used, and that the desktop + file is in fact intended to exclude one of them. + . + That the application from desktop environments like LXDE where it may work + fine. If this application supports any desktop environment except specific + ones, it would be better to instead specify the unsupported environments via + the <code>NotShowIn</code> field. diff --git a/tags/d/desktop-entry-missing-required-key.tag b/tags/d/desktop-entry-missing-required-key.tag new file mode 100644 index 0000000..159ae2b --- /dev/null +++ b/tags/d/desktop-entry-missing-required-key.tag @@ -0,0 +1,10 @@ +Tag: desktop-entry-missing-required-key +Severity: error +Check: menu-format +Explanation: Desktop entries must contain the keys <code>Type</code> and + <code>Name</code>. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff --git a/tags/d/desktop-entry-unknown-type.tag b/tags/d/desktop-entry-unknown-type.tag new file mode 100644 index 0000000..de3a534 --- /dev/null +++ b/tags/d/desktop-entry-unknown-type.tag @@ -0,0 +1,16 @@ +Tag: desktop-entry-unknown-type +Severity: warning +Check: menu-format +Explanation: This <code>desktop</code> entry uses a <code>Type</code> that is + not among the currently recognized values of <code>Application</code>, + <code>Link</code> or <code>Directory</code>. + . + Implementations normally ignore unknown values but this condition is probably + not intended. + . + The values are case-sensitive. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of desktop entries. +See-Also: + https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.html diff --git a/tags/d/desktop-entry-uses-reserved-category.tag b/tags/d/desktop-entry-uses-reserved-category.tag new file mode 100644 index 0000000..ec58bc3 --- /dev/null +++ b/tags/d/desktop-entry-uses-reserved-category.tag @@ -0,0 +1,16 @@ +Tag: desktop-entry-uses-reserved-category +Severity: warning +Check: menu-format +Explanation: This <code>desktop</code> entry uses a <code>Reserved Category</code> + as explained below, but does not include an <code>OnlyShowIn</code> key. + . + Reserved categories like <code>Screensaver</code>, <code>TrayIcon</code>, + <code>Applet</code> or <code>Shell</code> have a desktop-specific meaning + but have not been standardized yet. Desktop entry files that use such a + reserved category must also include an <code>OnlyShowIn</code> key to limit + the entry to environments that support the category. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of <code>desktop</code> entries. +See-Also: + https://specifications.freedesktop.org/menu-spec/latest/apas03.html diff --git a/tags/d/desktop-file-in-wrong-dir.tag b/tags/d/desktop-file-in-wrong-dir.tag new file mode 100644 index 0000000..5fed630 --- /dev/null +++ b/tags/d/desktop-file-in-wrong-dir.tag @@ -0,0 +1,9 @@ +Tag: desktop-file-in-wrong-dir +Severity: warning +Check: files/desktop +Explanation: The package contains a <code>.desktop</code> file in an obsolete + folder such as <code>/usr/share/gnome/apps</code>. + . + According to the latest draft of the <code>menu</code> specification available + on freedesktop.org, <code>.desktop</code> files intended to create menus should + be placed in <code>/usr/share/applications</code>. diff --git a/tags/d/desktop-mime-but-no-exec-code.tag b/tags/d/desktop-mime-but-no-exec-code.tag new file mode 100644 index 0000000..7cd48ee --- /dev/null +++ b/tags/d/desktop-mime-but-no-exec-code.tag @@ -0,0 +1,10 @@ +Tag: desktop-mime-but-no-exec-code +Severity: warning +Check: menu-format +Explanation: The named desktop entry indicates support for at least one MIME + type, but does not provide a code like %f, %F, %u or %U in the <code>Exec</code> + key. + . + If the application can in fact handle files of the given MIME types, the + <code>menu</code> item should somehow pass those filenames as parameters to the + executable. diff --git a/tags/d/development-package-ships-elf-binary-in-path.tag b/tags/d/development-package-ships-elf-binary-in-path.tag new file mode 100644 index 0000000..535e2ee --- /dev/null +++ b/tags/d/development-package-ships-elf-binary-in-path.tag @@ -0,0 +1,20 @@ +Tag: development-package-ships-elf-binary-in-path +Severity: info +Check: binaries/location +Experimental: yes +Explanation: This development package (ie. from the <code>libdevel</code> section of + the archive) installs an ELF binary within <code>$PATH</code>. + . + Commonly, executables in development packages provide values that are + relevant for using the library. Source packages that use such + development packages tend to execute those executables to discover how + to use the library. + . + When performing a cross build, host architecture binaries are generally not + executable. However, development packages need to be installed on the host + architecture so such files are useless. + . + An alternative approach is to use <code>pkg-config(1)</code> or potentially + splitting architecture-independent development tools into a separate + package that can be marked <code>Multi-Arch: foreign</code>. +See-Also: Bug#794295, Bug#794103 diff --git a/tags/d/dfsg-version-in-native-package.tag b/tags/d/dfsg-version-in-native-package.tag new file mode 100644 index 0000000..0cf6e6c --- /dev/null +++ b/tags/d/dfsg-version-in-native-package.tag @@ -0,0 +1,13 @@ +Tag: dfsg-version-in-native-package +Severity: warning +Check: fields/version/repack/native +Explanation: The version number contains the string <code>dfsg</code> but + the sources are native. + . + The string <code>dfsg</code> is used in Debian versions to indicate that + the sources were repackaged in order to comply with the Debian Free + Software Guidelines, but all native packages should comply with the + guidelines. +See-Also: + https://wiki.debian.org/DebianFreeSoftwareGuidelines, + https://wiki.debian.org/DFSGLicenses diff --git a/tags/d/dfsg-version-misspelled.tag b/tags/d/dfsg-version-misspelled.tag new file mode 100644 index 0000000..47c41aa --- /dev/null +++ b/tags/d/dfsg-version-misspelled.tag @@ -0,0 +1,6 @@ +Tag: dfsg-version-misspelled +Severity: warning +Check: fields/version/repack/typo +Explanation: The version contains the string <code>dsfg</code>. You probably + meant <code>dfsg</code>. That is the conventional marker for upstream sources + that were repackaged in order to comply with the Debian Free Software Guidelines. diff --git a/tags/d/dfsg-version-with-period.tag b/tags/d/dfsg-version-with-period.tag new file mode 100644 index 0000000..ed5e9ae --- /dev/null +++ b/tags/d/dfsg-version-with-period.tag @@ -0,0 +1,13 @@ +Tag: dfsg-version-with-period +Severity: info +Check: fields/version/repack/period +Explanation: The version contains the string <code>.dfsg</code>. + That versioning may harbor a subtle sorting issue, namely: <code>1.2.dfsg1</code> + is a more recent version than <code>1.2.1</code>. It will therefore be difficult + to find a nice version string for the next upstream release if it gains another + dotted digit at the end. + . + It is better to use <code>+dfsg</code> instead. The plus sign <code>+</code> sorts + before <code>.</code>, so the sorting that is usually desired can take place: + . + <code>1.2</code> < <code>1.2+dfsg</code> < <code>1.2.1</code> diff --git a/tags/d/dfsg-version-with-tilde.tag b/tags/d/dfsg-version-with-tilde.tag new file mode 100644 index 0000000..ada8c12 --- /dev/null +++ b/tags/d/dfsg-version-with-tilde.tag @@ -0,0 +1,16 @@ +Tag: dfsg-version-with-tilde +Severity: info +Check: fields/version/repack/tilde +Explanation: The source version string contains a tilde like <code>~dfsg</code>. + It is probably in a form like <code>1.0~dfsg-1</code>. + . + Most people should use a plus sign instead, as in <code>+dfsg</code>. It will + ensure proper version sorting. + . + We can think of two cases for which a tilde makes sense. First, upstream may release + a tarball again using the same version, but with the offending files removed. The + second case is when all DFSG concerns for a source tarball disappeared. In both cases, + repacking is no longer necessary. We think both cases are rare. +See-Also: + https://lists.debian.org/debian-devel/2021/10/msg00012.html, + https://salsa.debian.org/lintian/lintian/-/merge_requests/379 diff --git a/tags/d/dh-clean-k-is-deprecated.tag b/tags/d/dh-clean-k-is-deprecated.tag new file mode 100644 index 0000000..9cdf47c --- /dev/null +++ b/tags/d/dh-clean-k-is-deprecated.tag @@ -0,0 +1,6 @@ +Tag: dh-clean-k-is-deprecated +Severity: warning +Check: debhelper +See-Also: dh_clean(1) +Explanation: This package calls dh_clean -k in its <code>debian/rules</code> file + instead of dh_prep. diff --git a/tags/d/dh-exec-install-not-allowed-here.tag b/tags/d/dh-exec-install-not-allowed-here.tag new file mode 100644 index 0000000..bf444da --- /dev/null +++ b/tags/d/dh-exec-install-not-allowed-here.tag @@ -0,0 +1,8 @@ +Tag: dh-exec-install-not-allowed-here +Severity: error +Check: debhelper +Explanation: The package uses a dh-exec-install construct in a debhelper + config file, where it is not permitted. + . + The dh-exec-install constructs are only allowed in dh_install's + .install and dh_installman's .manpages files, and nowhere else. diff --git a/tags/d/dh-exec-private-helper.tag b/tags/d/dh-exec-private-helper.tag new file mode 100644 index 0000000..2071e6f --- /dev/null +++ b/tags/d/dh-exec-private-helper.tag @@ -0,0 +1,8 @@ +Tag: dh-exec-private-helper +Severity: error +Check: debhelper +Explanation: The packaging file uses dh-exec, but it does not use /usr/bin/dh-exec. + . + If running dh-exec with the default set of helpers is not desired, + use its --with or --without options instead of directly using the + desired helper. diff --git a/tags/d/dh-exec-script-without-dh-exec-features.tag b/tags/d/dh-exec-script-without-dh-exec-features.tag new file mode 100644 index 0000000..e0f887c --- /dev/null +++ b/tags/d/dh-exec-script-without-dh-exec-features.tag @@ -0,0 +1,8 @@ +Tag: dh-exec-script-without-dh-exec-features +Severity: warning +Check: debhelper +Explanation: The package uses dh-exec in at least one of its files, but does + not use any of the features provided by dh-exec. + . + If the features provided by dh-exec is not needed, please remove the + executable bit, and the dh-exec usage. diff --git a/tags/d/dh-exec-subst-unknown-variable.tag b/tags/d/dh-exec-subst-unknown-variable.tag new file mode 100644 index 0000000..dac9fd7 --- /dev/null +++ b/tags/d/dh-exec-subst-unknown-variable.tag @@ -0,0 +1,10 @@ +Tag: dh-exec-subst-unknown-variable +Severity: info +Check: debhelper +Explanation: The package uses a variable in one of its debhelper config + files, but the variable is not one known to dpkg-architecture. + . + It is recommended to use a known subset of variables. If the package + needs more than that, and makes sure the variable is exported through + the build one way or the other, then this tag can be safely ignored + or overridden. diff --git a/tags/d/dh-exec-useless-usage.tag b/tags/d/dh-exec-useless-usage.tag new file mode 100644 index 0000000..0670845 --- /dev/null +++ b/tags/d/dh-exec-useless-usage.tag @@ -0,0 +1,19 @@ +Tag: dh-exec-useless-usage +Severity: info +Check: debhelper +Explanation: The package uses dh-exec for things it is not needed for. + . + This typically includes using ${DEB_HOST_MULTIARCH} in an install + target where a wildcard would suffice. For example, if you had: + . + #! /usr/bin/dh-exec + usr/lib/${DEB_HOST_MULTIARCH} + . + This could be replaced with the following in most cases, dropping the + need for dh-exec: + . + usr/lib/* + . + However, there may be other directories that match the wildcard, + which one does not wish to install. In that case, this warning should + be ignored or overridden. diff --git a/tags/d/dh-make-template-in-source.tag b/tags/d/dh-make-template-in-source.tag new file mode 100644 index 0000000..27c9878 --- /dev/null +++ b/tags/d/dh-make-template-in-source.tag @@ -0,0 +1,10 @@ +Tag: dh-make-template-in-source +Severity: warning +Check: dh-make/template +Explanation: The named file looks like a <code>dh_make</code> template. + . + Source files like <code>debian/*.ex</code> or <code>debian/ex.*</code> + were usually installed by <code>dh_make</code>. They are meant to be + renamed after they were adapted by the maintainer. + . + Unused templates should be removed. diff --git a/tags/d/dh-quilt-addon-but-quilt-source-format.tag b/tags/d/dh-quilt-addon-but-quilt-source-format.tag new file mode 100644 index 0000000..3e61137 --- /dev/null +++ b/tags/d/dh-quilt-addon-but-quilt-source-format.tag @@ -0,0 +1,8 @@ +Tag: dh-quilt-addon-but-quilt-source-format +Severity: warning +Check: debhelper +Explanation: The package uses (for example) <code>dh $@ --with quilt</code> in + <code>debian/rules</code> but is already using the <code>3.0 (quilt)</code> + source format via the <code>debian/source/format</code> file. + . + Please remove the <code>--with quilt</code> argument. diff --git a/tags/d/dh_installmanpages-is-obsolete.tag b/tags/d/dh_installmanpages-is-obsolete.tag new file mode 100644 index 0000000..4cd0fe5 --- /dev/null +++ b/tags/d/dh_installmanpages-is-obsolete.tag @@ -0,0 +1,6 @@ +Tag: dh_installmanpages-is-obsolete +Severity: warning +Check: debhelper +See-Also: dh_installmanpages(1) +Explanation: This package calls dh_installmanpages in its <code>debian/rules</code> file. + dh_installmanpages is deprecated in favour of dh_installman. diff --git a/tags/d/dir-in-usr-local.tag b/tags/d/dir-in-usr-local.tag new file mode 100644 index 0000000..ee60f88 --- /dev/null +++ b/tags/d/dir-in-usr-local.tag @@ -0,0 +1,13 @@ +Tag: dir-in-usr-local +Severity: error +Check: files/hierarchy/standard +Explanation: The package installs a directory in <code>/usr/local/...</code>. That is + not allowed. + . + If you want to provide an empty directory in <code>/usr/local</code> for + convenience of the local system administrator, please follow the rules + in the policy manual (section 9.1.2), i.e. create the directories in + the <code>postinst</code> maintainer script but do not fail if the operation + is unsuccessful (for example, if <code>/usr/local</code> is mounted read-only). +See-Also: + debian-policy 9.1.2 diff --git a/tags/d/dir-or-file-in-build-tree.tag b/tags/d/dir-or-file-in-build-tree.tag new file mode 100644 index 0000000..84f0bc2 --- /dev/null +++ b/tags/d/dir-or-file-in-build-tree.tag @@ -0,0 +1,8 @@ +Tag: dir-or-file-in-build-tree +Severity: error +Check: files/build-path +Explanation: The package installs a file in common build paths. + . + This often occurs if the package uses regular expressions to + strip the build path without properly regex quoting the build + path. diff --git a/tags/d/dir-or-file-in-etc-opt.tag b/tags/d/dir-or-file-in-etc-opt.tag new file mode 100644 index 0000000..ad278b1 --- /dev/null +++ b/tags/d/dir-or-file-in-etc-opt.tag @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-etc-opt +Severity: error +Check: files/hierarchy/standard +Explanation: Debian packages should not install into <code>/etc/opt</code>, because it + is reserved for add-on software. +See-Also: filesystem-hierarchy optaddonapplicationsoftwarepackages diff --git a/tags/d/dir-or-file-in-home.tag b/tags/d/dir-or-file-in-home.tag new file mode 100644 index 0000000..1f20163 --- /dev/null +++ b/tags/d/dir-or-file-in-home.tag @@ -0,0 +1,5 @@ +Tag: dir-or-file-in-home +Severity: error +Check: files/hierarchy/standard +Explanation: Debian packages should not install into <code>/home</code>, because it + is reserved for users. diff --git a/tags/d/dir-or-file-in-mnt.tag b/tags/d/dir-or-file-in-mnt.tag new file mode 100644 index 0000000..21a0415 --- /dev/null +++ b/tags/d/dir-or-file-in-mnt.tag @@ -0,0 +1,7 @@ +Tag: dir-or-file-in-mnt +Severity: error +Check: files/hierarchy/standard +Explanation: Packages should not install into <code>/mnt</code>. The FHS states that + this directory is reserved for the local system administrator for + temporary mounts and that it must not be used by installation programs. +See-Also: filesystem-hierarchy mntmountpointforatemporarilymount diff --git a/tags/d/dir-or-file-in-opt.tag b/tags/d/dir-or-file-in-opt.tag new file mode 100644 index 0000000..2028621 --- /dev/null +++ b/tags/d/dir-or-file-in-opt.tag @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-opt +Severity: error +Check: files/hierarchy/standard +Explanation: Debian packages should not install into <code>/opt</code>, because it + is reserved for add-on software. +See-Also: filesystem-hierarchy optaddonapplicationsoftwarepackages diff --git a/tags/d/dir-or-file-in-run.tag b/tags/d/dir-or-file-in-run.tag new file mode 100644 index 0000000..f36f189 --- /dev/null +++ b/tags/d/dir-or-file-in-run.tag @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-run +Severity: error +Check: files/hierarchy/standard +Explanation: <code>/run</code> may be a temporary filesystem, so any directories + or files needed there must be created dynamically at boot time. +See-Also: debian-policy 9.3.2 diff --git a/tags/d/dir-or-file-in-srv.tag b/tags/d/dir-or-file-in-srv.tag new file mode 100644 index 0000000..afdd4ff --- /dev/null +++ b/tags/d/dir-or-file-in-srv.tag @@ -0,0 +1,18 @@ +Tag: dir-or-file-in-srv +Severity: error +Check: files/hierarchy/standard +Explanation: Debian packages should install nothing into <code>/srv</code>. + . + The specification for <code>/srv</code> states that its use is at the + discretion of the local administrator. No package should rely on a + particular layout. + . + Debian packages that install files there are unable to adjust to any local + policy. They force a local administrator's hand. + . + If a package wishes to place data below <code>/srv</code>, it must do so in + a way that permits the local administrator to select the folder (for + example, through post-install configuration, setup scripts, + <code>debconf</code> prompts, or similar). +See-Also: + filesystem-hierarchy srvdataforservicesprovidedbysystem diff --git a/tags/d/dir-or-file-in-tmp.tag b/tags/d/dir-or-file-in-tmp.tag new file mode 100644 index 0000000..7bd4fdc --- /dev/null +++ b/tags/d/dir-or-file-in-tmp.tag @@ -0,0 +1,9 @@ +Tag: dir-or-file-in-tmp +Severity: error +Check: files/hierarchy/standard +Explanation: Packages must not install files into <code>/tmp</code> or + <code>/var/tmp</code>. The File Hierarchy Standard specifies that such files + may be removed by the administrator and that programs may not depend on + any files in <code>/tmp</code> being preserved across invocations, which + combined mean that it makes no sense to ship files in these directories. +See-Also: filesystem-hierarchy tmptemporaryfiles, filesystem-hierarchy vartmptemporaryfilespreservedbetwee diff --git a/tags/d/dir-or-file-in-var-lock.tag b/tags/d/dir-or-file-in-var-lock.tag new file mode 100644 index 0000000..2c5b59f --- /dev/null +++ b/tags/d/dir-or-file-in-var-lock.tag @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-var-lock +Severity: error +Check: files/hierarchy/standard +Explanation: <code>/var/lock</code> may be a temporary filesystem, so any directories + or files needed there must be created dynamically at boot time. +See-Also: debian-policy 9.3.2 diff --git a/tags/d/dir-or-file-in-var-run.tag b/tags/d/dir-or-file-in-var-run.tag new file mode 100644 index 0000000..874a432 --- /dev/null +++ b/tags/d/dir-or-file-in-var-run.tag @@ -0,0 +1,6 @@ +Tag: dir-or-file-in-var-run +Severity: error +Check: files/hierarchy/standard +Explanation: <code>/var/run</code> may be a temporary filesystem, so any directories + or files needed there must be created dynamically at boot time. +See-Also: debian-policy 9.3.2 diff --git a/tags/d/dir-or-file-in-var-www.tag b/tags/d/dir-or-file-in-var-www.tag new file mode 100644 index 0000000..8250fcb --- /dev/null +++ b/tags/d/dir-or-file-in-var-www.tag @@ -0,0 +1,20 @@ +Tag: dir-or-file-in-var-www +Severity: error +Check: files/hierarchy/standard +See-Also: filesystem-hierarchy thevarhierarchy +Explanation: Debian packages should not install files under <code>/var/www</code>. + This is not one of the <code>/var</code> directories in the File Hierarchy + Standard and is under the control of the local administrator. Packages + should not assume that it is the document root for a web server; it is + very common for users to change the default document root and packages + should not assume that users will keep any particular setting. + . + Packages that want to make files available via an installed web server + should instead put instructions for the local administrator in a + README.Debian file and ideally include configuration fragments for common + web servers such as Apache. + . + As an exception, packages are permitted to create the <code>/var/www</code> + directory due to its past history as the default document root, but + should at most copy over a default file in postinst for a new install. + In this case, please add a Lintian override. diff --git a/tags/d/direct-changes-in-diff-but-no-patch-system.tag b/tags/d/direct-changes-in-diff-but-no-patch-system.tag new file mode 100644 index 0000000..91ca08d --- /dev/null +++ b/tags/d/direct-changes-in-diff-but-no-patch-system.tag @@ -0,0 +1,13 @@ +Tag: direct-changes-in-diff-but-no-patch-system +Severity: pedantic +Check: debian/patches +Explanation: The Debian diff.gz contains changes to files or creation of additional + files outside the <code>debian</code> directory. Keeping the changes as separate + patches under the control of a patch system allows for more fine grained + control over them. The package will also more easily support possible + future source package formats if all changes outside the <code>debian</code> + directory are stored as patches. + . + If the diff only creates new files that can be copied into place by the + package build rules, consider putting them in the <code>debian</code> + directory rather than using a patch system. diff --git a/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag b/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag new file mode 100644 index 0000000..dfbbb5e --- /dev/null +++ b/tags/d/directory-in-etc-sv-directory-without-executable-run-script.tag @@ -0,0 +1,10 @@ +Tag: directory-in-etc-sv-directory-without-executable-run-script +Severity: error +Check: init-d +Explanation: This package provides the specified directory under + <code>/etc/sv</code> but it does not ship a <code>run</code> script under this + directory. + . + Please check that you are installing your <code>run</code> script to the + right location and that has the correct executable permissions. +See-Also: dh_runit(1) diff --git a/tags/d/distant-prerequisite-in-shlibs.tag b/tags/d/distant-prerequisite-in-shlibs.tag new file mode 100644 index 0000000..e6d908b --- /dev/null +++ b/tags/d/distant-prerequisite-in-shlibs.tag @@ -0,0 +1,18 @@ +Tag: distant-prerequisite-in-shlibs +Severity: warning +Check: debian/shlibs +Renamed-From: + shlibs-declares-dependency-on-other-package +Explanation: This package declares in its shlibs control file either a dependency + on some other package not listed in the Provides of this package or on a + version of this package that the package version doesn't satisfy. + . + Packages should normally only list in their shlibs control file the + shared libraries included in that package, and therefore the dependencies + listed there should normally be satisfied by either the package itself or + one of its Provides. + . + In unusual circumstances where it's necessary to declare more complex + dependencies in the shlibs control file, please add a Lintian override + for this warning. +See-Also: debian-policy 8.6 diff --git a/tags/d/distribution-and-changes-mismatch.tag b/tags/d/distribution-and-changes-mismatch.tag new file mode 100644 index 0000000..47ab397 --- /dev/null +++ b/tags/d/distribution-and-changes-mismatch.tag @@ -0,0 +1,12 @@ +Tag: distribution-and-changes-mismatch +Severity: warning +Check: fields/distribution +Explanation: The <code>Distribution</code> in the <code>.changes</code> file indicates + that packages should be installed into one distribution (suite), but the + distribution in the <code>Changes</code> field copied from + <code>debian/changelog</code> indicates that a different distribution + was intended. + . + This is an easy mistake to make when invoking "sbuild ... foo.dsc". + Double-check the <code>-d</code> option if using sbuild in this way. +See-Also: Bug#542747, Bug#529281 diff --git a/tags/d/distribution-and-experimental-mismatch.tag b/tags/d/distribution-and-experimental-mismatch.tag new file mode 100644 index 0000000..6e84f18 --- /dev/null +++ b/tags/d/distribution-and-experimental-mismatch.tag @@ -0,0 +1,11 @@ +Tag: distribution-and-experimental-mismatch +Severity: error +Check: fields/distribution +Explanation: The <code>Distribution</code> in the <code>.changes</code> file indicates + that packages should be installed into a non-experimental distribution + (suite), but the distribution in the <code>Changes</code> field copied from + <code>debian/changelog</code> indicates that experimental was intended. + . + This is an easy mistake to make when invoking "sbuild ... foo.dsc". + Double-check the <code>-d</code> option if using sbuild in this way. +See-Also: Bug#542747, Bug#529281 diff --git a/tags/d/diversion-for-unknown-file.tag b/tags/d/diversion-for-unknown-file.tag new file mode 100644 index 0000000..edd4e36 --- /dev/null +++ b/tags/d/diversion-for-unknown-file.tag @@ -0,0 +1,5 @@ +Tag: diversion-for-unknown-file +Severity: error +Check: maintainer-scripts/diversion +Explanation: The named maintainer script adds a diversion for a file that + is not being provided by this package. diff --git a/tags/d/django-package-does-not-depend-on-django.tag b/tags/d/django-package-does-not-depend-on-django.tag new file mode 100644 index 0000000..0f782c4 --- /dev/null +++ b/tags/d/django-package-does-not-depend-on-django.tag @@ -0,0 +1,8 @@ +Tag: django-package-does-not-depend-on-django +Severity: warning +Check: languages/python +Explanation: This package appears to be library module for the Django web development + framework but it does not specify a binary dependency on the Django package + itself. + . + Please add a Depends on <code>python-django</code> or <code>python3-django</code>. diff --git a/tags/d/dm-upload-allowed-is-obsolete.tag b/tags/d/dm-upload-allowed-is-obsolete.tag new file mode 100644 index 0000000..398afeb --- /dev/null +++ b/tags/d/dm-upload-allowed-is-obsolete.tag @@ -0,0 +1,8 @@ +Tag: dm-upload-allowed-is-obsolete +Severity: warning +Check: fields/dm-upload-allowed +Explanation: The implementation of the "Debian Maintainers" GR has changed + and the "DM-Upload-Allowed" field is now obsolete. + . + Instead these permissions are granted via "dak-commands" files. +See-Also: https://lists.debian.org/debian-devel-announce/2012/09/msg00008.html diff --git a/tags/d/doc-base-abstract-field-is-template.tag b/tags/d/doc-base-abstract-field-is-template.tag new file mode 100644 index 0000000..f544f3a --- /dev/null +++ b/tags/d/doc-base-abstract-field-is-template.tag @@ -0,0 +1,8 @@ +Tag: doc-base-abstract-field-is-template +Severity: warning +Check: menus +Explanation: The <code>Abstract</code> field of the <code>doc-base</code> + control file contains the phrase "manage online manuals" that likely + originated from an sample control file in the <code>doc-base</code> manual. +See-also: + doc-base-manual 2.3.1 diff --git a/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag b/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag new file mode 100644 index 0000000..57c5a27 --- /dev/null +++ b/tags/d/doc-base-abstract-field-separator-extra-whitespace.tag @@ -0,0 +1,10 @@ +Tag: doc-base-abstract-field-separator-extra-whitespace +Severity: warning +Check: menus +Explanation: The line separating two paragraphs in an <code>Abstract</code> + field in the given <code>doc-base</code> contains additional whitespace. + . + The separator line should consist of a single space followed by a single dot, + and nothing else. +See-Also: + doc-base-manual 2.3.2 diff --git a/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag b/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag new file mode 100644 index 0000000..f62ce21 --- /dev/null +++ b/tags/d/doc-base-abstract-might-contain-extra-leading-whitespace.tag @@ -0,0 +1,8 @@ +Tag: doc-base-abstract-might-contain-extra-leading-whitespace +Severity: warning +Check: menus +Explanation: Continuation lines in the <code>Abstract</code> field of + a <code>doc-base</code> control file should start with a single space, + except when the spaces are meant to be shown by frontends. +See-Also: + doc-base-manual 2.3.2 diff --git a/tags/d/doc-base-document-field-ends-in-whitespace.tag b/tags/d/doc-base-document-field-ends-in-whitespace.tag new file mode 100644 index 0000000..5526004 --- /dev/null +++ b/tags/d/doc-base-document-field-ends-in-whitespace.tag @@ -0,0 +1,9 @@ +Tag: doc-base-document-field-ends-in-whitespace +Severity: error +Check: menus +Explanation: The <code>Document</code> field in a <code>doc-base</code> + file should not end in whitespace. Versions of <code>doc-base</code> as + recent as 0.8.5 cannot deal gracefully with such fields. + . + Also, Ddebhelper versions 5.0.57 or earlier may create files that end in + whitespace when such files are installed. diff --git a/tags/d/doc-base-document-field-not-in-first-line.tag b/tags/d/doc-base-document-field-not-in-first-line.tag new file mode 100644 index 0000000..66f896a --- /dev/null +++ b/tags/d/doc-base-document-field-not-in-first-line.tag @@ -0,0 +1,10 @@ +Tag: doc-base-document-field-not-in-first-line +Severity: error +Check: menus +Explanation: The <code>Document</code> field must be located in the first line + of the given <code>doc-base</code> control file. + . + For performance reasons, versions 0.8 and later of <code>doc-base</code> + parse only the first line of the file when unregistering documents. +See-Also: + doc-base-manual 2.3.2.1 diff --git a/tags/d/doc-base-file-lacks-required-field.tag b/tags/d/doc-base-file-lacks-required-field.tag new file mode 100644 index 0000000..4e23a99 --- /dev/null +++ b/tags/d/doc-base-file-lacks-required-field.tag @@ -0,0 +1,8 @@ +Tag: doc-base-file-lacks-required-field +Severity: error +Check: menus +Explanation: The named field is required in that particular section but + missing from the given <code>doc-base</code> control file. +See-Also: + doc-base-manual 2.3.2.1, + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-no-format-section.tag b/tags/d/doc-base-file-no-format-section.tag new file mode 100644 index 0000000..9a0ea12 --- /dev/null +++ b/tags/d/doc-base-file-no-format-section.tag @@ -0,0 +1,7 @@ +Tag: doc-base-file-no-format-section +Severity: error +Check: menus +Explanation: The given <code>doc-base</code> control file does specify + a <code>Format</code> section. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-no-format.tag b/tags/d/doc-base-file-no-format.tag new file mode 100644 index 0000000..db0066c --- /dev/null +++ b/tags/d/doc-base-file-no-format.tag @@ -0,0 +1,9 @@ +Tag: doc-base-file-no-format +Severity: error +Check: menus +Explanation: A <code>Format</code> sections in the given <code>doc-base</code> + control file does not actually specify a format. + . + Each section, except the first, must specify a format. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-no-index.tag b/tags/d/doc-base-file-no-index.tag new file mode 100644 index 0000000..3852ab6 --- /dev/null +++ b/tags/d/doc-base-file-no-index.tag @@ -0,0 +1,11 @@ +Tag: doc-base-file-no-index +Severity: error +Check: menus +Explanation: The <code>Format</code> sections in the given <code>doc-base</code> + control files for <code>HTML</code> or <code>Info</code> documents must also + contain an <code>Index</code> field that shows an appropriate starting point + for the document series. + . + The field must be present even if the documentation is a single file. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-references-missing-file.tag b/tags/d/doc-base-file-references-missing-file.tag new file mode 100644 index 0000000..52b8924 --- /dev/null +++ b/tags/d/doc-base-file-references-missing-file.tag @@ -0,0 +1,9 @@ +Tag: doc-base-file-references-missing-file +Severity: error +Check: menus +Explanation: One of the files mentioned in an <code>Index</code> or + <code>Files</code> field in this <code>doc-base</code> control file + does not exist in the package. + . + This issue can occur when installable packages attempt to register + documentation that is actually shipped in a related package. diff --git a/tags/d/doc-base-file-references-wrong-path.tag b/tags/d/doc-base-file-references-wrong-path.tag new file mode 100644 index 0000000..8c1002c --- /dev/null +++ b/tags/d/doc-base-file-references-wrong-path.tag @@ -0,0 +1,8 @@ +Tag: doc-base-file-references-wrong-path +Severity: error +Check: menus +Explanation: The given <code>doc-base</code> control file references a + file in an <code>Index</code> or <code>Files</code> field that does not + start with <code>/usr/share/doc</code> or <code>/usr/share/info</code>. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-separator-extra-whitespace.tag b/tags/d/doc-base-file-separator-extra-whitespace.tag new file mode 100644 index 0000000..35a7e7e --- /dev/null +++ b/tags/d/doc-base-file-separator-extra-whitespace.tag @@ -0,0 +1,11 @@ +Tag: doc-base-file-separator-extra-whitespace +Severity: warning +Check: menus +Explanation: The separating line between two <code>File</code> sections + in the given <code>doc-base</code> control file contains additional + whitespace. + . + The section separator should be just an empty line without any other + whitespace. +See-Also: + doc-base-manual 2.3.2 diff --git a/tags/d/doc-base-file-syntax-error.tag b/tags/d/doc-base-file-syntax-error.tag new file mode 100644 index 0000000..783a44c --- /dev/null +++ b/tags/d/doc-base-file-syntax-error.tag @@ -0,0 +1,7 @@ +Tag: doc-base-file-syntax-error +Severity: error +Check: menus +Explanation: Lintian found a syntax error in the give <code>doc-base</code> + control file. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-unknown-field.tag b/tags/d/doc-base-file-unknown-field.tag new file mode 100644 index 0000000..78e19ef --- /dev/null +++ b/tags/d/doc-base-file-unknown-field.tag @@ -0,0 +1,12 @@ +Tag: doc-base-file-unknown-field +Severity: error +Check: menus +Explanation: The <code>doc-base</code> control file contains a field that + is either unknown or invalid in the section in which it appears. + . + Possible reasons are a typo in field name, a missing empty line between + sections in the <doc-base> control file, or an extra empty line between + sections. +See-Also: + doc-base-manual 2.3.2.1, + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-file-unknown-format.tag b/tags/d/doc-base-file-unknown-format.tag new file mode 100644 index 0000000..c2d5da9 --- /dev/null +++ b/tags/d/doc-base-file-unknown-format.tag @@ -0,0 +1,13 @@ +Tag: doc-base-file-unknown-format +Severity: warning +Check: menus +Explanation: The <code>Format</code> field in this <code>doc-base</code> + control file declares an unsupported format. + . + Recognized formats are <code>HTML</code>, <code>Text</code>, <code>PDF</code>, + <code>PostScript</code>, <code>Info</code>, <code>DVI</code>, + and <code>DebianDoc-SGML</code>. + . + All of those are case-insensitive. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-index-references-multiple-files.tag b/tags/d/doc-base-index-references-multiple-files.tag new file mode 100644 index 0000000..d202966 --- /dev/null +++ b/tags/d/doc-base-index-references-multiple-files.tag @@ -0,0 +1,10 @@ +Tag: doc-base-index-references-multiple-files +Severity: error +Check: menus +Explanation: The <code>Index</code> field in a <code>doc-base</code> file + should reference the single index file for that document. + . + Any other files belonging to the same document should be listed in the + <code>Files</code> field. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/doc-base-invalid-document-field.tag b/tags/d/doc-base-invalid-document-field.tag new file mode 100644 index 0000000..d6c0cb1 --- /dev/null +++ b/tags/d/doc-base-invalid-document-field.tag @@ -0,0 +1,10 @@ +Tag: doc-base-invalid-document-field +Severity: error +Check: menus +Explanation: The <code>Document</code> field should consist only of lowercase letters + (<code>a-z</code>), digits (<code>0-9</code>), the plus sign (<code>+</code>), + the minus sign (<code>-</code>) sign, or dots (<code>.</code>). + . + Uppercase letters are not allowed. +See-Also: + doc-base-manual 2.2 diff --git a/tags/d/doc-base-unknown-section.tag b/tags/d/doc-base-unknown-section.tag new file mode 100644 index 0000000..a08800b --- /dev/null +++ b/tags/d/doc-base-unknown-section.tag @@ -0,0 +1,11 @@ +Tag: doc-base-unknown-section +Severity: warning +Check: menus +Explanation: The section name indicated in the given <code>doc-base</code> + control file is outside the <code>doc-base</code> standard. + . + The <code>doc-base</code> section names are loosely based on <code>menu</code> + sections, but are not the same. +See-Also: + doc-base-manual 2.3.3, + file:///usr/share/doc/doc-base/doc-base.html/index.html diff --git a/tags/d/doc-base-uses-applications-section.tag b/tags/d/doc-base-uses-applications-section.tag new file mode 100644 index 0000000..a0f9f47 --- /dev/null +++ b/tags/d/doc-base-uses-applications-section.tag @@ -0,0 +1,12 @@ +Tag: doc-base-uses-applications-section +Severity: warning +Check: menus +Explanation: The section indicated in the given <code>doc-base</code> + control file uses a top-level section named <code>Apps</code> or + <code>Applications</code>. Those names are only used in <code>menu</code>, + but not in <code>doc-base</code>. + . + You may just be able to drop the <code>Applications/</code> part in the + section. +See-Also: + doc-base-manual 2.3.3 diff --git a/tags/d/doc-package-depends-on-main-package.tag b/tags/d/doc-package-depends-on-main-package.tag new file mode 100644 index 0000000..4f63af0 --- /dev/null +++ b/tags/d/doc-package-depends-on-main-package.tag @@ -0,0 +1,9 @@ +Tag: doc-package-depends-on-main-package +Severity: warning +Check: fields/package-relations +Explanation: The name of this package suggests that it is a documentation package. + It is usually not desirable for documentation packages to depend on the + packages they document, because users may want to install the docs before + they decide whether they want to install the package. Also, documentation + packages are often architecture-independent, so on other architectures + the package on which it depends may not even exist. diff --git a/tags/d/documentation-package-not-architecture-independent.tag b/tags/d/documentation-package-not-architecture-independent.tag new file mode 100644 index 0000000..2dd7c63 --- /dev/null +++ b/tags/d/documentation-package-not-architecture-independent.tag @@ -0,0 +1,5 @@ +Tag: documentation-package-not-architecture-independent +Severity: warning +Check: fields/architecture +Explanation: Documentation packages usually shouldn't carry anything that requires + recompiling on various architectures, in order to save space on mirrors. diff --git a/tags/d/dot-before-repack-count.tag b/tags/d/dot-before-repack-count.tag new file mode 100644 index 0000000..db39328 --- /dev/null +++ b/tags/d/dot-before-repack-count.tag @@ -0,0 +1,15 @@ +Tag: dot-before-repack-count +Severity: info +Check: fields/version/repack/count +Explanation: The source version contains a repack count that is prefaced by a dot, + like <code>+dfsg.N</code>. + . + For proper version sorting, please use <code>+dfsgN</code> instead. + . + Please note, however, that a version containing the dot <code>+dfsg.N-1</code> (here + with a Debian revision) should not change to <code>+dfsgN-1</code> (without the dot) + for the same upstream release. That is because <code>1.0+dfsgN-1</code> always appears + less recent than the original <code>1.0+dfsg.1-1</code>. Please consider the new + format when upstream cuts the next release. +See-Also: + https://lists.debian.org/debian-devel/2021/10/msg00026.html diff --git a/tags/d/doubly-armored-upstream-signature.tag b/tags/d/doubly-armored-upstream-signature.tag new file mode 100644 index 0000000..14705f3 --- /dev/null +++ b/tags/d/doubly-armored-upstream-signature.tag @@ -0,0 +1,8 @@ +Tag: doubly-armored-upstream-signature +Severity: error +Check: upstream-signature +Explanation: The packaging includes a detached upstream signature file that was armored + twice (or more) using <code>gpg --enarmor</code>. That is an error. + . + Please armor the signature just once. You can also use standard tools such as + <code>gpg --armor --detach-sig</code>. diff --git a/tags/d/dpatch-build-dep-but-no-patch-list.tag b/tags/d/dpatch-build-dep-but-no-patch-list.tag new file mode 100644 index 0000000..d2159c8 --- /dev/null +++ b/tags/d/dpatch-build-dep-but-no-patch-list.tag @@ -0,0 +1,11 @@ +Tag: dpatch-build-dep-but-no-patch-list +Severity: warning +Check: debian/patches/dpatch +Explanation: Using dpatch requires you to explicitly list all patches you want + to apply in debian/patches/00list. This package build-depends on dpatch, + but does not provide a patch list. You should either remove the dpatch + build dependency or add a patch list. + . + Note that an empty file cannot be represented in the Debian diff, so an + empty patch list will disappear in the source package. If you intended + for the series file to be empty, add a comment line. diff --git a/tags/d/dpatch-index-references-non-existent-patch.tag b/tags/d/dpatch-index-references-non-existent-patch.tag new file mode 100644 index 0000000..685c0e3 --- /dev/null +++ b/tags/d/dpatch-index-references-non-existent-patch.tag @@ -0,0 +1,5 @@ +Tag: dpatch-index-references-non-existent-patch +Severity: error +Check: debian/patches/dpatch +Explanation: In the 00list file listing all your dpatches, you referenced a file + that does not exist. This will lead to a fatal error when calling dpatch. diff --git a/tags/d/dpatch-missing-description.tag b/tags/d/dpatch-missing-description.tag new file mode 100644 index 0000000..2930c74 --- /dev/null +++ b/tags/d/dpatch-missing-description.tag @@ -0,0 +1,14 @@ +Tag: dpatch-missing-description +Severity: info +Check: debian/patches/dpatch +Explanation: dpatch files should carry a description of the included patch. + Description lines start with "## DP:". + . + As well as a description of the purpose and function of the patch, the + description should ideally contain author information, a URL for the bug + report (if any), Debian or upstream bugs fixed by it, upstream status, + the Debian version and date the patch was first included, and any other + information that would be useful if someone were investigating the + patch and underlying problem. Please consider using the DEP 3 format for + this information. +See-Also: https://dep-team.pages.debian.net/deps/dep3/ diff --git a/tags/d/drop-python-version-declaration.tag b/tags/d/drop-python-version-declaration.tag new file mode 100644 index 0000000..67c0317 --- /dev/null +++ b/tags/d/drop-python-version-declaration.tag @@ -0,0 +1,16 @@ +Tag: drop-python-version-declaration +Severity: warning +Check: testsuite +Renamed-From: + query-requested-python-versions-in-test + query-declared-python-versions-in-test +Explanation: + Your sources request a specific set of Python versions via the control field + <code>X-Python3-Version</code> but all declared autopkgtests exercise all supported + Python versions by using the command <code>py3versions --supported</code>. + . + The <code>X-Python3-Version</code> control field is not needed when sources work + with all Python versions currently supported. +See-Also: + py3versions(1), + Bug#1001677 diff --git a/tags/d/duplicate-changelog-files.tag b/tags/d/duplicate-changelog-files.tag new file mode 100644 index 0000000..13f675c --- /dev/null +++ b/tags/d/duplicate-changelog-files.tag @@ -0,0 +1,9 @@ +Tag: duplicate-changelog-files +Severity: warning +Check: files/duplicates +Explanation: The package appears to be shipping two copies of the changelog. + . + If the second copy is really needed, consider making it a symlink to + the canonical place for the relevant changelog. + . + Both upstream and Debian changelogs are checked with this tag. diff --git a/tags/d/duplicate-conffile.tag b/tags/d/duplicate-conffile.tag new file mode 100644 index 0000000..79baba9 --- /dev/null +++ b/tags/d/duplicate-conffile.tag @@ -0,0 +1,7 @@ +Tag: duplicate-conffile +Severity: error +Check: conffiles +Explanation: The file is listed more than once in your <code>debian/conffiles</code> file. + Usually, this is because debhelper (dh_installdeb, compat level 3 or higher) + will add any files in your package located in /etc automatically to the list + of conffiles, so if you do that manually too, you'll get duplicates. diff --git a/tags/d/duplicate-contact.tag b/tags/d/duplicate-contact.tag new file mode 100644 index 0000000..8e0cfb2 --- /dev/null +++ b/tags/d/duplicate-contact.tag @@ -0,0 +1,5 @@ +Tag: duplicate-contact +Severity: warning +Check: fields/mail-address +Explanation: The contact appears more than once in the named field. + The duplicate information should be removed. diff --git a/tags/d/duplicate-entry-in-symbols-control-file.tag b/tags/d/duplicate-entry-in-symbols-control-file.tag new file mode 100644 index 0000000..f00b056 --- /dev/null +++ b/tags/d/duplicate-entry-in-symbols-control-file.tag @@ -0,0 +1,4 @@ +Tag: duplicate-entry-in-symbols-control-file +Severity: error +Check: debian/shlibs +Explanation: The symbols control file contains a duplicate entry. diff --git a/tags/d/duplicate-field-in-doc-base.tag b/tags/d/duplicate-field-in-doc-base.tag new file mode 100644 index 0000000..e9b9ba0 --- /dev/null +++ b/tags/d/duplicate-field-in-doc-base.tag @@ -0,0 +1,5 @@ +Tag: duplicate-field-in-doc-base +Severity: error +Check: menus +Renamed-From: doc-base-file-duplicated-field +Explanation: The <code>doc-base</code> control file contains the given field twice. diff --git a/tags/d/duplicate-files.tag b/tags/d/duplicate-files.tag new file mode 100644 index 0000000..a39eeea --- /dev/null +++ b/tags/d/duplicate-files.tag @@ -0,0 +1,16 @@ +Tag: duplicate-files +Severity: pedantic +Check: files/duplicates +Experimental: yes +See-Also: jdupes(1) +Explanation: The package ships the two (or more) files with the exact same + contents. + . + Duplicates can often be replaced with symlinks by running: + . + jdupes -rl debian/${binary}/usr + . + ... after they are installed, eg. in <code>override_dh_link</code>. In + addition, please consider reporting this upstream. + . + Note: empty files are exempt from this check. diff --git a/tags/d/duplicate-font-file.tag b/tags/d/duplicate-font-file.tag new file mode 100644 index 0000000..641acd7 --- /dev/null +++ b/tags/d/duplicate-font-file.tag @@ -0,0 +1,16 @@ +Tag: duplicate-font-file +Severity: warning +Check: fonts +Explanation: This package appears to include a font file that is already provided + by another package in Debian. Ideally it should instead depend on the + relevant font package. If the application in this package loads the font + file by name, you may need to include a symlink pointing to the file name + of the font in its Debian package. + . + Sometimes the font package containing the font is huge and you only need + one font. In that case, you have a few options: modify the package (in + conjunction with upstream) to use libfontconfig to find the font that you + prefer but fall back on whatever installed font is available, ask that + the font package be split apart into packages of a more reasonable size, + or add an override and be aware of the duplication when new versions of + the font are released. diff --git a/tags/d/duplicate-format-in-doc-base.tag b/tags/d/duplicate-format-in-doc-base.tag new file mode 100644 index 0000000..d57df93 --- /dev/null +++ b/tags/d/duplicate-format-in-doc-base.tag @@ -0,0 +1,11 @@ +Tag: duplicate-format-in-doc-base +Severity: error +Check: menus +Renamed-From: + doc-base-file-duplicated-format +Explanation: The <code>doc-base</code> control file contains the same file in + two different formats. + . + The files listed in <code>doc-base</code> must have distinct contents. +See-Also: + doc-base-manual 2.3.2.2 diff --git a/tags/d/duplicate-globbing-patterns.tag b/tags/d/duplicate-globbing-patterns.tag new file mode 100644 index 0000000..96976d5 --- /dev/null +++ b/tags/d/duplicate-globbing-patterns.tag @@ -0,0 +1,10 @@ +Tag: duplicate-globbing-patterns +Severity: error +Check: debian/copyright/dep5 +Explanation: A globbing pattern was used again in <code>debian/copyright</code>. + It always an error and may indicate confusion about the applicable + license for the author or any reader of the file. + . + Please remove all but one of the identical globbing patterns. +See-Also: Bug#90574, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff --git a/tags/d/duplicate-in-shlibs.tag b/tags/d/duplicate-in-shlibs.tag new file mode 100644 index 0000000..6e1ae9e --- /dev/null +++ b/tags/d/duplicate-in-shlibs.tag @@ -0,0 +1,6 @@ +Tag: duplicate-in-shlibs +Severity: error +Check: debian/shlibs +Renamed-From: + duplicate-entry-in-shlibs-control-file +Explanation: The shlibs control file contains a duplicate entry. diff --git a/tags/d/duplicate-key-in-desktop.tag b/tags/d/duplicate-key-in-desktop.tag new file mode 100644 index 0000000..164ed2c --- /dev/null +++ b/tags/d/duplicate-key-in-desktop.tag @@ -0,0 +1,9 @@ +Tag: duplicate-key-in-desktop +Severity: warning +Check: menu-format +Renamed-From: duplicated-key-in-desktop-entry +Explanation: The <code>desktop</code> entry contains the same key twice. The + standard does not define the behavior of such entries. + . + The <code>desktop-file-validate</code> tool in the <code>desktop-file-utils</code> + package may be useful when checking the syntax of <code>desktop</code> entries. diff --git a/tags/d/duplicate-long-description-in-template.tag b/tags/d/duplicate-long-description-in-template.tag new file mode 100644 index 0000000..066d9c6 --- /dev/null +++ b/tags/d/duplicate-long-description-in-template.tag @@ -0,0 +1,6 @@ +Tag: duplicate-long-description-in-template +Severity: warning +Check: debian/debconf +Explanation: The long description of one of the templates provided by this package + is a duplicate of the short description. If you cannot provide a good + extended description, it is better to leave it blank. diff --git a/tags/d/duplicate-long-description.tag b/tags/d/duplicate-long-description.tag new file mode 100644 index 0000000..dea1baf --- /dev/null +++ b/tags/d/duplicate-long-description.tag @@ -0,0 +1,10 @@ +Tag: duplicate-long-description +Severity: info +Check: debian/control/field/description/duplicate +Explanation: The listed binary packages all share the same extended description. + . + Please add some additional, useful information to the extended descriptions + that explain what is in each package and how it differs from the next. + . + It is not okay to rely only on package naming conventions to indicate what + is inside. diff --git a/tags/d/duplicate-override-context.tag b/tags/d/duplicate-override-context.tag new file mode 100644 index 0000000..77074c1 --- /dev/null +++ b/tags/d/duplicate-override-context.tag @@ -0,0 +1,12 @@ +Tag: duplicate-override-context +Severity: warning +Show-Always: yes +Check: debian/lintian-overrides/duplicate +Explanation: The named lines in the given <code>override</code> file + refer to the same tag with the same context. It is redundant, and + may indicate outdated overrides. + . + This condition is also flagged for renamed tags, for which it occurs + perhaps more often when the overrides are adjusted for new tag names. + . + Please remove one of the overrides or adjust in some way. diff --git a/tags/d/duplicate-p3dist-override.tag b/tags/d/duplicate-p3dist-override.tag new file mode 100644 index 0000000..a97f3d6 --- /dev/null +++ b/tags/d/duplicate-p3dist-override.tag @@ -0,0 +1,28 @@ +Tag: duplicate-p3dist-override +Severity: error +Check: languages/python/dist-overrides +Explanation: + <code>dh_python3</code> has an override mechanism + (<code>debian/py3dist-overrides</code>) that lets you specify different + prerequisites for particular Python + imports. + . + <code>debian/py3dist-overrides</code> is mainly used for Python programs + that use GObject introspection, since <code>dh_python3</code> cannot yet + detect that the packages <code>gir1.2-*-*</code> map to Python imports, + so overrides are needed. + . + When the same import appears twice in the file, the information from the + first one is used but all the others are discarded. That can lead to + missing prerequisites. + . + An example of a second line that gets ignored: + . + gi.repository.Gst gir1.2-gst-plugins-base-1.0 + gi.repository.Gst gir1.2-gstreamer-1.0 + . + An example of a double dependency that gets kept: + . + gi.repository.Gst gir1.2-gst-plugins-base-1.0, gir1.2-gstreamer-1.0 +See-Also: + Bug#980987 diff --git a/tags/d/duplicate-packaging-file.tag b/tags/d/duplicate-packaging-file.tag new file mode 100644 index 0000000..dab412c --- /dev/null +++ b/tags/d/duplicate-packaging-file.tag @@ -0,0 +1,14 @@ +Tag: duplicate-packaging-file +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 both a file with the proper name and also + a file with incorrect name. Please remove the file as indicated. + . + Please merge all relevant information into the surviving file. +See-Also: Bug#429510, Bug#946126 diff --git a/tags/d/duplicate-short-description.tag b/tags/d/duplicate-short-description.tag new file mode 100644 index 0000000..9694230 --- /dev/null +++ b/tags/d/duplicate-short-description.tag @@ -0,0 +1,11 @@ +Tag: duplicate-short-description +Severity: info +Check: debian/control/field/description/duplicate +Explanation: The listed binary packages all share the same short description, + i.e. the first line of the Description field in <code>debian/control</code>. + . + Please add a word or two, in parentheses if needed, to describe to users what + they are installing. + . + It is not okay to rely solely on package naming conventions to indicate what + is inside. diff --git a/tags/d/duplicate-tag-in-menu.tag b/tags/d/duplicate-tag-in-menu.tag new file mode 100644 index 0000000..3dc8462 --- /dev/null +++ b/tags/d/duplicate-tag-in-menu.tag @@ -0,0 +1,9 @@ +Tag: duplicate-tag-in-menu +Severity: warning +Check: menu-format +Renamed-From: + duplicated-tag-in-menu-item +Explanation: The <code>menu</code> item contains the same tag twice. At best, it is + a waste of space. The <code>menu</code> system will only use one of them. +See-Also: + menu-manual 3.2 diff --git a/tags/d/duplicate-updaterc.d-calls-in-postinst.tag b/tags/d/duplicate-updaterc.d-calls-in-postinst.tag new file mode 100644 index 0000000..ab763b7 --- /dev/null +++ b/tags/d/duplicate-updaterc.d-calls-in-postinst.tag @@ -0,0 +1,5 @@ +Tag: duplicate-updaterc.d-calls-in-postinst +Severity: error +Check: init-d +Explanation: The <code>postinst</code> script calls <code>update-rc.d</code> several + times for the same <code>/etc/init.d</code> script. diff --git a/tags/d/duplicate-updaterc.d-calls-in-postrm.tag b/tags/d/duplicate-updaterc.d-calls-in-postrm.tag new file mode 100644 index 0000000..88910a4 --- /dev/null +++ b/tags/d/duplicate-updaterc.d-calls-in-postrm.tag @@ -0,0 +1,5 @@ +Tag: duplicate-updaterc.d-calls-in-postrm +Severity: error +Check: init-d +Explanation: The <code>postrm</code> script calls <code>update-rc.d</code> several + times for the same <code>/etc/init.d</code> script. |