diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-14 13:42:30 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-14 13:42:30 +0000 |
commit | 75808db17caf8b960b351e3408e74142f4c85aac (patch) | |
tree | 7989e9c09a4240248bf4658a22208a0a52d991c4 /tags/m | |
parent | Initial commit. (diff) | |
download | lintian-75808db17caf8b960b351e3408e74142f4c85aac.tar.xz lintian-75808db17caf8b960b351e3408e74142f4c85aac.zip |
Adding upstream version 2.117.0.upstream/2.117.0upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
151 files changed, 1537 insertions, 0 deletions
diff --git a/tags/m/macos-ds-store-file-in-package.tag b/tags/m/macos-ds-store-file-in-package.tag new file mode 100644 index 0000000..07d0ff3 --- /dev/null +++ b/tags/m/macos-ds-store-file-in-package.tag @@ -0,0 +1,8 @@ +Tag: macos-ds-store-file-in-package +Severity: warning +Check: foreign-operating-systems +Explanation: There is a file in the package named <code>.DS_Store</code> or + <code>.DS_Store.gz</code>, the file name used by Mac OS X to store folder + attributes. Such files are generally useless in Debian packages and were + usually accidentally included by copying complete directories from the + source tarball. diff --git a/tags/m/macos-resource-fork-file-in-package.tag b/tags/m/macos-resource-fork-file-in-package.tag new file mode 100644 index 0000000..aa4a696 --- /dev/null +++ b/tags/m/macos-resource-fork-file-in-package.tag @@ -0,0 +1,8 @@ +Tag: macos-resource-fork-file-in-package +Severity: warning +Check: foreign-operating-systems +Explanation: There is a file in the package with a name starting with + <code>._</code>, the file name pattern used by Mac OS X to store resource + forks in non-native file systems. Such files are generally useless in + Debian packages and were usually accidentally included by copying + complete directories from the source tarball. diff --git a/tags/m/magic-arch-in-arch-list.tag b/tags/m/magic-arch-in-arch-list.tag new file mode 100644 index 0000000..3ba0441 --- /dev/null +++ b/tags/m/magic-arch-in-arch-list.tag @@ -0,0 +1,8 @@ +Tag: magic-arch-in-arch-list +Severity: error +Check: fields/architecture +Explanation: The special architecture value "any" only makes sense if it occurs + alone or (in a *.dsc file) together with "all". The value "all" may + appear together with other architectures in a *.dsc file but must + occur alone if used in a binary package. +See-Also: debian-policy 5.6.8, Bug#626775 diff --git a/tags/m/mail-address-loops-or-bounces.tag b/tags/m/mail-address-loops-or-bounces.tag new file mode 100644 index 0000000..fc07912 --- /dev/null +++ b/tags/m/mail-address-loops-or-bounces.tag @@ -0,0 +1,17 @@ +Tag: mail-address-loops-or-bounces +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-address-causes-mail-loops-or-bounces + uploader-address-causes-mail-loops-or-bounces +Explanation: The contact's mail address either loops back to itself or is known + to bounce. + . + Loops happen because an address is <code>package@packages.debian.org</code> + or to <code>package@packages.qa.debian.org</code>. Bounces happen when the + recipient, typically a mailing list, is known to bounce mails. + . + The mail address must accept messages from role accounts used to send + automated mails regarding the package, including those from the bug + tracking system. +See-Also: debian-policy 3.3 diff --git a/tags/m/mail-contact.tag b/tags/m/mail-contact.tag new file mode 100644 index 0000000..ee84799 --- /dev/null +++ b/tags/m/mail-contact.tag @@ -0,0 +1,7 @@ +Tag: mail-contact +Severity: classification +Check: fields/mail-address +Renamed-From: + maintainer + uploader +Explanation: This person is a contact in the named group for this package. diff --git a/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag b/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag new file mode 100644 index 0000000..7bf2857 --- /dev/null +++ b/tags/m/mail-transport-agent-dependency-does-not-specify-default-mta.tag @@ -0,0 +1,12 @@ +Tag: mail-transport-agent-dependency-does-not-specify-default-mta +Severity: warning +Check: fields/package-relations +Explanation: This package has a relationship with the mail-transport-agent + virtual package but does not specify the default-mta 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 default-mta before + mail-transport-agent. diff --git a/tags/m/mailing-list-on-alioth.tag b/tags/m/mailing-list-on-alioth.tag new file mode 100644 index 0000000..f41b481 --- /dev/null +++ b/tags/m/mailing-list-on-alioth.tag @@ -0,0 +1,10 @@ +Tag: mailing-list-on-alioth +Severity: classification +Check: fields/mail-address +Explanation: The specified email address uses lists.alioth.debian.org. That + system was migrated to a separate debian.net system run by DDs. + Teams were encouraged to migrate to the new system, but they are + also free to use the old address going forward if they like. + . + For further information, please consult the Debian Wiki. +See-Also: https://wiki.debian.org/Alioth/MailingListContinuation, Bug#962448 diff --git a/tags/m/maintainer-also-in-uploaders.tag b/tags/m/maintainer-also-in-uploaders.tag new file mode 100644 index 0000000..de1cf54 --- /dev/null +++ b/tags/m/maintainer-also-in-uploaders.tag @@ -0,0 +1,8 @@ +Tag: maintainer-also-in-uploaders +Severity: warning +Check: fields/uploaders +Explanation: The maintainer value also appears on the <code>Uploaders</code> field. + There were some reasons why this was useful when Uploaders support was + first introduced, but those have long-since been fixed and there is no + longer any need to list the maintainer in Uploaders. The duplicate + information should probably be removed. diff --git a/tags/m/maintainer-desktop-entry.tag b/tags/m/maintainer-desktop-entry.tag new file mode 100644 index 0000000..e14c9c0 --- /dev/null +++ b/tags/m/maintainer-desktop-entry.tag @@ -0,0 +1,10 @@ +Tag: maintainer-desktop-entry +Severity: pedantic +Check: debian/desktop-entries +Explanation: The maintainer keeps a desktop entry in ./debian. Please forward + the desktop entry upstream and ask them to include it in their version + control system, and in their next release. + . + If the desktop entry was already forwarded or rejected, or the upstream + is gone, please override the tag and annotate it with a suitable comment. +See-Also: social contract item 2, developer-reference 3.1.4, debian-policy 4.3 diff --git a/tags/m/maintainer-manual-page.tag b/tags/m/maintainer-manual-page.tag new file mode 100644 index 0000000..b825102 --- /dev/null +++ b/tags/m/maintainer-manual-page.tag @@ -0,0 +1,11 @@ +Tag: maintainer-manual-page +Severity: pedantic +Check: debian/manual-pages +Renamed-From: maintainer-manpage +Explanation: The maintainer keeps a manual page in ./debian. Please forward the + manual page upstream and ask them to include in their version control + system, and in their next release. + . + If the manual page was already forwarded or rejected, or the upstream is + gone, please override the tag and annotate it with a suitable comment. +See-Also: social contract item 2, developer-reference 3.1.4, debian-policy 4.3 diff --git a/tags/m/maintainer-script-calls-chown-improperly.tag b/tags/m/maintainer-script-calls-chown-improperly.tag new file mode 100644 index 0000000..a2d593d --- /dev/null +++ b/tags/m/maintainer-script-calls-chown-improperly.tag @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-chown-improperly +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-deprecated-chown-usage +Explanation: <code>chown user.group</code> is called in one of the maintainer + scripts. The correct syntax is <code>chown user:group</code>. Using "." as a + separator is still supported by the GNU tools, but it will fail as soon + as a system uses the "." in user or group names. +See-Also: chown(1) diff --git a/tags/m/maintainer-script-calls-gconftool.tag b/tags/m/maintainer-script-calls-gconftool.tag new file mode 100644 index 0000000..d21bc70 --- /dev/null +++ b/tags/m/maintainer-script-calls-gconftool.tag @@ -0,0 +1,6 @@ +Tag: maintainer-script-calls-gconftool +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-gconftool +Explanation: This script apparently runs gconftool or gconftool-2. It should + probably be calling gconf-schemas or update-gconf-defaults instead. diff --git a/tags/m/maintainer-script-calls-init-script-directly.tag b/tags/m/maintainer-script-calls-init-script-directly.tag new file mode 100644 index 0000000..fb33495 --- /dev/null +++ b/tags/m/maintainer-script-calls-init-script-directly.tag @@ -0,0 +1,11 @@ +Tag: maintainer-script-calls-init-script-directly +Severity: error +Check: init-d/maintainer-script +Explanation: The named maintainer script appear to run an <code>init</code> script in + <code>/etc/init.d/*</code> directly and not via <code>invoke-rc.d</code>, but + the use of <code>invoke-rc.d</code> is required. + . + Maintainer scripts may call an init script directly only when <code>invoke-rc.d</code> + is not available. +See-Also: + debian-policy 9.3.3.2 diff --git a/tags/m/maintainer-script-calls-install-sgmlcatalog.tag b/tags/m/maintainer-script-calls-install-sgmlcatalog.tag new file mode 100644 index 0000000..e4f57af --- /dev/null +++ b/tags/m/maintainer-script-calls-install-sgmlcatalog.tag @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-install-sgmlcatalog +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-use-install-sgmlcatalog +Explanation: The maintainer script apparently runs install-sgmlcatalog. + install-sgmlcatalog is deprecated and should only have been used + in postinst or prerm to remove the entries from earlier packages. + Given how long ago this transition was, consider removing it + entirely. diff --git a/tags/m/maintainer-script-calls-service.tag b/tags/m/maintainer-script-calls-service.tag new file mode 100644 index 0000000..77e7345 --- /dev/null +++ b/tags/m/maintainer-script-calls-service.tag @@ -0,0 +1,14 @@ +Tag: maintainer-script-calls-service +Severity: error +Check: scripts +Experimental: yes +Renamed-From: maintainer-script-should-not-use-service +Explanation: The maintainer script apparently runs the service command. This + command is reserved for local administrators and must never be used + by a Debian package. + . + Please replace with calls to <code>update-rc.d(8)</code> and + <code>invoke-rc.d(8)</code>. If your package installs this service, this + can be automated using <code>dh_installinit(1)</code> or + <code>dh_installsystemd(1)</code>. +See-Also: debian-policy 9.3.3 diff --git a/tags/m/maintainer-script-calls-start-stop-daemon.tag b/tags/m/maintainer-script-calls-start-stop-daemon.tag new file mode 100644 index 0000000..dcae214 --- /dev/null +++ b/tags/m/maintainer-script-calls-start-stop-daemon.tag @@ -0,0 +1,9 @@ +Tag: maintainer-script-calls-start-stop-daemon +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-start-stop-daemon +Explanation: The maintainer script seems to call <code>start-stop-daemon</code> + directly. Long-running daemons should be started and stopped via init + scripts using <code>invoke-rc.d</code> rather than directly in maintainer + scripts. +See-Also: debian-policy 9.3.3.2 diff --git a/tags/m/maintainer-script-calls-systemctl.tag b/tags/m/maintainer-script-calls-systemctl.tag new file mode 100644 index 0000000..adbaf3a --- /dev/null +++ b/tags/m/maintainer-script-calls-systemctl.tag @@ -0,0 +1,13 @@ +Tag: maintainer-script-calls-systemctl +Severity: warning +Check: maintainer-scripts/systemctl +Explanation: The maintainer script calls systemctl directly. Actions such as enabling + a unit file should be done using <code>deb-systemd-helper</code> so that they work + on machines with or without systemd. Starting a service should be done via + <code>invoke-rc.d</code> if the service has a corresponding sysvinit script or + <code>deb-systemd-invoke</code> if it does not. + . + If you are using debhelper, please use the <code>systemd</code> debhelper + addon, which is provided by <code>debhelper (>= 9.20160709~)</code>. +See-Also: + https://wiki.debian.org/Teams/pkg-systemd/Packaging diff --git a/tags/m/maintainer-script-changes-ld-so-conf.tag b/tags/m/maintainer-script-changes-ld-so-conf.tag new file mode 100644 index 0000000..45af7ad --- /dev/null +++ b/tags/m/maintainer-script-changes-ld-so-conf.tag @@ -0,0 +1,17 @@ +Tag: maintainer-script-changes-ld-so-conf +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-modify-ld-so-conf +Explanation: This package appears to modify <code>/etc/ld.so.conf</code> and does not + appear to be part of libc. Packages installing shared libraries in + non-standard locations were previously permitted to modify + /etc/ld.so.conf to add the non-standard path, but this permission was + removed in Policy 3.8.3. + . + Packages containing shared libraries should either install them into + <code>/usr/lib</code> or should require binaries built against them to set + RPATH to find the library at run-time. Installing libraries in a + different directory and modifying the run-time linker path is equivalent + to installing them into <code>/usr/lib</code> except now conflicting library + packages may cause random segfaults and difficult-to-debug problems + instead of conflicts in the package manager. diff --git a/tags/m/maintainer-script-changes-netbase.tag b/tags/m/maintainer-script-changes-netbase.tag new file mode 100644 index 0000000..b11a1c2 --- /dev/null +++ b/tags/m/maintainer-script-changes-netbase.tag @@ -0,0 +1,9 @@ +Tag: maintainer-script-changes-netbase +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-modify-netbase-managed-file +Explanation: The maintainer script modifies at least one of the files + <code>/etc/services</code>, <code>/etc/protocols</code>, and <code>/etc/rpc</code>, + which are managed by the netbase package. Instead of doing this, please + file a wishlist bug against netbase to have an appropriate entry added. +See-Also: debian-policy 11.2 diff --git a/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag b/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag new file mode 100644 index 0000000..7bac250 --- /dev/null +++ b/tags/m/maintainer-script-does-not-check-for-existence-of-installdocs.tag @@ -0,0 +1,12 @@ +Tag: maintainer-script-does-not-check-for-existence-of-installdocs +Severity: error +Check: menus +Explanation: The maintainer script calls the <code>install-docs</code> command without + checking that it exists, but the <code>doc-base</code> package, which provides + the command, is not an <code>essential</code> package and may not be available. + . + For example, you can use the following code in your maintainer script: + . + if which install-docs > /dev/null; then + install-docs -i /usr/share/doc-base/<your-package> + fi diff --git a/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag b/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag new file mode 100644 index 0000000..8fc6caf --- /dev/null +++ b/tags/m/maintainer-script-does-not-check-for-existence-of-updatemenus.tag @@ -0,0 +1,14 @@ +Tag: maintainer-script-does-not-check-for-existence-of-updatemenus +Severity: error +Check: menus +Explanation: The given maintainer script calls the <code>update-menus</code> + command but does not check if it exists. + . + The <code>menu</code> package that provides the command is not an "essential" + package. + . + For example, you can use the following code in your maintainer script: + . + if which update-menus > /dev/null; then + update-menus + fi diff --git a/tags/m/maintainer-script-empty.tag b/tags/m/maintainer-script-empty.tag new file mode 100644 index 0000000..613f77e --- /dev/null +++ b/tags/m/maintainer-script-empty.tag @@ -0,0 +1,13 @@ +Tag: maintainer-script-empty +Severity: warning +Check: maintainer-scripts/empty +Explanation: The named maintainer script does not appear to contain code + other than comments or boilerplate such as <code>set -e</code>, + <code>exit</code> statements, or a <code>case</code> statement + to parse options. + . + While harmless in most cases, it is not needed. The package may also leave + files behind until purged, and can contribute to rare problems when + <code>dpkg</code> fails because no maintainer scripts are present. + . + Please do not ship the maintainer script unless it does something useful. diff --git a/tags/m/maintainer-script-has-invalid-update-inetd-options.tag b/tags/m/maintainer-script-has-invalid-update-inetd-options.tag new file mode 100644 index 0000000..a16542b --- /dev/null +++ b/tags/m/maintainer-script-has-invalid-update-inetd-options.tag @@ -0,0 +1,16 @@ +Tag: maintainer-script-has-invalid-update-inetd-options +Severity: warning +Check: scripts +See-Also: update-inetd(1), Bug#909758, Bug#909506 +Explanation: The specified maintainer script seems to call + <code>update-inetd(1)</code> with an invalid option combination. + . + For example, the <code>--group</code> parameter is only valid in + combination with <code>--add</code> and <code>--pattern</code> is only valid + without <code>--add</code>. + . + Whilst these have been ignored in the past they now emit a warning + which will become an error in the future, resulting in upgrade/removal + failures. + . + Please correct the call to <code>update-inetd(1)</code>. diff --git a/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag b/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag new file mode 100644 index 0000000..949bdf5 --- /dev/null +++ b/tags/m/maintainer-script-has-unexpanded-debhelper-token.tag @@ -0,0 +1,9 @@ +Tag: maintainer-script-has-unexpanded-debhelper-token +Severity: warning +Check: build-systems/debhelper/maintainer-script/token +Explanation: The named maintainer script contains a <code>#DEBHELPER#</code> + token. Normally, <code>dh_installdeb</code> removes those tokens + when it makes substitutions in a script. + . + Please note that <code>dh_installdeb</code> does <strong>not</strong> + substitute the <code>#DEBHELPER#</code> token in <code>udebs</code>. diff --git a/tags/m/maintainer-script-hides-init-failure.tag b/tags/m/maintainer-script-hides-init-failure.tag new file mode 100644 index 0000000..cbbc848 --- /dev/null +++ b/tags/m/maintainer-script-hides-init-failure.tag @@ -0,0 +1,12 @@ +Tag: maintainer-script-hides-init-failure +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-hide-init-failure +Explanation: This script calls invoke-rc.d to run an init script but then, if the + init script fails, exits successfully (using || exit 0). If the init + script fails, the maintainer script should probably fail. + . + The most likely cause of this problem is that the package was built with + a debhelper version suffering from Bug#337664 that inserted incorrect + invoke-rc.d code in the generated maintainer script. The package needs to + be reuploaded (could be bin-NMUd, no source changes needed). diff --git a/tags/m/maintainer-script-ignores-errors.tag b/tags/m/maintainer-script-ignores-errors.tag new file mode 100644 index 0000000..767dd7a --- /dev/null +++ b/tags/m/maintainer-script-ignores-errors.tag @@ -0,0 +1,7 @@ +Tag: maintainer-script-ignores-errors +Severity: warning +Check: scripts +See-Also: debian-policy 10.4 +Explanation: The maintainer script doesn't seem to set the <code>-e</code> flag which + ensures that the script's execution is aborted when any executed command + fails. diff --git a/tags/m/maintainer-script-interpreter.tag b/tags/m/maintainer-script-interpreter.tag new file mode 100644 index 0000000..2247ad8 --- /dev/null +++ b/tags/m/maintainer-script-interpreter.tag @@ -0,0 +1,4 @@ +Tag: maintainer-script-interpreter +Severity: classification +Check: scripts +Explanation: Interpreter used in maintainer script or ELF diff --git a/tags/m/maintainer-script-lacks-debhelper-token.tag b/tags/m/maintainer-script-lacks-debhelper-token.tag new file mode 100644 index 0000000..3168b35 --- /dev/null +++ b/tags/m/maintainer-script-lacks-debhelper-token.tag @@ -0,0 +1,8 @@ +Tag: maintainer-script-lacks-debhelper-token +Severity: warning +Check: debhelper +Explanation: This package is built using debhelper commands that may modify + maintainer scripts, but the maintainer scripts do not contain + the "#DEBHELPER#" token debhelper uses to modify them. + . + Adding the token to the scripts is recommended. diff --git a/tags/m/maintainer-script-lacks-home-in-adduser.tag b/tags/m/maintainer-script-lacks-home-in-adduser.tag new file mode 100644 index 0000000..ce372cb --- /dev/null +++ b/tags/m/maintainer-script-lacks-home-in-adduser.tag @@ -0,0 +1,18 @@ +Tag: maintainer-script-lacks-home-in-adduser +Severity: error +Check: scripts +Renamed-From: maintainer-script-should-not-use-adduser-system-without-home +Explanation: The maintainer script apparently runs 'adduser --system' + but hardcodes a path under '/home' for the '--home' option or + does not use the '--home' option. + . + The FHS says: /home is a fairly standard concept, but it + is clearly a site-specific filesystem. The setup will differ + from host to host. Therefore, no program should rely on this + location. + . + Note that passing --no-create-home alone does not solve the issue + because home field of passwd file point to a non existing + /home subdirectory. Please use + <code>adduser --no-create-home --home /nonexistent</code> instead. +See-Also: filesystem-hierarchy homeuserhomedirectories, adduser(8) diff --git a/tags/m/maintainer-script-modifies-inetd-conf.tag b/tags/m/maintainer-script-modifies-inetd-conf.tag new file mode 100644 index 0000000..6127937 --- /dev/null +++ b/tags/m/maintainer-script-modifies-inetd-conf.tag @@ -0,0 +1,7 @@ +Tag: maintainer-script-modifies-inetd-conf +Severity: error +Check: scripts +Explanation: The maintainer script modifies <code>/etc/inetd.conf</code> directly. + This file must not be modified directly; instead, use the + <code>update-inetd</code> script or the <code>DebianNet.pm</code> Perl module. +See-Also: debian-policy 11.2 diff --git a/tags/m/maintainer-script-needs-depends-on-adduser.tag b/tags/m/maintainer-script-needs-depends-on-adduser.tag new file mode 100644 index 0000000..4cc9141 --- /dev/null +++ b/tags/m/maintainer-script-needs-depends-on-adduser.tag @@ -0,0 +1,5 @@ +Tag: maintainer-script-needs-depends-on-adduser +Severity: warning +Check: scripts +Explanation: This script calls adduser, but the package does not depend or + pre-depend on the adduser package. diff --git a/tags/m/maintainer-script-needs-depends-on-gconf2.tag b/tags/m/maintainer-script-needs-depends-on-gconf2.tag new file mode 100644 index 0000000..b5a6c3a --- /dev/null +++ b/tags/m/maintainer-script-needs-depends-on-gconf2.tag @@ -0,0 +1,7 @@ +Tag: maintainer-script-needs-depends-on-gconf2 +Severity: warning +Check: scripts +Explanation: This script calls gconf-schemas, which comes from the gconf2 package, + but does not depend or pre-depend on gconf2. If you are using dh_gconf, + add a dependency on ${misc:Depends} and dh_gconf will take care of this + for you. diff --git a/tags/m/maintainer-script-needs-depends-on-ucf.tag b/tags/m/maintainer-script-needs-depends-on-ucf.tag new file mode 100644 index 0000000..972e040 --- /dev/null +++ b/tags/m/maintainer-script-needs-depends-on-ucf.tag @@ -0,0 +1,5 @@ +Tag: maintainer-script-needs-depends-on-ucf +Severity: warning +Check: scripts +Explanation: This script calls ucf, but the package does not depend or pre-depend + on the ucf package. diff --git a/tags/m/maintainer-script-needs-depends-on-update-inetd.tag b/tags/m/maintainer-script-needs-depends-on-update-inetd.tag new file mode 100644 index 0000000..c7ffaff --- /dev/null +++ b/tags/m/maintainer-script-needs-depends-on-update-inetd.tag @@ -0,0 +1,10 @@ +Tag: maintainer-script-needs-depends-on-update-inetd +Severity: warning +Check: scripts +Explanation: This script calls update-inetd, but the package does not depend or + pre-depend on inet-superserver, any of the providers of inet-superserver + which provide it, or update-inetd. + . + update-inetd has been moved from netbase into a separate package, so a + dependency on netbase should be updated to depend on "openbsd-inetd | + inet-superserver". diff --git a/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag b/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag new file mode 100644 index 0000000..4a5ab1e --- /dev/null +++ b/tags/m/maintainer-script-needs-depends-on-xfonts-utils.tag @@ -0,0 +1,11 @@ +Tag: maintainer-script-needs-depends-on-xfonts-utils +Severity: warning +Check: scripts +Explanation: This script calls a utility provided by the xfonts-utils package + but does not depend or pre-depend on this package. + . + Packages that call update-fonts-scale, update-fonts-dir (etc.) need to + depend on xfonts-utils.If you are using debhelper. + . + Please add a dependency on ${misc:Depends} and dh_installxfonts will + take care of this for you. diff --git a/tags/m/maintainer-script-needs-depends-on-xml-core.tag b/tags/m/maintainer-script-needs-depends-on-xml-core.tag new file mode 100644 index 0000000..779484c --- /dev/null +++ b/tags/m/maintainer-script-needs-depends-on-xml-core.tag @@ -0,0 +1,8 @@ +Tag: maintainer-script-needs-depends-on-xml-core +Severity: warning +Check: scripts +Explanation: This script calls update-xmlcatalog, which comes from the xml-core + package, but does not depend or pre-depend on xml-core. Packages that call + update-xmlcatalog need to depend on xml-core. If you are using + dh_installxmlcatalogs, add a dependency on ${misc:Depends} and + dh_installxmlcatalogs will take care of this for you. diff --git a/tags/m/maintainer-script-removes-device-files.tag b/tags/m/maintainer-script-removes-device-files.tag new file mode 100644 index 0000000..5000d30 --- /dev/null +++ b/tags/m/maintainer-script-removes-device-files.tag @@ -0,0 +1,6 @@ +Tag: maintainer-script-removes-device-files +Severity: error +Check: scripts +See-Also: debian-policy 10.6 +Explanation: Maintainer scripts must not remove device files. This is left to + the system administrator. diff --git a/tags/m/maintainer-script-sets-alternative-improperly.tag b/tags/m/maintainer-script-sets-alternative-improperly.tag new file mode 100644 index 0000000..203875d --- /dev/null +++ b/tags/m/maintainer-script-sets-alternative-improperly.tag @@ -0,0 +1,12 @@ +Tag: maintainer-script-sets-alternative-improperly +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-update-alternatives-set +Explanation: The maintainer script calls <code>update-alternatives --set + <alternative> foo</code> or <code>update-alternatives --config + <alternative></code> or <code>update-alternatives --set-selections</code>. + . + This makes it impossible to distinguish between an alternative that's + manually set because the user set it and one that's manually set because + the package set it. +See-Also: update-alternatives(8) diff --git a/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag b/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag new file mode 100644 index 0000000..1da9065 --- /dev/null +++ b/tags/m/maintainer-script-should-not-parse-etc-passwd-or-group.tag @@ -0,0 +1,10 @@ +Tag: maintainer-script-should-not-parse-etc-passwd-or-group +Severity: warning +Check: scripts +See-Also: getent(1), nss(5) +Explanation: The maintainer script appears to manually parse <code>/etc/passwd</code> + or <code>/etc/group</code> instead of using the <code>getent(1)</code> utility + to display entries. + . + This bypasses the Name Service Switch (NSS), avoiding querying + centralised or networked user databases such as LDAP, etc. diff --git a/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag b/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag new file mode 100644 index 0000000..bd28c61 --- /dev/null +++ b/tags/m/maintainer-script-should-not-use-dpkg-maintscript-helper.tag @@ -0,0 +1,10 @@ +Tag: maintainer-script-should-not-use-dpkg-maintscript-helper +Severity: warning +Check: scripts +Explanation: The maintainer script seems to make manual calls to the + <code>dpkg-maintscript-helper(1)</code> utility. + . + Please use <code>package.maintscript</code> files instead; the + <code>dh_installdeb(1)</code> tool will do some basic validation of some of + the commands listed in this file to catch common mistakes. +See-Also: dpkg-maintscript-helper(1), dh_installdeb(1) diff --git a/tags/m/maintainer-script-should-not-use-piuparts-variable.tag b/tags/m/maintainer-script-should-not-use-piuparts-variable.tag new file mode 100644 index 0000000..6c1b2c8 --- /dev/null +++ b/tags/m/maintainer-script-should-not-use-piuparts-variable.tag @@ -0,0 +1,12 @@ +Tag: maintainer-script-should-not-use-piuparts-variable +Severity: warning +Check: scripts +See-Also: piuparts(1), https://piuparts.debian.org/doc/README.html +Explanation: The maintainer script appears to reference one of the + <code>PIUPARTS_*</code> variables such as <code>PIUPARTS_TEST</code> or + <code>PIUPARTS_PHASE</code>. + . + These variables are intended to be used by custom <code>piuparts(1)</code> + scripts and not by maintainer scripts themselves. + . + Please remove the references to this variable. diff --git a/tags/m/maintainer-script-supports-ancient-package-version.tag b/tags/m/maintainer-script-supports-ancient-package-version.tag new file mode 100644 index 0000000..f523bd4 --- /dev/null +++ b/tags/m/maintainer-script-supports-ancient-package-version.tag @@ -0,0 +1,8 @@ +Tag: maintainer-script-supports-ancient-package-version +Severity: info +Check: maintainer-scripts/ancient-version +Experimental: yes +Explanation: The named maintainer script appears to look for a package version + that is older than the current <code>oldstable</code> release. + . + Please remove the check for that version. Such upgrades are not supported. diff --git a/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag b/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag new file mode 100644 index 0000000..1b4c715 --- /dev/null +++ b/tags/m/maintainer-script-switches-dir-to-symlink-unsafely.tag @@ -0,0 +1,11 @@ +Tag: maintainer-script-switches-dir-to-symlink-unsafely +Severity: error +Check: scripts +Experimental: yes +Renamed-From: maintainer-script-may-use-dir_to_symlink_helper +Explanation: The maintainer script apparently change a directory to a symlink + not using dir_to_symlink command of dpkg-maintscript-helper, that take + great care to avoid a lot of problems. + . + Please use the dpkg-maintscript-helper dir_to_symlink command. +See-Also: dpkg-maintscript-helper(1) diff --git a/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag b/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag new file mode 100644 index 0000000..463c4ba --- /dev/null +++ b/tags/m/maintainer-script-updates-fontconfig-cache-improperly.tag @@ -0,0 +1,7 @@ +Tag: maintainer-script-updates-fontconfig-cache-improperly +Severity: warning +Check: scripts +Renamed-From: maintainer-script-should-not-use-fc-cache +Explanation: This script apparently runs fc-cache. Updating of the fontconfig + cache files is now handled automatically by triggers, so running fc-cache + from maintainer scripts is no longer necessary. diff --git a/tags/m/maintainer-script-without-set-e.tag b/tags/m/maintainer-script-without-set-e.tag new file mode 100644 index 0000000..1bd32f6 --- /dev/null +++ b/tags/m/maintainer-script-without-set-e.tag @@ -0,0 +1,10 @@ +Tag: maintainer-script-without-set-e +Severity: pedantic +Check: scripts +See-Also: debian-policy 10.4 +Explanation: The maintainer script passes <code>-e</code> to the shell on the + <code>#!</code> line rather than using <code>set -e</code> in the body of the + script. This is fine for normal operation, but if the script is run by + hand with <code>sh /path/to/script</code> (common in debugging), <code>-e</code> + will not be in effect. It's therefore better to use <code>set -e</code> in + the body of the script. diff --git a/tags/m/maintainer-shell-script-fails-syntax-check.tag b/tags/m/maintainer-shell-script-fails-syntax-check.tag new file mode 100644 index 0000000..51fe715 --- /dev/null +++ b/tags/m/maintainer-shell-script-fails-syntax-check.tag @@ -0,0 +1,8 @@ +Tag: maintainer-shell-script-fails-syntax-check +Severity: error +Check: script/syntax +Explanation: Running this shell script with the shell's -n option set fails, + which means that the script has syntax errors. This will likely make + the package uninstallable. + . + Run e.g. <code>sh -n yourscript</code> to see the errors yourself. diff --git a/tags/m/maintainer-upload-has-incorrect-version-number.tag b/tags/m/maintainer-upload-has-incorrect-version-number.tag new file mode 100644 index 0000000..6e4109d --- /dev/null +++ b/tags/m/maintainer-upload-has-incorrect-version-number.tag @@ -0,0 +1,7 @@ +Tag: maintainer-upload-has-incorrect-version-number +Severity: warning +Check: nmu +Explanation: A maintainer upload should have a Debian revision without dots. + Revisions with dots are reserved for Non-Maintainer Uploads (NMUs). If you + do a maintainer-upload with dots a potential NMU'er has problems choosing a + correct version number. diff --git a/tags/m/maintscript-calls-ldconfig.tag b/tags/m/maintscript-calls-ldconfig.tag new file mode 100644 index 0000000..19287cd --- /dev/null +++ b/tags/m/maintscript-calls-ldconfig.tag @@ -0,0 +1,24 @@ +Tag: maintscript-calls-ldconfig +Severity: warning +Check: maintainer-scripts/ldconfig +Explanation: The given maintainer script calls <code>ldconfig</code>, + but such calls in maintainer scripts should be replaced instead by a + <code>dpkg</code> trigger. + . + Please replace the <code>ldconfig</code> call with an <code>activate-noawait + ldconfig</code> trigger. With Debhelper, it is usually sufficient + to add that line to <code>debian/<package>.triggers</code>. + . + This warning may appear if the package was compiled with Debhelper older than + version 9.20151004. Assuming all <code>ldconfig</code> invocations were added + by Debhelper, this tag should disappear when the package is rebuilt with a + newer version of Debhelper. +See-Also: + https://lists.debian.org/debian-devel/2015/08/msg00412.html + +Screen: glibc/control/ldconfig +Advocates: Debian Lintian Maintainers <lintian-maint@debian.org> +Reason: The packages built from <code>glibc</code> (notably <code>libc-bin</code>) + need to call <code>ldconfig</code> in order to implement the <code>ldconfig</code> trigger. + . + Transferred from the check. diff --git a/tags/m/maintscript-includes-maint-script-parameters.tag b/tags/m/maintscript-includes-maint-script-parameters.tag new file mode 100644 index 0000000..1c7d20d --- /dev/null +++ b/tags/m/maintscript-includes-maint-script-parameters.tag @@ -0,0 +1,9 @@ +Tag: maintscript-includes-maint-script-parameters +Severity: warning +Check: debian/maintscript +Explanation: The named <code>debian/*.maintscript</code> file uses commands + or parameters from <code>dpkg-maintscript-helper(1)</code>. + . + Debhelper will add them automatically. Please do not include them manually. +See-Also: + dh_installdeb(1) diff --git a/tags/m/making-assumptions-about-interfaces-in-templates.tag b/tags/m/making-assumptions-about-interfaces-in-templates.tag new file mode 100644 index 0000000..162e694 --- /dev/null +++ b/tags/m/making-assumptions-about-interfaces-in-templates.tag @@ -0,0 +1,8 @@ +Tag: making-assumptions-about-interfaces-in-templates +Severity: warning +Check: debian/debconf +Explanation: Template text should not make reference to widgets belonging to + some debconf interfaces. Sentences like "If you answer Yes..." have no + meaning for users of graphical interfaces which use checkboxes for + boolean questions. +See-Also: developer-reference 6.5.2.4 diff --git a/tags/m/malformed-changes-file.tag b/tags/m/malformed-changes-file.tag new file mode 100644 index 0000000..74f0ed1 --- /dev/null +++ b/tags/m/malformed-changes-file.tag @@ -0,0 +1,11 @@ +Tag: malformed-changes-file +Severity: error +Check: fields/format +Explanation: There is no "Format" field in your .changes file. This probably + indicates some serious problem with the file. Perhaps it's not actually + a changes file, or it's not in the proper format, or it's PGP-signed + twice. + . + Since Lintian was unable to parse this .changes file, any further checks + on it were skipped. +See-Also: debian-policy 5.5 diff --git a/tags/m/malformed-contact.tag b/tags/m/malformed-contact.tag new file mode 100644 index 0000000..24e5ad2 --- /dev/null +++ b/tags/m/malformed-contact.tag @@ -0,0 +1,17 @@ +Tag: malformed-contact +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-address-missing + changed-by-address-missing + malformed-maintainer-field + malformed-uploaders-field + malformed-changed-by-field + maintainer-address-malformed + uploader-address-malformed + changed-by-address-malformed +Explanation: The named field identifying contact persons could not be + parsed according to the rules in the Policy Manual. +See-Also: debian-policy 5.6.2, + debian-policy 5.6.3, + debian-policy 5.6.4 diff --git a/tags/m/malformed-deb-archive.tag b/tags/m/malformed-deb-archive.tag new file mode 100644 index 0000000..39e956f --- /dev/null +++ b/tags/m/malformed-deb-archive.tag @@ -0,0 +1,11 @@ +Tag: malformed-deb-archive +Severity: error +Check: deb-format +Explanation: The binary package is not a correctly constructed archive. A binary + Debian package must be an ar archive with exactly three members: + <code>debian-binary</code>, <code>control.tar.gz</code>, and one of + <code>data.tar.gz</code>, <code>data.tar.bz2</code> or <code>data.tar.xz</code> + in exactly that order. The <code>debian-binary</code> member must start + with a single line containing the version number, with a major revision + of 2. +See-Also: deb(5) diff --git a/tags/m/malformed-debian-changelog-version.tag b/tags/m/malformed-debian-changelog-version.tag new file mode 100644 index 0000000..bfee2df --- /dev/null +++ b/tags/m/malformed-debian-changelog-version.tag @@ -0,0 +1,7 @@ +Tag: malformed-debian-changelog-version +Severity: error +Check: debian/changelog +Explanation: The version string in the latest changelog entry was not parsed + correctly. Usually, that means it does not conform to policy. +See-Also: + debian-policy 5.6.12 diff --git a/tags/m/malformed-dm-upload-allowed.tag b/tags/m/malformed-dm-upload-allowed.tag new file mode 100644 index 0000000..5b263d8 --- /dev/null +++ b/tags/m/malformed-dm-upload-allowed.tag @@ -0,0 +1,8 @@ +Tag: malformed-dm-upload-allowed +Severity: error +Check: fields/dm-upload-allowed +See-Also: https://www.debian.org/vote/2007/vote_003 +Explanation: The Dm-Upload-Allowed field in this package is set to something + other than "yes". The only standardized value for this field in the + Debian GR is "yes" and other values (including capitalization variants) + may not work as expected. diff --git a/tags/m/malformed-md5sums-control-file.tag b/tags/m/malformed-md5sums-control-file.tag new file mode 100644 index 0000000..5f0993b --- /dev/null +++ b/tags/m/malformed-md5sums-control-file.tag @@ -0,0 +1,7 @@ +Tag: malformed-md5sums-control-file +Severity: error +Check: md5sums +Explanation: The indicated line of the md5sums control file for this package was + malformed. Each line of an md5sums control file should contain an MD5 + checksum, some whitespace, and then the path to the file corresponding to + that checksum. diff --git a/tags/m/malformed-override.tag b/tags/m/malformed-override.tag new file mode 100644 index 0000000..e5df4fc --- /dev/null +++ b/tags/m/malformed-override.tag @@ -0,0 +1,15 @@ +Tag: malformed-override +Severity: error +Show-Always: yes +Check: debian/lintian-overrides/malformed +Explanation: Lintian discovered an override entry with an invalid format. An + override entry should have the format: + . + [[<package>][ <archlist>][ <type>]:] <tag>[ <extra> ...] + . + where <package> is the package name, <archlist> is an + architecture list, <type> specifies the package type (binary is the + default), <tag> is the tag to override, and <extra> is any + specific information for the particular tag to override. +See-Also: + lintian-manual 2.4.1 diff --git a/tags/m/malformed-prompt-in-templates.tag b/tags/m/malformed-prompt-in-templates.tag new file mode 100644 index 0000000..05cab6a --- /dev/null +++ b/tags/m/malformed-prompt-in-templates.tag @@ -0,0 +1,11 @@ +Tag: malformed-prompt-in-templates +Severity: warning +Check: debian/debconf +Explanation: The short description of a select, multiselect, string and password + debconf template is a prompt and not a title. Avoid question style + prompts ("IP Address?") in favour of "opened" prompts ("IP address:"). + The use of colons is recommended. + . + If this template is only used internally by the package and not displayed + to the user, put "for internal use" in the short description. +See-Also: developer-reference 6.5.4.2 diff --git a/tags/m/malformed-python-version.tag b/tags/m/malformed-python-version.tag new file mode 100644 index 0000000..bd299e6 --- /dev/null +++ b/tags/m/malformed-python-version.tag @@ -0,0 +1,16 @@ +Tag: malformed-python-version +Severity: error +Check: languages/python +See-Also: python-policy 3.4 +Explanation: The Python-Version or Python3-Version control field is not in one + of the valid formats. It should be in one of the following: + . + all + current + current, >= X.Y + >= X.Y + >= A.B, << X.Y + A.B, X.Y + . + (One or more specific versions may be listed with the last form.) A.B + and X.Y should be Python versions. diff --git a/tags/m/malformed-question-in-templates.tag b/tags/m/malformed-question-in-templates.tag new file mode 100644 index 0000000..5e6c5e2 --- /dev/null +++ b/tags/m/malformed-question-in-templates.tag @@ -0,0 +1,11 @@ +Tag: malformed-question-in-templates +Severity: warning +Check: debian/debconf +Explanation: The short description of a boolean debconf template should be + phrased in the form of a question which should be kept short and should + generally end with a question mark. Terse writing style is permitted and + even encouraged if the question is rather long. + . + If this template is only used internally by the package and not displayed + to the user, put "for internal use" in the short description. +See-Also: developer-reference 6.5.4.2.2 diff --git a/tags/m/malformed-template-name.tag b/tags/m/malformed-template-name.tag new file mode 100644 index 0000000..620ff53 --- /dev/null +++ b/tags/m/malformed-template-name.tag @@ -0,0 +1,6 @@ +Tag: malformed-template-name +Severity: error +Check: debian/debconf +Explanation: The "Template:" field should contain more than one component, each + separated by a slash ("/"). Each component may only consist of the + alphanumeric characters, "+", "-", and ".". diff --git a/tags/m/malformed-title-in-templates.tag b/tags/m/malformed-title-in-templates.tag new file mode 100644 index 0000000..0ee804a --- /dev/null +++ b/tags/m/malformed-title-in-templates.tag @@ -0,0 +1,7 @@ +Tag: malformed-title-in-templates +Severity: warning +Check: debian/debconf +Explanation: The short description of a note debconf template should be written + as a title and therefore should not end with a period, question mark, + colon, or semicolon. +See-Also: developer-reference 6.5.4.2.4 diff --git a/tags/m/manual-page-for-system-command.tag b/tags/m/manual-page-for-system-command.tag new file mode 100644 index 0000000..54a23f4 --- /dev/null +++ b/tags/m/manual-page-for-system-command.tag @@ -0,0 +1,16 @@ +Tag: manual-page-for-system-command +Check: documentation/manual +Severity: pedantic +Renamed-From: command-in-sbin-has-manpage-in-incorrect-section +Explanation: The command in <code>/sbin</code> or <code>/usr/sbin</code> are system + administration commands; their manual pages thus belong in section 8, + not section 1. + . + Please check whether the command is actually useful to non-privileged + user in which case it should be moved to <code>/bin</code> or + <code>/usr/bin</code>, or alternatively the manual page should be moved to + section 8 instead, ie. <code>/usr/share/man/man8</code>. +See-Also: + Bug#348864, + Bug#253011, + hier(7) diff --git a/tags/m/manual-page-from-template.tag b/tags/m/manual-page-from-template.tag new file mode 100644 index 0000000..93428bb --- /dev/null +++ b/tags/m/manual-page-from-template.tag @@ -0,0 +1,12 @@ +Tag: manual-page-from-template +Severity: error +Check: documentation/manual +Renamed-From: manpage-is-dh_make-template +Explanation: This manual page appears to be an unmodified or insufficiently + modified copy of the dh_make manual page template. It has a whatis entry + (the brief description found in the NAME section) of the form: + . + package - program to do something + . + Please double-check the manual page and replace the template language + with specific information about this program. diff --git a/tags/m/manual-page-in-udeb.tag b/tags/m/manual-page-in-udeb.tag new file mode 100644 index 0000000..79ca3f8 --- /dev/null +++ b/tags/m/manual-page-in-udeb.tag @@ -0,0 +1,5 @@ +Tag: manual-page-in-udeb +Severity: error +Check: documentation/manual +Renamed-From: manpage-in-udeb +Explanation: udeb packages should not contain any manual pages. diff --git a/tags/m/manual-page-with-generic-name.tag b/tags/m/manual-page-with-generic-name.tag new file mode 100644 index 0000000..28a4d3c --- /dev/null +++ b/tags/m/manual-page-with-generic-name.tag @@ -0,0 +1,8 @@ +Tag: manual-page-with-generic-name +Severity: error +Check: documentation/manual +Renamed-From: manpage-has-overly-generic-name +Explanation: The manual page appears to have an overly generic name that is likely to + clash with other packages. + . + Please check your debian/rules or upstream Makefile. diff --git a/tags/m/maven-plugin-in-usr-share-java.tag b/tags/m/maven-plugin-in-usr-share-java.tag new file mode 100644 index 0000000..df13ea5 --- /dev/null +++ b/tags/m/maven-plugin-in-usr-share-java.tag @@ -0,0 +1,5 @@ +Tag: maven-plugin-in-usr-share-java +Severity: warning +Check: languages/java +Explanation: A maven plugin is incorrectly installed in /usr/share/java. + Maven plugins should be installed in /usr/share/maven-repo diff --git a/tags/m/mawk-script-but-no-mawk-dep.tag b/tags/m/mawk-script-but-no-mawk-dep.tag new file mode 100644 index 0000000..77e3893 --- /dev/null +++ b/tags/m/mawk-script-but-no-mawk-dep.tag @@ -0,0 +1,9 @@ +Tag: mawk-script-but-no-mawk-dep +Severity: error +Check: scripts +Explanation: Packages that use mawk scripts must depend on the mawk package. + If they don't need mawk-specific features, and can just as easily work + with gawk, then they should be awk scripts instead. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff --git a/tags/m/maybe-not-arch-all-binnmuable.tag b/tags/m/maybe-not-arch-all-binnmuable.tag new file mode 100644 index 0000000..9b1a194 --- /dev/null +++ b/tags/m/maybe-not-arch-all-binnmuable.tag @@ -0,0 +1,10 @@ +Tag: maybe-not-arch-all-binnmuable +Severity: classification +Check: debian/version-substvars +Experimental: yes +Explanation: Tag to attempt to measure the number of packages that might + have an issue with arch:all binNMUs. + . + At this time, please do *not* attempt to "fix" the problem. It + is not clear what the solution is (if any at all), nor is it clear + that this is something that will or should be supported. diff --git a/tags/m/md5sum-mismatch.tag b/tags/m/md5sum-mismatch.tag new file mode 100644 index 0000000..a132cbe --- /dev/null +++ b/tags/m/md5sum-mismatch.tag @@ -0,0 +1,12 @@ +Tag: md5sum-mismatch +Severity: error +Check: md5sums +Explanation: The md5sum listed for the file does not match the actual file + contents. + . + Usually, this error occurs during the package build process if the + <code>debian/tmp/</code> directory is touched after <code>dh_md5sums</code> + is run. + . + Font files regenerated at post-install time by <code>t1c2pfb</code> + should be overridden. diff --git a/tags/m/md5sums-lists-nonexistent-file.tag b/tags/m/md5sums-lists-nonexistent-file.tag new file mode 100644 index 0000000..d1a0e2b --- /dev/null +++ b/tags/m/md5sums-lists-nonexistent-file.tag @@ -0,0 +1,9 @@ +Tag: md5sums-lists-nonexistent-file +Severity: error +Check: md5sums +Explanation: The md5sums control file lists a file which is not included in the + package. + . + Usually, this error occurs during the package build process if the + <code>debian/tmp/</code> directory is touched after <code>dh_md5sums</code> + is run. diff --git a/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag b/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag new file mode 100644 index 0000000..983d038 --- /dev/null +++ b/tags/m/mentions-deprecated-usr-lib-perl5-directory.tag @@ -0,0 +1,10 @@ +# Imported from pkg-perl-tools (named usr-lib-perl5-mentioned there) +Tag: mentions-deprecated-usr-lib-perl5-directory +Severity: error +Check: languages/perl/perl5 +Experimental: yes +Explanation: As of Perl 5.20, the vendorarch directory is /usr/lib/<triplet>/perl5, + but this package still uses usr/lib/perl5 in some of the files under debian/. + Please replace that with the value of $Config{vendorarch} configuration + parameter, e.g. + $(shell perl -MConfig -wE'say substr($$Config{vendorarch},1)') diff --git a/tags/m/menu-command-not-in-package.tag b/tags/m/menu-command-not-in-package.tag new file mode 100644 index 0000000..b8b8bbe --- /dev/null +++ b/tags/m/menu-command-not-in-package.tag @@ -0,0 +1,8 @@ +Tag: menu-command-not-in-package +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item specifies a command that is not shipped + in the package. + . + The condition can be caused by a typo. Sometimes, an executable was moved + without updating the <code>menu</code> file. diff --git a/tags/m/menu-file-in-usr-lib.tag b/tags/m/menu-file-in-usr-lib.tag new file mode 100644 index 0000000..d546a34 --- /dev/null +++ b/tags/m/menu-file-in-usr-lib.tag @@ -0,0 +1,11 @@ +Tag: menu-file-in-usr-lib +Severity: warning +Check: menus +Explanation: The installation location <code>/usr/lib/menu</code> for + <code>menu</code> files has been deprecated since version 2.1.25 (but + still works). Menu files should go into <code>/usr/share/menu</code>. + . + Only menu files that are compiled executables still need to go into + <code>/usr/lib/menu</code>. +See-Also: + menu-manual 3.1 diff --git a/tags/m/menu-icon-cannot-be-parsed.tag b/tags/m/menu-icon-cannot-be-parsed.tag new file mode 100644 index 0000000..d3acfb4 --- /dev/null +++ b/tags/m/menu-icon-cannot-be-parsed.tag @@ -0,0 +1,10 @@ +Tag: menu-icon-cannot-be-parsed +Severity: warning +Check: menu-format +Explanation: The <code>icon</code> file could not be parsed. + . + Sometimes, it is a bad XPM file. Sometimes, Lintian parsing needs to be + improved. + . + If window managers and other standard tools accept the file without + complaints, please file a bug against Lintian. diff --git a/tags/m/menu-icon-missing.tag b/tags/m/menu-icon-missing.tag new file mode 100644 index 0000000..7bb60ed --- /dev/null +++ b/tags/m/menu-icon-missing.tag @@ -0,0 +1,17 @@ +Tag: menu-icon-missing +Severity: warning +Check: menu-format +Explanation: The given icon file was not found. + . + If the path to the icon that is listed in the menu file is absolute, + make sure that your package also installs the icon at that path. + . + If the path is just a filename or otherwise a relative path, make sure + the icon is being installed in <code>/usr/share/pixmaps</code>, which + is the default location. + . + If the icon is provided by another package on which this package + depends, Lintian may not be able to determine if the icon is + available. In that case, please override this tag. +See-Also: + menu-manual 3.7 diff --git a/tags/m/menu-icon-not-in-xpm-format.tag b/tags/m/menu-icon-not-in-xpm-format.tag new file mode 100644 index 0000000..9f08f29 --- /dev/null +++ b/tags/m/menu-icon-not-in-xpm-format.tag @@ -0,0 +1,14 @@ +Tag: menu-icon-not-in-xpm-format +Severity: error +Check: menu-format +Explanation: The named icon is not in XPM format. + . + Icons in the Debian menu system should be in XPM format. + . + While other image types such as PNG seem to work as well, window managers + are not required to support them. + . + Using such non-XPM icons could break interoperability. +See-Also: + menu-manual 3.7, + Bug#591812 diff --git a/tags/m/menu-icon-too-big.tag b/tags/m/menu-icon-too-big.tag new file mode 100644 index 0000000..a2ad1de --- /dev/null +++ b/tags/m/menu-icon-too-big.tag @@ -0,0 +1,10 @@ +Tag: menu-icon-too-big +Severity: error +Check: menu-format +Explanation: Icons in the Debian <code>menu</code> system should be at most 32x32 + pixels in size. + . + Sometimes the size is even reflected in the icon name. For example, + <code>icon16x16</code> should be no larger than 16x16 pixels. +See-Also: + menu-manual 3.7 diff --git a/tags/m/menu-icon-uses-relative-path.tag b/tags/m/menu-icon-uses-relative-path.tag new file mode 100644 index 0000000..9869150 --- /dev/null +++ b/tags/m/menu-icon-uses-relative-path.tag @@ -0,0 +1,10 @@ +Tag: menu-icon-uses-relative-path +Severity: warning +Check: menu-format +Explanation: This package contains a <code>menu</code> file that refers to an icon + via a relative path. + . + Icons should be referenced by their absolute paths. +See-Also: + menu-manual 3.2, + Bug#693477 diff --git a/tags/m/menu-item-contains-unknown-tag.tag b/tags/m/menu-item-contains-unknown-tag.tag new file mode 100644 index 0000000..cec2470 --- /dev/null +++ b/tags/m/menu-item-contains-unknown-tag.tag @@ -0,0 +1,10 @@ +Tag: menu-item-contains-unknown-tag +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a line with a tag that is not + a standard tags, such as <code>needs=</code>, <code>section=</code>, + <code>title=</code>, <code>longtitle=</code>, or <code>command=</code> + etc. + . + While other tags can be used, it is rare. More commonly, the tag name was + misspelled. diff --git a/tags/m/menu-item-creates-new-root-section.tag b/tags/m/menu-item-creates-new-root-section.tag new file mode 100644 index 0000000..3500c37 --- /dev/null +++ b/tags/m/menu-item-creates-new-root-section.tag @@ -0,0 +1,8 @@ +Tag: menu-item-creates-new-root-section +Severity: error +Check: menu-format +Explanation: The <code>menu</code> item has a line that specifies a new menu section + in the root menu. + . + The addition of new sections at the root level should be cleared with the author + of <code>menu</code>. diff --git a/tags/m/menu-item-creates-new-section.tag b/tags/m/menu-item-creates-new-section.tag new file mode 100644 index 0000000..c34f6a7 --- /dev/null +++ b/tags/m/menu-item-creates-new-section.tag @@ -0,0 +1,11 @@ +Tag: menu-item-creates-new-section +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a line specifying an unknown + section, or it uses a section intended only as a menu root item that + applications should not use directly. + . + The section could be misspelled. Otherwise, please check the section + against the list of valid names in the menu policy. +See-Also: + menu-policy 2.1 diff --git a/tags/m/menu-item-missing-required-tag.tag b/tags/m/menu-item-missing-required-tag.tag new file mode 100644 index 0000000..1c6b9fe --- /dev/null +++ b/tags/m/menu-item-missing-required-tag.tag @@ -0,0 +1,9 @@ +Tag: menu-item-missing-required-tag +Severity: error +Check: menu-format +Explanation: A line in the given <code>menu</code> item is missing a + required tag. + . + Without the tag, the line probably has no effect whatsoever, except + <code>install-menu</code> may report an error during package + installation. diff --git a/tags/m/menu-item-needs-dwww.tag b/tags/m/menu-item-needs-dwww.tag new file mode 100644 index 0000000..09500be --- /dev/null +++ b/tags/m/menu-item-needs-dwww.tag @@ -0,0 +1,7 @@ +Tag: menu-item-needs-dwww +Severity: warning +Check: menu-format +Explanation: The menu item has <code>needs=dwww</code>, but that is deprecated. Please + register your documentation with <code>doc-base</code>. + . + The <code>dwww</code> entries will be generated automatically. diff --git a/tags/m/menu-item-needs-tag-has-unknown-value.tag b/tags/m/menu-item-needs-tag-has-unknown-value.tag new file mode 100644 index 0000000..95e9a0d --- /dev/null +++ b/tags/m/menu-item-needs-tag-has-unknown-value.tag @@ -0,0 +1,8 @@ +Tag: menu-item-needs-tag-has-unknown-value +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a strange value in a <code>needs=</code> + field. + . + It is possible the value is intentional. More than likely, however, there was + a typo that will cause <code>menu</code> to ignore the line. diff --git a/tags/m/menu-item-uses-apps-games-section.tag b/tags/m/menu-item-uses-apps-games-section.tag new file mode 100644 index 0000000..546331c --- /dev/null +++ b/tags/m/menu-item-uses-apps-games-section.tag @@ -0,0 +1,8 @@ +Tag: menu-item-uses-apps-games-section +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a line specifying a section under + <code>Apps/Games</code>. That section was renamed. It is now just called + <code>Games</code>. +See-Also: + menu-policy 2.1 diff --git a/tags/m/menu-item-uses-apps-section.tag b/tags/m/menu-item-uses-apps-section.tag new file mode 100644 index 0000000..309bc0e --- /dev/null +++ b/tags/m/menu-item-uses-apps-section.tag @@ -0,0 +1,8 @@ +Tag: menu-item-uses-apps-section +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a line specifying a section under + <code>Apps</code>. That section was renamed. It is now called + <code>Applications</code>. +See-Also: + menu-policy 2.1 diff --git a/tags/m/menu-item-uses-icon-none.tag b/tags/m/menu-item-uses-icon-none.tag new file mode 100644 index 0000000..387a8ef --- /dev/null +++ b/tags/m/menu-item-uses-icon-none.tag @@ -0,0 +1,6 @@ +Tag: menu-item-uses-icon-none +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a line that uses <code>icon=none</code>. + It is redundant and deprecated. If there is no icon, just leave off the + <code>icon</code> tag. diff --git a/tags/m/menu-item-uses-windowmanagers-section.tag b/tags/m/menu-item-uses-windowmanagers-section.tag new file mode 100644 index 0000000..7b48b7f --- /dev/null +++ b/tags/m/menu-item-uses-windowmanagers-section.tag @@ -0,0 +1,8 @@ +Tag: menu-item-uses-windowmanagers-section +Severity: warning +Check: menu-format +Explanation: The <code>menu</code> item has a line specifying a section under + <code>WindowManagers</code>. That section was renamed. It is now called + <code>Window Managers</code>. +See-Also: + menu-policy 2.1 diff --git a/tags/m/menu-method-lacks-include.tag b/tags/m/menu-method-lacks-include.tag new file mode 100644 index 0000000..7d94744 --- /dev/null +++ b/tags/m/menu-method-lacks-include.tag @@ -0,0 +1,12 @@ +Tag: menu-method-lacks-include +Severity: error +Check: menus +Renamed-From: + menu-method-should-include-menu-h +Explanation: A <code>menu-method</code> file must include the <code>menu.h</code> + configuration file, like so: + . + (using "!include menu.h"). +See-Also: + menu-manual 5, + http://www.tldp.org/HOWTO/NCURSES-Programming-HOWTO/menus.html diff --git a/tags/m/mismatch-translated-choices.tag b/tags/m/mismatch-translated-choices.tag new file mode 100644 index 0000000..f249587 --- /dev/null +++ b/tags/m/mismatch-translated-choices.tag @@ -0,0 +1,12 @@ +Tag: mismatch-translated-choices +Severity: error +Check: debian/debconf +Explanation: A "Choices:" field is a comma separated list, and translated + "Choices:" fields must have the exact same number of elements. One + of the translations does not follow this rule, you should contact the + translator and request for a new translation where elements of "Choices:" + fields have no embedded commas. + . + Cdebconf understands escaped commas in such fields, but packages + outside the scope of debian-installer must not have them until they are + also supported by debconf. diff --git a/tags/m/mismatched-override.tag b/tags/m/mismatched-override.tag new file mode 100644 index 0000000..9adb9b1 --- /dev/null +++ b/tags/m/mismatched-override.tag @@ -0,0 +1,15 @@ +Tag: mismatched-override +Severity: warning +Show-Always: yes +Check: lintian +Explanation: The named tag would have been silenced except the context + specified with the override did not match. + . + Lintian may now provide a different context for the tag, or something + could have changed in a new version of your package. Either way, + overrides work best when you require as little context as needed. + . + You can use wildcards, such as * or ? in the context to + make a match more likely. + . + Please remove or adjust the override. diff --git a/tags/m/mismatched-python-substvar.tag b/tags/m/mismatched-python-substvar.tag new file mode 100644 index 0000000..98cd69f --- /dev/null +++ b/tags/m/mismatched-python-substvar.tag @@ -0,0 +1,8 @@ +Tag: mismatched-python-substvar +Severity: warning +Check: languages/python +Explanation: The specified package declares a dependency on <code>${python:Depends}</code> + whilst appearing to be a Python 3.x package or a dependency on + <code>${python3:Depends}</code> when it appears to be a package for Python 2.x. + . + Please adjust the substvar to match the intended Python version. diff --git a/tags/m/misnamed-po-file.tag b/tags/m/misnamed-po-file.tag new file mode 100644 index 0000000..45333f7 --- /dev/null +++ b/tags/m/misnamed-po-file.tag @@ -0,0 +1,13 @@ +Tag: misnamed-po-file +Severity: warning +Check: debian/po-debconf +Explanation: The name of this PO file doesn't appear to be a valid language + code. Any files in <code>debian/po</code> ending in <code>.po</code> will be + processed as translations by po2debconf for the language code equal to + the file name without the trailing <code>.po</code>. If the file name does + not correctly reflect the language of the translation, the translation + will not be accessible to users of that language. + . + If this file isn't actually a PO file, rename it to something that + doesn't end in <code>.po</code> or move it to another directory so that + translation merging programs will not be confused. diff --git a/tags/m/misplaced-extra-member-in-deb.tag b/tags/m/misplaced-extra-member-in-deb.tag new file mode 100644 index 0000000..94edf61 --- /dev/null +++ b/tags/m/misplaced-extra-member-in-deb.tag @@ -0,0 +1,6 @@ +Tag: misplaced-extra-member-in-deb +Severity: error +Check: deb-format +Explanation: The binary package contains an extra member that Lintian did not + expect or expected at a different position. +See-Also: deb(5) diff --git a/tags/m/misplaced-systemd-tmpfiles.tag b/tags/m/misplaced-systemd-tmpfiles.tag new file mode 100644 index 0000000..8cd4af4 --- /dev/null +++ b/tags/m/misplaced-systemd-tmpfiles.tag @@ -0,0 +1,7 @@ +Tag: misplaced-systemd-tmpfiles +Severity: error +Check: systemd/tmpfiles +Renamed-from: + systemd-tmpfiles.d-outside-usr-lib +Explanation: The package ships a systemd tmpfiles.d(5) conf file outside + <code>/usr/lib/tmpfiles.d/</code> diff --git a/tags/m/missing-build-dependency-for-dh-addon.tag b/tags/m/missing-build-dependency-for-dh-addon.tag new file mode 100644 index 0000000..ee1b627 --- /dev/null +++ b/tags/m/missing-build-dependency-for-dh-addon.tag @@ -0,0 +1,6 @@ +Tag: missing-build-dependency-for-dh-addon +Severity: error +Check: debhelper +Explanation: The source package appears to be using a dh addon but doesn't build + depend on the package that actually provides it. If it uses it, it must + build depend on it. diff --git a/tags/m/missing-build-dependency-for-dh_-command.tag b/tags/m/missing-build-dependency-for-dh_-command.tag new file mode 100644 index 0000000..ae59ea2 --- /dev/null +++ b/tags/m/missing-build-dependency-for-dh_-command.tag @@ -0,0 +1,6 @@ +Tag: missing-build-dependency-for-dh_-command +Severity: error +Check: debhelper +Explanation: The source package appears to be using a dh_ command but doesn't build + depend on the package that actually provides it. If it uses it, it must + build depend on it. diff --git a/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag b/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag new file mode 100644 index 0000000..d6668de --- /dev/null +++ b/tags/m/missing-build-depends-for-clean-target-in-debian-rules.tag @@ -0,0 +1,18 @@ +Tag: missing-build-depends-for-clean-target-in-debian-rules +Severity: error +Check: debian/rules +Renamed-From: + clean-should-be-satisfied-by-build-depends +Explanation: The specified condition must be satisfied to run the <code>clean</code> + target in <code>debian/rules</code>. + . + Please add a suitable prerequisite to <code>Build-Depends</code> (and not + <code>Build-Depends-Indep</code>) even if no architecture-dependent packages + are being built. + . + The condition you see in the context is not a recommendation on what to add. If + you see a list, more than likely only one member is needed to make this tag go + away. You probably also do not need the <code>:any</code> multiarch qualifier, + if you see one. +See-Also: + debian-policy 7.7 diff --git a/tags/m/missing-built-using-field-for-golang-package.tag b/tags/m/missing-built-using-field-for-golang-package.tag new file mode 100644 index 0000000..6460424 --- /dev/null +++ b/tags/m/missing-built-using-field-for-golang-package.tag @@ -0,0 +1,14 @@ +Tag: missing-built-using-field-for-golang-package +Severity: info +Check: languages/golang/built-using +Explanation: The stanza for a Golang installation package in the + <code>debian/control</code> file does not include a + <code>Built-Using</code> field that contains the <code>${misc:Built-Using}</code> + substitution variable. + . + The <code>dh-golang(1)</code> build system provides the <code>${misc:Built-Using}</code> + variable. It is used when scheduling binNMUs. + . + Please add the following line to the relevant stanza: + . + <code>Built-Using: ${misc:Built-Using}</code> diff --git a/tags/m/missing-call-to-dpkg-maintscript-helper.tag b/tags/m/missing-call-to-dpkg-maintscript-helper.tag new file mode 100644 index 0000000..10c291b --- /dev/null +++ b/tags/m/missing-call-to-dpkg-maintscript-helper.tag @@ -0,0 +1,8 @@ +Tag: missing-call-to-dpkg-maintscript-helper +Severity: error +Check: maintainer-scripts/helper/dpkg +Explanation: The maintainer script is missing a call to the specified + <code>dpkg-maintscript-helper</code> command. The uses are coordinated + and need each other. +See-Also: + dpkg-maintscript-helper(1) diff --git a/tags/m/missing-call-to-update-fonts.tag b/tags/m/missing-call-to-update-fonts.tag new file mode 100644 index 0000000..757b66b --- /dev/null +++ b/tags/m/missing-call-to-update-fonts.tag @@ -0,0 +1,11 @@ +Tag: missing-call-to-update-fonts +Severity: warning +Check: desktop/x11/font/update +Explanation: The named maintainer script ships the specified X11 font but does + not appear to call <code>update-fonts-scale</code> or <code>update-fonts-dir</code> + in its <code>postinst</code> script. + . + If you are using <code>dh_installxfonts</code>, add <code>${misc:Depends}</code> + as a prerequisite and <code>dh_installxfonts</code> will take care of it for you. +See-Also: + https://lists.debian.org/msgid-search/CAJqvfD-A1EPXxF_mS=_BaQ0FtqygVwRUf+23WqSqrkSmYgVAtA@mail.gmail.com diff --git a/tags/m/missing-conffile.tag b/tags/m/missing-conffile.tag new file mode 100644 index 0000000..571bd64 --- /dev/null +++ b/tags/m/missing-conffile.tag @@ -0,0 +1,12 @@ +Tag: missing-conffile +Severity: error +Check: conffiles +Renamed-From: conffile-is-not-in-package +Explanation: The conffiles control file lists this path, but the path does + not appear to exist in the package. Lintian may also emit this tag + when the file exists, but the canonical name is used in the + "conffiles" control file (e.g. if a parent segment are symlinks). + . + Note that dpkg and Lintian strips all whitespace from the right hand + side of each line. Thus it is not possible for a file ending with + trailing whitespace to be marked as a conffile. diff --git a/tags/m/missing-debconf-dependency-for-preinst.tag b/tags/m/missing-debconf-dependency-for-preinst.tag new file mode 100644 index 0000000..998942f --- /dev/null +++ b/tags/m/missing-debconf-dependency-for-preinst.tag @@ -0,0 +1,8 @@ +Tag: missing-debconf-dependency-for-preinst +Severity: warning +Check: debian/debconf +Explanation: Packages using debconf in their preinst scripts must pre-depend + on debconf. + . + Since debconf is usually installed already, that is better than + depending on it but falling back to a different configuration system. diff --git a/tags/m/missing-debconf-dependency.tag b/tags/m/missing-debconf-dependency.tag new file mode 100644 index 0000000..f7be858 --- /dev/null +++ b/tags/m/missing-debconf-dependency.tag @@ -0,0 +1,5 @@ +Tag: missing-debconf-dependency +Severity: warning +Check: debian/debconf +Explanation: Packages using debconf should depend on it, since debconf is not an + essential package. diff --git a/tags/m/missing-debian-source-format.tag b/tags/m/missing-debian-source-format.tag new file mode 100644 index 0000000..1f0739e --- /dev/null +++ b/tags/m/missing-debian-source-format.tag @@ -0,0 +1,19 @@ +Tag: missing-debian-source-format +Severity: warning +Check: debian/source-dir +Explanation: Explicitly selecting a source format by putting the format in + <code>debian/source/format</code> is recommended. This allows for + future removal of the 1.0 default for the package source format and, + depending on the source format, may allow unambiguous declaration of + whether this package is native or non-native. + . + If you don't have a reason to stay with the old format for this package, + please consider switching to "3.0 (quilt)" (for packages with a separate + upstream tarball) or to "3.0 (native)" (for Debian native packages). + . + If you wish to keep using the old format, please create that file and put + "1.0" in it to be explicit about the source package version. If you have + problems with the 3.0 format, the dpkg maintainers are interested in + hearing, at debian-dpkg@lists.debian.org, the (technical) reasons why the + new formats do not suit you. +See-Also: dpkg-source(1), https://wiki.debian.org/Projects/DebSrc3.0 diff --git a/tags/m/missing-debian-watch-file-standard.tag b/tags/m/missing-debian-watch-file-standard.tag new file mode 100644 index 0000000..1cca43f --- /dev/null +++ b/tags/m/missing-debian-watch-file-standard.tag @@ -0,0 +1,11 @@ +Tag: missing-debian-watch-file-standard +Severity: warning +Check: debian/watch/standard +Renamed-From: + debian-watch-file-missing-version +Explanation: The <code>debian/watch</code> file in this package doesn't start a + <code>version=</code> line. The first non-comment line of + <code>debian/watch</code> should be a <code>version=</code> declaration. This + may mean that this is an old version one watch file that should be + updated to the current version. +See-Also: uscan(1) diff --git a/tags/m/missing-dep-for-interpreter.tag b/tags/m/missing-dep-for-interpreter.tag new file mode 100644 index 0000000..d948e24 --- /dev/null +++ b/tags/m/missing-dep-for-interpreter.tag @@ -0,0 +1,9 @@ +Tag: missing-dep-for-interpreter +Severity: error +Check: scripts +Explanation: You used an interpreter for a script that is not in an essential + package. In most cases, you will need to add a Dependency on the + package that contains the interpreter. + . + In some cases a weaker relationship, such as Suggests or Recommends, will + be more appropriate. diff --git a/tags/m/missing-dep-on-jarwrapper.tag b/tags/m/missing-dep-on-jarwrapper.tag new file mode 100644 index 0000000..98914f7 --- /dev/null +++ b/tags/m/missing-dep-on-jarwrapper.tag @@ -0,0 +1,6 @@ +Tag: missing-dep-on-jarwrapper +Severity: error +Check: languages/java +See-Also: java-policy 2.2 +Explanation: Packages containing an executable JAR must depend on jarwrapper or + other packages providing similar functionalities. diff --git a/tags/m/missing-dependency-on-libc.tag b/tags/m/missing-dependency-on-libc.tag new file mode 100644 index 0000000..f1eb346 --- /dev/null +++ b/tags/m/missing-dependency-on-libc.tag @@ -0,0 +1,15 @@ +Tag: missing-dependency-on-libc +Severity: error +Check: binaries/prerequisites +Explanation: The listed file appears to be linked against the C library, but the + package doesn't depend on the C library package. Normally this indicates + that ${shlibs:Depends} was omitted from the Depends line for this package + in <code>debian/control</code>. + . + All shared libraries and compiled binaries must be run through + dpkg-shlibdeps to find out any libraries they are linked against (often + via the dh_shlibdeps debhelper command). The package containing these + files must then depend on ${shlibs:Depends} in <code>debian/control</code> to + get the proper package dependencies for those libraries. +See-Also: + debian-policy 8.6.1 diff --git a/tags/m/missing-dependency-on-libstdc++.tag b/tags/m/missing-dependency-on-libstdc++.tag new file mode 100644 index 0000000..1d4bc01 --- /dev/null +++ b/tags/m/missing-dependency-on-libstdc++.tag @@ -0,0 +1,16 @@ +Tag: missing-dependency-on-libstdc++ +Severity: error +Check: binaries/prerequisites +Experimental: yes +Explanation: The listed file appears to be linked against the C++ library, but the + package doesn't depend on the C++ library package. Normally this indicates + that ${shlibs:Depends} was omitted from the Depends line for this package + in <code>debian/control</code>. + . + All shared libraries and compiled binaries must be run through + dpkg-shlibdeps to find out any libraries they are linked against (often + via the dh_shlibdeps debhelper command). The package containing these + files must then depend on ${shlibs:Depends} in <code>debian/control</code> to + get the proper package dependencies for those libraries. +See-Also: + debian-policy 8.6.1 diff --git a/tags/m/missing-dependency-on-numpy-abi.tag b/tags/m/missing-dependency-on-numpy-abi.tag new file mode 100644 index 0000000..5eb1424 --- /dev/null +++ b/tags/m/missing-dependency-on-numpy-abi.tag @@ -0,0 +1,9 @@ +Tag: missing-dependency-on-numpy-abi +Severity: error +Check: binaries/prerequisites/numpy +Explanation: This package includes a Python extension module, which uses Numpy via its + binary interface. Such packages must depend on python3-numpy-abi*N*. + . + If the package is using debhelper, this problem is usually due to a + missing dh_numpy3 call in <code>debian/rules</code>. +See-Also: /usr/share/doc/python3-numpy/README.DebianMaints diff --git a/tags/m/missing-dependency-on-perlapi.tag b/tags/m/missing-dependency-on-perlapi.tag new file mode 100644 index 0000000..354f29c --- /dev/null +++ b/tags/m/missing-dependency-on-perlapi.tag @@ -0,0 +1,11 @@ +Tag: missing-dependency-on-perlapi +Severity: error +Check: binaries/prerequisites/perl +Explanation: This package includes a *.so file in <code>/usr/lib/.../perl5</code>, + normally indicating that it includes a binary Perl module. Binary Perl + modules must depend on perlapi-$Config{version} (from the Config module). + If the package is using debhelper, this problem is usually due to a + missing dh_perl call in <code>debian/rules</code> or a missing + ${perl:Depends} substitution variable in the Depends line in + <code>debian/control</code>. +See-Also: perl-policy 4.4.2 diff --git a/tags/m/missing-dependency-on-phpapi.tag b/tags/m/missing-dependency-on-phpapi.tag new file mode 100644 index 0000000..de6b8ab --- /dev/null +++ b/tags/m/missing-dependency-on-phpapi.tag @@ -0,0 +1,15 @@ +Tag: missing-dependency-on-phpapi +Severity: error +Check: binaries/prerequisites/php +Explanation: This package includes a *.so file in <code>/usr/lib/phpN</code> + (where N is a number representing the major PHP version), normally + indicating that it includes a PHP extension. PHP extensions must + depend on phpapi-$(php-configN --phpapi), without adding an + alternative package with the OR operator. + . + This can usually be achieved by, for example, adding the following + code to the binary-arch target of the rules file and adding + <code>${php:Depends}</code> to the <code>Depends</code> field of the binary + package shipping the extension: + . + echo "php:Depends=phpapi-$(php-config5 --phpapi)" > debian/substvars diff --git a/tags/m/missing-depends-on-sensible-utils.tag b/tags/m/missing-depends-on-sensible-utils.tag new file mode 100644 index 0000000..73ae3d2 --- /dev/null +++ b/tags/m/missing-depends-on-sensible-utils.tag @@ -0,0 +1,14 @@ +Tag: missing-depends-on-sensible-utils +Severity: error +Check: files/contents +Explanation: The listed file appears to use one or more of the binaries + in <code>sensible-utils</code> but no binary declares a dependency for + this package. + . + As part of the transition to split <code>sensible-utils</code> and + <code>debianutils</code>, the remaining <code>Depends</code> from + <code>debianutils</code> was removed in version 4.8.2. + . + In most cases you will need to add a <code>Depends</code>, + <code>Recommends</code>, <code>Pre-Depends</code> or <code>Suggests</code> + on <code>sensible-utils</code>. diff --git a/tags/m/missing-explanation-for-contrib-or-non-free-package.tag b/tags/m/missing-explanation-for-contrib-or-non-free-package.tag new file mode 100644 index 0000000..30ef5a3 --- /dev/null +++ b/tags/m/missing-explanation-for-contrib-or-non-free-package.tag @@ -0,0 +1,10 @@ +Tag: missing-explanation-for-contrib-or-non-free-package +Severity: info +Check: debian/copyright/dep5 +Explanation: The specified package is in the contrib or non-free archive + area but does not include a "Comment" (or "Disclaimer") field in + its copyright file. + . + Please add a brief comment why this package cannot be part of the + main Debian distribution. +See-Also: debian-policy 12.5 diff --git a/tags/m/missing-explanation-for-repacked-upstream-tarball.tag b/tags/m/missing-explanation-for-repacked-upstream-tarball.tag new file mode 100644 index 0000000..edb4a30 --- /dev/null +++ b/tags/m/missing-explanation-for-repacked-upstream-tarball.tag @@ -0,0 +1,10 @@ +Tag: missing-explanation-for-repacked-upstream-tarball +Severity: info +Check: debian/copyright/dep5 +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, but there is no "Comment" or "Files-Excluded" + field in its copyright file which explains the reason why. + . + Please add a comment why this tarball was repacked or add a suitable + "Files-Excluded" field. diff --git a/tags/m/missing-field-in-dep5-copyright.tag b/tags/m/missing-field-in-dep5-copyright.tag new file mode 100644 index 0000000..80a3520 --- /dev/null +++ b/tags/m/missing-field-in-dep5-copyright.tag @@ -0,0 +1,6 @@ +Tag: missing-field-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Explanation: The paragraph in the machine readable copyright file is missing a field + that is required by the specification. diff --git a/tags/m/missing-file-from-potfiles-in.tag b/tags/m/missing-file-from-potfiles-in.tag new file mode 100644 index 0000000..e10b4d1 --- /dev/null +++ b/tags/m/missing-file-from-potfiles-in.tag @@ -0,0 +1,6 @@ +Tag: missing-file-from-potfiles-in +Severity: warning +Check: debian/po-debconf +Explanation: A file listed in <code>debian/po/POTFILES.in</code> could not be found + in the source package. +See-Also: po-debconf(7) diff --git a/tags/m/missing-intermediate-directory.tag b/tags/m/missing-intermediate-directory.tag new file mode 100644 index 0000000..dc40dbd --- /dev/null +++ b/tags/m/missing-intermediate-directory.tag @@ -0,0 +1,7 @@ +Tag: missing-intermediate-directory +Severity: warning +Check: files/missing +Explanation: The package contains files in the listed directory, but does + not contain the actual directory itself. Some tools do not cope + very well with this case. Notably Lintian prior to 2.5.32 would + crash on such packages. diff --git a/tags/m/missing-license-paragraph-in-dep5-copyright.tag b/tags/m/missing-license-paragraph-in-dep5-copyright.tag new file mode 100644 index 0000000..451e174 --- /dev/null +++ b/tags/m/missing-license-paragraph-in-dep5-copyright.tag @@ -0,0 +1,12 @@ +Tag: missing-license-paragraph-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +Explanation: The <code>Files</code> paragraph in the machine readable copyright file + references a license for which no stand-alone <code>License</code> paragraph + exists. + . + Sometimes this tag appears because of incorrect ordering. Stand-alone + <code>License</code> paragraphs must appear *after* all <code>Files</code> + paragraphs. +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/, + Bug#959067 diff --git a/tags/m/missing-license-text-in-dep5-copyright.tag b/tags/m/missing-license-text-in-dep5-copyright.tag new file mode 100644 index 0000000..20e85b9 --- /dev/null +++ b/tags/m/missing-license-text-in-dep5-copyright.tag @@ -0,0 +1,6 @@ +Tag: missing-license-text-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Explanation: The standalone “License” paragraph contains only short license + name, but not the license text. diff --git a/tags/m/missing-manifest.tag b/tags/m/missing-manifest.tag new file mode 100644 index 0000000..2785bbb --- /dev/null +++ b/tags/m/missing-manifest.tag @@ -0,0 +1,5 @@ +Tag: missing-manifest +Severity: info +Check: languages/java +Explanation: The jar file contains .class files but no manifest. This may + indicate a build misconfiguration. diff --git a/tags/m/missing-notice-file-for-apache-license.tag b/tags/m/missing-notice-file-for-apache-license.tag new file mode 100644 index 0000000..56864fc --- /dev/null +++ b/tags/m/missing-notice-file-for-apache-license.tag @@ -0,0 +1,18 @@ +Tag: missing-notice-file-for-apache-license +Severity: error +Check: debian/copyright/apache-notice +Explanation: The package appears to be licensed under the Apache 2.0 license and + a <code>NOTICE</code> file (or similar) exists in the source tree. However, no + files called <code>NOTICE</code> or <code>NOTICE.txt</code> are installed in any + of the binary packages. + . + The Apache 2.0 license requires distributing of such files: + . + (d) If the Work includes a "NOTICE" text file as part of its + distribution, then any Derivative Works that You distribute must + include a readable copy of the attribution notices contained + within such NOTICE file [..] + . + Please include the file in your package, for example by adding + <code>path/to/NOTICE</code> to a <code>debian/package.docs</code> file. +See-Also: /usr/share/common-licenses/Apache-2.0 diff --git a/tags/m/missing-pkg-php-tools-addon.tag b/tags/m/missing-pkg-php-tools-addon.tag new file mode 100644 index 0000000..dac8919 --- /dev/null +++ b/tags/m/missing-pkg-php-tools-addon.tag @@ -0,0 +1,10 @@ +Tag: missing-pkg-php-tools-addon +Severity: warning +Check: languages/php/pear +Explanation: The package uses pkg-php-tools but dh command is called without + --with phppear or --with phpcomposer. A PECL package should also have + --with php. + . + pkg-php-tools db addons are the recommended tool for building PHP PEAR or + Composer packages. For more information, install it and read the included + README.PEAR or README.Composer. diff --git a/tags/m/missing-pkg-php-tools-buildsystem.tag b/tags/m/missing-pkg-php-tools-buildsystem.tag new file mode 100644 index 0000000..5b488f1 --- /dev/null +++ b/tags/m/missing-pkg-php-tools-buildsystem.tag @@ -0,0 +1,8 @@ +Tag: missing-pkg-php-tools-buildsystem +Severity: warning +Check: languages/php/pear +Explanation: The package uses pkg-php-tools but dh command is called without + --buildsystem=phppear + . + pkg-php-tools build system is the recommended tool for building PHP PEAR + packages. For more information, install it and read the included README.PEAR. diff --git a/tags/m/missing-potfiles-in.tag b/tags/m/missing-potfiles-in.tag new file mode 100644 index 0000000..136e0ba --- /dev/null +++ b/tags/m/missing-potfiles-in.tag @@ -0,0 +1,6 @@ +Tag: missing-potfiles-in +Severity: warning +Check: debian/po-debconf +Explanation: The required file <code>POTFILES.in</code> is missing from + <code>debian/po</code>. +See-Also: po-debconf(7) diff --git a/tags/m/missing-prerequisite-for-gfortran-module.tag b/tags/m/missing-prerequisite-for-gfortran-module.tag new file mode 100644 index 0000000..22dd98d --- /dev/null +++ b/tags/m/missing-prerequisite-for-gfortran-module.tag @@ -0,0 +1,9 @@ +Tag: missing-prerequisite-for-gfortran-module +Severity: warning +Check: languages/fortran/gfortran +Explanation: The installation package ships a GFORTRAN module but does not depend + on gfortran-mod-<n>, where <n> is the module version (e.g. gfortran-mod-14 + for modules built using GCC 5). +See-Also: Bug#796352, + Bug#714730, + https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff --git a/tags/m/missing-prerequisite-for-pyproject-backend.tag b/tags/m/missing-prerequisite-for-pyproject-backend.tag new file mode 100644 index 0000000..fbeb4b8 --- /dev/null +++ b/tags/m/missing-prerequisite-for-pyproject-backend.tag @@ -0,0 +1,14 @@ +Tag: missing-prerequisite-for-pyproject-backend +Severity: info +Check: languages/python +Explanation: <code>pybuild</code> now supports building with PEP-517 standard + interfaces natively. These sources could be built using <code>pybuild</code>'s + generic <code>pyproject</code> plugin and the named build backend. + . + Please declare both named prerequisites in <code>Build-Depends</code>. You will + need both the generic <code>pybuild-plugin-pyproject</code> as well as the + specific one to the named backend. It is usually <code>python3-${backend}</code>. + . + No changes are required if you are using <code>pybuild</code>'s dedicated + <code>flit</code> plugin, although that plugin will eventually be deprecated in + favor of the generic <code>pyproject</code> plugin mentioned above. diff --git a/tags/m/missing-runtime-test-file.tag b/tags/m/missing-runtime-test-file.tag new file mode 100644 index 0000000..14f4e3e --- /dev/null +++ b/tags/m/missing-runtime-test-file.tag @@ -0,0 +1,6 @@ +Tag: missing-runtime-test-file +Severity: warning +Check: testsuite +Explanation: A test file listed in the debian/tests/control file does not + exist in the package source. +See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff --git a/tags/m/missing-separator-between-items.tag b/tags/m/missing-separator-between-items.tag new file mode 100644 index 0000000..a45486a --- /dev/null +++ b/tags/m/missing-separator-between-items.tag @@ -0,0 +1,7 @@ +Tag: missing-separator-between-items +Severity: error +Check: debian/control/field/relation +Explanation: The named field in the <code>debian/control</code> file is supposed to + list items that are separated by commas or pipes. A separator seems to be missing. + . + Needless to say, it can lead to bogus or incomplete package relationships. diff --git a/tags/m/missing-systemd-service-for-init.d-rcS-script.tag b/tags/m/missing-systemd-service-for-init.d-rcS-script.tag new file mode 100644 index 0000000..fd8c466 --- /dev/null +++ b/tags/m/missing-systemd-service-for-init.d-rcS-script.tag @@ -0,0 +1,15 @@ +Tag: missing-systemd-service-for-init.d-rcS-script +Severity: error +Check: systemd +See-Also: https://wiki.debian.org/Teams/pkg-systemd/rcSMigration +Explanation: The rcS init.d script has no systemd equivalent. + . + Systemd has a SysV init.d script compatibility mode. It provides access to + each SysV init.d script as long as there is no native service file with the + same name (e.g. <code>/lib/systemd/system/rsyslog.service</code> corresponds to + <code>/etc/init.d/rsyslog</code>). + . + Services in rcS.d are particularly problematic, because they often cause + dependency loops, as they are ordered very early in the boot sequence. +Renamed-From: + systemd-no-service-for-init-rcS-script diff --git a/tags/m/missing-systemd-service-for-init.d-script.tag b/tags/m/missing-systemd-service-for-init.d-script.tag new file mode 100644 index 0000000..30a8d8f --- /dev/null +++ b/tags/m/missing-systemd-service-for-init.d-script.tag @@ -0,0 +1,11 @@ +Tag: missing-systemd-service-for-init.d-script +Severity: warning +Check: systemd +Explanation: The specified init.d script has no equivalent systemd service. + . + Whilst systemd has a SysV init.d script compatibility mode, providing + native systemd support has many advantages such as being able to specify + security hardening features. Moreover, the systemd SysV generator will be + deprecated in the future. + . + Please provide a suitable .service file for this script. diff --git a/tags/m/missing-systemd-timer-for-cron-script.tag b/tags/m/missing-systemd-timer-for-cron-script.tag new file mode 100644 index 0000000..5da8fdc --- /dev/null +++ b/tags/m/missing-systemd-timer-for-cron-script.tag @@ -0,0 +1,16 @@ +Tag: missing-systemd-timer-for-cron-script +Severity: warning +Check: systemd +Explanation: This package ships the specified cron script but does not ship a + equivalent systemd <code>.timer</code> unit. + . + The "desktop" and "laptop" tasks no longer pull in anacron(8), the + usual solution for desktop installations that are not running all the + time. + . + Please consider shipping an equivalent <code>.timer</code> file for this + script. +See-Also: + systemd.timer(5), + anacron(8), + Bug#1007257 diff --git a/tags/m/missing-templates-pot.tag b/tags/m/missing-templates-pot.tag new file mode 100644 index 0000000..98cb0f4 --- /dev/null +++ b/tags/m/missing-templates-pot.tag @@ -0,0 +1,6 @@ +Tag: missing-templates-pot +Severity: warning +Check: debian/po-debconf +Explanation: The required file <code>templates.pot</code> is missing from + <code>debian/po</code>. +See-Also: po-debconf(7) diff --git a/tags/m/missing-tests-control.tag b/tags/m/missing-tests-control.tag new file mode 100644 index 0000000..cc7ee84 --- /dev/null +++ b/tags/m/missing-tests-control.tag @@ -0,0 +1,11 @@ +Tag: missing-tests-control +Severity: error +Check: testsuite +Renamed-From: + testsuite-autopkgtest-missing +Explanation: The source package declares the generic <code>Testsuite: autopkgtest</code> + field but provides no <code>debian/tests/control</code> file. + . + The control file is not needed when a specialized test suite such as + <code>autopkgtest-pkg-perl</code> is being used. +See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff --git a/tags/m/missing-vcs-browser-field.tag b/tags/m/missing-vcs-browser-field.tag new file mode 100644 index 0000000..8cd50b1 --- /dev/null +++ b/tags/m/missing-vcs-browser-field.tag @@ -0,0 +1,10 @@ +Tag: missing-vcs-browser-field +Severity: info +Check: fields/vcs +Explanation: A Vcs-* field in this package is pointing to a repository that + supports browsing of the repository via a web browser. + . + This is typically a nicer user-experience for developers and avoids + unnecessary and time-consuming clones of the repository. + . + Please add a suitable Vcs-Browser field to the package. diff --git a/tags/m/missing-xs-go-import-path-for-golang-package.tag b/tags/m/missing-xs-go-import-path-for-golang-package.tag new file mode 100644 index 0000000..1a0f3cb --- /dev/null +++ b/tags/m/missing-xs-go-import-path-for-golang-package.tag @@ -0,0 +1,21 @@ +Tag: missing-xs-go-import-path-for-golang-package +Severity: info +Check: languages/golang/import-path +Explanation: This Golang source does not declare a <code>XS-Go-Import-Path</code> + field in the <code>debian/control</code> file.. + . + Many tools like <code>dh-make-golang(1)</code> use the field to resolve + prerequisites correctly. It is also used in the Golang team's CI. + . + When using <code>dh-golang</code>, the field's value should be the same as + <code>DH_GOPKG</code> in <code>debian/rules</code>. The + <code>dh-golang</code> build system then automatically sets <code>DH_GOPKG</code> + to the value from <code>XS-Go-Import-Path</code>. + . + For packages that do not use <code>dh-golang</code>, or for packages whose upstream + does not publish the sources in a way compatible with <code>go get</code> (and hence + does not have a canonical import path) you should use a fake import path. Please + contact the Golang team at for more advice. +See-Also: + https://go-team.pages.debian.net, + https://go-team.pages.debian.net/ci.html. diff --git a/tags/m/misspelled-closes-bug.tag b/tags/m/misspelled-closes-bug.tag new file mode 100644 index 0000000..6e943f7 --- /dev/null +++ b/tags/m/misspelled-closes-bug.tag @@ -0,0 +1,6 @@ +Tag: misspelled-closes-bug +Severity: warning +Check: debian/changelog +See-Also: debian-policy 5.6.22 +Explanation: The last changelog entry uses Close: #123456 instead of correct + Closes: #123456 diff --git a/tags/m/mknod-in-maintainer-script.tag b/tags/m/mknod-in-maintainer-script.tag new file mode 100644 index 0000000..1290c72 --- /dev/null +++ b/tags/m/mknod-in-maintainer-script.tag @@ -0,0 +1,10 @@ +Tag: mknod-in-maintainer-script +Severity: error +Check: maintainer-scripts/mknod +Explanation: Maintainer scripts must not create device files directly. They + should call <code>MAKEDEV</code> instead. + . + If <code>mknod</code> is being used to create a FIFO (named pipe), use + <code>mkfifo</code> instead to avoid triggering this tag. +See-Also: + debian-policy 10.6 diff --git a/tags/m/more-than-one-patch-system.tag b/tags/m/more-than-one-patch-system.tag new file mode 100644 index 0000000..77bf019 --- /dev/null +++ b/tags/m/more-than-one-patch-system.tag @@ -0,0 +1,9 @@ +Tag: more-than-one-patch-system +Severity: warning +Check: debian/patches +Explanation: Either the build-dependencies list more than one patch system or the + package uses the <code>3.0 (quilt)</code> source format but also has a + dependency on <code>dpatch</code>. It's unlikely that you need both patch + systems at the same time, and having multiple patch systems in play + simultaneously can make understanding and modifying the source package + unnecessarily complex. diff --git a/tags/m/multi-arch-same-package-calls-pycompile.tag b/tags/m/multi-arch-same-package-calls-pycompile.tag new file mode 100644 index 0000000..7c85f81 --- /dev/null +++ b/tags/m/multi-arch-same-package-calls-pycompile.tag @@ -0,0 +1,24 @@ +Tag: multi-arch-same-package-calls-pycompile +Severity: warning +Check: scripts +Explanation: This <code>Multi-Arch: same</code> package uses <code>pycompile</code> or + <code>py3compile</code> in the specified maintainer script. + . + <code>py{,3}compile</code> are tools used to byte-compile Python source + files. It is typically run on installation of Debian packages that ship + Python modules. However, they do not support installing several + architectures of the same package and this is not Multi-Arch: safe. + . + If the contents of the package is not architecture dependent, it should + usually be made binary-all. + . + If the contents of the package is architecture dependent, it should + usually get a dependency on the Python interpreter for the same + architecture. This is a dependency in the form of <code>python3</code>, not + an architecture-qualified dependency such as <code>python3:any</code> (which + can be fulfilled by the Python interpreter for any architecture). + . + If a dependency on the Python interpreter for the same architecture + exists (usually generated by <code>dh-python</code>), the + <code>Multi-Arch: same</code> has no effect and should be dropped. +See-Also: pycompile(1), py3compile(1), Bug#812228 diff --git a/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag b/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag new file mode 100644 index 0000000..2e509c8 --- /dev/null +++ b/tags/m/multi-arch-same-package-has-arch-specific-overrides.tag @@ -0,0 +1,8 @@ +Tag: multi-arch-same-package-has-arch-specific-overrides +Severity: warning +Check: fields/multi-arch +Explanation: The specified file contains architecture-specific Lintian overrides + but the package is declared as <code>Multi-Arch: same</code>. +See-Also: + lintian-manual 2.4.3, + Bug#787406 diff --git a/tags/m/multiarch-foreign-cmake-file.tag b/tags/m/multiarch-foreign-cmake-file.tag new file mode 100644 index 0000000..3a44f00 --- /dev/null +++ b/tags/m/multiarch-foreign-cmake-file.tag @@ -0,0 +1,10 @@ +Tag: multiarch-foreign-cmake-file +Severity: error +Check: files/multi-arch +Explanation: The package is architecture-dependent, ships a cmake file in a public, + architecture-dependent cmake search path and is marked <code>Multi-Arch: + foreign</code>. CMake will be unable to find this file, unless it is installed + for a matching architecture, but the <code>foreign</code> marking says that the + architecture should not matter. + . + Please remove the <code>Multi-Arch: foreign</code> stanza. diff --git a/tags/m/multiarch-foreign-pkgconfig.tag b/tags/m/multiarch-foreign-pkgconfig.tag new file mode 100644 index 0000000..ee3edc2 --- /dev/null +++ b/tags/m/multiarch-foreign-pkgconfig.tag @@ -0,0 +1,10 @@ +Tag: multiarch-foreign-pkgconfig +Severity: error +Check: files/multi-arch +Explanation: The package is architecture-dependent, ships a pkg-config file in a + public, architecture-dependent pkg-config search path and is marked + <code>Multi-Arch: foreign</code>. pkg-config will be unable to find this file, + unless it is installed for a matching architecture, but the <code>foreign</code> + marking says that the architecture should not matter. + . + Please remove the <code>Multi-Arch: foreign</code> stanza. diff --git a/tags/m/multiarch-foreign-shared-library.tag b/tags/m/multiarch-foreign-shared-library.tag new file mode 100644 index 0000000..ffc8e9a --- /dev/null +++ b/tags/m/multiarch-foreign-shared-library.tag @@ -0,0 +1,11 @@ +Tag: multiarch-foreign-shared-library +Severity: error +Check: files/multi-arch +Explanation: The package is architecture-dependent, ships a shared library in + a public library search path and is marked <code>Multi-Arch: + foreign</code>. Typically, shared libraries are marked <code>Multi-Arch: + same</code> when possible. Sometimes, private shared libraries are put + into the public library search path to accommodate programs in the + same package, but this package does not contain any programs. + . + Please remove the <code>Multi-Arch: foreign</code> stanza. diff --git a/tags/m/multiarch-foreign-static-library.tag b/tags/m/multiarch-foreign-static-library.tag new file mode 100644 index 0000000..d870a86 --- /dev/null +++ b/tags/m/multiarch-foreign-static-library.tag @@ -0,0 +1,10 @@ +Tag: multiarch-foreign-static-library +Severity: error +Check: files/multi-arch +Explanation: The package is architecture-dependent, ships a static library in a + public, architecture-dependent library search path and is marked + <code>Multi-Arch: foreign</code>. A compiler will be unable to find this file, + unless it is installed for a matching architecture, but the <code>foreign</code> + marking says that the architecture should not matter. + . + Please remove the <code>Multi-Arch: foreign</code> stanza. diff --git a/tags/m/multiline-architecture-field.tag b/tags/m/multiline-architecture-field.tag new file mode 100644 index 0000000..6307f0e --- /dev/null +++ b/tags/m/multiline-architecture-field.tag @@ -0,0 +1,8 @@ +Tag: multiline-architecture-field +Severity: error +Check: debian/control/field/architecture/multiline +Explanation: The values in the <code>Architecture</code> field of the + <code>debian/control</code> file may not be separated by anything other + than spaces. The values must be in a single line of text. +See-Also: + debian-policy 5.6.8 diff --git a/tags/m/multiline-field.tag b/tags/m/multiline-field.tag new file mode 100644 index 0000000..66c2ad1 --- /dev/null +++ b/tags/m/multiline-field.tag @@ -0,0 +1,5 @@ +Tag: multiline-field +Severity: error +Check: fields/multi-line +Explanation: Most control fields must have only a single line of data. +See-Also: debian-policy 5.1 diff --git a/tags/m/multiple-debian-watch-file-standards.tag b/tags/m/multiple-debian-watch-file-standards.tag new file mode 100644 index 0000000..5048bc4 --- /dev/null +++ b/tags/m/multiple-debian-watch-file-standards.tag @@ -0,0 +1,9 @@ +Tag: multiple-debian-watch-file-standards +Severity: warning +Check: debian/watch/standard +Renamed-From: + debian-watch-file-declares-multiple-versions +Explanation: The <code>debian/watch</code> file in this package contains multiple + lines starting with <code>version=</code>. There should be only one version + declaration in a watch file, on the first non-comment line of the file. +See-Also: uscan(1) diff --git a/tags/m/multiple-distributions-in-changes-file.tag b/tags/m/multiple-distributions-in-changes-file.tag new file mode 100644 index 0000000..0d42fa9 --- /dev/null +++ b/tags/m/multiple-distributions-in-changes-file.tag @@ -0,0 +1,11 @@ +Tag: multiple-distributions-in-changes-file +Severity: error +Check: fields/distribution +Explanation: You've specified more than one target distribution for your upload + in the <code>*.changes</code> file, probably via the most recent entry in the + <code>debian/changelog</code> file. + . + Although this syntax is valid, it is not accepted by the Debian archive + management software. This may not be a problem if this upload is + targeted at an archive other than Debian's. +See-Also: debian-policy 5.6.14 |