Differences between revisions 6 and 7
Revision 6 as of 2010-08-09 02:46:04
Size: 592562
Editor: ?newacct
Comment:
Revision 7 as of 2020-11-01 03:16:32
Size: 0
Editor: PaulWise
Comment: remove manually generated and outdated page
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#language en
#format wiki

This page contains some data that are automatically imported, and
used in pages:
 * [[Lintian/Tags]]

To refresh this page with the latest lintian tags, simply grab the
python script below. The script will generate this wiki page using
your local copy of lintian. Just copy and paste the generated page
into this page.


Last updated with:
 {{{
lintian (2.4.3) unstable; urgency=low
}}}
{{{{{#!wiki comment
########################################################################
== conffiles ==
########################################################################

Self:Lintian/Tags/file-in-usr-marked-as-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-usr-marked-as-conffile.html|file-in-usr-marked-as-conffile]]''':<<BR>>
 All configuration files must reside in {{{/etc}}}. Files below {{{/usr}}} may not be marked as conffiles since {{{/usr}}} might be mounted read-only. The local system administrator would therefore not have a chance to modify this configuration file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.7.2]]
}}}}
##END:Lintian/Tags/file-in-usr-marked-as-conffile

Self:Lintian/Tags/non-etc-file-marked-as-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-etc-file-marked-as-conffile.html|non-etc-file-marked-as-conffile]]''':<<BR>>
 A file installed in some other directory than {{{/etc}}} is marked as conffile. A conffile typically implies a configuration file, and Policy mandates such files to be in {{{/etc}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.7.2]]
}}}}
##END:Lintian/Tags/non-etc-file-marked-as-conffile

Self:Lintian/Tags/relative-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/relative-conffile.html|relative-conffile]]''':<<BR>>
 All entries in the {{{debian/conffiles}}} control file should have an absolute path specification.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy E.1]]
}}}}
##END:Lintian/Tags/relative-conffile

Self:Lintian/Tags/duplicate-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-conffile.html|duplicate-conffile]]''':<<BR>>
 The file is listed more than once in your {{{debian/conffiles}}} file. Usually, this is because debhelper (dh_installdeb, compat level 3 or higher) will add any files in your package located in /etc automatically to the list of conffiles, so if you do that manually too, you'll get duplicates.
}}}}
##END:Lintian/Tags/duplicate-conffile

########################################################################
== files ==
########################################################################

Self:Lintian/Tags/package-contains-ancient-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-ancient-file.html|package-contains-ancient-file]]''':<<BR>>
 Your package contains a file that claims to have been generated more than 20 years ago. This is most probably an error. Your package will be rejected by the Debian archive scripts if it contains a file with such a timestamp.
}}}}
##END:Lintian/Tags/package-contains-ancient-file

Self:Lintian/Tags/old-app-defaults-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/old-app-defaults-directory.html|old-app-defaults-directory]]''':<<BR>>
 The app-defaults files have moved to /etc/X11/app-defaults/. Files in the old directory, /usr/X11R6/lib/X11/app-defaults/, will no longer be used by X. The old directory should not exist in packages at all; this prevents X from replacing it with a compatibility symlink.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.6]]
}}}}
##END:Lintian/Tags/old-app-defaults-directory

Self:Lintian/Tags/package-installs-font-to-usr-x11r6
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-font-to-usr-x11r6.html|package-installs-font-to-usr-x11r6]]''':<<BR>>
 The standard location for X fonts has moved to /usr/share/fonts/X11. Packages providing X fonts must install them into the new path. Fonts installed into the old /usr/X11R6/lib/X11/fonts path may not be seen by the X server.

 If the package uses imake, it must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct paths. If it uses dh_installxfonts to handle X font installation, it must build-depend on debhelper (>= 5.0.31).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.5]]
}}}}
##END:Lintian/Tags/package-installs-font-to-usr-x11r6

Self:Lintian/Tags/package-installs-file-to-usr-x11r6-bin
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-file-to-usr-x11r6-bin.html|package-installs-file-to-usr-x11r6-bin]]''':<<BR>>
 Debian has switched to the modular X tree which now uses the regular FHS paths, and all packages must follow. All packages installing binaries must install them into /usr/bin (or some other appropriate location) instead of /usr/X11R6/bin.

 The x11-common package attempts to change /usr/X11R6/bin into a symlink to /usr/bin, so if this migration has already occurred, a package installing files into /usr/X11R6/bin may appear to install successfully. However, such a package will be left in an inconsistent state and may orphan files when the compatibility link goes away.

 If the package uses imake, it must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct paths.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.7]]
}}}}
##END:Lintian/Tags/package-installs-file-to-usr-x11r6-bin

Self:Lintian/Tags/package-installs-file-to-usr-x11r6
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-file-to-usr-x11r6.html|package-installs-file-to-usr-x11r6]]''':<<BR>>
 Packages using the X Window System should not be configured to install files under the /usr/X11R6/ directory. Debian has switched to the modular X tree which now uses regular FHS paths and all packages should follow.

 Programs that use GNU autoconf and automake are usually easily configured at compile time to use /usr/ instead of /usr/X11R6/. Packages that use imake must build-depend on xutils-dev (>= 1:1.0.2-2) for the correct paths.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.7]]
}}}}
##END:Lintian/Tags/package-installs-file-to-usr-x11r6

Self:Lintian/Tags/config-file-reserved
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/config-file-reserved.html|config-file-reserved]]''':<<BR>>
 This file is reserved by a specific package. Please email the maintainer of the package in question if you have questions.
}}}}
##END:Lintian/Tags/config-file-reserved

Self:Lintian/Tags/package-uses-obsolete-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-uses-obsolete-file.html|package-uses-obsolete-file]]''':<<BR>>
 the file, /etc/nntpserver, is no longer recommenced. As of policy revision 2.5.1.0, /etc/news/server is the preferred file to use to specify a news server.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.7]]
}}}}
##END:Lintian/Tags/package-uses-obsolete-file

Self:Lintian/Tags/FSSTND-dir-in-usr
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/FSSTND-dir-in-usr.html|FSSTND-dir-in-usr]]''':<<BR>>
 As of policy version 3.0.0.0, Debian no longer follows the FSSTND.

 Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is used. You can find it in /usr/share/doc/debian-policy/fhs/ .

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.1.1]]
}}}}
##END:Lintian/Tags/FSSTND-dir-in-usr

Self:Lintian/Tags/FSSTND-dir-in-var
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/FSSTND-dir-in-var.html|FSSTND-dir-in-var]]''':<<BR>>
 As of policy version 3.0.0.0, Debian no longer follows the FSSTND.

 Instead, the Filesystem Hierarchy Standard (FHS), version 2.3, is used. You can find it in /usr/share/doc/debian-policy/fhs/ .

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.1.1]]
}}}}
##END:Lintian/Tags/FSSTND-dir-in-var

Self:Lintian/Tags/package-installs-into-etc-gconf-schemas
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-into-etc-gconf-schemas.html|package-installs-into-etc-gconf-schemas]]''':<<BR>>
 The package installs files into the {{{/etc/gconf/schemas}}} directory. No package should do this; this directory is reserved for local overrides. Instead, schemas should be installed into {{{/usr/share/gconf/schemas}}}.
}}}}
##END:Lintian/Tags/package-installs-into-etc-gconf-schemas

Self:Lintian/Tags/package-installs-into-etc-rc.d
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-into-etc-rc.d.html|package-installs-into-etc-rc.d]]''':<<BR>>
 The package installs files into the {{{/etc/rc.d}}} or {{{/etc/rc?.d}}} which is not allowed.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3]]
}}}}
##END:Lintian/Tags/package-installs-into-etc-rc.d

Self:Lintian/Tags/package-installs-into-etc-rc.boot
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-into-etc-rc.boot.html|package-installs-into-etc-rc.boot]]''':<<BR>>
 The package installs files in the {{{/etc/rc.boot}}} directory, which is obsolete. See rc.boot(5) for details.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.4]]
}}}}
##END:Lintian/Tags/package-installs-into-etc-rc.boot

Self:Lintian/Tags/non-standard-file-permissions-for-etc-init.d-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-file-permissions-for-etc-init.d-script.html|non-standard-file-permissions-for-etc-init.d-script]]''':<<BR>>
 Usually, scripts in the {{{/etc/init.d}}} directory should have mode 0755.
}}}}
##END:Lintian/Tags/non-standard-file-permissions-for-etc-init.d-script

Self:Lintian/Tags/file-directly-in-usr-share
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-directly-in-usr-share.html|file-directly-in-usr-share]]''':<<BR>>
 Packages should not install files directly in {{{/usr/share}}}, i.e., without a subdirectory.

 You should either create a subdirectory {{{/usr/share/...}}} for your package or place the file in {{{/usr/share/misc}}}.
}}}}
##END:Lintian/Tags/file-directly-in-usr-share

Self:Lintian/Tags/file-in-usr-local
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-usr-local.html|file-in-usr-local]]''':<<BR>>
 The package installs a file in {{{/usr/local/...}}} which is not allowed.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.1.2]]
}}}}
##END:Lintian/Tags/file-in-usr-local

Self:Lintian/Tags/stray-directory-in-manpage-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/stray-directory-in-manpage-directory.html|stray-directory-in-manpage-directory]]''':<<BR>>
 This package installs a directory under {{{/usr/share/man}}} or {{{/usr/X11R6/man}}} that isn't a manual section directory or locale directory.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs usrsharemanmanualpages]]
}}}}
##END:Lintian/Tags/stray-directory-in-manpage-directory

Self:Lintian/Tags/executable-manpage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-manpage.html|executable-manpage]]''':<<BR>>
 Manual pages are not meant to be executed.
}}}}
##END:Lintian/Tags/executable-manpage

Self:Lintian/Tags/dir-in-usr-local
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-in-usr-local.html|dir-in-usr-local]]''':<<BR>>
 The package installs a directory in {{{/usr/local/...}}} which is not allowed.

 If you want to provide an empty directory in {{{/usr/local}}} for convenience of the local system administrator, please follow the rules in the policy manual (section 9.1.2), i.e., create the directories in the postinst script but don't fail if this isn't possible (e.g., if {{{/usr/local}}} is mounted read-only).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.1.2]]
}}}}
##END:Lintian/Tags/dir-in-usr-local

Self:Lintian/Tags/non-standard-dir-perm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-dir-perm.html|non-standard-dir-perm]]''':<<BR>>
 The directory has a mode different from 0755, and it's not one of the known exceptions.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/non-standard-dir-perm

Self:Lintian/Tags/executable-is-not-world-readable
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-is-not-world-readable.html|executable-is-not-world-readable]]''':<<BR>>
 All executables should be readable by any user. Since anyone can download the Debian package and obtain a copy of the executable, no security is gained by making the executable unreadable even for setuid binaries. If only members of a certain group may execute this file, remove execute permission for world, but leave read permission.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/executable-is-not-world-readable

Self:Lintian/Tags/non-standard-executable-perm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-executable-perm.html|non-standard-executable-perm]]''':<<BR>>
 Executables that are not setuid or setgid should always have a mode of 0755. Since anyone can obtain the executable by downloading the Debian package and extracting it, restricting access serves little purpose.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/non-standard-executable-perm

Self:Lintian/Tags/non-standard-game-executable-perm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-game-executable-perm.html|non-standard-game-executable-perm]]''':<<BR>>
 The file is owned by the games group but is not mode 2755. If a game does not have to be setgid games, it should be owned by the root group like any other executable. This executable is either owned by the wrong group or is not setgid when it should be.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.11]]
}}}}
##END:Lintian/Tags/non-standard-game-executable-perm

Self:Lintian/Tags/non-standard-setuid-executable-perm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-setuid-executable-perm.html|non-standard-setuid-executable-perm]]''':<<BR>>
 The file is setuid or setgid and has a mode different from any of 2755, 4755, 4754, or 6755. Any other permissions on setuid executables is probably a bug. In particular, removing root write privileges serves no purpose, group-writable setuid or setgid executables are probably bad ideas, and setgid executables that are not world-executable serve little purpose.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/non-standard-setuid-executable-perm

Self:Lintian/Tags/setuid-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/setuid-binary.html|setuid-binary]]''':<<BR>>
 The file is tagged SETUID. In some cases this is intentional, but in other cases this is a bug. If this is intentional, please add a lintian override to document this fact.
}}}}
##END:Lintian/Tags/setuid-binary

Self:Lintian/Tags/setgid-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/setgid-binary.html|setgid-binary]]''':<<BR>>
 The file is tagged SETGID. In some cases this is intentional, but in other cases this is a bug. If this is intentional, please add a lintian override to document this fact.
}}}}
##END:Lintian/Tags/setgid-binary

Self:Lintian/Tags/setuid-gid-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/setuid-gid-binary.html|setuid-gid-binary]]''':<<BR>>
 The file is tagged SETUID and SETGID. In some cases this is intentional, but in other cases this is a bug. If this is intentional, please add a lintian override to document this fact.
}}}}
##END:Lintian/Tags/setuid-gid-binary

Self:Lintian/Tags/non-standard-file-perm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-file-perm.html|non-standard-file-perm]]''':<<BR>>
 The file has a mode different from 0644. In some cases this is intentional, but in other cases this is a bug.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/non-standard-file-perm

Self:Lintian/Tags/special-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/special-file.html|special-file]]''':<<BR>>
 The package contains a special file (e.g., a device file). This is forbidden by current policy. If your program needs this device, you should create it by calling {{{makedev}}} from the postinst script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.6]]
}}}}
##END:Lintian/Tags/special-file

Self:Lintian/Tags/old-style-example-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/old-style-example-dir.html|old-style-example-dir]]''':<<BR>>
 The package installs some files into the old {{{/usr/doc/examples}}} directory. The new location for examples is {{{/usr/share/doc/pkg/examples}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.6]]
}}}}
##END:Lintian/Tags/old-style-example-dir

Self:Lintian/Tags/compressed-symlink-with-wrong-ext
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/compressed-symlink-with-wrong-ext.html|compressed-symlink-with-wrong-ext]]''':<<BR>>
 The package installs a symbolic link pointing to a compressed file, but the symbolic link does not use the same file extension than the referenced file. In most cases, this can produce troubles when the user or a program tries to access the file through the link.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/compressed-symlink-with-wrong-ext

Self:Lintian/Tags/symlink-has-double-slash
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-has-double-slash.html|symlink-has-double-slash]]''':<<BR>>
 This symlink contains two successive slashes (//). This is in violation of policy, where it is stated that symlinks should be as short as possible

 If you use debhelper, running dh_link after creating the package structure will fix this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/symlink-has-double-slash

Self:Lintian/Tags/symlink-ends-with-slash
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-ends-with-slash.html|symlink-ends-with-slash]]''':<<BR>>
 This symlink ends with a slash (/). This is in violation of policy, where it is stated that symlinks should be as short as possible

 If you use debhelper, running dh_link after creating the package structure will fix this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/symlink-ends-with-slash

Self:Lintian/Tags/symlink-should-be-relative
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-should-be-relative.html|symlink-should-be-relative]]''':<<BR>>
 Symlinks to files which are in the same top-level directory should be relative according to policy. (In other words, a link in /usr to another file in /usr should be relative, while a link in /usr to a file in /etc should be absolute.)

 If you use debhelper, running dh_link after creating the package structure will fix this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/symlink-should-be-relative

Self:Lintian/Tags/symlink-should-be-absolute
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-should-be-absolute.html|symlink-should-be-absolute]]''':<<BR>>
 Symbolic links between different top-level directories should be absolute.

 If you use debhelper, running dh_link after creating the package structure will fix this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/symlink-should-be-absolute

Self:Lintian/Tags/udeb-contains-documentation-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/udeb-contains-documentation-file.html|udeb-contains-documentation-file]]''':<<BR>>
 udeb packages should not contain any documentation.
}}}}
##END:Lintian/Tags/udeb-contains-documentation-file

Self:Lintian/Tags/executable-in-usr-share-doc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-in-usr-share-doc.html|executable-in-usr-share-doc]]''':<<BR>>
 Usually, documentation files in {{{/usr/share/doc}}} should have mode 0644. If the executable is an example, it should go in {{{/usr/share/doc/pkg/examples}}}.
}}}}
##END:Lintian/Tags/executable-in-usr-share-doc

Self:Lintian/Tags/script-in-usr-share-doc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-in-usr-share-doc.html|script-in-usr-share-doc]]''':<<BR>>
 Scripts are usually not documentation files, unless they are examples, in which case they should be in the {{{/usr/share/doc/pkg/examples}}} directory.
}}}}
##END:Lintian/Tags/script-in-usr-share-doc

Self:Lintian/Tags/symlink-has-too-many-up-segments
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-has-too-many-up-segments.html|symlink-has-too-many-up-segments]]''':<<BR>>
 The symlink references a directory beyond the root directory "/".

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/symlink-has-too-many-up-segments

Self:Lintian/Tags/lengthy-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/lengthy-symlink.html|lengthy-symlink]]''':<<BR>>
 This link goes up, and then back down into the same subdirectory. Making it shorter will improve its chances of finding the right file if the user's system has lots of symlinked directories.

 If you use debhelper, running dh_link after creating the package structure will fix this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/lengthy-symlink

Self:Lintian/Tags/symlink-is-self-recursive
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-is-self-recursive.html|symlink-is-self-recursive]]''':<<BR>>
 The symbolic link is recursive to a higher directory of the symlink itself. This means, that you can infinitely chdir with this symlink. This is usually not okay, but sometimes wanted behaviour.
}}}}
##END:Lintian/Tags/symlink-is-self-recursive

Self:Lintian/Tags/symlink-contains-spurious-segments
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symlink-contains-spurious-segments.html|symlink-contains-spurious-segments]]''':<<BR>>
 The symbolic link has needless segments like ".." and "." in the middle. These are unneeded and make the link longer than it could be, which is in violation of policy. They can also cause problems in the presence of symlinked directories.

 If you use debhelper, running dh_link after creating the package structure will fix this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.5]]
}}}}
##END:Lintian/Tags/symlink-contains-spurious-segments

Self:Lintian/Tags/run-parts-cron-filename-contains-full-stop
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/run-parts-cron-filename-contains-full-stop.html|run-parts-cron-filename-contains-full-stop]]''':<<BR>>
 The script in /etc/cron.<time-interval> will not be executed by run-parts(8) because the filename contains a "." (full stop).

Reference(s): [[DebianMan:8/run-parts|run-parts(8)]]
}}}}
##END:Lintian/Tags/run-parts-cron-filename-contains-full-stop

Self:Lintian/Tags/bad-permissions-for-etc-cron.d-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-permissions-for-etc-cron.d-script.html|bad-permissions-for-etc-cron.d-script]]''':<<BR>>
 Files in {{{/etc/cron.d}}} are configuration files for cron and not scripts. Thus, they should not be marked executable.
}}}}
##END:Lintian/Tags/bad-permissions-for-etc-cron.d-script

Self:Lintian/Tags/bad-permissions-for-etc-emacs-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-permissions-for-etc-emacs-script.html|bad-permissions-for-etc-emacs-script]]''':<<BR>>
 Files in the {{{/etc/emacs*}}} directories should not be marked executable.
}}}}
##END:Lintian/Tags/bad-permissions-for-etc-emacs-script

Self:Lintian/Tags/image-file-in-usr-lib
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/image-file-in-usr-lib.html|image-file-in-usr-lib]]''':<<BR>>
 This package installs a pixmap or a bitmap within {{{/usr/lib}}}. According to the Filesystem Hierarchy Standard, architecture-independent files need to be placed within {{{/usr/share}}} instead.
}}}}
##END:Lintian/Tags/image-file-in-usr-lib

Self:Lintian/Tags/file-directly-in-usr-share-doc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-directly-in-usr-share-doc.html|file-directly-in-usr-share-doc]]''':<<BR>>
 Documentation files have to be installed in {{{/usr/share/doc/pkg}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.3]]
}}}}
##END:Lintian/Tags/file-directly-in-usr-share-doc

Self:Lintian/Tags/bad-owner-for-doc-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-owner-for-doc-file.html|bad-owner-for-doc-file]]''':<<BR>>
 Documentation files should be owned by {{{root/root}}}.
}}}}
##END:Lintian/Tags/bad-owner-for-doc-file

Self:Lintian/Tags/dir-or-file-in-var-lock
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-var-lock.html|dir-or-file-in-var-lock]]''':<<BR>>
 {{{/var/lock}}} may be a temporary filesystem, so any directories or files needed there must be created dynamically at boot time.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.2]]
}}}}
##END:Lintian/Tags/dir-or-file-in-var-lock

Self:Lintian/Tags/dir-or-file-in-var-run
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-var-run.html|dir-or-file-in-var-run]]''':<<BR>>
 {{{/var/run}}} may be a temporary filesystem, so any directories or files needed there must be created dynamically at boot time.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.2]]
}}}}
##END:Lintian/Tags/dir-or-file-in-var-run

Self:Lintian/Tags/dir-or-file-in-var-www
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-var-www.html|dir-or-file-in-var-www]]''':<<BR>>
 Debian packages should not install files under {{{/var/www}}}. This is not one of the {{{/var}}} directories in the File Hierarchy Standard and is under the control of the local administrator. Packages should not assume that it is the document root for a web server; it is very common for users to change the default document root and packages should not assume that users will keep any particular setting.

 Packages that want to make files available via an installed web server should instead put instructions for the local administrator in a README.Debian file and ideally include configuration fragments for common web servers such as Apache.

 As an exception, packages are permitted to create the {{{/var/www}}} directory due to its past history as the default document root, but should at most copy over a default file in postinst for a new install. In this case, please add a Lintian override.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs thevarhierarchy]]
}}}}
##END:Lintian/Tags/dir-or-file-in-var-www

Self:Lintian/Tags/dir-or-file-in-tmp
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-tmp.html|dir-or-file-in-tmp]]''':<<BR>>
 Packages must not install files into {{{/tmp}}} or {{{/var/tmp}}}. The File Hierarchy Standard specifies that such files may be removed by the administrator and that programs may not depend on any files in {{{/tmp}}} being preserved across invocations, which combined mean that it makes no sense to ship files in these directories.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs tmptemporaryfiles]], [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs vartmptemporaryfilespreservedbetwee]]
}}}}
##END:Lintian/Tags/dir-or-file-in-tmp

Self:Lintian/Tags/dir-or-file-in-mnt
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-mnt.html|dir-or-file-in-mnt]]''':<<BR>>
 Packages should not install into {{{/mnt}}}. The FHS states that this directory is reserved for the local system administrator for temporary mounts and that it must not be used by installation programs.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs mntmountpointforatemporarilymount]]
}}}}
##END:Lintian/Tags/dir-or-file-in-mnt

Self:Lintian/Tags/dir-or-file-in-opt
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-opt.html|dir-or-file-in-opt]]''':<<BR>>
 Debian packages should not install into {{{/opt}}}, because it is reserved for add-on software.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs optaddonapplicationsoftwarepackages]]
}}}}
##END:Lintian/Tags/dir-or-file-in-opt

Self:Lintian/Tags/dir-or-file-in-srv
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dir-or-file-in-srv.html|dir-or-file-in-srv]]''':<<BR>>
 Debian packages should not install into {{{/srv}}}. The specification of {{{/srv}}} states that its structure is at the discretion of the local administrator and no package should rely on any particular structure. Debian packages that install files directly into {{{/srv}}} can't adjust for local policy about its structure and in essence force a particular structure.

 If a package wishes to put its data in {{{/srv}}}, it must do this in a way that allows the local administrator to specify and preserve their chosen directory structure (such as through post-install configuration, setup scripts, debconf prompting, etc.).

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs srvdataforservicesprovidedbysystem]]
}}}}
##END:Lintian/Tags/dir-or-file-in-srv

Self:Lintian/Tags/third-party-package-in-python-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/third-party-package-in-python-dir.html|third-party-package-in-python-dir]]''':<<BR>>
 Third-party Python packages should install their files in {{{/usr/lib/pythonVERSION/site-packages}}} for Python versions before 2.6 and {{{/usr/lib/pythonVERSION/dist-packages}}} for Python 2.6 and later. All other directories in {{{/usr/lib/pythonVERSION}}} are for use by the core python packages.
}}}}
##END:Lintian/Tags/third-party-package-in-python-dir

Self:Lintian/Tags/perl-module-in-core-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/perl-module-in-core-directory.html|perl-module-in-core-directory]]''':<<BR>>
 Packaged modules must not be installed into the core perl directories as those directories change with each upstream perl revision. The vendor directories are provided for this purpose.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/perl-policy/|perl-policy 3.1]]
}}}}
##END:Lintian/Tags/perl-module-in-core-directory

Self:Lintian/Tags/backup-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/backup-file-in-package.html|backup-file-in-package]]''':<<BR>>
 There is a file in the package whose name matches the format emacs or vim uses for backup and autosave files. It may have been installed by accident.
}}}}
##END:Lintian/Tags/backup-file-in-package

Self:Lintian/Tags/nfs-temporary-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/nfs-temporary-file-in-package.html|nfs-temporary-file-in-package]]''':<<BR>>
 There is a file in the package whose name matches the format NFS uses to temporarily save files that were deleted while another process had them open. It may have been included in the package by accident while building the package in an NFS filesystem.
}}}}
##END:Lintian/Tags/nfs-temporary-file-in-package

Self:Lintian/Tags/windows-thumbnail-database-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/windows-thumbnail-database-in-package.html|windows-thumbnail-database-in-package]]''':<<BR>>
 There is a file in the package named {{{Thumbs.db}}} or {{{Thumbs.db.gz}}}, which is normally a Windows image thumbnail database. Such databases are generally useless in Debian packages and were usually accidentally included by copying complete directories from the source tarball.
}}}}
##END:Lintian/Tags/windows-thumbnail-database-in-package

Self:Lintian/Tags/macos-ds-store-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/macos-ds-store-file-in-package.html|macos-ds-store-file-in-package]]''':<<BR>>
 There is a file in the package named {{{.DS_Store}}} or {{{.DS_Store.gz}}}, 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.
}}}}
##END:Lintian/Tags/macos-ds-store-file-in-package

Self:Lintian/Tags/macos-resource-fork-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/macos-resource-fork-file-in-package.html|macos-resource-fork-file-in-package]]''':<<BR>>
 There is a file in the package with a name starting with {{{._}}}, 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.
}}}}
##END:Lintian/Tags/macos-resource-fork-file-in-package

Self:Lintian/Tags/package-installs-perllocal-pod
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-perllocal-pod.html|package-installs-perllocal-pod]]''':<<BR>>
 This package installs a file {{{perllocal.pod}}}. Since that file is intended for local documentation, it is not likely that it is a good place for documentation supplied by a Debian package. In fact, installing this package will wipe out whatever local documentation existed there.
}}}}
##END:Lintian/Tags/package-installs-perllocal-pod

Self:Lintian/Tags/extra-license-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/extra-license-file.html|extra-license-file]]''':<<BR>>
 All license information should be collected in the {{{debian/copyright}}} file. This usually makes it unnecessary for the package to install this information in other places as well.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/extra-license-file

Self:Lintian/Tags/non-standard-toplevel-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-toplevel-dir.html|non-standard-toplevel-dir]]''':<<BR>>
 The Filesystem Hierarchy Standard forbids the installation of new files or directories in the root directory.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs therootfilesystem]]
}}}}
##END:Lintian/Tags/non-standard-toplevel-dir

Self:Lintian/Tags/subdir-in-bin
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/subdir-in-bin.html|subdir-in-bin]]''':<<BR>>
 The Filesystem Hierarchy Standard forbids the installation of new directories in {{{/bin}}}.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs binessentialusercommandbinaries]]
}}}}
##END:Lintian/Tags/subdir-in-bin

Self:Lintian/Tags/subdir-in-usr-bin
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/subdir-in-usr-bin.html|subdir-in-usr-bin]]''':<<BR>>
 The Filesystem Hierarchy Standard forbids the installation of new directories in {{{/usr/bin}}} other than {{{/usr/bin/mh}}}.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs usrbinmostusercommands]]
}}}}
##END:Lintian/Tags/subdir-in-usr-bin

Self:Lintian/Tags/non-standard-dir-in-usr
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-dir-in-usr.html|non-standard-dir-in-usr]]''':<<BR>>
 The FHS says "No large software packages should use a direct subdirectory under the {{{/usr}}} hierarchy". This package contains a directory in {{{/usr}}} that is not mentioned in the Filesystem Hierarchy Standard.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs theusrhierarchy]]
}}}}
##END:Lintian/Tags/non-standard-dir-in-usr

Self:Lintian/Tags/non-standard-dir-in-var
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-standard-dir-in-var.html|non-standard-dir-in-var]]''':<<BR>>
 The FHS says "Applications should generally not add directories to the top level of {{{/var}}}. Such directories should only be added if they have some system-wide implication, and in consultation with the FHS mailing list."

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs thevarhierarchy]]
}}}}
##END:Lintian/Tags/non-standard-dir-in-var

Self:Lintian/Tags/use-of-compat-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/use-of-compat-symlink.html|use-of-compat-symlink]]''':<<BR>>
 This package uses a directory that, according to the Filesystem Hierarchy Standard, should exist only as a compatibility symlink. Packages should not traverse such symlinks when installing files, they should use the standard directories instead.
}}}}
##END:Lintian/Tags/use-of-compat-symlink

Self:Lintian/Tags/file-in-unusual-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-unusual-dir.html|file-in-unusual-dir]]''':<<BR>>
 This file or symbolic link is in a directory where files are not normally installed by Debian packages.
}}}}
##END:Lintian/Tags/file-in-unusual-dir

Self:Lintian/Tags/package-installs-packlist
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-packlist.html|package-installs-packlist]]''':<<BR>>
 Packages built using the perl MakeMaker package will have a file named .packlist in them. Those files are useless, and (in some cases) have the additional problem of creating an architecture-specific directory name in an architecture-independent package.

 They can be suppressed by adding the following to {{{debian/rules}}}:

   find debian/pkg -type f -name .packlist | xargs rm -f

 or by telling MakeMaker to use vendor install dirs; consult a recent version of Perl policy. Perl 5.6.0-12 or higher supports this.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/perl-policy/|perl-policy 4.1]]
}}}}
##END:Lintian/Tags/package-installs-packlist

Self:Lintian/Tags/zero-byte-file-in-doc-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/zero-byte-file-in-doc-directory.html|zero-byte-file-in-doc-directory]]''':<<BR>>
 The documentation directory for this package contains an empty file. This is often due to installing an upstream NEWS or README file without realizing it's empty and hence not useful.

 Files in the examples subdirectory are excluded from this check, but there are some cases where empty files are legitimate parts of the documentation without being examples. In those cases, please add an override.
}}}}
##END:Lintian/Tags/zero-byte-file-in-doc-directory

Self:Lintian/Tags/override-file-in-wrong-location
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/override-file-in-wrong-location.html|override-file-in-wrong-location]]''':<<BR>>
 Lintian overrides should be put in a regular file named /usr/share/lintian/overrides/{{{package}}}, not in a subdirectory named for the package or in the obsolete location under /usr/share/doc. See the Lintian documentation for more information on proper naming and format.

Reference(s): [[http://lintian.debian.org/manual/|lintian 2.4]]
}}}}
##END:Lintian/Tags/override-file-in-wrong-location

Self:Lintian/Tags/package-contains-upstream-install-documentation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-upstream-install-documentation.html|package-contains-upstream-install-documentation]]''':<<BR>>
 Binary packages do not need to contain the instructions for building and installing the package as this info is not needed by package users. If the info contained is important for configuration perhaps it could be summarized in README.Debian, otherwise an override may be added.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.3]]
}}}}
##END:Lintian/Tags/package-contains-upstream-install-documentation

Self:Lintian/Tags/package-contains-hardlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-hardlink.html|package-contains-hardlink]]''':<<BR>>
 The package contains a hardlink in {{{/etc}}} or across different directories. This might not work at all if directories are on different filesystems (which can happen anytime as the system administrator sees fit), certain filesystems such as AFS don't even support cross-directory hardlinks at all.

 For configuration files, certain editors might break hardlinks, and so does dpkg in certain cases.

 A better solution might be using symlinks here.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.7.3]]
}}}}
##END:Lintian/Tags/package-contains-hardlink

Self:Lintian/Tags/package-contains-bts-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-bts-control-dir.html|package-contains-bts-control-dir]]''':<<BR>>
 The package contains a control directory for a bug tracking system. It was most likely installed by accident, since bug tracking directories usually don't belong in packages.
}}}}
##END:Lintian/Tags/package-contains-bts-control-dir

Self:Lintian/Tags/package-contains-vcs-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-vcs-control-dir.html|package-contains-vcs-control-dir]]''':<<BR>>
 The package contains a control directory for a version control system. It was most likely installed by accident, since version control directories usually don't belong in packages.
}}}}
##END:Lintian/Tags/package-contains-vcs-control-dir

Self:Lintian/Tags/package-contains-xvpics-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-xvpics-dir.html|package-contains-xvpics-dir]]''':<<BR>>
 Package contains a .xvpics directory. It was most likely installed by accident, since thumbnails usually don't belong in packages.
}}}}
##END:Lintian/Tags/package-contains-xvpics-dir

Self:Lintian/Tags/package-contains-vcs-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-vcs-control-file.html|package-contains-vcs-control-file]]''':<<BR>>
 The package contains a VCS control file such as .(cvs|git|hg)ignore. Files such as these are used by revision control systems to, for example, specify untracked files it should ignore or inventory files. This file is generally useless in an installed package and was probably installed by accident.
}}}}
##END:Lintian/Tags/package-contains-vcs-control-file

Self:Lintian/Tags/svn-commit-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/svn-commit-file-in-package.html|svn-commit-file-in-package]]''':<<BR>>
 The package contains an svn-commit(.NNN).tmp file. This file is almost certainly a left-over from a failed Subversion commit, and does not belong in a Debian package.
}}}}
##END:Lintian/Tags/svn-commit-file-in-package

Self:Lintian/Tags/svk-commit-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/svk-commit-file-in-package.html|svk-commit-file-in-package]]''':<<BR>>
 The package contains an svk-commitNNN.tmp file. This file is almost certainly a left-over from a failed Subversion commit, and does not belong in a Debian package.
}}}}
##END:Lintian/Tags/svk-commit-file-in-package

Self:Lintian/Tags/nested-examples-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/nested-examples-directory.html|nested-examples-directory]]''':<<BR>>
 Package contains a {{{usr/share/doc/something/examples/examples}}} directory. It was most likely installed by accident, since one examples/ directory should be enough for everybody(tm).
}}}}
##END:Lintian/Tags/nested-examples-directory

Self:Lintian/Tags/package-installs-nonbinary-perl-in-usr-lib-perl5
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-nonbinary-perl-in-usr-lib-perl5.html|package-installs-nonbinary-perl-in-usr-lib-perl5]]''':<<BR>>
 Architecture-independent Perl code should be placed in {{{/usr/share/perl5}}}, not {{{/usr/lib/perl5}}} unless there is at least one architecture-dependent file in the module.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/perl-policy/|perl-policy 2.3]]
}}}}
##END:Lintian/Tags/package-installs-nonbinary-perl-in-usr-lib-perl5

Self:Lintian/Tags/file-in-usr-lib-site-python
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-usr-lib-site-python.html|file-in-usr-lib-site-python]]''':<<BR>>
 The directory /usr/lib/site-python has been deprecated as a location for installing Python modules and may be dropped from Python's module search path in a future version. Most likely this module is a private module and should be packaged in a directory outside of Python's default search path.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/python-policy/|python-policy 1.5]]
}}}}
##END:Lintian/Tags/file-in-usr-lib-site-python

Self:Lintian/Tags/package-installs-python-pyc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-installs-python-pyc.html|package-installs-python-pyc]]''':<<BR>>
 Compiled python source files must not be included in the package. These files should be removed from the package and created at package installation time in the postinst.
}}}}
##END:Lintian/Tags/package-installs-python-pyc

Self:Lintian/Tags/bad-permissions-for-ali-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-permissions-for-ali-file.html|bad-permissions-for-ali-file]]''':<<BR>>
 Ada Library Information (*.ali) files are required to be read-only (mode 0444) by GNAT.

 If at least one user can write the *.ali file, GNAT considers whether or not to recompile the corresponding source file. Such recompilation would fail because normal users don't have write permission on the files. Moreover, such recompilation would defeat the purpose of library packages, which provide *.a and *.so libraries to link against).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.4]]
}}}}
##END:Lintian/Tags/bad-permissions-for-ali-file

Self:Lintian/Tags/package-contains-readme-for-other-platform-or-distro
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-readme-for-other-platform-or-distro.html|package-contains-readme-for-other-platform-or-distro]]''':<<BR>>
 package contains a README.(platform) file that contains instructions specific to a platform or distribution other than Debian and thus can most likely be removed. If it contains information that pertains to Debian, please consider renaming it, or including it in an already existing README file.
}}}}
##END:Lintian/Tags/package-contains-readme-for-other-platform-or-distro

Self:Lintian/Tags/desktop-file-in-wrong-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-file-in-wrong-dir.html|desktop-file-in-wrong-dir]]''':<<BR>>
 The package contains a .desktop file in an obsolete directory. According to the menu-spec draft on freedesktop.org, those .desktop files that are intended to create a menu should be placed in {{{/usr/share/applications}}}, not {{{/usr/share/gnome/apps}}}.
}}}}
##END:Lintian/Tags/desktop-file-in-wrong-dir

Self:Lintian/Tags/script-with-language-extension
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-with-language-extension.html|script-with-language-extension]]''':<<BR>>
 When scripts are installed into a directory in the system PATH, the script name should not include an extension such as {{{.sh}}} or {{{.pl}}} that denotes the scripting language currently used to implement it. The implementation language may change; if it does, leaving the name the same would be confusing and changing it would be disruptive.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/script-with-language-extension

Self:Lintian/Tags/file-in-usr-lib-sgml
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-usr-lib-sgml.html|file-in-usr-lib-sgml]]''':<<BR>>
 This package installs a file in {{{/usr/lib/sgml}}}. This was the old location for SGML catalogs and similar flies. All those files should now go into {{{/usr/share/sgml}}}.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs theusrhierarchy]]
}}}}
##END:Lintian/Tags/file-in-usr-lib-sgml

Self:Lintian/Tags/file-name-ends-in-whitespace
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-name-ends-in-whitespace.html|file-name-ends-in-whitespace]]''':<<BR>>
 This package installs a file or directory whose name ends in whitespace. This might be intentional but it's normally a mistake. If it is intentional, add a lintian override.

 One possible cause is using debhelper 5.0.57 or earlier to install a doc-base file with a Document field that ends in whitespace.
}}}}
##END:Lintian/Tags/file-name-ends-in-whitespace

Self:Lintian/Tags/package-contains-empty-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-empty-directory.html|package-contains-empty-directory]]''':<<BR>>
 This package installs an empty directory. This might be intentional but it's normally a mistake. If it is intentional, add a lintian override.

 If a package ships with or installs empty directories, you can remove them in debian/rules by calling:

  $ find path/to/base/dir -type d -empty -delete
}}}}
##END:Lintian/Tags/package-contains-empty-directory

Self:Lintian/Tags/package-section-games-but-contains-no-game
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-section-games-but-contains-no-game.html|package-section-games-but-contains-no-game]]''':<<BR>>
 This package is marked as part of the section games, but doesn't contain files in {{{/usr/games}}}. Binaries of games must be installed in {{{/usr/games}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.11]]
}}}}
##END:Lintian/Tags/package-section-games-but-contains-no-game

Self:Lintian/Tags/package-section-games-but-has-usr-bin
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-section-games-but-has-usr-bin.html|package-section-games-but-has-usr-bin]]''':<<BR>>
 This package is marked as part of the section games, but contains executables in {{{/bin}}} or {{{/usr/bin/}}}. This can be intentional, but is usually a mistake.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.11]]
}}}}
##END:Lintian/Tags/package-section-games-but-has-usr-bin

Self:Lintian/Tags/games-package-should-be-section-games
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/games-package-should-be-section-games.html|games-package-should-be-section-games]]''':<<BR>>
 All the executables in this package are in {{{/usr/games}}}, but the package is not in section games. This can be intentional but is usually a mistake.
}}}}
##END:Lintian/Tags/games-package-should-be-section-games

Self:Lintian/Tags/package-contains-devhelp-file-without-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-devhelp-file-without-symlink.html|package-contains-devhelp-file-without-symlink]]''':<<BR>>
 This package contains a *.devhelp or *.devhelp2 file which is not in the devhelp search path ({{{/usr/share/devhelp/books}}} and {{{/usr/share/gtk-doc/html}}}) and is apparently not in a directory linked into the devhelp search path. This will prevent devhelp from finding the documentation.

 If the devhelp documentation is installed in a path outside the devhelp search path (such as {{{/usr/share/doc}}}), create a symlink in {{{/usr/share/gtk-doc/html}}} pointing to the documentation directory.
}}}}
##END:Lintian/Tags/package-contains-devhelp-file-without-symlink

Self:Lintian/Tags/debug-package-should-be-named-dbg
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debug-package-should-be-named-dbg.html|debug-package-should-be-named-dbg]]''':<<BR>>
 This package provides at least one file in {{{/usr/lib/debug}}}, which is intended for detached debugging symbols, but the package name does not end in "-dbg". Detached debugging symbols should be put into a separate package, Priority: extra, with a package name ending in "-dbg".

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.7.9]]
}}}}
##END:Lintian/Tags/debug-package-should-be-named-dbg

Self:Lintian/Tags/package-contains-linda-override
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-linda-override.html|package-contains-linda-override]]''':<<BR>>
 This package contains a linda override file in {{{/usr/share/linda/overrides}}}. Linda is obsolete and has been removed from the archive as of 2008-03-04. Linda overrides should probably be dropped from packages.
}}}}
##END:Lintian/Tags/package-contains-linda-override

Self:Lintian/Tags/wrong-file-owner-uid-or-gid
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-file-owner-uid-or-gid.html|wrong-file-owner-uid-or-gid]]''':<<BR>>
 The user or group ID of the owner of the file is invalid. The owner user and group IDs must be in the set of globally allocated IDs, because other IDs are dynamically allocated and might be used for varying purposes on different systems, or are reserved. The set of the allowed, globally allocated IDs consists of the ranges 0-99, 64000-64999 and 65534.

 It's possible for a Policy-compliant package to trigger this bug if the user is created in the preinst maintainer script, but this is a very rare case and doesn't appear to be necessary. If you found yourself needing to create a package that works this way, please file a bug against Lintian to let the maintainers know.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.2]]
}}}}
##END:Lintian/Tags/wrong-file-owner-uid-or-gid

Self:Lintian/Tags/embedded-javascript-library
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-javascript-library.html|embedded-javascript-library]]''':<<BR>>
 This package contains an embedded copy of JavaScript libraries that are now available in their own packages (for example, JQuery, Prototype, Mochikit or "Cropper"). Please depend on the appropriate package and symlink the library into the appropriate location.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-javascript-library

Self:Lintian/Tags/embedded-feedparser-library
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-feedparser-library.html|embedded-feedparser-library]]''':<<BR>>
 This package contains an embedded copy of Mark Pilgrim's Universal Feed Parser. Please depend on the "python-feedparser" package and use the normal Python import mechanism to load it.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-feedparser-library

Self:Lintian/Tags/embedded-pear-module
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-pear-module.html|embedded-pear-module]]''':<<BR>>
 This package appears to contain an embedded copy of a PEAR module. Please depend on the respective PEAR package providing the module and make sure the library can be found by the scripts via the include_path.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-pear-module

Self:Lintian/Tags/embedded-php-library
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-php-library.html|embedded-php-library]]''':<<BR>>
 This package appears to contain an embedded copy of a PHP library. Please depend on the respective package providing the library and make sure it can be found by the scripts via the include_path.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-php-library

Self:Lintian/Tags/windows-devel-file-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/windows-devel-file-in-package.html|windows-devel-file-in-package]]''':<<BR>>
 This package appears to contain development files only meaningful to Windows environments. Such files are generally useless in Debian packages and were usually accidentally included by copying complete directories from the source tarball.
}}}}
##END:Lintian/Tags/windows-devel-file-in-package

Self:Lintian/Tags/font-in-non-font-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/font-in-non-font-package.html|font-in-non-font-package]]''':<<BR>>
 This package contains a *.ttf, *.otf, or *.pfb file, file extensions used by TrueType, OpenType, or Type 1 fonts, but the package does not appear to be a dedicated font package. Dedicated font package names should begin with {{{ttf-}}}, {{{otf-}}}, or {{{t1-}}}, depending on the types of fonts included. (Type 1 fonts are also allowed in packages starting with {{{xfonts-}}}.) If the font is already packaged, you should depend on that package instead. Otherwise, normally the font should be packaged separately, since fonts are usually useful outside of the package that embeds them.
}}}}
##END:Lintian/Tags/font-in-non-font-package

Self:Lintian/Tags/duplicate-font-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-font-file.html|duplicate-font-file]]''':<<BR>>
 This package appears to include a font file that is already provided by another package in Debian. Ideally it should instead depend on the relevant font package. If the application in this package loads the font file by name, you may need to include a symlink pointing to the file name of the font in its Debian package.

 Sometimes the font package containing the font is huge and you only need one font. In that case, you have a few options: modify the package (in conjunction with upstream) to use libfontconfig to find the font that you prefer but fall back on whatever installed font is available, ask that the font package be split apart into packages of a more reasonable size, or add an override and be aware of the duplication when new versions of the font are released.
}}}}
##END:Lintian/Tags/duplicate-font-file

Self:Lintian/Tags/icon-size-and-directory-name-mismatch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/icon-size-and-directory-name-mismatch.html|icon-size-and-directory-name-mismatch]]''':<<BR>>
 The icon has a size that differs from the size specified by the name of the directory under which it was installed. The icon was probably mistakenly installed into the wrong directory.
}}}}
##END:Lintian/Tags/icon-size-and-directory-name-mismatch

Self:Lintian/Tags/gz-file-not-gzip
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/gz-file-not-gzip.html|gz-file-not-gzip]]''':<<BR>>
 The given file ends with {{{.gz}}}, which normally indicates it is compressed with gzip. However, it doesn't seem to be a gzip-compressed file. gzip will fail with an error on such files. Normally this indicates a mistake in the installation process of the package.
}}}}
##END:Lintian/Tags/gz-file-not-gzip

Self:Lintian/Tags/non-free-flash
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-free-flash.html|non-free-flash]]''':<<BR>>
 The given Flash file has a filename which suggests that it may be one of a number of known Flash files with non-free content.
}}}}
##END:Lintian/Tags/non-free-flash

Self:Lintian/Tags/non-conf-file-in-modprobe.d
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-conf-file-in-modprobe.d.html|non-conf-file-in-modprobe.d]]''':<<BR>>
 Files in {{{/etc/modprobe.d}}} should use filenames ending in {{{.conf}}}. modprobe currently warns about files which do not match this convention and at some point in the future the files will no longer be processed.

 If the file is an example containing only comments, consider installing it in another location as files in {{{/etc/modprobe.d}}} are read each time modprobe is run (which is often at boot time).

Reference(s): [[http://lists.debian.org/debian-devel/2009/03/msg00119.html]]
}}}}
##END:Lintian/Tags/non-conf-file-in-modprobe.d

Self:Lintian/Tags/file-in-discouraged-x11-font-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-discouraged-x11-font-directory.html|file-in-discouraged-x11-font-directory]]''':<<BR>>
 For historical reasons, use of {{{PEX}}}, {{{CID}}}, {{{Speedo}}}, and {{{cyrillic}}} subdirectories of {{{/usr/share/fonts/X11}}} are permitted, but installation of files into these directories is discouraged. Support for the first three font types is deprecated or no longer available, and Cyrillic fonts should use the normal font directories where possible.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.5]]
}}}}
##END:Lintian/Tags/file-in-discouraged-x11-font-directory

Self:Lintian/Tags/file-in-unknown-x11-font-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-unknown-x11-font-directory.html|file-in-unknown-x11-font-directory]]''':<<BR>>
 Subdirectories of {{{/usr/share/fonts/X11}}} other than {{{100dpi}}}, {{{75dpi}}}, {{{misc}}}, {{{Type1}}}, and some historic exceptions must be neither created nor used. (The directories {{{encodings}}} and {{{util}}}, used by some X Window System packages, are also permitted by Lintian.)

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.5]]
}}}}
##END:Lintian/Tags/file-in-unknown-x11-font-directory

Self:Lintian/Tags/package-contains-multiple-dpi-fonts
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-multiple-dpi-fonts.html|package-contains-multiple-dpi-fonts]]''':<<BR>>
 This package contains both 100dpi and 75dpi bitmapped fonts. Both versions should not be included in a single package. If both resolutions are available, they should be provided in separate binary packages with {{{-75dpi}}} or {{{-100dpi}}} appended to the package name for the corresponding fonts.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.5]]
}}}}
##END:Lintian/Tags/package-contains-multiple-dpi-fonts

Self:Lintian/Tags/package-mixes-misc-and-dpi-fonts
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-mixes-misc-and-dpi-fonts.html|package-mixes-misc-and-dpi-fonts]]''':<<BR>>
 This package contains both bitmapped fonts for a specific DPI (100dpi or 75dpi) and misc bitmapped fonts. These should not be combined in the same package. Instead, the misc bitmapped fonts should be provided in a separate package with {{{-misc}}} appended to its name.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.5]]
}}}}
##END:Lintian/Tags/package-mixes-misc-and-dpi-fonts

Self:Lintian/Tags/package-contains-info-dir-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-info-dir-file.html|package-contains-info-dir-file]]''':<<BR>>
 This package contains a file named {{{dir}}} or {{{dir.old}}}, possibly compressed, in {{{/usr/share/info}}}. This is the directory (or backup) of info pages and is generated automatically by install-info when a package containing info documentation is installed. Some upstream build systems create it automatically, but it must not be included in a package since it needs to be generated dynamically based on the installed info files on the system.
}}}}
##END:Lintian/Tags/package-contains-info-dir-file

Self:Lintian/Tags/package-contains-mime-cache-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-mime-cache-file.html|package-contains-mime-cache-file]]''':<<BR>>
 This package contains a cache file generated automatically by update-mime-database when a package containing MIME-Info Database files is installed. Some upstream build systems create them automatically, but they must not be included in a package since they need to be generated dynamically based on the installed MIME-Info Database files on the system.
}}}}
##END:Lintian/Tags/package-contains-mime-cache-file

Self:Lintian/Tags/package-contains-mimeinfo.cache-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-contains-mimeinfo.cache-file.html|package-contains-mimeinfo.cache-file]]''':<<BR>>
 This package contains a file named {{{mimeinfo.cache}}}, possibly compressed, in {{{/usr/share/applications}}}. This file is generated automatically by update-desktop-database when a package containing {{{.desktop}}} files associated to MIME types is installed. Some upstream build systems create it automatically, but it must not be included in a package since it needs to be generated dynamically based on the installed .desktop files on the system.
}}}}
##END:Lintian/Tags/package-contains-mimeinfo.cache-file

Self:Lintian/Tags/package-modifies-ld.so-search-path
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-modifies-ld.so-search-path.html|package-modifies-ld.so-search-path]]''':<<BR>>
 This package installs a file in {{{/etc/ld.so.conf.d}}}, presumably to modify the search path of the run-time linker, and does not appear to be part of libc.

 Packages containing shared libraries should either install them into {{{/usr/lib}}} 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 {{{/usr/lib}}} except now conflicting library packages may cause random segfaults and difficult-to-debug problems instead of conflicts in the package manager.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.2]]
}}}}
##END:Lintian/Tags/package-modifies-ld.so-search-path

Self:Lintian/Tags/global-data-in-games-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/global-data-in-games-directory.html|global-data-in-games-directory]]''':<<BR>>
 This package contains files under {{{/usr/share/games}}}, such as desktop files, icons, pixmaps, or MIME type entries, that are global system data. The user's desktop environment will only check in the directories directly under {{{/usr/share}}} and this information should be put in the global directory even if it is for games.

 The most common cause of this problem is using a {{{--datadir=/usr/share/games}}} argument to configure or an equivalent and using the upstream installation rules. These files need to be moved into the corresponding directories directly under {{{/usr/share}}}.
}}}}
##END:Lintian/Tags/global-data-in-games-directory

Self:Lintian/Tags/duplicated-compressed-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicated-compressed-file.html|duplicated-compressed-file]]''':<<BR>>
 The given, apparently compressed, file is shipped in the package in addition to another file with the same name without the compression-method extension. Normally this indicates a mistake in the installation process of the package.
}}}}
##END:Lintian/Tags/duplicated-compressed-file

Self:Lintian/Tags/udev-rule-in-etc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/udev-rule-in-etc.html|udev-rule-in-etc]]''':<<BR>>
 This package ships a udev rule and installs it under {{{/etc/udev/rules.d}}}, which is reserved for user-installed files. The correct directory for system rules is {{{/lib/udev/rules.d}}}.

Reference(s): [[http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559208]]
}}}}
##END:Lintian/Tags/udev-rule-in-etc

Self:Lintian/Tags/obsolete-comments-style-in-php-ini
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/obsolete-comments-style-in-php-ini.html|obsolete-comments-style-in-php-ini]]''':<<BR>>
 This package ships a {{{.ini}}} file used to configure php but it has comments using the old-style comment separator {{{#}}}. Instead, the {{{;}}} separator should be used.

 Since version 5.3, the PHP interpreter warns about the use of the old style of comment separator.
}}}}
##END:Lintian/Tags/obsolete-comments-style-in-php-ini

Self:Lintian/Tags/triplet-dir-and-architecture-mismatch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/triplet-dir-and-architecture-mismatch.html|triplet-dir-and-architecture-mismatch]]''':<<BR>>
 This package contains a directory under {{{/lib}}} or {{{/usr/lib}}} which doesn't match the proper triplet for the binary package's architecture. This is very likely to be a mistake when indicating the underlying build system where the files should be installed.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.1.1]]
}}}}
##END:Lintian/Tags/triplet-dir-and-architecture-mismatch

Self:Lintian/Tags/empty-binary-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/empty-binary-package.html|empty-binary-package]]''':<<BR>>
 This binary package appears to be empty, and its description does not say that it's a meta-package or a transitional package. This is often due to problems with updating debhelper *.install files during package renames or similar problems where installation rules don't put files in the correct place.

 If the package is deliberately empty, please mention in the package long description one of the phrases "meta-package," "dummy," "dependency package," "empty package," or "virtual package."
}}}}
##END:Lintian/Tags/empty-binary-package

Self:Lintian/Tags/star-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/star-file.html|star-file]]''':<<BR>>
 The given file is literally installed as {{{*}}} (star symbol). Normally this indicates a mistake in the installation process of the package either when creating symlinks or renaming files.
}}}}
##END:Lintian/Tags/star-file

Self:Lintian/Tags/incorrect-locale-code
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/incorrect-locale-code.html|incorrect-locale-code]]''':<<BR>>
 The package appears to ship locales for a language but uses an incorrect locale code as a subdirectory of {{{/usr/share/locale}}}. This usually results in users of the intended target language not finding the locale. The language codes used in the locale directories are those from the ISO 639-1 and ISO 639-2 standards, not those usually used as TLDs (which are from the ISO 3166 standard).

 Lintian only knows about some commonly-mistaken set of incorrect locale codes.
}}}}
##END:Lintian/Tags/incorrect-locale-code

Self:Lintian/Tags/unknown-locale-code
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-locale-code.html|unknown-locale-code]]''':<<BR>>
 The package appears to ship locales for a language but uses an unknown locale code as a subdirectory of {{{/usr/share/locale}}}. This usually results in users of the intended target language not finding the locale. The language codes used in the locale directories are those from the ISO 639-1 and ISO 639-2 standards, not those usually used as TLDs (which are from the ISO 3166 standard).

 It is possible that the language code was mistyped or incorrectly guessed from the language's or country's name.

Reference(s): [[http://www.loc.gov/standards/iso639-2/php/code_list.php]]
}}}}
##END:Lintian/Tags/unknown-locale-code

########################################################################
== etcfiles ==
########################################################################

Self:Lintian/Tags/file-in-etc-not-marked-as-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-etc-not-marked-as-conffile.html|file-in-etc-not-marked-as-conffile]]''':<<BR>>
 Files in {{{/etc}}} must be marked conffiles if they are included in a package. Otherwise they should be created by maintainer scripts.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.7]]
}}}}
##END:Lintian/Tags/file-in-etc-not-marked-as-conffile

########################################################################
== menu-format ==
########################################################################

Self:Lintian/Tags/old-format-menu-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/old-format-menu-file.html|old-format-menu-file]]''':<<BR>>
 The package contains a menu file that is in the old menu file format. This format is deprecated. Convert the menu file to the new menu format. Note that lintian will not test this file for any other problems.
}}}}
##END:Lintian/Tags/old-format-menu-file

Self:Lintian/Tags/whitespace-after-continuation-character
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/whitespace-after-continuation-character.html|whitespace-after-continuation-character]]''':<<BR>>
 The menu item is split up over 2 or more lines using '\' at the end of the line to join them together. However, there is some whitespace after the '\' character, which is not guaranteed to be handled correctly. The '\' should be at the end of the line.
}}}}
##END:Lintian/Tags/whitespace-after-continuation-character

Self:Lintian/Tags/bad-test-in-menu-item
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-test-in-menu-item.html|bad-test-in-menu-item]]''':<<BR>>
 The menu file contains an item that does not start with the text "?package(somepackage):". All menu file lines must test for the existence of a package in this way.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.2]]
}}}}
##END:Lintian/Tags/bad-test-in-menu-item

Self:Lintian/Tags/unparsable-menu-item
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unparsable-menu-item.html|unparsable-menu-item]]''':<<BR>>
 An item of the menu file cannot be parsed as a series of tag=value pairs. This could be because you didn't close a set of double quotes.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.2]]
}}}}
##END:Lintian/Tags/unparsable-menu-item

Self:Lintian/Tags/pkg-not-in-package-test
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/pkg-not-in-package-test.html|pkg-not-in-package-test]]''':<<BR>>
 This menu item doesn't test to see if the package containing it is installed. The start of any menu item is a conditional testing whether the required packages are installed. Normally this conditional should always check at least the package containing it, since menu items should be included in the package that provides the application the menu refers to.

 This error usually indicates a misspelling of the package name in the menu entry or a copied menu entry from another package that doesn't apply to this one.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.2]]
}}}}
##END:Lintian/Tags/pkg-not-in-package-test

Self:Lintian/Tags/duplicated-tag-in-menu-item
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicated-tag-in-menu-item.html|duplicated-tag-in-menu-item]]''':<<BR>>
 The menu item contains two instances of the same tag. This is just a waste of space, as menu will only use one of them.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.2]]
}}}}
##END:Lintian/Tags/duplicated-tag-in-menu-item

Self:Lintian/Tags/menu-item-missing-required-tag
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-missing-required-tag.html|menu-item-missing-required-tag]]''':<<BR>>
 The menu item has a line that is missing a required tag. It's likely that the line will have no effect without this tag. {{{install-menu}}} may report this as an error during package installation.
}}}}
##END:Lintian/Tags/menu-item-missing-required-tag

Self:Lintian/Tags/menu-item-contains-unknown-tag
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-contains-unknown-tag.html|menu-item-contains-unknown-tag]]''':<<BR>>
 The menu item has a line that has a tag in it that is not one of the standard tags (needs=, section=, title=, longtitle=, command=, etc). While other tags can be used for specialized purposes, this is rare and it's more likely the tag's name is misspelled.
}}}}
##END:Lintian/Tags/menu-item-contains-unknown-tag

Self:Lintian/Tags/menu-item-uses-icon-none
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-uses-icon-none.html|menu-item-uses-icon-none]]''':<<BR>>
 The menu item has a line that uses icon=none. This is redundant and deprecated -- if there is no icon, just leave off the icon tag.
}}}}
##END:Lintian/Tags/menu-item-uses-icon-none

Self:Lintian/Tags/menu-item-needs-tag-has-unknown-value
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-needs-tag-has-unknown-value.html|menu-item-needs-tag-has-unknown-value]]''':<<BR>>
 The menu item has a line that has a needs= field with a strange value. This may be intentional, but it's probably a typo that will make menu ignore the line.
}}}}
##END:Lintian/Tags/menu-item-needs-tag-has-unknown-value

Self:Lintian/Tags/menu-item-uses-apps-games-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-uses-apps-games-section.html|menu-item-uses-apps-games-section]]''':<<BR>>
 The menu item has a line that specifies a section under "Apps/Games". This section has been moved to just "Games".

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu-policy/|menu-policy 2.1]]
}}}}
##END:Lintian/Tags/menu-item-uses-apps-games-section

Self:Lintian/Tags/menu-item-uses-apps-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-uses-apps-section.html|menu-item-uses-apps-section]]''':<<BR>>
 The menu item has a line that specifies a section under "Apps". This section has been moved to "Applications".

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu-policy/|menu-policy 2.1]]
}}}}
##END:Lintian/Tags/menu-item-uses-apps-section

Self:Lintian/Tags/menu-item-uses-windowmanagers-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-uses-windowmanagers-section.html|menu-item-uses-windowmanagers-section]]''':<<BR>>
 The menu item has a line that specifies a section under "WindowManagers". This section has been moved to "Window Managers".

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu-policy/|menu-policy 2.1]]
}}}}
##END:Lintian/Tags/menu-item-uses-windowmanagers-section

Self:Lintian/Tags/menu-item-creates-new-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-creates-new-section.html|menu-item-creates-new-section]]''':<<BR>>
 The menu item has a line that specifies an unknown section or uses a section that is intended only as a menu root, not as a section that applications should use directly. Check the spelling of the section and check the section against the list in the menu policy. (The menu sections changed as of June of 2007.)

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu-policy/|menu-policy 2.1]]
}}}}
##END:Lintian/Tags/menu-item-creates-new-section

Self:Lintian/Tags/menu-item-creates-new-root-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-creates-new-root-section.html|menu-item-creates-new-root-section]]''':<<BR>>
 The menu item has a line that specifies a new section to put a menu entry in, and this section appears right in the root menu. This is almost certainly an error. No new sections should be added to the root menu without discussion with the author of menu.
}}}}
##END:Lintian/Tags/menu-item-creates-new-root-section

Self:Lintian/Tags/menu-icon-not-in-xpm-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-icon-not-in-xpm-format.html|menu-icon-not-in-xpm-format]]''':<<BR>>
 Icons in the Debian menu system should be in XPM format.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.7]]
}}}}
##END:Lintian/Tags/menu-icon-not-in-xpm-format

Self:Lintian/Tags/menu-icon-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-icon-missing.html|menu-icon-missing]]''':<<BR>>
 This icon file couldn't be found. If the path to the icon in the menu file is an absolute path, make sure that icon exists at that path in the package. If the path is relative or a simple filename, make sure the icon is installed in {{{/usr/share/pixmaps}}}, the default location.

 If the icon is in a package this package depends on, add a lintian override for this warning. lintian cannot check icons in other packages.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.7]]
}}}}
##END:Lintian/Tags/menu-icon-missing

Self:Lintian/Tags/menu-icon-too-big
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-icon-too-big.html|menu-icon-too-big]]''':<<BR>>
 Icons in the Debian menu system should be at most 32x32 pixels (icon16x16 icons should of course be at most 16x16 pixels)

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.7]]
}}}}
##END:Lintian/Tags/menu-icon-too-big

Self:Lintian/Tags/menu-icon-cannot-be-parsed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-icon-cannot-be-parsed.html|menu-icon-cannot-be-parsed]]''':<<BR>>
 The icon file could not be parsed. Perhaps this means a bad XPM file, or perhaps it means the lintian parsing needs to be improved. If the window managers and standard tools accept the file then probably it's the latter; please file a bug on lintian then.
}}}}
##END:Lintian/Tags/menu-icon-cannot-be-parsed

Self:Lintian/Tags/su-wrapper-without--c
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/su-wrapper-without--c.html|su-wrapper-without--c]]''':<<BR>>
 The menu item command or desktop file uses an su wrapper such as su-to-root without the -c flag. This is a syntax error.

Reference(s): [[DebianMan:1/su-to-root|su-to-root(1)]]
}}}}
##END:Lintian/Tags/su-wrapper-without--c

Self:Lintian/Tags/su-to-root-with-usr-sbin
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/su-to-root-with-usr-sbin.html|su-to-root-with-usr-sbin]]''':<<BR>>
 The menu item or desktop file command uses su-to-root as /usr/sbin/su-to-root. Since sarge su-to-root is located in /usr/bin and /usr/sbin/su-to-root is only a compatibility symlink that may get dropped in the future.

 Since su-to-root is now located in /usr/bin you can use it without absolute path now.
}}}}
##END:Lintian/Tags/su-to-root-with-usr-sbin

Self:Lintian/Tags/su-wrapper-not-su-to-root
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/su-wrapper-not-su-to-root.html|su-wrapper-not-su-to-root]]''':<<BR>>
 The menu item or desktop file command uses an su wrapper other than su-to-root. On Debian systems, please use {{{su-to-root -X}}}, which will pick the correct wrapper based on what's installed on the system and the current desktop environment. Using su-to-root is also important for Live CD systems which need to use sudo rather than su. su-to-root permits global configuration to use sudo.
}}}}
##END:Lintian/Tags/su-wrapper-not-su-to-root

Self:Lintian/Tags/menu-item-needs-dwww
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-item-needs-dwww.html|menu-item-needs-dwww]]''':<<BR>>
 The menu item has needs=dwww. This is deprecated. Instead, you should register your documentation with doc-base, and dwww entries will be automatically generated.
}}}}
##END:Lintian/Tags/menu-item-needs-dwww

Self:Lintian/Tags/non-wm-in-windowmanager-menu-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-wm-in-windowmanager-menu-section.html|non-wm-in-windowmanager-menu-section]]''':<<BR>>
 The menu item is in the Window Manager section but does not needs=wm. Either it is a window manager and it should needs=wm, either it isn't and then it must be moved in another section.
}}}}
##END:Lintian/Tags/non-wm-in-windowmanager-menu-section

Self:Lintian/Tags/non-wm-module-in-wm-modules-menu-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-wm-module-in-wm-modules-menu-section.html|non-wm-module-in-wm-modules-menu-section]]''':<<BR>>
 The menu item is in the FVWM Modules or Window Maker section but does not declare that it needs a specific window manager (using the needs key in the menu file). Modules for Fvwm should have needs="fvwmmodule". Modules for WindowMaker should have needs="wmmaker".
}}}}
##END:Lintian/Tags/non-wm-module-in-wm-modules-menu-section

Self:Lintian/Tags/unquoted-string-in-menu-item
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unquoted-string-in-menu-item.html|unquoted-string-in-menu-item]]''':<<BR>>
 The menu item includes a tag with an unquoted string like section=Games instead of section="Games". This is deprecated. Use a quoted string instead.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.2]]
}}}}
##END:Lintian/Tags/unquoted-string-in-menu-item

Self:Lintian/Tags/menu-command-not-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-command-not-in-package.html|menu-command-not-in-package]]''':<<BR>>
 The menu item specifies a command which is not available in the package. In most cases this is a typo or after you moved a binary around, but forgot to update the menu file.
}}}}
##END:Lintian/Tags/menu-command-not-in-package

Self:Lintian/Tags/executable-desktop-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-desktop-file.html|executable-desktop-file]]''':<<BR>>
 The desktop entry file is marked executable. Desktop entries are regular files and should be installed mode 0644.
}}}}
##END:Lintian/Tags/executable-desktop-file

Self:Lintian/Tags/desktop-entry-file-has-crs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-file-has-crs.html|desktop-entry-file-has-crs]]''':<<BR>>
 The desktop entry file has lines ending in CRLF instead of just LF. The Desktop Entry Specification is explicit that lines should end with only LF. The CR may be taken by some software as part of the field.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/ar01s02.html]]
}}}}
##END:Lintian/Tags/desktop-entry-file-has-crs

Self:Lintian/Tags/duplicated-key-in-desktop-entry
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicated-key-in-desktop-entry.html|duplicated-key-in-desktop-entry]]''':<<BR>>
 The desktop entry contains two instances of the same key. The behavior of such desktop entries is not well-defined by the standard.

 The desktop-file-validate tool in the desktop-file-utils package is useful for checking the syntax of desktop entries.
}}}}
##END:Lintian/Tags/duplicated-key-in-desktop-entry

Self:Lintian/Tags/desktop-entry-missing-required-key
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-missing-required-key.html|desktop-entry-missing-required-key]]''':<<BR>>
 Desktop entries must contain, at a minimum, the keys Type and Name.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/ar01s05.html]]
}}}}
##END:Lintian/Tags/desktop-entry-missing-required-key

Self:Lintian/Tags/desktop-entry-contains-unknown-key
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-contains-unknown-key.html|desktop-entry-contains-unknown-key]]''':<<BR>>
 The key on this line of the desktop entry is not one of the standard keys defined in the FreeDesktop specification, not one of the legacy KDE keywords, and one that does not begin with {{{X-}}}. It's most likely that the key was misspelled.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/ar01s05.html]]
}}}}
##END:Lintian/Tags/desktop-entry-contains-unknown-key

Self:Lintian/Tags/desktop-entry-contains-deprecated-key
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-contains-deprecated-key.html|desktop-entry-contains-deprecated-key]]''':<<BR>>
 The key on this line of the desktop entry has been deprecated in the FreeDesktop specification.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/apc.html]]
}}}}
##END:Lintian/Tags/desktop-entry-contains-deprecated-key

Self:Lintian/Tags/desktop-entry-contains-encoding-key
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-contains-encoding-key.html|desktop-entry-contains-encoding-key]]''':<<BR>>
 The Encoding key is now deprecated by the FreeDesktop standard and all strings are required to be encoded in UTF-8. This desktop entry explicitly specifies an Encoding of UTF-8, which is harmless but no longer necessary.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/apc.html]]
}}}}
##END:Lintian/Tags/desktop-entry-contains-encoding-key

Self:Lintian/Tags/desktop-entry-lacks-main-category
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-lacks-main-category.html|desktop-entry-lacks-main-category]]''':<<BR>>
 The categories for this desktop entry do not contain any Main Categories, only Additional Categories. Additional Categories should only be used on conjunction with one or more Main Categories.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/menu-spec/1.0/apa.html]]
}}}}
##END:Lintian/Tags/desktop-entry-lacks-main-category

Self:Lintian/Tags/desktop-entry-uses-reserved-category
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-uses-reserved-category.html|desktop-entry-uses-reserved-category]]''':<<BR>>
 This desktop entry includes a Reserved Category, one which has a desktop-specific meaning that has not yet been standardized, but does not include an OnlyShowIn key. Desktop entries using a Reserved Category must include an OnlyShowIn key limiting the entry to those environments that support the category.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/menu-spec/1.0/apa.html]]
}}}}
##END:Lintian/Tags/desktop-entry-uses-reserved-category

Self:Lintian/Tags/desktop-entry-invalid-category
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-invalid-category.html|desktop-entry-invalid-category]]''':<<BR>>
 This desktop entry lists a category that is not one of the registered Main or Additional Categories in the FreeDesktop specification. Note that case is significant and whitespace is only allowed immediately before and after the equal sign in the Category key, not elsewhere in the field.

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/menu-spec/1.0/apa.html]]
}}}}
##END:Lintian/Tags/desktop-entry-invalid-category

Self:Lintian/Tags/desktop-command-not-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-command-not-in-package.html|desktop-command-not-in-package]]''':<<BR>>
 The desktop entry specifies a command that is not available in the package. In most cases, this is a typo or a forgotten update of the desktop file after the install location of the binary was changed. A desktop file for a command should be included in the same package as that command.
}}}}
##END:Lintian/Tags/desktop-command-not-in-package

Self:Lintian/Tags/desktop-contains-deprecated-header
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-contains-deprecated-header.html|desktop-contains-deprecated-header]]''':<<BR>>
 The header on this line of the desktop entry has been deprecated in the FreeDesktop specification. If the header is "KDE Desktop Entry", the right fix is normally changing it to "Desktop Entry".

 The desktop-file-validate took in the desktop-file-utils package is useful for checking the syntax of desktop entries.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/apc.html]]
}}}}
##END:Lintian/Tags/desktop-contains-deprecated-header

Self:Lintian/Tags/deprecated-kdelnk-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/deprecated-kdelnk-file.html|deprecated-kdelnk-file]]''':<<BR>>
 kdelnk files were used by KDE 1 and since KDE 2 desktop files are used instead. Renaming the file and removing the deprecated header and keys is often all that needs to be done.

Reference(s): [[http://standards.freedesktop.org/desktop-entry-spec/1.0/apc.html]]
}}}}
##END:Lintian/Tags/deprecated-kdelnk-file

Self:Lintian/Tags/desktop-entry-limited-to-environments
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/desktop-entry-limited-to-environments.html|desktop-entry-limited-to-environments]]''':<<BR>>
 This desktop entry uses OnlyShowIn to limit the environments in which it's displayed but lists multiple environments. This is often a sign of a desktop file written assuming that only GNOME, KDE, and Xfce are in use and the desktop file intended to exclude one of them. This unintentionally hides the application from desktop environments such as LXDE where it would work fine. If this application supports any desktop environment except some specific ones, it should list the unsupported environments in the NotShowIn key instead.
}}}}
##END:Lintian/Tags/desktop-entry-limited-to-environments

########################################################################
== shared-libs ==
########################################################################

Self:Lintian/Tags/shlib-with-executable-bit
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-with-executable-bit.html|shlib-with-executable-bit]]''':<<BR>>
 Shared libraries should be mode 0644.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1]]
}}}}
##END:Lintian/Tags/shlib-with-executable-bit

Self:Lintian/Tags/shlib-with-bad-permissions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-with-bad-permissions.html|shlib-with-bad-permissions]]''':<<BR>>
 Shared libraries should be mode 0644.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1]]
}}}}
##END:Lintian/Tags/shlib-with-bad-permissions

Self:Lintian/Tags/shlib-with-non-pic-code
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-with-non-pic-code.html|shlib-with-non-pic-code]]''':<<BR>>
 The listed shared libraries contain object code that was compiled without -fPIC. All object code in shared libraries should be recompiled separately from the static libraries with the -fPIC option.

 Another common mistake that causes this problem is linking with {{{gcc -Wl,-shared}}} instead of {{{gcc -shared}}}.

 In some cases, exceptions to this rule are warranted. If this is such a case, follow the procedure outlined in Policy and then please document the exception by adding a lintian override to this package.

 To check whether a shared library has this problem, run {{{readelf -d}}} on the shared library. If a tag of type TEXTREL is present, the shared library contains non-PIC code.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.2]]
}}}}
##END:Lintian/Tags/shlib-with-non-pic-code

Self:Lintian/Tags/shlib-without-versioned-soname
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-without-versioned-soname.html|shlib-without-versioned-soname]]''':<<BR>>
 The listed shared library in a public library directory has an SONAME that does not contain any versioning information, either after the {{{.so}}} or before it and set off by a hyphen. It cannot therefore be represented in the shlibs system, and if linked by binaries its interface cannot safely change. There is no backward-compatible way to migrate programs linked against it to a new ABI.

 Normally, this means the shared library is a private library for a particular application and is not meant for general use. Policy recommends that such libraries be installed in a subdirectory of {{{/usr/lib}}} rather than in a public shared library directory.

 To view the SONAME of a shared library, run {{{readelf -d}}} on the shared library and look for the tag of type SONAME.

 There are some special stub libraries or special-purpose shared objects for which an ABI version is not meaningful. If this is one of those cases, please add an override.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.2]], [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/shlib-without-versioned-soname

Self:Lintian/Tags/ldconfig-symlink-missing-for-shlib
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ldconfig-symlink-missing-for-shlib.html|ldconfig-symlink-missing-for-shlib]]''':<<BR>>
 The package should not only include the shared library itself, but also the symbolic link which ldconfig would produce. (This is necessary, so that the link gets removed by dpkg automatically when the package gets removed.) If the symlink is in the package, check that the SONAME of the library matches the info in the shlibs file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1]]
}}}}
##END:Lintian/Tags/ldconfig-symlink-missing-for-shlib

Self:Lintian/Tags/ldconfig-symlink-before-shlib-in-deb
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ldconfig-symlink-before-shlib-in-deb.html|ldconfig-symlink-before-shlib-in-deb]]''':<<BR>>
 In the package contents list, the shared library has to come before any symbolic links referencing the shared library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1]]
}}}}
##END:Lintian/Tags/ldconfig-symlink-before-shlib-in-deb

Self:Lintian/Tags/dev-pkg-without-shlib-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dev-pkg-without-shlib-symlink.html|dev-pkg-without-shlib-symlink]]''':<<BR>>
 A "-dev" package is supposed to install a "libsomething.so" symbolic link referencing the corresponding shared library. Notice how the link name doesn't include the version number -- this is because such a link is used by the linker when other programs are built against this shared library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.4]]
}}}}
##END:Lintian/Tags/dev-pkg-without-shlib-symlink

Self:Lintian/Tags/non-dev-pkg-with-shlib-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-dev-pkg-with-shlib-symlink.html|non-dev-pkg-with-shlib-symlink]]''':<<BR>>
 Although this package is not a "-dev" package, it installs a "libsomething.so" symbolic link referencing the corresponding shared library. When the link doesn't include the version number, it is used by the linker when other programs are built against this shared library.

 Shared libraries are supposed to place such symbolic links in their respective "-dev" packages, so it is a bug to include it with the main library package.

 However, if this is a small package which includes the runtime and the development libraries, this is not a bug. In the latter case, please override this warning.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.4]]
}}}}
##END:Lintian/Tags/non-dev-pkg-with-shlib-symlink

Self:Lintian/Tags/preinst-calls-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/preinst-calls-ldconfig.html|preinst-calls-ldconfig]]''':<<BR>>
 The preinst script calls ldconfig. Calls to ldconfig should only be in postinst and postrm scripts.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/preinst-calls-ldconfig

Self:Lintian/Tags/prerm-calls-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/prerm-calls-ldconfig.html|prerm-calls-ldconfig]]''':<<BR>>
 The prerm script calls ldconfig. Calls to ldconfig should only be in postinst and postrm scripts.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/prerm-calls-ldconfig

Self:Lintian/Tags/postrm-unsafe-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-unsafe-ldconfig.html|postrm-unsafe-ldconfig]]''':<<BR>>
 The postrm script calls ldconfig unsafely. The postrm must only call ldconfig when given the argument "remove".

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/postrm-unsafe-ldconfig

Self:Lintian/Tags/no-shlibs-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-shlibs-control-file.html|no-shlibs-control-file]]''':<<BR>>
 Although the package includes a shared library, the package does not have a shlibs control file. If this is intentional, please override this error.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/no-shlibs-control-file

Self:Lintian/Tags/pkg-has-shlibs-control-file-but-no-actual-shared-libs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/pkg-has-shlibs-control-file-but-no-actual-shared-libs.html|pkg-has-shlibs-control-file-but-no-actual-shared-libs]]''':<<BR>>
 Although the package does not include any shared libraries, it does have a shlibs control file. If you did include a shared library, check that the SONAME of the library is set and that it matches the contents of the shlibs file.

 SONAMEs are set with something like {{{gcc -Wl,-soname,libfoo.so.0}}}, where 0 is the major version of the library. If your package uses libtool, then libtool invoked with the right options should be doing this.
}}}}
##END:Lintian/Tags/pkg-has-shlibs-control-file-but-no-actual-shared-libs

Self:Lintian/Tags/duplicate-entry-in-shlibs-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-entry-in-shlibs-control-file.html|duplicate-entry-in-shlibs-control-file]]''':<<BR>>
 The shlibs control file contains a duplicate entry.
}}}}
##END:Lintian/Tags/duplicate-entry-in-shlibs-control-file

Self:Lintian/Tags/shlib-missing-in-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-missing-in-control-file.html|shlib-missing-in-control-file]]''':<<BR>>
 The package contains a shared library that is not listed in the shlibs control file. If this is intentional, please override this error.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/shlib-missing-in-control-file

Self:Lintian/Tags/unused-shlib-entry-in-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unused-shlib-entry-in-control-file.html|unused-shlib-entry-in-control-file]]''':<<BR>>
 The shlibs control file contains an entry for a shared library that is not installed by this package.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/unused-shlib-entry-in-control-file

Self:Lintian/Tags/shlibs-declares-dependency-on-other-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlibs-declares-dependency-on-other-package.html|shlibs-declares-dependency-on-other-package]]''':<<BR>>
 This package declares in its shlibs control file either a dependency on some other package not listed in the Provides of this package or on a version of this package that the package version doesn't satisfy.

 Packages should normally only list in their shlibs control file the shared libraries included in that package, and therefore the dependencies listed there should normally be satisfied by either the package itself or one of its Provides.

 In unusual circumstances where it's necessary to declare more complex dependencies in the shlibs control file, please add a lintian override for this warning.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/shlibs-declares-dependency-on-other-package

Self:Lintian/Tags/ldconfig-symlink-referencing-wrong-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ldconfig-symlink-referencing-wrong-file.html|ldconfig-symlink-referencing-wrong-file]]''':<<BR>>
 The symbolic link references the wrong file. (It should reference the shared library.)

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1]]
}}}}
##END:Lintian/Tags/ldconfig-symlink-referencing-wrong-file

Self:Lintian/Tags/ldconfig-symlink-is-not-a-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ldconfig-symlink-is-not-a-symlink.html|ldconfig-symlink-is-not-a-symlink]]''':<<BR>>
 The package installs a file with the name, ldconfig would use for the symbolic link to reference the shared library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1]]
}}}}
##END:Lintian/Tags/ldconfig-symlink-is-not-a-symlink

Self:Lintian/Tags/postinst-has-useless-call-to-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-has-useless-call-to-ldconfig.html|postinst-has-useless-call-to-ldconfig]]''':<<BR>>
 The postinst script calls ldconfig even though no shared libraries are installed in a directory controlled by the dynamic library loader.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/postinst-has-useless-call-to-ldconfig

Self:Lintian/Tags/udeb-postinst-must-not-call-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/udeb-postinst-must-not-call-ldconfig.html|udeb-postinst-must-not-call-ldconfig]]''':<<BR>>
 The postinst script calls ldconfig, which is an error in udebs. ldconfig is not available and not needed in debian-installer
}}}}
##END:Lintian/Tags/udeb-postinst-must-not-call-ldconfig

Self:Lintian/Tags/postrm-has-useless-call-to-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-has-useless-call-to-ldconfig.html|postrm-has-useless-call-to-ldconfig]]''':<<BR>>
 The postrm script calls ldconfig even though no shared libraries are installed in a directory controlled by the dynamic library loader.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/postrm-has-useless-call-to-ldconfig

Self:Lintian/Tags/postinst-must-call-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-must-call-ldconfig.html|postinst-must-call-ldconfig]]''':<<BR>>
 The package installs shared libraries in a directory controlled by the dynamic library loader. Therefore, the package must call "ldconfig" in its postinst script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/postinst-must-call-ldconfig

Self:Lintian/Tags/postrm-should-call-ldconfig
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-should-call-ldconfig.html|postrm-should-call-ldconfig]]''':<<BR>>
 The package installs shared libraries in a directory controlled by the dynamic library loader. Therefore, the package should call "ldconfig" in its postrm script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.1.1]]
}}}}
##END:Lintian/Tags/postrm-should-call-ldconfig

Self:Lintian/Tags/sharedobject-in-library-directory-missing-soname
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/sharedobject-in-library-directory-missing-soname.html|sharedobject-in-library-directory-missing-soname]]''':<<BR>>
 A shared object was identified in a library directory (a directory in the standard linker path) which doesn't have a SONAME. This is usually an error.

 SONAMEs are set with something like {{{gcc -Wl,-soname,libfoo.so.0}}}, where 0 is the major version of the library. If your package uses libtool, then libtool invoked with the right options should be doing this.

 To view the SONAME of a shared library, run {{{readelf -d}}} on the shared library and look for the tag of type SONAME.
}}}}
##END:Lintian/Tags/sharedobject-in-library-directory-missing-soname

Self:Lintian/Tags/shlib-without-PT_GNU_STACK-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-without-PT_GNU_STACK-section.html|shlib-without-PT_GNU_STACK-section]]''':<<BR>>
 The listed shared libraries lacks a PT_GNU_STACK section. This forces the dynamic linker to make the stack executable.

 The shared lib is linked either with a non-GNU linker or a linker which is very old. This problem can be fixed with a rebuild.

 To see whether a shared library has this section, run {{{readelf -l}}} on it and look for a program header of type GNU_STACK.
}}}}
##END:Lintian/Tags/shlib-without-PT_GNU_STACK-section

Self:Lintian/Tags/shlib-with-executable-stack
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-with-executable-stack.html|shlib-with-executable-stack]]''':<<BR>>
 The listed shared libraries declares the stack as executable.

 Executable stack is usually an error as it is only needed if the code contains GCC trampolines or similar constructs which uses code on the stack. One possible source for false positives are object files built from assembler files which don't define a proper .note.GNU-stack section.

 To see the permissions on the stack, run {{{readelf -l}}} on the shared library and look for the program header of type GNU_STACK. In the flag column, there should not be an E flag set.
}}}}
##END:Lintian/Tags/shlib-with-executable-stack

Self:Lintian/Tags/symbols-file-contains-current-version-with-debian-revision
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symbols-file-contains-current-version-with-debian-revision.html|symbols-file-contains-current-version-with-debian-revision]]''':<<BR>>
 Debian revisions should be stripped from versions in symbols files. Not doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo << 1.0-1 while 1.0-1~bpo >= 1.0). If the debian revision can't be stripped because the symbol really appeared between two specific Debian revisions, you should postfix the version with a single "~" (example: 1.0-3~ if the symbol appeared in 1.0-3).

 This problem normally means that the symbols were added automatically by dpkg-gensymbols. dpkg-gensymbols uses the full version number for the dependency associated to any new symbol that it detects. The maintainer must update the {{{debian/<package>.symbols}}} file by adding the new symbols with the corresponding upstream version.
}}}}
##END:Lintian/Tags/symbols-file-contains-current-version-with-debian-revision

Self:Lintian/Tags/symbols-file-contains-debian-revision
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symbols-file-contains-debian-revision.html|symbols-file-contains-debian-revision]]''':<<BR>>
 Debian revisions should be stripped from versions in symbols files. Not doing so leads to dependencies unsatisfiable by backports (1.0-1~bpo << 1.0-1 while 1.0-1~bpo >= 1.0). If the debian revision can't be stripped because the symbol really appeared between two specific Debian revisions, you should postfix the version with a single "~" (example: 1.0-3~ if the symbol appeared in 1.0-3).

Reference(s): [[DebianMan:1/dpkg-gensymbols|dpkg-gensymbols(1)]], [[http://wiki.debian.org/UsingSymbolsFiles]]
}}}}
##END:Lintian/Tags/symbols-file-contains-debian-revision

Self:Lintian/Tags/syntax-error-in-symbols-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/syntax-error-in-symbols-file.html|syntax-error-in-symbols-file]]''':<<BR>>
 The symbols file contains an entry that does not follow the syntax rules for symbols files.

 This may be due to the entry appearing out of sequence.

Reference(s): [[DebianMan:5/deb-symbols|deb-symbols(5)]]
}}}}
##END:Lintian/Tags/syntax-error-in-symbols-file

Self:Lintian/Tags/duplicate-entry-in-symbols-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-entry-in-symbols-control-file.html|duplicate-entry-in-symbols-control-file]]''':<<BR>>
 The symbols control file contains a duplicate entry.
}}}}
##END:Lintian/Tags/duplicate-entry-in-symbols-control-file

Self:Lintian/Tags/no-symbols-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-symbols-control-file.html|no-symbols-control-file]]''':<<BR>>
 Although the package includes a shared library, the package does not have a symbols control file.

 dpkg can use symbols files in order to generate more accurate library dependencies for applications, based on the symbols from the library that are actually used by the application.

Reference(s): [[DebianMan:1/dpkg-gensymbols|dpkg-gensymbols(1)]], [[http://wiki.debian.org/UsingSymbolsFiles]]
}}}}
##END:Lintian/Tags/no-symbols-control-file

Self:Lintian/Tags/pkg-has-symbols-control-file-but-no-shared-libs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/pkg-has-symbols-control-file-but-no-shared-libs.html|pkg-has-symbols-control-file-but-no-shared-libs]]''':<<BR>>
 Although the package does not include any shared libraries, it does have a symbols control file. If you did include a shared library, check that the SONAME of the library is set and that it matches the contents of the symbols file.

 SONAMEs are set with something like {{{gcc -Wl,-soname,libfoo.so.0}}}, where 0 is the major version of the library. If your package uses libtool, then libtool invoked with the right options should be doing this.
}}}}
##END:Lintian/Tags/pkg-has-symbols-control-file-but-no-shared-libs

Self:Lintian/Tags/shlib-missing-in-symbols-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-missing-in-symbols-control-file.html|shlib-missing-in-symbols-control-file]]''':<<BR>>
 The package contains a shared library that is not listed in the symbols control file. This may not be a problem if, for example, the library is a C++ library.
}}}}
##END:Lintian/Tags/shlib-missing-in-symbols-control-file

Self:Lintian/Tags/unused-shlib-entry-in-symbols-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unused-shlib-entry-in-symbols-control-file.html|unused-shlib-entry-in-symbols-control-file]]''':<<BR>>
 The symbols control file contains an entry for a shared library that is not installed by this package.
}}}}
##END:Lintian/Tags/unused-shlib-entry-in-symbols-control-file

Self:Lintian/Tags/symbols-declares-dependency-on-other-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symbols-declares-dependency-on-other-package.html|symbols-declares-dependency-on-other-package]]''':<<BR>>
 This package declares in its symbols control file a dependency on some other package (and not one listed in the Provides of this package).

 Packages should normally only list in their symbols control file the shared libraries included in that package, and therefore the dependencies listed there should normally be satisfied by either the package itself or one of its Provides.

 In unusual circumstances where it's necessary to declare more complex dependencies in the symbols control file, please add a lintian override for this warning.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/symbols-declares-dependency-on-other-package

Self:Lintian/Tags/invalid-template-id-in-symbols-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/invalid-template-id-in-symbols-file.html|invalid-template-id-in-symbols-file]]''':<<BR>>
 The symbol definition refers to an alternative dependency template which is not defined for the library containing the symbol.

 The first alternative dependency template for a library the id number of 1, with the ids of subsequent alternative templates increasing in sequence.
}}}}
##END:Lintian/Tags/invalid-template-id-in-symbols-file

Self:Lintian/Tags/unknown-meta-field-in-symbols-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-meta-field-in-symbols-file.html|unknown-meta-field-in-symbols-file]]''':<<BR>>
 The symbols control file contains an unknown meta-information field.

 A list of currently supported fields may be found in deb-control(5).

Reference(s): [[DebianMan:5/deb-control|deb-control(5)]]
}}}}
##END:Lintian/Tags/unknown-meta-field-in-symbols-file

Self:Lintian/Tags/symbols-declared-but-not-shlib
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/symbols-declared-but-not-shlib.html|symbols-declared-but-not-shlib]]''':<<BR>>
 The symbols control file contains dependency and symbol information for a shared library which is not listed in the shlibs control file.
}}}}
##END:Lintian/Tags/symbols-declared-but-not-shlib

Self:Lintian/Tags/shlib-calls-exit
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shlib-calls-exit.html|shlib-calls-exit]]''':<<BR>>
 The listed shared library calls the C library exit() or _exit() functions.

 In the case of an error, the library should instead return an appropriate error code to the calling program which can then determine how to handle the error, including performing any required clean-up.

 In most cases, removing the call should be discussed with upstream, particularly as it may produce an ABI change.
}}}}
##END:Lintian/Tags/shlib-calls-exit

Self:Lintian/Tags/incorrect-libdir-in-la-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/incorrect-libdir-in-la-file.html|incorrect-libdir-in-la-file]]''':<<BR>>
 The given .la file points to a libdir other than the path where it is installed. This can be caused by resetting {{{prefix}}} at make install time instead of using {{{DESTDIR}}}. The incorrect path will cause packages linking to this library using libtool to build incorrectly (adding incorrect paths to RPATH, for example).
}}}}
##END:Lintian/Tags/incorrect-libdir-in-la-file

########################################################################
== infofiles ==
########################################################################

Self:Lintian/Tags/info-document-not-compressed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/info-document-not-compressed.html|info-document-not-compressed]]''':<<BR>>
 Info documents should be compressed with {{{gzip -9}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.2]]
}}}}
##END:Lintian/Tags/info-document-not-compressed

Self:Lintian/Tags/info-document-not-compressed-with-gzip
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/info-document-not-compressed-with-gzip.html|info-document-not-compressed-with-gzip]]''':<<BR>>
 Info documents should be compressed with {{{gzip -9}}}. This file ends in {{{.gz}}} but doesn't appear to be a gzip-compressed file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.2]]
}}}}
##END:Lintian/Tags/info-document-not-compressed-with-gzip

Self:Lintian/Tags/info-document-not-compressed-with-max-compression
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/info-document-not-compressed-with-max-compression.html|info-document-not-compressed-with-max-compression]]''':<<BR>>
 Info documents should be compressed with {{{gzip -9}}}. This file is compressed with gzip, but without using maximum compression.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.2]]
}}}}
##END:Lintian/Tags/info-document-not-compressed-with-max-compression

Self:Lintian/Tags/info-document-has-wrong-extension
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/info-document-has-wrong-extension.html|info-document-has-wrong-extension]]''':<<BR>>
 The info document has an extension other than info*.gz.
}}}}
##END:Lintian/Tags/info-document-has-wrong-extension

Self:Lintian/Tags/info-document-missing-dir-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/info-document-missing-dir-section.html|info-document-missing-dir-section]]''':<<BR>>
 This info document has no INFO-DIR-SECTION line. {{{install-info}}} will be unable to determine the section into which this info page should be put. The best solution is to add a line like:

   @dircategory Development

 to the texinfo source so that the generated info file will contain a section. See {{{/usr/share/info/dir}}} for sections to choose from. You will have to ensure that the build process builds new info files rather than using ones built by upstream.
}}}}
##END:Lintian/Tags/info-document-missing-dir-section

Self:Lintian/Tags/info-document-missing-dir-entry
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/info-document-missing-dir-entry.html|info-document-missing-dir-entry]]''':<<BR>>
 This info document has no directory entry. This is text between START-INFO-DIR-ENTRY and END-INFO-DIR-ENTRY lines which is copied into the {{{dir}}} file in {{{/usr/share/info}}} by {{{install-info}}}. The best solution is to add lines like:

   @direntry * foo: (foo). Foo creator and editor @end direntry

 to the texinfo source so that the generated info file will contain an appropriate entry. You will have to ensure that the build process builds new info files rather than using ones built by upstream.
}}}}
##END:Lintian/Tags/info-document-missing-dir-entry

Self:Lintian/Tags/missing-dependency-on-install-info
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-dependency-on-install-info.html|missing-dependency-on-install-info]]''':<<BR>>
 This package appears to contain at least one info document but does not depend on {{{dpkg (>= 1.15.4) | install-info}}} as recommended by Policy. This dependency is needed for the transition to triggerized install-info to correctly build the info directory during partial upgrades from lenny.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.2]]
}}}}
##END:Lintian/Tags/missing-dependency-on-install-info

########################################################################
== copyright-file ==
########################################################################

Self:Lintian/Tags/no-copyright-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-copyright-file.html|no-copyright-file]]''':<<BR>>
 Each binary package has to include a plain file /usr/share/doc/pkg/copyright

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/no-copyright-file

Self:Lintian/Tags/copyright-refers-to-old-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-old-directory.html|copyright-refers-to-old-directory]]''':<<BR>>
 The common licenses (GPL, BSD, Artistic, etc) have been moved from /usr/doc/copyright to /usr/share/common-licenses. Copyright files should be updated.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-refers-to-old-directory

Self:Lintian/Tags/copyright-file-compressed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-file-compressed.html|copyright-file-compressed]]''':<<BR>>
 The copyright file /usr/share/doc/pkg/copyright must not be compressed.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-file-compressed

Self:Lintian/Tags/copyright-file-is-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-file-is-symlink.html|copyright-file-is-symlink]]''':<<BR>>
 The copyright file /usr/share/doc/pkg/copyright must not be a symbolic link.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-file-is-symlink

Self:Lintian/Tags/copyright-file-contains-full-gpl-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-file-contains-full-gpl-license.html|copyright-file-contains-full-gpl-license]]''':<<BR>>
 The copyright file /usr/share/doc/pkg/copyright contains the complete text of the GPL v1, v2, or v3. It should refer to the file {{{/usr/share/common-licenses/GPL-1}}}, {{{GPL-2}}}, or {{{GPL-3}}} instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-file-contains-full-gpl-license

Self:Lintian/Tags/copyright-file-contains-full-gfdl-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-file-contains-full-gfdl-license.html|copyright-file-contains-full-gfdl-license]]''':<<BR>>
 The copyright file /usr/share/doc/pkg/copyright contains the complete text of the GFDL v1.2. It should refer to the file {{{/usr/share/common-licenses/GFDL-1.2}}} instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-file-contains-full-gfdl-license

Self:Lintian/Tags/copyright-file-contains-full-apache-2-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-file-contains-full-apache-2-license.html|copyright-file-contains-full-apache-2-license]]''':<<BR>>
 The copyright file /usr/share/doc/pkg/copyright contains the complete text of the Apache 2.0 license. It should refer to the file {{{/usr/share/common-licenses/Apache-2.0}}} instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-file-contains-full-apache-2-license

Self:Lintian/Tags/usr-share-doc-symlink-without-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/usr-share-doc-symlink-without-dependency.html|usr-share-doc-symlink-without-dependency]]''':<<BR>>
 If the package installs a symbolic link {{{/usr/share/doc/pkg1 -> pkg2}}}, then pkg1 must depend on pkg2 directory, with the same version as pkg1.

 Adding the dependency just to fix this bug is often not a good solution. Usually, it's better to include a real {{{/usr/share/doc/pkg1}}} directory within pkg1 and copy the copyright file into that directory.

 Transitive dependencies are not allowed here. In other words, if the documentation directory is shipped in pkg3 and pkg1 depends on pkg2, which in turn depends on pkg3, that's still an error. Copyright file extractors are not required to go more than one level deep when resolving dependencies. Each package should have a direct dependency on the package which includes its documentation directory.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/usr-share-doc-symlink-without-dependency

Self:Lintian/Tags/usr-share-doc-symlink-to-foreign-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/usr-share-doc-symlink-to-foreign-package.html|usr-share-doc-symlink-to-foreign-package]]''':<<BR>>
 If the package installs a symbolic link {{{/usr/share/doc/pkg1 -> pkg2}}}, then pkg1 and pkg2 must both come from the same source package.

 The best solution is probably to stop symlinking the {{{/usr/share/doc}}} directory for this package and instead include a real /usr/share/doc/pkg1 directory within pkg1 with the appropriate contents (such as the {{{copyright}}} and {{{changelog.Debian.gz}}} files).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/usr-share-doc-symlink-to-foreign-package

Self:Lintian/Tags/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package.html|cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package]]''':<<BR>>
 There is a symlink /usr/share/doc/pkg1 -> pkg2 in your package. This means that pkg1 and pkg2 must both come from the same source package. I can't check this right now however since I'm only checking a binary package and I only can check this when I'm checking both the binary and the corresponding source package.
}}}}
##END:Lintian/Tags/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package

Self:Lintian/Tags/old-style-copyright-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/old-style-copyright-file.html|old-style-copyright-file]]''':<<BR>>
 The package installs a /usr/doc/copyright/pkg file. Instead, you should place the copyright file in /usr/share/doc/pkg/copyright.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/old-style-copyright-file

Self:Lintian/Tags/old-fsf-address-in-copyright-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/old-fsf-address-in-copyright-file.html|old-fsf-address-in-copyright-file]]''':<<BR>>
 The /usr/share/doc/pkg/copyright file refers to the old postal address of the Free Software Foundation (FSF). The new address is:

   Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
}}}}
##END:Lintian/Tags/old-fsf-address-in-copyright-file

Self:Lintian/Tags/helper-templates-in-copyright
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/helper-templates-in-copyright.html|helper-templates-in-copyright]]''':<<BR>>
 The /usr/share/doc/pkg/copyright file still contains template markers from a packaging helper. Please fill in the actual license, upstream copyright holders, and download information about the package and remove any remaining templates generated by the packaging helper.
}}}}
##END:Lintian/Tags/helper-templates-in-copyright

Self:Lintian/Tags/copyright-refers-to-compressed-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-compressed-license.html|copyright-refers-to-compressed-license]]''':<<BR>>
 The /usr/share/doc/pkg/copyright file refers to a standard license /usr/share/common-licenses/{GPL,LGPL,Artistic,BSD}.gz as a compressed file. Please update the reference (the licenses are installed uncompressed).
}}}}
##END:Lintian/Tags/copyright-refers-to-compressed-license

Self:Lintian/Tags/usr-share-doc-symlink-points-outside-of-usr-share-doc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/usr-share-doc-symlink-points-outside-of-usr-share-doc.html|usr-share-doc-symlink-points-outside-of-usr-share-doc]]''':<<BR>>
 The /usr/share/doc/pkg symbolic link is pointing to a directory outside of {{{/usr/share/doc}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/usr-share-doc-symlink-points-outside-of-usr-share-doc

Self:Lintian/Tags/copyright-does-not-refer-to-common-license-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-does-not-refer-to-common-license-file.html|copyright-does-not-refer-to-common-license-file]]''':<<BR>>
 If your package uses any one of the licenses in {{{/usr/share/common-licenses}}}, the copyright file should refer to files therein.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-does-not-refer-to-common-license-file

Self:Lintian/Tags/copyright-refers-to-incorrect-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-incorrect-directory.html|copyright-refers-to-incorrect-directory]]''':<<BR>>
 In the directory name /usr/share/common-licenses, licenses is spelled with an "s", not as licences with a "c".

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-refers-to-incorrect-directory

Self:Lintian/Tags/copyright-file-lacks-pointer-to-perl-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-file-lacks-pointer-to-perl-license.html|copyright-file-lacks-pointer-to-perl-license]]''':<<BR>>
 If your package is released under the same terms as Perl itself, it should refer to the Artistic and GPL license files in the {{{/usr/share/common-licenses}}} directory.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-file-lacks-pointer-to-perl-license

Self:Lintian/Tags/copyright-should-refer-to-common-license-file-for-gpl
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-should-refer-to-common-license-file-for-gpl.html|copyright-should-refer-to-common-license-file-for-gpl]]''':<<BR>>
 The strings "GNU General Public License" or "GPL" appear in the copyright file for this package, but the copyright file does not reference {{{/usr/share/common-licenses}}} as the location of the GPL on Debian systems.

 If the package uses some other license that just mentions the GPL and that Lintian should detect as an exception, please file a Lintian bug. If the copyright file must mention the GPL for reasons other than stating the license of the package, please add a Lintian override.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-should-refer-to-common-license-file-for-gpl

Self:Lintian/Tags/copyright-should-refer-to-common-license-file-for-gfdl
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-should-refer-to-common-license-file-for-gfdl.html|copyright-should-refer-to-common-license-file-for-gfdl]]''':<<BR>>
 The strings "GNU Free Documentation License" or "GFDL" appear in the copyright file for this package, but the copyright file does not reference {{{/usr/share/common-licenses}}} as the location of the GFDL on Debian systems.

 If the package uses some other license that just mentions the GFDL and that Lintian should detect as an exception, please file a Lintian bug. If the copyright file must mention the GFDL for reasons other than stating the license of the package, please add a Lintian override.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-should-refer-to-common-license-file-for-gfdl

Self:Lintian/Tags/copyright-should-refer-to-common-license-file-for-lgpl
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-should-refer-to-common-license-file-for-lgpl.html|copyright-should-refer-to-common-license-file-for-lgpl]]''':<<BR>>
 The strings "GNU Lesser General Public License", "GNU Library General Public License", or "LGPL" appear in the copyright file for this package, but the copyright file does not reference {{{/usr/share/common-licenses}}} as the location of the LGPL on Debian systems.

 If the package uses some other license that just mentions the LGPL and that Lintian should detect as an exception, please file a Lintian bug. If the copyright file must mention the LGPL for reasons other than stating the license of the package, please add a Lintian override.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-should-refer-to-common-license-file-for-lgpl

Self:Lintian/Tags/copyright-has-url-from-dh_make-boilerplate
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-has-url-from-dh_make-boilerplate.html|copyright-has-url-from-dh_make-boilerplate]]''':<<BR>>
 There is "url://example.com" in your copyright file. This was most likely a remnant from the dh_make template.

 Make sure you include the real location where you obtained the upstream sources (if any).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-has-url-from-dh_make-boilerplate

Self:Lintian/Tags/debian-copyright-file-uses-obsolete-national-encoding
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-copyright-file-uses-obsolete-national-encoding.html|debian-copyright-file-uses-obsolete-national-encoding]]''':<<BR>>
 The Debian copyright file should be valid UTF-8, an encoding of the Unicode character set.

 There are many ways to convert a copyright file from an obsoleted encoding like ISO-8859-1; you may for example use "iconv" like:

  $ iconv -f ISO-8859-1 -t UTF-8 copyright > copyright.new $ mv copyright.new copyright
}}}}
##END:Lintian/Tags/debian-copyright-file-uses-obsolete-national-encoding

Self:Lintian/Tags/copyright-contains-dh_make-todo-boilerplate
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-contains-dh_make-todo-boilerplate.html|copyright-contains-dh_make-todo-boilerplate]]''':<<BR>>
 The string "Please also look if..." appears in the copyright file, which indicates that you either didn't check the whole source to find additional copyright/license, or that you didn't remove that paragraph after having done so.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-contains-dh_make-todo-boilerplate

Self:Lintian/Tags/copyright-contains-dh-make-perl-boilerplate
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-contains-dh-make-perl-boilerplate.html|copyright-contains-dh-make-perl-boilerplate]]''':<<BR>>
 The string "This copyright info was automatically extracted" appears in the copyright file, which indicates that you either didn't check the whole source to find additional copyright/license, or that you didn't remove that paragraph after having done so.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.5]]
}}}}
##END:Lintian/Tags/copyright-contains-dh-make-perl-boilerplate

Self:Lintian/Tags/copyright-with-old-dh-make-debian-copyright
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-with-old-dh-make-debian-copyright.html|copyright-with-old-dh-make-debian-copyright]]''':<<BR>>
 The copyright file contains the incomplete Debian packaging copyright boilerplate from older versions of {{{dh_make}}}. {{{(C)}}} is not considered as a valid way to express the copyright ownership. The word {{{Copyright}}} or the © symbol should be used instead or in addition to {{{(C)}}}.
}}}}
##END:Lintian/Tags/copyright-with-old-dh-make-debian-copyright

Self:Lintian/Tags/copyright-refers-to-bad-php-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-bad-php-license.html|copyright-refers-to-bad-php-license]]''':<<BR>>
 This package appears to be covered by version 2.x of the PHP license, which is not appropriate for anything other than PHP itself.

Reference(s): [[http://ftp-master.debian.org/REJECT-FAQ.html]]
}}}}
##END:Lintian/Tags/copyright-refers-to-bad-php-license

Self:Lintian/Tags/copyright-refers-to-problematic-php-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-problematic-php-license.html|copyright-refers-to-problematic-php-license]]''':<<BR>>
 This package appears to be covered by version 3.0 (exactly) of the PHP license. This license is not applicable to anything that is not PHP and has no contributions from the PHP Group.

Reference(s): [[http://ftp-master.debian.org/REJECT-FAQ.html]]
}}}}
##END:Lintian/Tags/copyright-refers-to-problematic-php-license

Self:Lintian/Tags/copyright-without-copyright-notice
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-without-copyright-notice.html|copyright-without-copyright-notice]]''':<<BR>>
 The copyright file for this package does not appear to contain a copyright notice. You should copy the copyright notice from the upstream source (or add one of your own for a native package). A copyright notice must consist of Copyright, Copr., or the Unicode symbol of C in a circle followed by the years and the copyright holder. A copyright notice is not required for a work to be copyrighted, but Debian requires the copyright file include the authors and years of copyright, and including a valid copyright notice is the best way to do that. Examples:

   Copyright YYYY Firstname Lastname <address@example.com> Copr. YYYY-YYYY Firstname Lastname <address@example.com> © YYYY,YYYY Firstname Lastname <address@example.com>

 If the package is in the public domain rather than copyrighted, be sure to mention "public domain" in the copyright file. Please be aware that this is very rare and not the same as a DFSG-free license. True public domain software is generally limited to such special cases as a work product of a United States government agency.

Reference(s): [[http://ftp-master.debian.org/REJECT-FAQ.html]]
}}}}
##END:Lintian/Tags/copyright-without-copyright-notice

Self:Lintian/Tags/spelling-error-in-copyright
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-copyright.html|spelling-error-in-copyright]]''':<<BR>>
 Lintian found a spelling error in the copyright file. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does. If this is a spelling error in the upstream license, in supporting email messages, or a case of Lintian being confused by non-English text, add an override.
}}}}
##END:Lintian/Tags/spelling-error-in-copyright

Self:Lintian/Tags/possible-gpl-code-linked-with-openssl
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-gpl-code-linked-with-openssl.html|possible-gpl-code-linked-with-openssl]]''':<<BR>>
 This package appears to be covered by the GNU GPL but depends on the OpenSSL libssl package and does not mention a license exemption or exception for OpenSSL in its copyright file. The GPL (including version 3) is incompatible with some terms of the OpenSSL license, and therefore Debian does not allow GPL-licensed code linked with OpenSSL libraries unless there is a license exception explicitly permitting this.

 If only the Debian packaging, or some other part of the package not linked with OpenSSL, is covered by the GNU GPL, please add a lintian override for this tag. Lintian currently has no good way of distinguishing between that case and problematic packages.
}}}}
##END:Lintian/Tags/possible-gpl-code-linked-with-openssl

Self:Lintian/Tags/copyright-refers-to-symlink-license
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-symlink-license.html|copyright-refers-to-symlink-license]]''':<<BR>>
 The copyright file refers to the versionless symlink in {{{/usr/share/common-licenses}}} for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement.

 For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the {{{debian/copyright}}} file should refer to {{{/usr/share/common-licenses/GPL-2}}}, not {{{/GPL}}}.

 For packages released under the same terms as Perl, Perl references the GPL version 1, so point to {{{/usr/share/common-licenses/GPL-1}}}.
}}}}
##END:Lintian/Tags/copyright-refers-to-symlink-license

Self:Lintian/Tags/copyright-refers-to-versionless-license-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-versionless-license-file.html|copyright-refers-to-versionless-license-file]]''':<<BR>>
 The copyright file refers to the versionless symlink in {{{/usr/share/common-licenses}}} for the full text of the GPL, LGPL, or GFDL license, but the package does not appear to allow distribution under later versions of the license. This symlink will change with each release of a new version of the license and may therefore point to a different version than the package is released under. {{{debian/copyright}}} should instead refers to the specific version of the license that the package references.

 For example, if the package says something like "you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; version 2 dated June, 1991," the {{{debian/copyright}}} file should refer to {{{/usr/share/common-licenses/GPL-2}}}, not {{{/GPL}}}.
}}}}
##END:Lintian/Tags/copyright-refers-to-versionless-license-file

Self:Lintian/Tags/copyright-refers-to-nonexistent-license-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-nonexistent-license-file.html|copyright-refers-to-nonexistent-license-file]]''':<<BR>>
 The copyright file refers to a license in {{{/usr/share/common-licenses}}} that doesn't exist. Usually this is a typo, such as accidentally omitting the {{{-}}} between the license name and the version number.
}}}}
##END:Lintian/Tags/copyright-refers-to-nonexistent-license-file

Self:Lintian/Tags/copyright-refers-to-deprecated-bsd-license-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/copyright-refers-to-deprecated-bsd-license-file.html|copyright-refers-to-deprecated-bsd-license-file]]''':<<BR>>
 The copyright file refers to {{{/usr/share/common-licenses/BSD}}}. Due to the brevity of this license, the specificity of this copy to code whose copyright is held by the Regents of the University of California, and the frequency of minor wording changes in the license, its text should be included in the coypright file directly rather than referencing this file.

 This file may be removed from a future version of base-files if references to it drop sufficiently.

Reference(s): Policy 12.5
}}}}
##END:Lintian/Tags/copyright-refers-to-deprecated-bsd-license-file

########################################################################
== md5sums ==
########################################################################

Self:Lintian/Tags/no-md5sums-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-md5sums-control-file.html|no-md5sums-control-file]]''':<<BR>>
 This package does not contain an md5sums control file. This control file listing the MD5 checksums of the contents of the package is not required, but if present debsums can use it to verify that no files shipped with your package have been modified. Providing it is recommended.

 If you are using debhelper to create your package, just add a call to {{{dh_md5sums}}} at the end of your binary-indep or binary-arch target, right before {{{dh_builddeb}}}.
}}}}
##END:Lintian/Tags/no-md5sums-control-file

Self:Lintian/Tags/malformed-md5sums-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-md5sums-control-file.html|malformed-md5sums-control-file]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/malformed-md5sums-control-file

Self:Lintian/Tags/md5sum-mismatch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/md5sum-mismatch.html|md5sum-mismatch]]''':<<BR>>
 The md5sum listed for the file does not match the actual file contents.

 Usually, this error occurs during the package build process, if the {{{debian/tmp/}}} directory is touched after {{{dh_md5sums}}} or {{{debstd}}} is run.
}}}}
##END:Lintian/Tags/md5sum-mismatch

Self:Lintian/Tags/md5sums-lists-nonexisting-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/md5sums-lists-nonexisting-file.html|md5sums-lists-nonexisting-file]]''':<<BR>>
 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 {{{debian/tmp/}}} directory is touched after {{{dh_md5sums}}} or {{{debstd}}} is run.

 If all the files in the {{{DEBIAN/}}} subdirectory are listed above, the problem was probably caused by building the package using a buggy debstd/debmake. In this case, rebuilding the package with an updated debstd should fix the problem.
}}}}
##END:Lintian/Tags/md5sums-lists-nonexisting-file

Self:Lintian/Tags/file-missing-in-md5sums
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-missing-in-md5sums.html|file-missing-in-md5sums]]''':<<BR>>
 The package contains a file which isn't listed in the md5sums control file.

 Usually, this error occurs during the package build process, if the {{{debian/tmp/}}} directory is touched after {{{dh_md5sums}}} or {{{debstd}}} is run.
}}}}
##END:Lintian/Tags/file-missing-in-md5sums

########################################################################
== description ==
########################################################################

Self:Lintian/Tags/package-has-no-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-has-no-description.html|package-has-no-description]]''':<<BR>>
 The binary package does not have a "Description:" control field.
}}}}
##END:Lintian/Tags/package-has-no-description

Self:Lintian/Tags/description-synopsis-is-empty
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-synopsis-is-empty.html|description-synopsis-is-empty]]''':<<BR>>
 The first line in the "Description:" is empty.
}}}}
##END:Lintian/Tags/description-synopsis-is-empty

Self:Lintian/Tags/extended-description-is-empty
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/extended-description-is-empty.html|extended-description-is-empty]]''':<<BR>>
 The extended description (the lines after the first line of the "Description:" field) is empty.
}}}}
##END:Lintian/Tags/extended-description-is-empty

Self:Lintian/Tags/extended-description-is-probably-too-short
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/extended-description-is-probably-too-short.html|extended-description-is-probably-too-short]]''':<<BR>>
 The extended description (the lines after the first line of the "Description:" field) is only one or two lines long. The extended description should provide a user with enough information to decide whether they want to install this package, what it contains, and how it compares to similar packages. One or two lines is normally not enough to do this.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.2.1]], [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.2.3]]
}}}}
##END:Lintian/Tags/extended-description-is-probably-too-short

Self:Lintian/Tags/description-contains-invalid-control-statement
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-contains-invalid-control-statement.html|description-contains-invalid-control-statement]]''':<<BR>>
 The description contains a line starting with a dot (.). This is not allowed.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.13]]
}}}}
##END:Lintian/Tags/description-contains-invalid-control-statement

Self:Lintian/Tags/description-too-long
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-too-long.html|description-too-long]]''':<<BR>>
 The first line of the "Description:" must not exceed 80 characters.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.4.1]]
}}}}
##END:Lintian/Tags/description-too-long

Self:Lintian/Tags/description-starts-with-package-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-starts-with-package-name.html|description-starts-with-package-name]]''':<<BR>>
 The first line of the "Description:" should not start with the package name. For example, the package {{{foo}}} should not have a description like this: "foo is a program that...".

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.4.1]]
}}}}
##END:Lintian/Tags/description-starts-with-package-name

Self:Lintian/Tags/description-contains-tabs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-contains-tabs.html|description-contains-tabs]]''':<<BR>>
 The package "Description:" must not contain tab characters.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.13]]
}}}}
##END:Lintian/Tags/description-contains-tabs

Self:Lintian/Tags/description-starts-with-leading-spaces
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-starts-with-leading-spaces.html|description-starts-with-leading-spaces]]''':<<BR>>
 The package "Description:" starts with leading spaces. Usually, leading spaces are used to switch "verbatim display" on (i.e., lines are not wrapped) so this might be a bug in the package.
}}}}
##END:Lintian/Tags/description-starts-with-leading-spaces

Self:Lintian/Tags/possible-unindented-list-in-extended-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-unindented-list-in-extended-description.html|possible-unindented-list-in-extended-description]]''':<<BR>>
 The package "Description:" contains an unindented line which starts with a dash (-) or asterisk (*). If this was meant to be a list of items these lines need to be indented (dselect would word-wrap these lines otherwise).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.13]]
}}}}
##END:Lintian/Tags/possible-unindented-list-in-extended-description

Self:Lintian/Tags/description-is-debmake-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-is-debmake-template.html|description-is-debmake-template]]''':<<BR>>
 The synopsis or the extended description just says "Missing", which is a template provided by debmake.
}}}}
##END:Lintian/Tags/description-is-debmake-template

Self:Lintian/Tags/description-is-dh_make-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-is-dh_make-template.html|description-is-dh_make-template]]''':<<BR>>
 The synopsis or the extended description has not been changed from the template provided by dh_make.
}}}}
##END:Lintian/Tags/description-is-dh_make-template

Self:Lintian/Tags/description-contains-dh-make-perl-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-contains-dh-make-perl-template.html|description-contains-dh-make-perl-template]]''':<<BR>>
 The extended description contains the statement that it was automagically extracted by dh-make-perl. Please check the description for correctness and usefulness and remove the dh-make-perl statement to signal that you have done so.
}}}}
##END:Lintian/Tags/description-contains-dh-make-perl-template

Self:Lintian/Tags/description-synopsis-might-not-be-phrased-properly
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-synopsis-might-not-be-phrased-properly.html|description-synopsis-might-not-be-phrased-properly]]''':<<BR>>
 The synopsis (first line in the package "Description:" field, the short description) ends with a full stop "." character. This is not necessary, as the synopsis doesn't need to be a full sentence. It is recommended that a descriptive phrase is used instead.

 Note also that the synopsis is not part of the rest of the "Description:" field.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.2.2]]
}}}}
##END:Lintian/Tags/description-synopsis-might-not-be-phrased-properly

Self:Lintian/Tags/description-synopsis-is-duplicated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-synopsis-is-duplicated.html|description-synopsis-is-duplicated]]''':<<BR>>
 The first line of the extended Description: should not repeat the synopsis exactly. This indicates that either the synopsis is badly formed or that the extended description has been wrongly copied and pasted.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.4.2]]
}}}}
##END:Lintian/Tags/description-synopsis-is-duplicated

Self:Lintian/Tags/extended-description-line-too-long
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/extended-description-line-too-long.html|extended-description-line-too-long]]''':<<BR>>
 One or more lines in the extended part of the "Description:" field have been found to contain more than 80 characters. For the benefit of users of 80x25 terminals, it is recommended that the lines do not exceed 80 characters.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.4.1]]
}}}}
##END:Lintian/Tags/extended-description-line-too-long

Self:Lintian/Tags/description-contains-homepage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-contains-homepage.html|description-contains-homepage]]''':<<BR>>
 The extended description contains a "Homepage:" pseudo-header following the old Developer's Reference recommendation. As of 1.14.6, dpkg now supports Homepage: as a regular field in {{{debian/control}}}. This header should be moved from the extended description to the fields for the relevant source or binary packages.
}}}}
##END:Lintian/Tags/description-contains-homepage

Self:Lintian/Tags/spelling-error-in-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-description.html|spelling-error-in-description]]''':<<BR>>
 Lintian found a spelling error in the package description. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does. It is particularly picky about spelling and capitalization in package descriptions since they're very visible to end users.
}}}}
##END:Lintian/Tags/spelling-error-in-description

Self:Lintian/Tags/capitalization-error-in-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/capitalization-error-in-description.html|capitalization-error-in-description]]''':<<BR>>
 Lintian found a possible capitalization error in the package description. Lintian has a list of common capitalization errors, primarily of upstream projects, that it looks for. It does not have a dictionary like a spelling checker does.

 This is a particularly picky check of capitalization in package descriptions, since they're very visible to end users, but it will have false positives for project names used in a context where they should be lowercase, such as package names or executable names.
}}}}
##END:Lintian/Tags/capitalization-error-in-description

Self:Lintian/Tags/description-contains-duplicated-word
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-contains-duplicated-word.html|description-contains-duplicated-word]]''':<<BR>>
 The description contains a duplicated word. Usually this is a mistake, or at least an awkward phrasing.
}}}}
##END:Lintian/Tags/description-contains-duplicated-word

Self:Lintian/Tags/using-first-person-in-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/using-first-person-in-description.html|using-first-person-in-description]]''':<<BR>>
 You should avoid the use of first person ("I will do this..." or "We recommend..."). The computer is not a person and the description does not speak for the maintainer or maintainers. Instead, use a more neutral construction and try to rephrase into factual statements about the package.

 For example, rather than saying "I don't recommend this package if you are short on memory," say something like "this package is not suitable for low-memory systems."
}}}}
##END:Lintian/Tags/using-first-person-in-description

Self:Lintian/Tags/description-possibly-contains-homepage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/description-possibly-contains-homepage.html|description-possibly-contains-homepage]]''':<<BR>>
 This package has no Homepage field but has a URL in the description and wording that might indicate this is the package Homepage. If it is, add a Homepage control field containing it rather than mentioning it in the package description.
}}}}
##END:Lintian/Tags/description-possibly-contains-homepage

########################################################################
== changelog-file ==
########################################################################

Self:Lintian/Tags/html-changelog-without-text-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/html-changelog-without-text-version.html|html-changelog-without-text-version]]''':<<BR>>
 If the upstream changelog file is HTML formatted, a text version should also be accessible as "changelog.gz". (This can be created by "lynx -dump -nolist")

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/html-changelog-without-text-version

Self:Lintian/Tags/changelog-file-not-compressed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-file-not-compressed.html|changelog-file-not-compressed]]''':<<BR>>
 Changelog files should be compressed using "gzip -9". Even if they start out small, they will become large with time.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/changelog-file-not-compressed

Self:Lintian/Tags/debian-news-file-not-compressed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-news-file-not-compressed.html|debian-news-file-not-compressed]]''':<<BR>>
 NEWS.Debian files should be compressed using "gzip -9". The file must always have the same name.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.3.4]]
}}}}
##END:Lintian/Tags/debian-news-file-not-compressed

Self:Lintian/Tags/changelog-not-compressed-with-max-compression
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-not-compressed-with-max-compression.html|changelog-not-compressed-with-max-compression]]''':<<BR>>
 Changelog files should be compressed using "gzip -9"; i.e., using the maximum compression level via the -9 option to gzip.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/changelog-not-compressed-with-max-compression

Self:Lintian/Tags/wrong-name-for-changelog-of-native-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-name-for-changelog-of-native-package.html|wrong-name-for-changelog-of-native-package]]''':<<BR>>
 The changelog file of a native Debian package (i.e., if there is no upstream source) should usually be installed as /usr/share/doc/pkg/changelog.gz

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/wrong-name-for-changelog-of-native-package

Self:Lintian/Tags/changelog-file-missing-in-native-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-file-missing-in-native-package.html|changelog-file-missing-in-native-package]]''':<<BR>>
 Each Debian package (which provides a /usr/share/doc/pkg directory) has to install a changelog file. Since this package seems to be a native Debian package (i.e., there is no upstream source), the file should usually be installed as /usr/share/doc/pkg/changelog.gz

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/changelog-file-missing-in-native-package

Self:Lintian/Tags/wrong-name-for-upstream-changelog
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-name-for-upstream-changelog.html|wrong-name-for-upstream-changelog]]''':<<BR>>
 If there is an upstream changelog file, it should usually be installed as /usr/share/doc/pkg/changelog.gz

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/wrong-name-for-upstream-changelog

Self:Lintian/Tags/no-upstream-changelog
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-upstream-changelog.html|no-upstream-changelog]]''':<<BR>>
 The package does not install an upstream changelog file. If upstream provides a changelog, it should be accessible as {{{/usr/share/doc/pkg/changelog.gz}}}.

 It's currently unclear how best to handle multiple binary packages from the same source. Some maintainers put a copy of the upstream changelog in each package, but it can be quite long. Some include it in one package and add symlinks to the other packages, but this requires there be dependencies between the packages. Some only include it in a "central" binary package and omit it from more ancillary packages.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/no-upstream-changelog

Self:Lintian/Tags/wrong-name-for-debian-changelog-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-name-for-debian-changelog-file.html|wrong-name-for-debian-changelog-file]]''':<<BR>>
 The Debian changelog file should usually be installed as /usr/share/doc/pkg/changelog.Debian.gz

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/wrong-name-for-debian-changelog-file

Self:Lintian/Tags/wrong-name-for-debian-news-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-name-for-debian-news-file.html|wrong-name-for-debian-news-file]]''':<<BR>>
 The Debian news file must be installed as /usr/share/doc/pkg/NEWS.Debian.gz with exactly that capitalization or automated tools may not find it correctly.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.3.4]]
}}}}
##END:Lintian/Tags/wrong-name-for-debian-news-file

Self:Lintian/Tags/debian-changelog-file-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-missing.html|debian-changelog-file-missing]]''':<<BR>>
 Each Debian package (which provides a /usr/share/doc/pkg directory) has to install a Debian changelog file /usr/share/doc/pkg/changelog.Debian.gz

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/debian-changelog-file-missing

Self:Lintian/Tags/debian-changelog-file-is-a-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-is-a-symlink.html|debian-changelog-file-is-a-symlink]]''':<<BR>>
 The Debian changelog file is a symlink to a file in a different directory or not found in this package. Please don't do this. It makes package checking and manipulation unnecessarily difficult. Because it was a symlink, the Debian changelog file was not checked for other problems. (Symlinks to another file in /usr/share/doc/pkg or a subdirectory thereof are fine and should not trigger this warning.)

 To refer to the changelog, copyright, and other documentation files of another package that this one depends on, please symlink the entire /usr/share/doc/pkg directory rather than individual files.
}}}}
##END:Lintian/Tags/debian-changelog-file-is-a-symlink

Self:Lintian/Tags/debian-changelog-file-missing-or-wrong-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-missing-or-wrong-name.html|debian-changelog-file-missing-or-wrong-name]]''':<<BR>>
 Each Debian package (which provides a /usr/share/doc/pkg directory) must install a Debian changelog file in /usr/share/doc/pkg/changelog.Debian.gz

 A common error is to name the Debian changelog like an upstream changelog (/usr/share/doc/pkg/changelog.gz); therefore, lintian will apply further checks to such a file if it exists even after issuing this error.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.7]]
}}}}
##END:Lintian/Tags/debian-changelog-file-missing-or-wrong-name

Self:Lintian/Tags/debian-changelog-file-contains-obsolete-user-emacs-settings
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-contains-obsolete-user-emacs-settings.html|debian-changelog-file-contains-obsolete-user-emacs-settings]]''':<<BR>>
 The add-log-mailing-address variable is no longer honored in debian-changelog-mode, and should not appear in packages' changelog files. Instead, put something like this in your ~/.emacs:

 (setq debian-changelog-mailing-address "userid@debian.org")
}}}}
##END:Lintian/Tags/debian-changelog-file-contains-obsolete-user-emacs-settings

Self:Lintian/Tags/debian-changelog-file-contains-debmake-default-email-address
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-contains-debmake-default-email-address.html|debian-changelog-file-contains-debmake-default-email-address]]''':<<BR>>
 The changelog file contains an email address (<..@unknown>) that was not updated to the maintainer's real address.
}}}}
##END:Lintian/Tags/debian-changelog-file-contains-debmake-default-email-address

Self:Lintian/Tags/debian-changelog-file-contains-invalid-email-address
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-contains-invalid-email-address.html|debian-changelog-file-contains-invalid-email-address]]''':<<BR>>
 The changelog file contains an invalid email address: the domain needs at least one dot. This looks like a mistake.
}}}}
##END:Lintian/Tags/debian-changelog-file-contains-invalid-email-address

Self:Lintian/Tags/debian-changelog-file-uses-obsolete-national-encoding
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-file-uses-obsolete-national-encoding.html|debian-changelog-file-uses-obsolete-national-encoding]]''':<<BR>>
 The Debian changelog file must be valid UTF-8, an encoding of the Unicode character set.

 There are many ways to convert a changelog from an obsoleted encoding like ISO-8859-1; you may for example use "iconv" like:

  $ iconv -f ISO-8859-1 -t UTF-8 changelog > changelog.new $ mv changelog.new changelog

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.4]]
}}}}
##END:Lintian/Tags/debian-changelog-file-uses-obsolete-national-encoding

Self:Lintian/Tags/debian-news-file-uses-obsolete-national-encoding
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-news-file-uses-obsolete-national-encoding.html|debian-news-file-uses-obsolete-national-encoding]]''':<<BR>>
 The NEWS.Debian file must be valid UTF-8, an encoding of the Unicode character set.

 There are many ways to convert a changelog from an obsoleted encoding like ISO-8859-1; you may for example use "iconv" like:

  $ iconv -f ISO-8859-1 -t UTF-8 NEWS.Debian > NEWS.Debian.new $ mv NEWS.Debian.new NEWS.Debian
}}}}
##END:Lintian/Tags/debian-news-file-uses-obsolete-national-encoding

Self:Lintian/Tags/latest-debian-changelog-entry-without-new-date
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/latest-debian-changelog-entry-without-new-date.html|latest-debian-changelog-entry-without-new-date]]''':<<BR>>
 The latest Debian changelog entry has either the same or even an older date as the entry before.
}}}}
##END:Lintian/Tags/latest-debian-changelog-entry-without-new-date

Self:Lintian/Tags/latest-debian-changelog-entry-without-new-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/latest-debian-changelog-entry-without-new-version.html|latest-debian-changelog-entry-without-new-version]]''':<<BR>>
 The latest Debian changelog entry has a version number that's either the same or smaller than the version number of the entry before.
}}}}
##END:Lintian/Tags/latest-debian-changelog-entry-without-new-version

Self:Lintian/Tags/latest-debian-changelog-entry-changed-to-native
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/latest-debian-changelog-entry-changed-to-native.html|latest-debian-changelog-entry-changed-to-native]]''':<<BR>>
 The latest package has a Debian native version number, while the previous version number was not native. This is usually a mistake made by the maintainer by forgetting to append -1 when uploading a new upstream version.
}}}}
##END:Lintian/Tags/latest-debian-changelog-entry-changed-to-native

Self:Lintian/Tags/possible-new-upstream-release-without-new-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-new-upstream-release-without-new-version.html|possible-new-upstream-release-without-new-version]]''':<<BR>>
 The most recent changelog entry contains an entry that appears to say this is a new upstream release (a comment similar to "new upstream release," possibly with a word between "upstream" and "release"), but the upstream portion of the package version number didn't change. This may indicate that the package version was not updated properly in {{{debian/changelog}}}.
}}}}
##END:Lintian/Tags/possible-new-upstream-release-without-new-version

Self:Lintian/Tags/experimental-to-unstable-without-comment
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/experimental-to-unstable-without-comment.html|experimental-to-unstable-without-comment]]''':<<BR>>
 The previous version of this package had a distribution of experimental, this version has a distribution of unstable, and there's apparently no comment about the change of distributions (Lintian looks for the phrase "to unstable"). This may indicate a mistake in setting the distribution and accidentally uploading to unstable a package intended for experimental.
}}}}
##END:Lintian/Tags/experimental-to-unstable-without-comment

Self:Lintian/Tags/syntax-error-in-debian-changelog
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/syntax-error-in-debian-changelog.html|syntax-error-in-debian-changelog]]''':<<BR>>
 While parsing the Debian changelog, a syntax error was found. If you have old changelog entries that don't follow the current syntax but that you want to keep as-is for the historical record, add the line:

   Old Changelog:

 with no leading whitespace before the legacy entries. This line and everything after it will be ignored.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.4]]
}}}}
##END:Lintian/Tags/syntax-error-in-debian-changelog

Self:Lintian/Tags/syntax-error-in-debian-news-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/syntax-error-in-debian-news-file.html|syntax-error-in-debian-news-file]]''':<<BR>>
 While parsing the NEWS.Debian file, a syntax error was found.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.3.4]]
}}}}
##END:Lintian/Tags/syntax-error-in-debian-news-file

Self:Lintian/Tags/improbable-bug-number-in-closes
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/improbable-bug-number-in-closes.html|improbable-bug-number-in-closes]]''':<<BR>>
 The most recent changelog closes a bug numbered less than 100. While this is distantly possible, it's more likely a typo or a placeholder value that mistakenly wasn't filled in.
}}}}
##END:Lintian/Tags/improbable-bug-number-in-closes

Self:Lintian/Tags/wrong-bug-number-in-closes
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-bug-number-in-closes.html|wrong-bug-number-in-closes]]''':<<BR>>
 Bug numbers can only contain digits.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.4]]
}}}}
##END:Lintian/Tags/wrong-bug-number-in-closes

Self:Lintian/Tags/possible-missing-colon-in-closes
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-missing-colon-in-closes.html|possible-missing-colon-in-closes]]''':<<BR>>
 To close a bug in the Debian changelog, the word "closes" must be followed by a colon. This entry looked like it was intended to close a bug, but there's no colon after "closes".

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.4]]
}}}}
##END:Lintian/Tags/possible-missing-colon-in-closes

Self:Lintian/Tags/debian-news-entry-has-strange-distribution
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-news-entry-has-strange-distribution.html|debian-news-entry-has-strange-distribution]]''':<<BR>>
 The latest entry in NEWS.Debian has an unusual distribution name. This field is ignored by the archive software, so its value doesn't truly matter, but it may be confusing to users reading the entry if the distribution doesn't match the distribution for the same entry in the Debian changelog file.
}}}}
##END:Lintian/Tags/debian-news-entry-has-strange-distribution

Self:Lintian/Tags/debian-news-entry-uses-asterisk
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-news-entry-uses-asterisk.html|debian-news-entry-uses-asterisk]]''':<<BR>>
 The latest entry in NEWS.Debian appears to use asterisks to present changes in a bulleted list, similar to the normal changelog syntax. The Debian Developer's Reference recommends using regular paragraphs in NEWS.Debian rather than a bulleted list.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.3.4]]
}}}}
##END:Lintian/Tags/debian-news-entry-uses-asterisk

Self:Lintian/Tags/debian-news-entry-has-unknown-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-news-entry-has-unknown-version.html|debian-news-entry-has-unknown-version]]''':<<BR>>
 The version number of the most recent {{{NEWS.Debian}}} entry does not match any of the version numbers in the changelog file for this package. This usually means the version in {{{NEWS.Debian}}} needs to be updated to match a change to package version that happened after the {{{NEWS.Debian}}} entry was written.
}}}}
##END:Lintian/Tags/debian-news-entry-has-unknown-version

Self:Lintian/Tags/spelling-error-in-changelog
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-changelog.html|spelling-error-in-changelog]]''':<<BR>>
 Lintian found a spelling error in the latest entry of the Debian changelog. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does.

 When writing a changelog entry for a spelling fix that includes the misspelling, ensure the word "spelling" is on the same line as the misspelled word to avoid triggering this warning.
}}}}
##END:Lintian/Tags/spelling-error-in-changelog

Self:Lintian/Tags/spelling-error-in-news-debian
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-news-debian.html|spelling-error-in-news-debian]]''':<<BR>>
 Lintian found a spelling error in the latest entry of the NEWS.Debian file. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does.
}}}}
##END:Lintian/Tags/spelling-error-in-news-debian

Self:Lintian/Tags/new-package-should-close-itp-bug
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/new-package-should-close-itp-bug.html|new-package-should-close-itp-bug]]''':<<BR>>
 This package appears to be the first packaging of a new upstream software package (there is only one changelog entry and the Debian revision is 1), but it does not close any bugs. The initial upload of a new package should close the corresponding ITP bug for that package.

 This warning can be ignored if the package is not intended for Debian or if it is a split of an existing Debian package.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.1]]
}}}}
##END:Lintian/Tags/new-package-should-close-itp-bug

Self:Lintian/Tags/debian-changelog-line-too-long
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-changelog-line-too-long.html|debian-changelog-line-too-long]]''':<<BR>>
 The given line of the latest changelog entry is over 80 columns. Such changelog entries may look poor in terminal windows and mail messages and be annoying to read. Please wrap changelog entries at 80 columns or less where possible.
}}}}
##END:Lintian/Tags/debian-changelog-line-too-long

Self:Lintian/Tags/changelog-news-debian-mismatch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-news-debian-mismatch.html|changelog-news-debian-mismatch]]''':<<BR>>
 The latest entries in the Debian changelog file and NEWS.Debian file are for the same version but the given field doesn't match. The changelog information is canonical and the NEWS.Debian information is ignored, but it may be confusing to users to have them be different.
}}}}
##END:Lintian/Tags/changelog-news-debian-mismatch

Self:Lintian/Tags/version-refers-to-distribution
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/version-refers-to-distribution.html|version-refers-to-distribution]]''':<<BR>>
 The Debian portion of the package version contains a reference to a particular Debian release or distribution. This should only be done for uploads targeted at a particular release, not at unstable or experimental, and should refer to the release by version number or code name.

 Using "testing" or "stable" in a package version targeted at the current testing or stable release is less informative than using the code name or version number and may cause annoying version sequencing issues if the package doesn't change before the next release cycle starts.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.13.3]]
}}}}
##END:Lintian/Tags/version-refers-to-distribution

########################################################################
== binaries ==
########################################################################

Self:Lintian/Tags/arch-independent-package-contains-binary-or-object
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/arch-independent-package-contains-binary-or-object.html|arch-independent-package-contains-binary-or-object]]''':<<BR>>
 The package contains a binary or object file but is tagged Architecture: all.

 If this package contains binaries or objects for cross-compiling or binary blobs for other purposes independent of the host architecture (such as BIOS updates or firmware), please add a Lintian override.
}}}}
##END:Lintian/Tags/arch-independent-package-contains-binary-or-object

Self:Lintian/Tags/unstripped-binary-or-object
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unstripped-binary-or-object.html|unstripped-binary-or-object]]''':<<BR>>
 The package installs an unstripped binary or object file.

 Please note, that shared libraries have to be stripped with the {{{--strip-unneeded}}} option.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.1]], [[http://www.debian.org/doc/debian-policy/|policy 10.2]]
}}}}
##END:Lintian/Tags/unstripped-binary-or-object

Self:Lintian/Tags/library-in-debug-or-profile-should-not-be-stripped
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/library-in-debug-or-profile-should-not-be-stripped.html|library-in-debug-or-profile-should-not-be-stripped]]''':<<BR>>
 Libraries in {{{.../lib/debug}}} or in {{{.../lib/profile}}} must not be stripped; this defeats the whole point of the separate library.
}}}}
##END:Lintian/Tags/library-in-debug-or-profile-should-not-be-stripped

Self:Lintian/Tags/statically-linked-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/statically-linked-binary.html|statically-linked-binary]]''':<<BR>>
 The package installs a statically linked binary or object file.

 Usually this is a bug. Otherwise, please add an override if your package is an exception. Binaries named *-static and *.static are automatically excluded, as are any binaries in packages named *-static.
}}}}
##END:Lintian/Tags/statically-linked-binary

Self:Lintian/Tags/library-not-linked-against-libc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/library-not-linked-against-libc.html|library-not-linked-against-libc]]''':<<BR>>
 The package installs a library which is not dynamically linked against libc.
}}}}
##END:Lintian/Tags/library-not-linked-against-libc

Self:Lintian/Tags/program-not-linked-against-libc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/program-not-linked-against-libc.html|program-not-linked-against-libc]]''':<<BR>>
 The package installs a binary which is not dynamically linked against libc.
}}}}
##END:Lintian/Tags/program-not-linked-against-libc

Self:Lintian/Tags/binary-or-shlib-defines-rpath
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-or-shlib-defines-rpath.html|binary-or-shlib-defines-rpath]]''':<<BR>>
 The binary or shared library sets RPATH. This overrides the normal library search path, possibly interfering with local policy and causing problems for multilib, among other issues.

 The only time a binary or shared library in a Debian package should set RPATH is if it is linked to private shared libraries in the same package. In that case, place those private shared libraries in {{{/usr/lib/package}}}. Libraries used by binaries in other packages should be placed in {{{/lib}}} or {{{/usr/lib}}} as appropriate, with a proper SONAME, in which case RPATH is unnecessary.

 To fix this problem, look for link lines like: gcc test.o -o test -Wl,--rpath,/usr/local/lib or gcc test.o -o test -R/usr/local/lib and remove the {{{-Wl,--rpath}}} or {{{-R}}} argument. You can also use the chrpath utility to remove the RPATH.

Reference(s): [[http://wiki.debian.org/RpathIssue]]
}}}}
##END:Lintian/Tags/binary-or-shlib-defines-rpath

Self:Lintian/Tags/binary-has-unneeded-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-has-unneeded-section.html|binary-has-unneeded-section]]''':<<BR>>
 The binary or shared library is stripped, but still contains a section that is not useful. You should call strip with {{{--remove-section=.comment --remove-section=.note}}} to remove the {{{.note}}} and {{{.comment}}} sections.

 {{{dh_strip}}} will do this automatically for you, but {{{install -s}}} not because it calls strip without any arguments.
}}}}
##END:Lintian/Tags/binary-has-unneeded-section

Self:Lintian/Tags/missing-depends-line
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-depends-line.html|missing-depends-line]]''':<<BR>>
 The package contains an ELF binary with dynamic dependencies, but does not have a Depends line in its control file. This usually means that a call to {{{dpkg-shlibdeps}}} is missing from the package's {{{debian/rules}}} file.
}}}}
##END:Lintian/Tags/missing-depends-line

Self:Lintian/Tags/shared-lib-without-dependency-information
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shared-lib-without-dependency-information.html|shared-lib-without-dependency-information]]''':<<BR>>
 The listed shared library doesn't include information about which other libraries the library was linked against. (When running "{{{ldd foo.so}}}" ldd should report about these other libraries. In your case, ldd just reports "statically linked".)

 To fix this, you should explicitly specify the libraries which are used (e.g., "-lc") when building the shared library with "ld".

 If you have questions about this, please contact &debdev;.
}}}}
##END:Lintian/Tags/shared-lib-without-dependency-information

Self:Lintian/Tags/arch-dependent-file-in-usr-share
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/arch-dependent-file-in-usr-share.html|arch-dependent-file-in-usr-share]]''':<<BR>>
 This package installs an ELF binary in the {{{/usr/share}}} hierarchy, which is reserved for architecture-independent files.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs usrsharearchitectureindependentdata]]
}}}}
##END:Lintian/Tags/arch-dependent-file-in-usr-share

Self:Lintian/Tags/binary-in-etc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-in-etc.html|binary-in-etc]]''':<<BR>>
 This package installs an ELF binary in {{{/etc}}}. The Filesystem Hierarchy Standard forbids this.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs etchostspecificsystemconfiguration]]
}}}}
##END:Lintian/Tags/binary-in-etc

Self:Lintian/Tags/binary-compiled-with-profiling-enabled
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-compiled-with-profiling-enabled.html|binary-compiled-with-profiling-enabled]]''':<<BR>>
 While profiling is useful for testing and debugging purposes, enabling it causes a program to leave gmon.out files whenever a user runs it.
}}}}
##END:Lintian/Tags/binary-compiled-with-profiling-enabled

Self:Lintian/Tags/binary-file-compressed-with-upx
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-file-compressed-with-upx.html|binary-file-compressed-with-upx]]''':<<BR>>
 Debian does not allow binaries to be compressed by UPX.
}}}}
##END:Lintian/Tags/binary-file-compressed-with-upx

Self:Lintian/Tags/package-name-doesnt-match-sonames
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-name-doesnt-match-sonames.html|package-name-doesnt-match-sonames]]''':<<BR>>
 The package name of a library package should usually reflect the soname of the included library. The package name can determined from the library file name with the following code snippet:

  $ objdump -p /path/to/libfoo-bar.so.1.2.3 | sed -n -e's/^[[:space:]]*SONAME[[:space:]]*//p' | sed -e's/\([0-9]\)\.so\./\1-/; s/\.so\.//'

Reference(s): libpkg-guide 5
}}}}
##END:Lintian/Tags/package-name-doesnt-match-sonames

Self:Lintian/Tags/binary-with-bad-dynamic-table
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-with-bad-dynamic-table.html|binary-with-bad-dynamic-table]]''':<<BR>>
 This appears to be an ELF file but objdump -T cannot parse it. If it is external debugging symbols for another file, it should be installed under /usr/lib/debug.
}}}}
##END:Lintian/Tags/binary-with-bad-dynamic-table

Self:Lintian/Tags/apparently-corrupted-elf-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/apparently-corrupted-elf-binary.html|apparently-corrupted-elf-binary]]''':<<BR>>
 This appears to be an ELF file but objdump -T doesn't recognize it as valid. This may be a mistake or a corrupted file, you may need to install binutils-multiarch on the system running lintian so that non-native binaries are handled correctly, or it may be a misidentification of a file as ELF that actually isn't.
}}}}
##END:Lintian/Tags/apparently-corrupted-elf-binary

Self:Lintian/Tags/apparently-truncated-elf-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/apparently-truncated-elf-binary.html|apparently-truncated-elf-binary]]''':<<BR>>
 This appears to be an ELF file, but objdump believes it is truncated. This may be a mistake or a corrupted file, or it may be a misidentification of a file as ELF that actually isn't.
}}}}
##END:Lintian/Tags/apparently-truncated-elf-binary

Self:Lintian/Tags/missing-dependency-on-libc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-dependency-on-libc.html|missing-dependency-on-libc]]''':<<BR>>
 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 {{{debian/control}}}.

 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 {{{debian/control}}} to get the proper package dependencies for those libraries.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.6]]
}}}}
##END:Lintian/Tags/missing-dependency-on-libc

Self:Lintian/Tags/missing-dependency-on-perlapi
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-dependency-on-perlapi.html|missing-dependency-on-perlapi]]''':<<BR>>
 This package includes a *.so file in {{{/usr/lib/perl5}}}, 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 {{{debian/rules}}} or a missing ${perl:Depends} substitution variable in the Depends line in {{{debian/control}}}.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/perl-policy/|perl-policy 4.4.2]]
}}}}
##END:Lintian/Tags/missing-dependency-on-perlapi

Self:Lintian/Tags/missing-dependency-on-phpapi
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-dependency-on-phpapi.html|missing-dependency-on-phpapi]]''':<<BR>>
 This package includes a *.so file in {{{/usr/lib/phpN}}} (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 {{{${php:Depends} }}} to the {{{Depends}}} field of the binary package shipping the extension:

 echo "php:Depends=phpapi-$(php-config5 --phpapi)" > debian/substvars
}}}}
##END:Lintian/Tags/missing-dependency-on-phpapi

Self:Lintian/Tags/debug-file-should-use-detached-symbols
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debug-file-should-use-detached-symbols.html|debug-file-should-use-detached-symbols]]''':<<BR>>
 This file is in a location generally used for detached debugging symbols, but it appears to contain a complete copy of the executable or library instead of only the debugging symbols. Files in subdirectories of {{{/usr/lib/debug}}} mirroring the main file system should contain only debugging information generated by {{{objcopy --only-keep-debug}}}. Binaries or shared objects built with extra debugging should be installed directly in {{{/usr/lib/debug}}} or in subdirectories corresponding to the package, not in the directories that mirror the main file system.

 If you are using dh_strip with the --dbg-package flag, don't also install the library in {{{/usr/lib/debug}}}. dh_strip does all the work for you.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.7.9]]
}}}}
##END:Lintian/Tags/debug-file-should-use-detached-symbols

Self:Lintian/Tags/binary-from-other-architecture
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-from-other-architecture.html|binary-from-other-architecture]]''':<<BR>>
 This ELF binary appears to have been built for an architecture other than the one of the binary package being tested. This may occur when a pre-built binary is shipped in the package or when an attempt to cross-compile didn't work.
}}}}
##END:Lintian/Tags/binary-from-other-architecture

Self:Lintian/Tags/spelling-error-in-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-binary.html|spelling-error-in-binary]]''':<<BR>>
 Lintian found a spelling error in the given binary. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does.

 If the string containing the spelling error is translated with the help of gettext or a similar tool, please fix the error in the translations as well as the English text to avoid making the translations fuzzy. With gettext, for example, this means you should also fix the spelling mistake in the corresponding msgids in the *.po files.

 You can often find the word in the source code by running:

  grep -rw <word> <source-tree>

 This tag may produce false positives for words that contain non-ASCII characters due to limitations in {{{strings}}}.
}}}}
##END:Lintian/Tags/spelling-error-in-binary

Self:Lintian/Tags/embedded-zlib
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-zlib.html|embedded-zlib]]''':<<BR>>
 The given ELF object appears to have been statically linked to zlib. Doing this is strongly discouraged due to the extra work needed by the security team to fix all the extra embedded copies or trigger the package rebuilds, as appropriate.

 Some packages have to use a modified version of zlib due to requirements in that package. If this is the case, please add an override.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-zlib

Self:Lintian/Tags/embedded-libpng
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-libpng.html|embedded-libpng]]''':<<BR>>
 The given ELF object appears to have been statically linked to libpng. Doing this is strongly discouraged due to the extra work needed by the security team to fix all the extra embedded copies or trigger the package rebuilds, as appropriate.

 If the package uses a modified version of libpng it is highly recommended to coordinate with the libpng maintainer to include the changes on the system version of the library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-libpng

Self:Lintian/Tags/embedded-libjpeg
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-libjpeg.html|embedded-libjpeg]]''':<<BR>>
 The given ELF object appears to have been statically linked to libjpeg. Doing this is strongly discouraged due to the extra work needed by the security team to fix all the extra embedded copies or trigger the package rebuilds, as appropriate.

 If the package uses a modified version of libjpeg it is highly recommended to coordinate with the libjpeg maintainer to include the changes on the system version of the library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-libjpeg

Self:Lintian/Tags/embedded-libopenjpeg
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-libopenjpeg.html|embedded-libopenjpeg]]''':<<BR>>
 The given ELF object appears to have been statically linked to libopenjpeg. Doing this is strongly discouraged due to the extra work needed by the security team to fix all the extra embedded copies or trigger the package rebuilds, as appropriate.

 If the package uses a modified version of libopenjpeg it is highly recommended to coordinate with the libopenjpeg maintainer to include the changes on the system version of the library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-libopenjpeg

Self:Lintian/Tags/embedded-library
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/embedded-library.html|embedded-library]]''':<<BR>>
 The given ELF object appears to have been statically linked to a library. Doing this is strongly discouraged due to the extra work needed by the security team to fix all the extra embedded copies or trigger the package rebuilds, as appropriate.

 If the package uses a modified version of the given library it is highly recommended to coordinate with the library's maintainer to include the changes on the system version of the library.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.13]]
}}}}
##END:Lintian/Tags/embedded-library

Self:Lintian/Tags/debug-symbols-directly-in-usr-lib-debug
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debug-symbols-directly-in-usr-lib-debug.html|debug-symbols-directly-in-usr-lib-debug]]''':<<BR>>
 The given debugging symbols-only object is installed directly in {{{/usr/lib/debug}}}, although it should be installed in a subdirectory. For example, debug symbols of a binary in {{{/usr/bin}}} should be placed in {{{/usr/lib/debug/usr/bin}}}. gdb, when looking for debugging symbols, prepends {{{/usr/lib/debug}}} to the path of the original binary.
}}}}
##END:Lintian/Tags/debug-symbols-directly-in-usr-lib-debug

Self:Lintian/Tags/ocaml-custom-executable
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-custom-executable.html|ocaml-custom-executable]]''':<<BR>>
 This package provides an OCaml bytecode executable linked with a custom runtime. Such executables cannot be stripped and require special care. Their usage is deprecated in favour of shared libraries for C stubs (dll*.so).
}}}}
##END:Lintian/Tags/ocaml-custom-executable

########################################################################
== po-debconf ==
########################################################################

Self:Lintian/Tags/not-using-po-debconf
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/not-using-po-debconf.html|not-using-po-debconf]]''':<<BR>>
 This package seems to be using debconf templates, but it does not use po-debconf to make translations possible ({{{debian/po}}} doesn't exist). Debian Policy requires that all packages using debconf use a gettext-based translation system. If this package uses one other than po-debconf, please report this as a lintian bug along with how to detect that system.

Reference(s): 3.9.1
}}}}
##END:Lintian/Tags/not-using-po-debconf

Self:Lintian/Tags/stray-translated-debconf-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/stray-translated-debconf-templates.html|stray-translated-debconf-templates]]''':<<BR>>
 This package contains a file named *templates.XX or *templates.XX_XX. This was the naming convention for the translated templates merged using debconf-mergetemplate. Since the package is using po-debconf, these files should be replaced by language-specific files in the {{{debian/po}}} directory and should no longer be needed.
}}}}
##END:Lintian/Tags/stray-translated-debconf-templates

Self:Lintian/Tags/missing-potfiles-in
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-potfiles-in.html|missing-potfiles-in]]''':<<BR>>
 The required file {{{POTFILES.in}}} is missing from {{{debian/po}}}.

Reference(s): [[DebianMan:7/po-debconf|po-debconf(7)]]
}}}}
##END:Lintian/Tags/missing-potfiles-in

Self:Lintian/Tags/missing-file-from-potfiles-in
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-file-from-potfiles-in.html|missing-file-from-potfiles-in]]''':<<BR>>
 A file listed in {{{debian/po/POTFILES.in}}} could not be found in the source package.

Reference(s): [[DebianMan:7/po-debconf|po-debconf(7)]]
}}}}
##END:Lintian/Tags/missing-file-from-potfiles-in

Self:Lintian/Tags/missing-templates-pot
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-templates-pot.html|missing-templates-pot]]''':<<BR>>
 The required file {{{templates.pot}}} is missing from {{{debian/po}}}.

Reference(s): [[DebianMan:7/po-debconf|po-debconf(7)]]
}}}}
##END:Lintian/Tags/missing-templates-pot

Self:Lintian/Tags/unknown-encoding-in-po-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-encoding-in-po-file.html|unknown-encoding-in-po-file]]''':<<BR>>
 Encoding must be declared in PO files. Otherwise, charset conversions cannot be performed.
}}}}
##END:Lintian/Tags/unknown-encoding-in-po-file

Self:Lintian/Tags/invalid-po-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/invalid-po-file.html|invalid-po-file]]''':<<BR>>
 Errors were found in the listed PO file that will cause its content to be discarded. Run {{{msgfmt}}} on the file to see the error messages.
}}}}
##END:Lintian/Tags/invalid-po-file

Self:Lintian/Tags/misnamed-po-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/misnamed-po-file.html|misnamed-po-file]]''':<<BR>>
 The name of this PO file doesn't appear to be a valid language code. Any files in {{{debian/po}}} ending in {{{.po}}} will be processed as translations by po2debconf for the language code equal to the file name without the trailing {{{.po}}}. 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 {{{.po}}} or move it to another directory so that translation merging programs will not be confused.
}}}}
##END:Lintian/Tags/misnamed-po-file

Self:Lintian/Tags/newer-debconf-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/newer-debconf-templates.html|newer-debconf-templates]]''':<<BR>>
 debconf-updatepo has not been run since the last change to your debconf templates.

 You should run debconf-updatepo whenever debconf templates files are changed so that translators can be warned that their files are outdated.

 This can be ensured by running debconf-updatepo in the 'clean' target of {{{debian/rules}}}. PO files will then always be up-to-date when building the source package.
}}}}
##END:Lintian/Tags/newer-debconf-templates

Self:Lintian/Tags/translated-default-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/translated-default-field.html|translated-default-field]]''':<<BR>>
 You should not mark as translatable "Default:" or "DefaultChoice:" fields, unless explicitly needed (e.g. default country, default language, etc.). If this Default field really should be translated, you should explain translators how they should translate it by using brackets. For example:

   _Default: English[ Default language name, but not translated]

Reference(s): [[DebianMan:7/po-debconf|po-debconf(7)]]
}}}}
##END:Lintian/Tags/translated-default-field

Self:Lintian/Tags/no-complete-debconf-translation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-complete-debconf-translation.html|no-complete-debconf-translation]]''':<<BR>>
 Even though this package provides debconf translation support, there are no translations or none of the translations are complete. This may mean that translators weren't properly warned about new strings.

 Translators may be notified of changes using podebconf-report-po, for example:

  podebconf-report-po --call --withtranslators --deadline="+10 days" \ --languageteam

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.2.2]]
}}}}
##END:Lintian/Tags/no-complete-debconf-translation

########################################################################
== changes-file ==
########################################################################

Self:Lintian/Tags/malformed-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-changes-file.html|malformed-changes-file]]''':<<BR>>
 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.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.5]]
}}}}
##END:Lintian/Tags/malformed-changes-file

Self:Lintian/Tags/no-description-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-description-in-changes-file.html|no-description-in-changes-file]]''':<<BR>>
 There is no "Description" field in your .changes file. A description is mandatory and is usually constructed from the descriptions in the control file of the package by the package build tools.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.5]]
}}}}
##END:Lintian/Tags/no-description-in-changes-file

Self:Lintian/Tags/bad-distribution-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-distribution-in-changes-file.html|bad-distribution-in-changes-file]]''':<<BR>>
 You've specified an unknown target distribution for your upload in the {{{debian/changelog}}} file.

 Note that the distributions {{{non-free}}} and {{{contrib}}} are no longer valid. You'll have to use distribution {{{unstable}}} and {{{Section: non-free/xxx}}} or {{{Section: contrib/xxx}}} instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.14]]
}}}}
##END:Lintian/Tags/bad-distribution-in-changes-file

Self:Lintian/Tags/bad-ubuntu-distribution-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-ubuntu-distribution-in-changes-file.html|bad-ubuntu-distribution-in-changes-file]]''':<<BR>>
 You've specified an unknown target distribution for your upload in the {{{debian/changelog}}} file.

 Your version string suggests this package is for Ubuntu, so your distribution should be one of maverick, lucid, karmic, jaunty, intrepid, hardy, or dapper.
}}}}
##END:Lintian/Tags/bad-ubuntu-distribution-in-changes-file

Self:Lintian/Tags/multiple-distributions-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/multiple-distributions-in-changes-file.html|multiple-distributions-in-changes-file]]''':<<BR>>
 You've specified more than one target distribution for your upload in the {{{*.changes}}} file, probably via the most recent entry in the {{{debian/changelog}}} 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.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.14]]
}}}}
##END:Lintian/Tags/multiple-distributions-in-changes-file

Self:Lintian/Tags/no-urgency-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-urgency-in-changes-file.html|no-urgency-in-changes-file]]''':<<BR>>
 There is no "Urgency" field in the .changes file. This field is recommended by policy and is usually derived from the first line of the most recent changelog entry by the package build tools.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.5]]
}}}}
##END:Lintian/Tags/no-urgency-in-changes-file

Self:Lintian/Tags/bad-urgency-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-urgency-in-changes-file.html|bad-urgency-in-changes-file]]''':<<BR>>
 The keyword value of the "Urgency" field in the .changes file is not one of the allowed values of low, medium, high, critical, and emergency (case-insensitive). This value normally taken from the first line of the most recent entry in {{{debian/changelog}}}, which is probably where the error is.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.17]]
}}}}
##END:Lintian/Tags/bad-urgency-in-changes-file

Self:Lintian/Tags/file-size-mismatch-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-size-mismatch-in-changes-file.html|file-size-mismatch-in-changes-file]]''':<<BR>>
 The actual file size does not match what's listed in the {{{.changes}}} file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.21]], [[http://www.debian.org/doc/debian-policy/|policy 5.6.24]]
}}}}
##END:Lintian/Tags/file-size-mismatch-in-changes-file

Self:Lintian/Tags/checksum-mismatch-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/checksum-mismatch-in-changes-file.html|checksum-mismatch-in-changes-file]]''':<<BR>>
 The actual checksum does not match what's listed in the {{{.changes}}} file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.21]], [[http://www.debian.org/doc/debian-policy/|policy 5.6.24]]
}}}}
##END:Lintian/Tags/checksum-mismatch-in-changes-file

Self:Lintian/Tags/bad-section-in-changes-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-section-in-changes-file.html|bad-section-in-changes-file]]''':<<BR>>
 The sections {{{non-free}}} and {{{contrib}}} are no longer valid. Please use section {{{non-free/xxx}}} or {{{contrib/xxx}}} instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 2.4]]
}}}}
##END:Lintian/Tags/bad-section-in-changes-file

Self:Lintian/Tags/changed-by-name-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changed-by-name-missing.html|changed-by-name-missing]]''':<<BR>>
 The Changed-By field seems to contain just an email address. It must contain the package maintainer's name and email address.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.4]]
}}}}
##END:Lintian/Tags/changed-by-name-missing

Self:Lintian/Tags/changed-by-address-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changed-by-address-missing.html|changed-by-address-missing]]''':<<BR>>
 The Changed-By field should contain the package builder's name and email address, with the name followed by the address inside angle brackets (< and >). The address seems to be missing.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.4]]
}}}}
##END:Lintian/Tags/changed-by-address-missing

Self:Lintian/Tags/changed-by-address-malformed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changed-by-address-malformed.html|changed-by-address-malformed]]''':<<BR>>
 The Changed-By field could not be parsed according to the rules in the Policy Manual.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.4]]
}}}}
##END:Lintian/Tags/changed-by-address-malformed

Self:Lintian/Tags/changed-by-address-looks-weird
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changed-by-address-looks-weird.html|changed-by-address-looks-weird]]''':<<BR>>
 The Changed-By field does not have whitespace between the name and the email address.
}}}}
##END:Lintian/Tags/changed-by-address-looks-weird

Self:Lintian/Tags/changed-by-address-is-on-localhost
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changed-by-address-is-on-localhost.html|changed-by-address-is-on-localhost]]''':<<BR>>
 The Changed-By address includes localhost(.localdomain), which is an invalid e-mail address.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/changed-by-address-is-on-localhost

########################################################################
== fields ==
########################################################################

Self:Lintian/Tags/unsupported-source-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unsupported-source-format.html|unsupported-source-format]]''':<<BR>>
 This package uses a different source package format than "1.0", "3.0 (quilt)" or "3.0 (native)". Other packages formats are supported by dpkg-source, but they are not allowed in the Debian archive.
}}}}
##END:Lintian/Tags/unsupported-source-format

Self:Lintian/Tags/no-package-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-package-name.html|no-package-name]]''':<<BR>>
 The package does not have a "Package:" field in its control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/no-package-name

Self:Lintian/Tags/bad-package-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-package-name.html|bad-package-name]]''':<<BR>>
 A package name should be at least two characters long, must consist of the alphanumerics and "+" "-" and ".", and must start with an alphanumeric character.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.7]]
}}}}
##END:Lintian/Tags/bad-package-name

Self:Lintian/Tags/package-not-lowercase
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-not-lowercase.html|package-not-lowercase]]''':<<BR>>
 New packages should not use uppercase characters in their names.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.7]]
}}}}
##END:Lintian/Tags/package-not-lowercase

Self:Lintian/Tags/bad-provided-package-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-provided-package-name.html|bad-provided-package-name]]''':<<BR>>
 A package name should be at least two characters long, must consist of the alphanumerics (lowercase characters only) and "+" "-" and ".", and must start with an alphanumeric character.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.7]]
}}}}
##END:Lintian/Tags/bad-provided-package-name

Self:Lintian/Tags/no-version-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-version-field.html|no-version-field]]''':<<BR>>
 The package does not have a "Version:" field in its control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/no-version-field

Self:Lintian/Tags/bad-version-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-version-number.html|bad-version-number]]''':<<BR>>
 The version number fails one of the syntactic requirements of dpkg.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.12]]
}}}}
##END:Lintian/Tags/bad-version-number

Self:Lintian/Tags/upstream-version-not-numeric
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/upstream-version-not-numeric.html|upstream-version-not-numeric]]''':<<BR>>
 The upstream version number should start with a digit.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.12]]
}}}}
##END:Lintian/Tags/upstream-version-not-numeric

Self:Lintian/Tags/debian-revision-not-well-formed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-revision-not-well-formed.html|debian-revision-not-well-formed]]''':<<BR>>
 The debian version part (the part after the -) should consist of one or two dot-separated parts: one for a regular maintainer release or two for a source-NMU.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.11.2]], [[http://www.debian.org/doc/debian-policy/|policy 5.6.12]]
}}}}
##END:Lintian/Tags/debian-revision-not-well-formed

Self:Lintian/Tags/debian-revision-should-not-be-zero
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-revision-should-not-be-zero.html|debian-revision-should-not-be-zero]]''':<<BR>>
 The debian version part (the part after the -) should start with one, not with zero. This is to ensure that a correctly-done Maintainer Upload will always have a higher version number than a Non-Maintainer upload: a NMU could have been prepared which introduces this upstream version with Debian-revision -0.1

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.11.2]]
}}}}
##END:Lintian/Tags/debian-revision-should-not-be-zero

Self:Lintian/Tags/no-architecture-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-architecture-field.html|no-architecture-field]]''':<<BR>>
 The package does not have an "Architecture:" field in its control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/no-architecture-field

Self:Lintian/Tags/magic-arch-in-arch-list
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/magic-arch-in-arch-list.html|magic-arch-in-arch-list]]''':<<BR>>
 The special architecture value "any" only make sense if it occurs alone. The value "all" may appear together with other architectures in a *.dsc file but must occur alone if used in a binary package.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.8]]
}}}}
##END:Lintian/Tags/magic-arch-in-arch-list

Self:Lintian/Tags/unknown-architecture
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-architecture.html|unknown-architecture]]''':<<BR>>
 This package claims to be for an unknown architecture. The architecture should be one of the values supported by dpkg or one of the special values "all" or "any". The special value "source" is only used in *.changes files and does not make sense in a binary package or a *.dsc file.
}}}}
##END:Lintian/Tags/unknown-architecture

Self:Lintian/Tags/too-many-architectures
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/too-many-architectures.html|too-many-architectures]]''':<<BR>>
 A binary package should list exactly one architecture (the one it is compiled for), or the special value "all" if it is architecture-independent.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.8]]
}}}}
##END:Lintian/Tags/too-many-architectures

Self:Lintian/Tags/arch-wildcard-in-binary-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/arch-wildcard-in-binary-package.html|arch-wildcard-in-binary-package]]''':<<BR>>
 Architecture wildcards, including the special architecture value "any", do not make sense in a binary package. A binary package must either be architecture-independent or built for a specific architecture.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.8]]
}}}}
##END:Lintian/Tags/arch-wildcard-in-binary-package

Self:Lintian/Tags/aspell-package-not-arch-all
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/aspell-package-not-arch-all.html|aspell-package-not-arch-all]]''':<<BR>>
 This package appears to be an aspell dictionary package, but it is not Architecture: all. The binary hashes should be built at install-time by calling aspell-autobuildhash, so the contents of the package should be architecture-independent.

Reference(s): [[DebianMan:8/aspell-autobuildhash|aspell-autobuildhash(8)]]
}}}}
##END:Lintian/Tags/aspell-package-not-arch-all

Self:Lintian/Tags/no-maintainer-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-maintainer-field.html|no-maintainer-field]]''':<<BR>>
 The package does not have a "Maintainer:" field in its control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/no-maintainer-field

Self:Lintian/Tags/maintainer-name-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-name-missing.html|maintainer-name-missing]]''':<<BR>>
 The maintainer field seems to contain just an email address. It must contain the package maintainer's name and email address.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/maintainer-name-missing

Self:Lintian/Tags/maintainer-address-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-address-missing.html|maintainer-address-missing]]''':<<BR>>
 The maintainer field must contain the package maintainer's name and email address, with the name followed by the address inside angle brackets (< and >). The address seems to be missing.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/maintainer-address-missing

Self:Lintian/Tags/maintainer-address-malformed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-address-malformed.html|maintainer-address-malformed]]''':<<BR>>
 The maintainer field could not be parsed according to the rules in the Policy Manual.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/maintainer-address-malformed

Self:Lintian/Tags/maintainer-not-full-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-not-full-name.html|maintainer-not-full-name]]''':<<BR>>
 The "name" part of this maintainer field is just one word, so it might not be a full name.
}}}}
##END:Lintian/Tags/maintainer-not-full-name

Self:Lintian/Tags/maintainer-address-looks-weird
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-address-looks-weird.html|maintainer-address-looks-weird]]''':<<BR>>
 The maintainer address does not have whitespace between the name and the email address.
}}}}
##END:Lintian/Tags/maintainer-address-looks-weird

Self:Lintian/Tags/maintainer-address-is-on-localhost
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-address-is-on-localhost.html|maintainer-address-is-on-localhost]]''':<<BR>>
 The maintainer address includes localhost(.localdomain), which is an invalid e-mail address.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/maintainer-address-is-on-localhost

Self:Lintian/Tags/uploader-name-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uploader-name-missing.html|uploader-name-missing]]''':<<BR>>
 The uploader field seems to contain just an email address. It must contain the package uploader's name and email address.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/uploader-name-missing

Self:Lintian/Tags/uploader-address-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uploader-address-missing.html|uploader-address-missing]]''':<<BR>>
 The uploader field should contain the package uploader's name and email address, with the name followed by the address inside angle brackets (< and >). The address seems to be missing.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/uploader-address-missing

Self:Lintian/Tags/uploader-address-malformed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uploader-address-malformed.html|uploader-address-malformed]]''':<<BR>>
 The uploader field could not be parsed according to the rules in the Policy Manual.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/uploader-address-malformed

Self:Lintian/Tags/uploader-not-full-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uploader-not-full-name.html|uploader-not-full-name]]''':<<BR>>
 The "name" part of this uploader field is just one word, so it might not be a full name.
}}}}
##END:Lintian/Tags/uploader-not-full-name

Self:Lintian/Tags/uploader-address-looks-weird
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uploader-address-looks-weird.html|uploader-address-looks-weird]]''':<<BR>>
 The uploader address does not have whitespace between the name and the email address.
}}}}
##END:Lintian/Tags/uploader-address-looks-weird

Self:Lintian/Tags/uploader-address-is-on-localhost
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uploader-address-is-on-localhost.html|uploader-address-is-on-localhost]]''':<<BR>>
 The uploader address includes localhost(.localdomain), which is an invalid e-mail address.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.2]]
}}}}
##END:Lintian/Tags/uploader-address-is-on-localhost

Self:Lintian/Tags/wrong-debian-qa-address-set-as-maintainer
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-debian-qa-address-set-as-maintainer.html|wrong-debian-qa-address-set-as-maintainer]]''':<<BR>>
 Orphaned packages should no longer have the address <debian-qa@lists.debian.org> in the Maintainer field.

 The correct Maintainer field for orphaned packages is Debian QA Group <packages@qa.debian.org>.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.9.4]]
}}}}
##END:Lintian/Tags/wrong-debian-qa-address-set-as-maintainer

Self:Lintian/Tags/wrong-debian-qa-group-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-debian-qa-group-name.html|wrong-debian-qa-group-name]]''':<<BR>>
 Orphaned packages should have "Debian QA Group <packages@qa.debian.org>" in the maintainer field.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.9.4]]
}}}}
##END:Lintian/Tags/wrong-debian-qa-group-name

Self:Lintian/Tags/no-human-maintainers
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-human-maintainers.html|no-human-maintainers]]''':<<BR>>
 The Maintainer address for this package is a mailing list and there are no Uploaders listed. Team-maintained packages should list the human maintainers in the Uploaders field.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.12]]
}}}}
##END:Lintian/Tags/no-human-maintainers

Self:Lintian/Tags/no-source-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-source-field.html|no-source-field]]''':<<BR>>
 The package does not have a "Source:" field in its control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.2]]
}}}}
##END:Lintian/Tags/no-source-field

Self:Lintian/Tags/source-field-does-not-match-pkg-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-field-does-not-match-pkg-name.html|source-field-does-not-match-pkg-name]]''':<<BR>>
 The source package's filename is not the same as the name given in its Source field. The Source field should name the package.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.1]]
}}}}
##END:Lintian/Tags/source-field-does-not-match-pkg-name

Self:Lintian/Tags/source-field-malformed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-field-malformed.html|source-field-malformed]]''':<<BR>>
 In {{{debian/control}}} or a {{{.dsc}}} file, the Source field must contain only the name of the source package. In a binary package, the Source field may also optionally contain the version number of the corresponding source package in parentheses.

 Source package names must consist only of lowercase letters, digits, plus and minus signs, and periods. They must be at least two characters long and must start with an alphanumeric character.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.1]]
}}}}
##END:Lintian/Tags/source-field-malformed

Self:Lintian/Tags/essential-in-source-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/essential-in-source-package.html|essential-in-source-package]]''':<<BR>>
 This field should only appear in binary packages.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.9]]
}}}}
##END:Lintian/Tags/essential-in-source-package

Self:Lintian/Tags/essential-no-not-needed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/essential-no-not-needed.html|essential-no-not-needed]]''':<<BR>>
 Having "Essential: no" is the same as not having the field at all, so it just makes the Packages file longer with no benefit.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.9]]
}}}}
##END:Lintian/Tags/essential-no-not-needed

Self:Lintian/Tags/unknown-essential-value
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-essential-value.html|unknown-essential-value]]''':<<BR>>
 The only valid values for the Essential field are yes and no.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.9]]
}}}}
##END:Lintian/Tags/unknown-essential-value

Self:Lintian/Tags/no-section-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-section-field.html|no-section-field]]''':<<BR>>
 The package does not have a "Section:" field in its control file.

 The field is mandatory for source packages and optional for binary packages, which use the source package's value as default is nothing else is specified.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/no-section-field

Self:Lintian/Tags/unknown-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-section.html|unknown-section]]''':<<BR>>
 The "Section:" field in this package's control file is not one of the sections in use on the ftp archive. Valid sections are currently admin, comm, cli-mono, database, debug, devel, doc, editors, electronics, embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, haskell, httpd, interpreters, java, kde, libdevel, libs, lisp, localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, otherosfs, perl, php, python, ruby, science, shells, sound, tex, text, utils, vcs, video, web, x11, xfce, zope.

 The section name should be preceded by "non-free/" if the package is in the non-free archive area, and by "contrib/" if the package is in the contrib archive area.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 2.4]]
}}}}
##END:Lintian/Tags/unknown-section

Self:Lintian/Tags/section-is-dh_make-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/section-is-dh_make-template.html|section-is-dh_make-template]]''':<<BR>>
 The "Section:" field in this package's control file is set to unknown. This is not a valid section, and usually means a dh_make template control file was used and never modified to set the correct section.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 2.4]]
}}}}
##END:Lintian/Tags/section-is-dh_make-template

Self:Lintian/Tags/wrong-section-for-udeb
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-section-for-udeb.html|wrong-section-for-udeb]]''':<<BR>>
 udeb packages should have "Section: debian-installer".
}}}}
##END:Lintian/Tags/wrong-section-for-udeb

Self:Lintian/Tags/no-priority-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-priority-field.html|no-priority-field]]''':<<BR>>
 The package does not have a "Priority:" field in its control file.

 The Priority field can be included in a binary package by passing the -ip or -isp flags to dpkg-gencontrol when building the package. The field is optional in binary packages.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/no-priority-field

Self:Lintian/Tags/unknown-priority
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-priority.html|unknown-priority]]''':<<BR>>
 The "Priority:" field in this package's control file is not one of the priorities defined in the Policy Manual.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 2.5]]
}}}}
##END:Lintian/Tags/unknown-priority

Self:Lintian/Tags/superfluous-clutter-in-homepage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/superfluous-clutter-in-homepage.html|superfluous-clutter-in-homepage]]''':<<BR>>
 The "Homepage:" field in this package's control file contains superfluous markup around the URL, like enclosing < and >. This is unnecessary and needlessly complicates using this information.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.23]]
}}}}
##END:Lintian/Tags/superfluous-clutter-in-homepage

Self:Lintian/Tags/bad-homepage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-homepage.html|bad-homepage]]''':<<BR>>
 The "Homepage:" field in this package's control file does not contain a valid absolute URL. Most probably you forgot to specify the scheme (e.g. http).
}}}}
##END:Lintian/Tags/bad-homepage

Self:Lintian/Tags/no-homepage-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-homepage-field.html|no-homepage-field]]''':<<BR>>
 This non-native package lacks a {{{Homepage}}} field. If the package has an upstream home page that contains useful information or resources for the end user, consider adding a {{{Homepage}}} control field to {{{debian/control}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.23]]
}}}}
##END:Lintian/Tags/no-homepage-field

Self:Lintian/Tags/homepage-for-cpan-package-contains-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/homepage-for-cpan-package-contains-version.html|homepage-for-cpan-package-contains-version]]''':<<BR>>
 The Homepage field for this package points to CPAN and the URL includes the version. It's better to link to the unversioned CPAN page so that the URL doesn't have to be updated for each new release. For example, use:

   http://search.cpan.org/~samtregar/HTML-Template/

 not:

   http://search.cpan.org/~samtregar/HTML-Template-2.9/
}}}}
##END:Lintian/Tags/homepage-for-cpan-package-contains-version

Self:Lintian/Tags/obsolete-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/obsolete-field.html|obsolete-field]]''':<<BR>>
 This field is listed in the Policy Manual as obsolete and not-to-be-present in any package.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy D.2.6]]
}}}}
##END:Lintian/Tags/obsolete-field

Self:Lintian/Tags/unknown-field-in-dsc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-field-in-dsc.html|unknown-field-in-dsc]]''':<<BR>>
 See the Policy Manual for a list of the possible fields in a source package control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.4]]
}}}}
##END:Lintian/Tags/unknown-field-in-dsc

Self:Lintian/Tags/unknown-field-in-control
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-field-in-control.html|unknown-field-in-control]]''':<<BR>>
 See the Policy Manual for a list of the possible fields in a binary package control file.

 In udeb packages the fields pre-depends, conflicts, essential and suggests are disallowed, but they can contain the new fields subarchitecture and installer-menu-item.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.3]]
}}}}
##END:Lintian/Tags/unknown-field-in-control

Self:Lintian/Tags/multiline-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/multiline-field.html|multiline-field]]''':<<BR>>
 Most control fields must have only a single line of data.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.1]]
}}}}
##END:Lintian/Tags/multiline-field

Self:Lintian/Tags/alternates-not-allowed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/alternates-not-allowed.html|alternates-not-allowed]]''':<<BR>>
 Only the "Depends", "Recommends", "Suggests" and "Pre-Depends" fields may specify alternate dependencies using the "|" symbol.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.1]]
}}}}
##END:Lintian/Tags/alternates-not-allowed

Self:Lintian/Tags/versioned-provides
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/versioned-provides.html|versioned-provides]]''':<<BR>>
 The "Provides" field may not specify a version range.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.1]]
}}}}
##END:Lintian/Tags/versioned-provides

Self:Lintian/Tags/obsolete-relation-form
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/obsolete-relation-form.html|obsolete-relation-form]]''':<<BR>>
 The forms "<" and ">" mean "<=" and ">=", not "<<" and ">>" as one might expect. For that reason these forms are obsolete, and should not be used in new packages. Use the longer forms instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.1]]
}}}}
##END:Lintian/Tags/obsolete-relation-form

Self:Lintian/Tags/bad-version-in-relation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-version-in-relation.html|bad-version-in-relation]]''':<<BR>>
 The version number used in this relationship does not match the defined format of a version number.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.12]]
}}}}
##END:Lintian/Tags/bad-version-in-relation

Self:Lintian/Tags/package-relation-with-self
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-relation-with-self.html|package-relation-with-self]]''':<<BR>>
 The package declares a relationship with itself. This is not very useful, except in the case of a package Conflicting with itself, if its package name doubles as a virtual package.
}}}}
##END:Lintian/Tags/package-relation-with-self

Self:Lintian/Tags/bad-relation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-relation.html|bad-relation]]''':<<BR>>
 The package declares a relationship that could not be parsed according to the rules given in the Policy Manual.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.1]]
}}}}
##END:Lintian/Tags/bad-relation

Self:Lintian/Tags/new-essential-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/new-essential-package.html|new-essential-package]]''':<<BR>>
 This package has the Essential flag set. New Essential packages are sufficiently rare that it seems worth warning about. They should be discussed on debian-devel first.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.8]]
}}}}
##END:Lintian/Tags/new-essential-package

Self:Lintian/Tags/doc-package-depends-on-main-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-package-depends-on-main-package.html|doc-package-depends-on-main-package]]''':<<BR>>
 The name of this package suggests that it is a documentation package. It is usually not desirable for documentation packages to depend on the packages they document, because users may want to install the docs before they decide whether they want to install the package. Also, documentation packages are often architecture-independent, so on other architectures the package on which it depends may not even exist.
}}}}
##END:Lintian/Tags/doc-package-depends-on-main-package

Self:Lintian/Tags/depends-on-obsolete-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-obsolete-package.html|depends-on-obsolete-package]]''':<<BR>>
 The package depends on a package that has been superseded. If the superseded package is part of an ORed group, it should not be the first package in the group.
}}}}
##END:Lintian/Tags/depends-on-obsolete-package

Self:Lintian/Tags/ored-depends-on-obsolete-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ored-depends-on-obsolete-package.html|ored-depends-on-obsolete-package]]''':<<BR>>
 The package depends on an ORed group of packages which includes a package that has been superseded.
}}}}
##END:Lintian/Tags/ored-depends-on-obsolete-package

Self:Lintian/Tags/build-depends-on-obsolete-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-obsolete-package.html|build-depends-on-obsolete-package]]''':<<BR>>
 The package build-depends on a package that has been superseded. If the superseded package is part of an ORed group, it should not be the first package in the group.
}}}}
##END:Lintian/Tags/build-depends-on-obsolete-package

Self:Lintian/Tags/ored-build-depends-on-obsolete-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ored-build-depends-on-obsolete-package.html|ored-build-depends-on-obsolete-package]]''':<<BR>>
 The package build-depends on an ORed group of packages which includes a package that has been superseded.
}}}}
##END:Lintian/Tags/ored-build-depends-on-obsolete-package

Self:Lintian/Tags/depends-on-old-emacs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-old-emacs.html|depends-on-old-emacs]]''':<<BR>>
 The package lists an old version of Emacs as its first dependency. It should probably be updated to support the current version of Emacs in the archive and then list that version first in the list of Emacs flavors it supports.

 If the package intentionally only supports older versions of Emacs (if, for example, it was included with later versions of Emacs), add a lintian override.
}}}}
##END:Lintian/Tags/depends-on-old-emacs

Self:Lintian/Tags/depends-on-metapackage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-metapackage.html|depends-on-metapackage]]''':<<BR>>
 This package is one of the packages that Lintian believes is a metapackage: a package that exists for the convenience of users or installers to install a set of related packages. Packages that are not themselves metapackages must not depend on metapackages, since this may prevent the user from removing portions of the package set they don't need.
}}}}
##END:Lintian/Tags/depends-on-metapackage

Self:Lintian/Tags/build-depends-on-metapackage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-metapackage.html|build-depends-on-metapackage]]''':<<BR>>
 Packages must not build-depend on X Window System metapackages.

 The metapackages xorg, xorg-dev, x-window-system, x-window-system-dev, and x-window-system-core exist only for the benefit of users and should not be used in package build dependencies.
}}}}
##END:Lintian/Tags/build-depends-on-metapackage

Self:Lintian/Tags/depends-on-essential-package-without-using-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-essential-package-without-using-version.html|depends-on-essential-package-without-using-version]]''':<<BR>>
 The package declares a depends on an essential package, e.g. dpkg, without using a versioned depends. Packages do not need to depend on essential packages; essential means that they will always be present. The only reason to list an explicit dependency on an essential package is if you need a particular version of that package, in which case the version should be given in the dependency.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.5]]
}}}}
##END:Lintian/Tags/depends-on-essential-package-without-using-version

Self:Lintian/Tags/build-depends-on-essential-package-without-using-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-essential-package-without-using-version.html|build-depends-on-essential-package-without-using-version]]''':<<BR>>
 The package declares a build-depends on an essential package, e.g. dpkg, without using a versioned depends. Packages do not need to build-depend on essential packages; essential means that they will always be present. The only reason to list an explicit dependency on an essential package is if you need a particular version of that package, in which case the version should be given in the dependency.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.2]]
}}}}
##END:Lintian/Tags/build-depends-on-essential-package-without-using-version

Self:Lintian/Tags/build-depends-on-non-build-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-non-build-package.html|build-depends-on-non-build-package]]''':<<BR>>
 The package declares a build dependency on a package that is not appropriate for build dependencies, usually because it's only for interactive use or cannot be correctly installed in a build environment. See the description or documentation of the package for more information.
}}}}
##END:Lintian/Tags/build-depends-on-non-build-package

Self:Lintian/Tags/virtual-package-depends-without-real-package-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/virtual-package-depends-without-real-package-depends.html|virtual-package-depends-without-real-package-depends]]''':<<BR>>
 The package declares a depends on a virtual package without listing a real package as an alternative first.

 If this package could ever be a build dependency, it should list a real package as the first alternative to any virtual package in its Depends. Otherwise, the build daemons will not be able to provide a consistent build environment.

 If it will never be a build dependency, this isn't necessary, but you may want to consider doing so anyway if there is a real package providing that virtual package that most users will want to use.
}}}}
##END:Lintian/Tags/virtual-package-depends-without-real-package-depends

Self:Lintian/Tags/invalid-arch-string-in-source-relation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/invalid-arch-string-in-source-relation.html|invalid-arch-string-in-source-relation]]''':<<BR>>
 The architecture string in the source relation includes an unknown architecture. This may be a typo, or it may be an architecture that dpkg doesn't know about yet. A common problem is incorrectly separating architectures with a comma, such as {{{[i386, m68k]}}}. Architectures are separated by spaces; this should instead be {{{[i386 m68k]}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.8]]
}}}}
##END:Lintian/Tags/invalid-arch-string-in-source-relation

Self:Lintian/Tags/conflicting-negation-in-source-relation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/conflicting-negation-in-source-relation.html|conflicting-negation-in-source-relation]]''':<<BR>>
 The architecture string in this source relation has some negated architectures (prepended by {{{!}}}) and others that are not negated. This is not permitted by Policy. Either all architectures must be negated or none of them may be.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.1]]
}}}}
##END:Lintian/Tags/conflicting-negation-in-source-relation

Self:Lintian/Tags/depends-on-build-essential-package-without-using-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-build-essential-package-without-using-version.html|depends-on-build-essential-package-without-using-version]]''':<<BR>>
 The package declares a depends on a build essential package without using a versioned depends. Packages do not have to build-depend on any package included in build-essential. It is the responsibility of anyone building packages to have all build-essential packages installed. The only reason for an explicit dependency on a package included in build-essential is if a particular version of that package is required, in which case the dependency should include the version.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.2]]
}}}}
##END:Lintian/Tags/depends-on-build-essential-package-without-using-version

Self:Lintian/Tags/package-depends-on-an-x-font-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-an-x-font-package.html|package-depends-on-an-x-font-package]]''':<<BR>>
 Packages must not depend on X Window System font packages.

 If one or more of the fonts so packaged are necessary for proper operation of the package with which they are associated the font package may be Recommended; if the fonts merely provide an enhancement, a Suggests relationship may be used.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.8.5]]
}}}}
##END:Lintian/Tags/package-depends-on-an-x-font-package

Self:Lintian/Tags/build-depends-indep-without-arch-indep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-indep-without-arch-indep.html|build-depends-indep-without-arch-indep]]''':<<BR>>
 The control file specifies source relations for architecture-independent packages, but no architecture-independent packages are built.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.7]]
}}}}
##END:Lintian/Tags/build-depends-indep-without-arch-indep

Self:Lintian/Tags/build-conflicts-with-build-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-conflicts-with-build-dependency.html|build-conflicts-with-build-dependency]]''':<<BR>>
 The package build-conflicts with a package that it also build-depends on.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.7]]
}}}}
##END:Lintian/Tags/build-conflicts-with-build-dependency

Self:Lintian/Tags/package-has-a-duplicate-build-relation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-has-a-duplicate-build-relation.html|package-has-a-duplicate-build-relation]]''':<<BR>>
 The package declares the given build relations on the same package in either Build-Depends or Build-Depends-Indep, but the build relations imply each other and are therefore redundant.
}}}}
##END:Lintian/Tags/package-has-a-duplicate-build-relation

Self:Lintian/Tags/build-depends-on-1-revision
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-1-revision.html|build-depends-on-1-revision]]''':<<BR>>
 The package declares a build dependency on a version of a package with a -1 Debian revision such as "libfoo (>= 1.2-1)". Such a dependency will not be satisfied by a backport of libfoo 1.2-1 and therefore makes backporting unnecessarily difficult. Normally, the -1 version is unneeded and a dependency such as "libfoo (>= 1.2)" would be sufficient. If there was an earlier -0.X version of libfoo that would not satisfy the dependency, use "libfoo (>= 1.2-1~)" instead.
}}}}
##END:Lintian/Tags/build-depends-on-1-revision

Self:Lintian/Tags/needlessly-depends-on-awk
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/needlessly-depends-on-awk.html|needlessly-depends-on-awk]]''':<<BR>>
 The package seems to declare a relation on awk. awk is a virtual package, but it is special since it's de facto essential. If you don't need to depend on a specific version of awk (which wouldn't work anyway, as dpkg doesn't support versioned provides), you should remove the dependency on awk.
}}}}
##END:Lintian/Tags/needlessly-depends-on-awk

Self:Lintian/Tags/package-depends-on-multiple-libstdc-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-multiple-libstdc-versions.html|package-depends-on-multiple-libstdc-versions]]''':<<BR>>
 The package seems to declare several relations to a libstdc version. This is not only sloppy but in the case of libraries, it may well break the runtime execution of programs.
}}}}
##END:Lintian/Tags/package-depends-on-multiple-libstdc-versions

Self:Lintian/Tags/package-depends-on-multiple-tcl-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-multiple-tcl-versions.html|package-depends-on-multiple-tcl-versions]]''':<<BR>>
 The package seems to declare several relations to a tcl version. This is not only sloppy but in the case of libraries, it may well break the runtime execution of programs.
}}}}
##END:Lintian/Tags/package-depends-on-multiple-tcl-versions

Self:Lintian/Tags/package-depends-on-multiple-tclx-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-multiple-tclx-versions.html|package-depends-on-multiple-tclx-versions]]''':<<BR>>
 The package seems to declare several relations to a tclx version. This is not only sloppy but in the case of libraries, it may well break the runtime execution of programs.
}}}}
##END:Lintian/Tags/package-depends-on-multiple-tclx-versions

Self:Lintian/Tags/package-depends-on-multiple-tk-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-multiple-tk-versions.html|package-depends-on-multiple-tk-versions]]''':<<BR>>
 The package seems to declare several relations to a tk version. This is not only sloppy but in the case of libraries, it may well break the runtime execution of programs.
}}}}
##END:Lintian/Tags/package-depends-on-multiple-tk-versions

Self:Lintian/Tags/package-depends-on-multiple-tkx-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-multiple-tkx-versions.html|package-depends-on-multiple-tkx-versions]]''':<<BR>>
 The package seems to declare several relations to a tkx version. This is not only sloppy but in the case of libraries, it may well break the runtime execution of programs.
}}}}
##END:Lintian/Tags/package-depends-on-multiple-tkx-versions

Self:Lintian/Tags/package-depends-on-multiple-libpng-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-multiple-libpng-versions.html|package-depends-on-multiple-libpng-versions]]''':<<BR>>
 The package seems to declare several relations to a libpng version. This is not only sloppy but in the case of libraries, it may well break the runtime execution of programs.
}}}}
##END:Lintian/Tags/package-depends-on-multiple-libpng-versions

Self:Lintian/Tags/depends-on-libdb1-compat
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-libdb1-compat.html|depends-on-libdb1-compat]]''':<<BR>>
 The package seems to declare a relation on libdb1-compat. This library exists for compatibility with applications built against glibc 2.0 or 2.1. There is intentionally no corresponding development package. Do not link new applications against this library!
}}}}
##END:Lintian/Tags/depends-on-libdb1-compat

Self:Lintian/Tags/depends-on-python-minimal
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-on-python-minimal.html|depends-on-python-minimal]]''':<<BR>>
 The python-minimal package (and versioned variants thereof) exists only to possibly become an Essential package. Depending on it is always an error since it should never be installed without python. If it becomes Essential, there is no need to depend on it, and until then, packages that require Python must depend on python.
}}}}
##END:Lintian/Tags/depends-on-python-minimal

Self:Lintian/Tags/depends-exclusively-on-makedev
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/depends-exclusively-on-makedev.html|depends-exclusively-on-makedev]]''':<<BR>>
 This package depends on makedev without a udev alternative. This probably means that it doesn't have udev rules and relies on makedev to create devices, which won't work if udev is installed and running. Alternatively, it may mean that there are udev rules, but udev was not added as an alternative to the makedev dependency.
}}}}
##END:Lintian/Tags/depends-exclusively-on-makedev

Self:Lintian/Tags/dbg-package-missing-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dbg-package-missing-depends.html|dbg-package-missing-depends]]''':<<BR>>
 The given binary package has a name of the form of "X-dbg", indicating it contains detached debugging symbols for the package X. If so, it should depend on the corresponding package, generally with (= ${binary:Version}) since the debugging symbols are only useful with the binaries created by the same build.

 If this package provides debugging symbols for multiple other packages, it should normally depend on all of those packages as alternatives. In other words, {{{pkga (= ${binary:Version}) | pkgb (= ${binary:Version)}}} and so forth.
}}}}
##END:Lintian/Tags/dbg-package-missing-depends

Self:Lintian/Tags/conflicts-with-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/conflicts-with-dependency.html|conflicts-with-dependency]]''':<<BR>>
 The package seems to conflict with one of its dependencies, recommendations, or suggestions by listing it in Conflicts or Breaks.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.4]]
}}}}
##END:Lintian/Tags/conflicts-with-dependency

Self:Lintian/Tags/breaks-without-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/breaks-without-version.html|breaks-without-version]]''':<<BR>>
 This package declares a Breaks relationship with another package that has no version number. Normally, Breaks should be used to indicate an incompatibility with a specific version of another package, or with all versions predating a fix. If the two packages can never be installed at the same time, Conflicts should normally be used instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.3]]
}}}}
##END:Lintian/Tags/breaks-without-version

Self:Lintian/Tags/conflicts-with-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/conflicts-with-version.html|conflicts-with-version]]''':<<BR>>
 An earlier-than version clause is normally an indication that Breaks should be used instead of Conflicts. Breaks is a weaker requirement that provides the package manager more leeway to find a valid upgrade path. Conflicts should only be used if two packages can never be unpacked at the same time, or for some situations involving virtual packages (where a version clause is not appropriate). In particular, when moving files between packages, use Breaks plus Replaces, not Conflicts plus Replaces.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.4]]
}}}}
##END:Lintian/Tags/conflicts-with-version

Self:Lintian/Tags/bad-menu-item
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-menu-item.html|bad-menu-item]]''':<<BR>>
 The field Installer-Menu-Item should only contain positive integer values.
}}}}
##END:Lintian/Tags/bad-menu-item

Self:Lintian/Tags/redundant-origin-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/redundant-origin-field.html|redundant-origin-field]]''':<<BR>>
 You use the Origin field though the field value is the default (Debian). In this case the field is redundant and should be removed.
}}}}
##END:Lintian/Tags/redundant-origin-field

Self:Lintian/Tags/binary-nmu-uses-old-version-style
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-nmu-uses-old-version-style.html|binary-nmu-uses-old-version-style]]''':<<BR>>
 The version number of a binary NMU should be formed by appending {{{+b}}} and a digit to the source version. This version scheme is special-cased by the archive software. The -x.x.x version number style should no longer be used.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.10.2.1]]
}}}}
##END:Lintian/Tags/binary-nmu-uses-old-version-style

Self:Lintian/Tags/binary-nmu-debian-revision-in-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-nmu-debian-revision-in-source.html|binary-nmu-debian-revision-in-source]]''':<<BR>>
 The version number of your source package ends in +b and a number or has a Debian revision containing three parts. These version numbers are used by binary NMUs and should not be used as the source version. (The +b form is the current standard; the three-part version number now obsolete.)

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.10.2.1]]
}}}}
##END:Lintian/Tags/binary-nmu-debian-revision-in-source

Self:Lintian/Tags/dfsg-version-in-native-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dfsg-version-in-native-package.html|dfsg-version-in-native-package]]''':<<BR>>
 The version number of this package contains "dfsg", but it's a native package. "dfsg" is conventionally used in the upstream version of packages that are repackaged for Debian Free Software Guidelines compliance reasons. The convention doesn't make sense in native packages.
}}}}
##END:Lintian/Tags/dfsg-version-in-native-package

Self:Lintian/Tags/dfsg-version-with-period
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dfsg-version-with-period.html|dfsg-version-with-period]]''':<<BR>>
 The version number of this package contains ".dfsg", probably in a form like "1.2.dfsg1". There is a subtle sorting problem with this version method: 1.2.dfsg1 is considered a later version than 1.2.1. If upstream adds another level to its versioning, finding a good version number for the next upstream release will be awkward.

 Upstream may never do this, in which case this isn't a problem, but it's normally better to use "+dfsg" instead (such as "1.2+dfsg1"). "+" sorts before ".", so 1.2 < 1.2+dfsg1 < 1.2.1 as normally desired.
}}}}
##END:Lintian/Tags/dfsg-version-with-period

Self:Lintian/Tags/dfsg-version-misspelled
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dfsg-version-misspelled.html|dfsg-version-misspelled]]''':<<BR>>
 The version number of this package contains "dsfg". You probably meant "dfsg", the conventional marker for upstream packages that are repackaged for Debian Free Software Guidelines compliance reasons.
}}}}
##END:Lintian/Tags/dfsg-version-misspelled

Self:Lintian/Tags/redundant-bugs-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/redundant-bugs-field.html|redundant-bugs-field]]''':<<BR>>
 You use the Bugs field though the field value is the default (debbugs://bugs.debian.org/). In this case the field is redundant and should be removed.
}}}}
##END:Lintian/Tags/redundant-bugs-field

Self:Lintian/Tags/build-depends-on-build-essential
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-build-essential.html|build-depends-on-build-essential]]''':<<BR>>
 You depend on the build-essential package, which is only a meta-package depending on build tools that have to be installed in all build environments.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.7]]
}}}}
##END:Lintian/Tags/build-depends-on-build-essential

Self:Lintian/Tags/malformed-python-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-python-version.html|malformed-python-version]]''':<<BR>>
 The Python-Version control field is not in one of the valid formats. It should be in one of the following formats:

     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.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/python-policy/|python-policy 2.3]]
}}}}
##END:Lintian/Tags/malformed-python-version

Self:Lintian/Tags/old-versioned-python-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/old-versioned-python-dependency.html|old-versioned-python-dependency]]''':<<BR>>
 This package appears to be an architecture-independent Python module but has a dependency on a version of python less than a particular version, doesn't use python-support and no Python-Version control field. This normally means that the package isn't using the current Python policy; most architecture-independent Python packages will work with any future version of Python if they follow the new policy.

 If this package really does require only a particular range of Python versions and uses python-central, add a Python-Version control field (as described in 2.3 of the Python policy) to resolve this warning.
}}}}
##END:Lintian/Tags/old-versioned-python-dependency

Self:Lintian/Tags/malformed-dm-upload-allowed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-dm-upload-allowed.html|malformed-dm-upload-allowed]]''':<<BR>>
 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.

Reference(s): [[http://www.debian.org/vote/2007/vote_003]]
}}}}
##END:Lintian/Tags/malformed-dm-upload-allowed

Self:Lintian/Tags/wrong-section-according-to-package-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-section-according-to-package-name.html|wrong-section-according-to-package-name]]''':<<BR>>
 This package has a name suggesting that it belongs to a section other than the one it is currently categorized in.
}}}}
##END:Lintian/Tags/wrong-section-according-to-package-name

Self:Lintian/Tags/debug-package-should-be-priority-extra
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debug-package-should-be-priority-extra.html|debug-package-should-be-priority-extra]]''':<<BR>>
 This package has a name suggesting that it contains detached debugging symbols. If so, it should have priority "extra" since users normally do not need such packages.
}}}}
##END:Lintian/Tags/debug-package-should-be-priority-extra

Self:Lintian/Tags/maintainer-also-in-uploaders
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-also-in-uploaders.html|maintainer-also-in-uploaders]]''':<<BR>>
 The maintainer value also appears on the {{{Uploaders}}} 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.
}}}}
##END:Lintian/Tags/maintainer-also-in-uploaders

Self:Lintian/Tags/duplicate-uploader
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-uploader.html|duplicate-uploader]]''':<<BR>>
 The uploader appears more than once in the {{{Uploaders}}} field. The duplicate information should be removed.
}}}}
##END:Lintian/Tags/duplicate-uploader

Self:Lintian/Tags/versioned-dependency-satisfied-by-perl
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/versioned-dependency-satisfied-by-perl.html|versioned-dependency-satisfied-by-perl]]''':<<BR>>
 This package declares an unnecessary versioned dependency on a package that is also provided by one of the Perl core packages (perl, perl-base, perl-modules) with at least the required version.

 As versioned dependencies are not satisfied by provided packages, this unnecessarily pulls in a separately packaged newer version of the module.

 The recommended way to express the dependency without needless complications on backporting packages is to use alternative dependencies. The perl package should be the preferred alternative and the versioned dependency a secondary one.

 Example: perl (>= 5.10.0) | libmodule-build-perl (>= 0.26)

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.5]]
}}}}
##END:Lintian/Tags/versioned-dependency-satisfied-by-perl

Self:Lintian/Tags/package-superseded-by-perl
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-superseded-by-perl.html|package-superseded-by-perl]]''':<<BR>>
 This package is also provided by one of the Perl core packages (perl, perl-base, perl-modules), and the core version is at least as new as this one.

 The package should either be upgraded to a newer upstream version or removed from the archive as unnecessary. In the removal case, any versioned dependencies on this package must first be changed to include the Perl core package (because versioned dependencies are not satisfied by provided packages).

 The recommended way to express the dependency without needless complications on backporting packages is to use alternative dependencies. The perl package should be the preferred alternative and the versioned dependency a secondary one.

 Example: perl (>= 5.10.0) | libmodule-build-perl (>= 0.26)

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.5]]
}}}}
##END:Lintian/Tags/package-superseded-by-perl

Self:Lintian/Tags/vcs-field-uses-not-recommended-uri-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/vcs-field-uses-not-recommended-uri-format.html|vcs-field-uses-not-recommended-uri-format]]''':<<BR>>
 The VCS-* field uses an URI which doesn't match the recommended format, but still looks valid. Examples for not recommended URI formats are protocols that require authentication (like SSH). Instead where possible you should provide an URI that is accessible for everyone without authentication.
}}}}
##END:Lintian/Tags/vcs-field-uses-not-recommended-uri-format

Self:Lintian/Tags/vcs-field-uses-unknown-uri-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/vcs-field-uses-unknown-uri-format.html|vcs-field-uses-unknown-uri-format]]''':<<BR>>
 The VCS-* field uses an URI which doesn't match any known format. You might have forgotten the protocol before the hostname.
}}}}
##END:Lintian/Tags/vcs-field-uses-unknown-uri-format

Self:Lintian/Tags/lib-recommends-documentation
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/lib-recommends-documentation.html|lib-recommends-documentation]]''':<<BR>>
 The given package appears to be a library package, but it recommends a documentation package. Doing this can pull in unwanted (and often large) documentation packages since recommends are installed by default and library packages are pulled by applications that use them. Users usually only care about the library documentation if they're developing against the library, not just using it, so the development package should recommend the documentation instead. If there is no development package (for modules for scripting languages, for example), consider Suggests instead of Recommends.
}}}}
##END:Lintian/Tags/lib-recommends-documentation

Self:Lintian/Tags/build-depends-on-python-dev-with-no-arch-any
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-depends-on-python-dev-with-no-arch-any.html|build-depends-on-python-dev-with-no-arch-any]]''':<<BR>>
 The given package appears to have a Python development package (python-dev, python-all-dev or pythonX.Y-dev) listed in its Build-Depends or Build-Depends-Indep fields, but only "Architecture: all" packages are built by this source package. Python applications and modules do not usually require those dev packages, so you should consider removing them in favour of python, python-all or pythonX.Y.

 If you are building a Python extension instead, you should have development packages listed in Build-Depends, but normally there should be at least one Architecture: any package.
}}}}
##END:Lintian/Tags/build-depends-on-python-dev-with-no-arch-any

########################################################################
== scripts ==
########################################################################

Self:Lintian/Tags/script-without-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-without-interpreter.html|script-without-interpreter]]''':<<BR>>
 This file starts with the #! sequence that identifies scripts, but it does not name an interpreter.
}}}}
##END:Lintian/Tags/script-without-interpreter

Self:Lintian/Tags/example-script-without-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-script-without-interpreter.html|example-script-without-interpreter]]''':<<BR>>
 This example file starts with the #! sequence that identifies scripts, but it does not name an interpreter.
}}}}
##END:Lintian/Tags/example-script-without-interpreter

Self:Lintian/Tags/executable-not-elf-or-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-not-elf-or-script.html|executable-not-elf-or-script]]''':<<BR>>
 This executable file is not an ELF format binary, and does not start with the #! sequence that marks interpreted scripts. It might be a sh script that fails to name /bin/sh as its shell, or it may be incorrectly marked as executable. Sometimes upstream files developed on Windows are marked unnecessarily as executable on other systems.

 If you are using debhelper to build your package, running dh_fixperms will often correct this problem for you.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/executable-not-elf-or-script

Self:Lintian/Tags/script-not-executable
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-not-executable.html|script-not-executable]]''':<<BR>>
 This file starts with the #! sequence that marks interpreted scripts, but it is not executable.
}}}}
##END:Lintian/Tags/script-not-executable

Self:Lintian/Tags/interpreter-not-absolute
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/interpreter-not-absolute.html|interpreter-not-absolute]]''':<<BR>>
 This script uses a relative path to locate its interpreter. This path will be taken relative to the caller's current directory, not the script's, so it is not likely to be what was intended.
}}}}
##END:Lintian/Tags/interpreter-not-absolute

Self:Lintian/Tags/example-interpreter-not-absolute
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-interpreter-not-absolute.html|example-interpreter-not-absolute]]''':<<BR>>
 This example script uses a relative path to locate its interpreter. This path will be taken relative to the caller's current directory, not the script's, so a user will probably not be able to run the example without modification. This tag can also be caused by script headers like {{{#!@BASH@}}}, which usually mean that the examples were copied out of the source tree before proper Autoconf path substitution.
}}}}
##END:Lintian/Tags/example-interpreter-not-absolute

Self:Lintian/Tags/unusual-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unusual-interpreter.html|unusual-interpreter]]''':<<BR>>
 This package contains a script for an interpreter that the Lintian maintainers have not heard of. It could be a typo for a common interpreter. If not, please file a wishlist bug on lintian so that the Lintian maintainers can add this interpreter to their list.
}}}}
##END:Lintian/Tags/unusual-interpreter

Self:Lintian/Tags/example-unusual-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-unusual-interpreter.html|example-unusual-interpreter]]''':<<BR>>
 This package contains an example script for an interpreter that the Lintian maintainers have not heard of. It could be a typo for a common interpreter.
}}}}
##END:Lintian/Tags/example-unusual-interpreter

Self:Lintian/Tags/script-uses-bin-env
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-uses-bin-env.html|script-uses-bin-env]]''':<<BR>>
 This script uses /bin/env as its interpreter (used to find the actual interpreter on the user's path). There is no /bin/env on Debian systems; env is instead installed as /usr/bin/env. Usually, the path to env in the script should be changed.
}}}}
##END:Lintian/Tags/script-uses-bin-env

Self:Lintian/Tags/example-script-uses-bin-env
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-script-uses-bin-env.html|example-script-uses-bin-env]]''':<<BR>>
 This example script uses /bin/env as its interpreter (used to find the actual interpreter on the user's path). There is no /bin/env on Debian systems; env is instead installed as /usr/bin/env. Usually, the path to env in the script should be changed.
}}}}
##END:Lintian/Tags/example-script-uses-bin-env

Self:Lintian/Tags/forbidden-config-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/forbidden-config-interpreter.html|forbidden-config-interpreter]]''':<<BR>>
 This package contains a {{{config}}} script for pre-configuring the package. During pre-configuration, however, only essential packages are guaranteed to be installed, so you cannot use a non-essential interpreter.
}}}}
##END:Lintian/Tags/forbidden-config-interpreter

Self:Lintian/Tags/forbidden-postrm-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/forbidden-postrm-interpreter.html|forbidden-postrm-interpreter]]''':<<BR>>
 This package contains a {{{postrm}}} maintainer script that uses an interpreter that isn't essential. The {{{purge}}} action of {{{postrm}}} can only rely on essential packages, which means the interpreter used by {{{postrm}}} must be one of the essential ones ({{{sh}}}, {{{bash}}}, or {{{perl}}}).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.2]]
}}}}
##END:Lintian/Tags/forbidden-postrm-interpreter

Self:Lintian/Tags/unusual-control-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unusual-control-interpreter.html|unusual-control-interpreter]]''':<<BR>>
 This package contains a control script for an interpreter that is not normally used for control scripts. This is permissible but not recommended. It makes it harder for other developers to understand your package.
}}}}
##END:Lintian/Tags/unusual-control-interpreter

Self:Lintian/Tags/unknown-control-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-control-interpreter.html|unknown-control-interpreter]]''':<<BR>>
 This package contains a maintainer script that uses an interpreter that the Lintian maintainers have not heard of. This is usually a typo for a common interpreter. If not, please file a wishlist bug on lintian so that the Lintian maintainers can add this interpreter to their list.
}}}}
##END:Lintian/Tags/unknown-control-interpreter

Self:Lintian/Tags/interpreter-in-usr-local
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/interpreter-in-usr-local.html|interpreter-in-usr-local]]''':<<BR>>
 This package contains a script that looks for an interpreter in a directory in /usr/local. Since Debian does not install anything in /usr/local, this is the wrong place to look.
}}}}
##END:Lintian/Tags/interpreter-in-usr-local

Self:Lintian/Tags/example-interpreter-in-usr-local
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-interpreter-in-usr-local.html|example-interpreter-in-usr-local]]''':<<BR>>
 This package contains an example script that looks for an interpreter in a directory in /usr/local. Since Debian does not install anything in /usr/local, the example script would probably need modifications before a user could run it.
}}}}
##END:Lintian/Tags/example-interpreter-in-usr-local

Self:Lintian/Tags/control-interpreter-in-usr-local
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/control-interpreter-in-usr-local.html|control-interpreter-in-usr-local]]''':<<BR>>
 A control script for this package references an interpreter in a directory in {{{/usr/local}}}. Control scripts must use interpreters provided by Debian packages, and Debian packages do not install anything in {{{/usr/local}}}.
}}}}
##END:Lintian/Tags/control-interpreter-in-usr-local

Self:Lintian/Tags/preinst-interpreter-without-predepends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/preinst-interpreter-without-predepends.html|preinst-interpreter-without-predepends]]''':<<BR>>
 The package contains a {{{preinst}}} maintainer script that uses an unusual and non-essential interpreter but does not declare a pre-dependency on the package that provides this interpreter.

 {{{preinst}}} scripts should be written using only essential interpreters to avoid additional dependency complexity. Please do not add a pre-dependency without following the policy for doing so (Policy section 3.5).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.2]]
}}}}
##END:Lintian/Tags/preinst-interpreter-without-predepends

Self:Lintian/Tags/control-interpreter-without-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/control-interpreter-without-depends.html|control-interpreter-without-depends]]''':<<BR>>
 The package contains a maintainer script that uses an unusual and non-essential interpreter but does not declare a dependency on the package that provides this interpreter.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.2]]
}}}}
##END:Lintian/Tags/control-interpreter-without-depends

Self:Lintian/Tags/missing-dep-for-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-dep-for-interpreter.html|missing-dep-for-interpreter]]''':<<BR>>
 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. If the dependency is already present, please file a bug against Lintian with the details of your package so that its database can be updated.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/missing-dep-for-interpreter

Self:Lintian/Tags/csh-considered-harmful
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/csh-considered-harmful.html|csh-considered-harmful]]''':<<BR>>
 The Debian policy for scripts explicitly warns against using csh and tcsh as scripting languages.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/csh-considered-harmful

Self:Lintian/Tags/suid-perl-script-but-no-perl-suid-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/suid-perl-script-but-no-perl-suid-dep.html|suid-perl-script-but-no-perl-suid-dep]]''':<<BR>>
 Packages that use perl scripts that are suid must depend on the perl-suid package.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/suid-perl-script-but-no-perl-suid-dep

Self:Lintian/Tags/wrong-path-for-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wrong-path-for-interpreter.html|wrong-path-for-interpreter]]''':<<BR>>
 The interpreter you used is installed at another location on Debian systems.
}}}}
##END:Lintian/Tags/wrong-path-for-interpreter

Self:Lintian/Tags/example-wrong-path-for-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-wrong-path-for-interpreter.html|example-wrong-path-for-interpreter]]''':<<BR>>
 The interpreter used by this example script is installed at another location on Debian systems. Normally the path should be updated to match the Debian location.
}}}}
##END:Lintian/Tags/example-wrong-path-for-interpreter

Self:Lintian/Tags/gawk-script-but-no-gawk-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/gawk-script-but-no-gawk-dep.html|gawk-script-but-no-gawk-dep]]''':<<BR>>
 Packages that use gawk scripts must depend on the gawk package. If they don't need gawk-specific features, and can just as easily work with mawk, then they should be awk scripts instead.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/gawk-script-but-no-gawk-dep

Self:Lintian/Tags/mawk-script-but-no-mawk-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/mawk-script-but-no-mawk-dep.html|mawk-script-but-no-mawk-dep]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/mawk-script-but-no-mawk-dep

Self:Lintian/Tags/php-script-but-no-phpX-cli-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/php-script-but-no-phpX-cli-dep.html|php-script-but-no-phpX-cli-dep]]''':<<BR>>
 Packages with PHP scripts must depend on a phpX-cli package such as php5-cli. Note that a dependency on a php-cgi package (such as php5-cgi) is needlessly strict and forces the user to install a package that isn't needed.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.

 Lintian can only recognize phpX-cli dependencies for values of X that it knows are available in the archive. You will get this warning if you allow, as alternatives, versions of PHP that are so old they're not available in stable. The correct fix in those cases is probably to drop the old alternative. If this package depends on a newer php-cli package that Lintian doesn't know about, please file a bug against Lintian so that it can be updated.
}}}}
##END:Lintian/Tags/php-script-but-no-phpX-cli-dep

Self:Lintian/Tags/python-script-but-no-python-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/python-script-but-no-python-dep.html|python-script-but-no-python-dep]]''':<<BR>>
 Packages with Python scripts should depend on the package {{{python}}}. Those with scripts that specify a specific version of Python must depend on that version of Python (exactly).

 For example, if a script in the package uses {{{#!/usr/bin/python}}}, the package needs a dependency on {{{python}}}. If a script uses {{{#!/usr/bin/python2.6}}}, the package needs a dependency on {{{python2.6}}}. A dependency on {{{python (>= 2.6)}}} is not correct, since later versions of Python may not provide the {{{/usr/bin/python2.6}}} binary.

 If you are using debhelper, adding {{{${python:Depends} }}} to the Depends field and ensuring dh_pysupport or dh_pycentral are run during the build should take care of adding the correct dependency.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/python-script-but-no-python-dep

Self:Lintian/Tags/ruby-script-but-no-ruby-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ruby-script-but-no-ruby-dep.html|ruby-script-but-no-ruby-dep]]''':<<BR>>
 Packages with Ruby scripts must depend on the package ruby. Those that have Ruby scripts that run under a specific version of Ruby need a dependency on the equivalent version of Ruby.

 For example, if a script in the package uses {{{#!/usr/bin/ruby}}}, the package needs a dependency on "ruby". If a script uses {{{#!/usr/bin/ruby1.9}}}, then the package need a dependency on "ruby1.9".

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/ruby-script-but-no-ruby-dep

Self:Lintian/Tags/wish-script-but-no-wish-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/wish-script-but-no-wish-dep.html|wish-script-but-no-wish-dep]]''':<<BR>>
 Packages that include wish scripts must depend on the virtual package wish or, if they require a specific version of wish or tk, that version of tk.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/wish-script-but-no-wish-dep

Self:Lintian/Tags/tclsh-script-but-no-tclsh-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/tclsh-script-but-no-tclsh-dep.html|tclsh-script-but-no-tclsh-dep]]''':<<BR>>
 Packages that include tclsh scripts must depend on the virtual package tclsh or, if they require a specific version of tcl, that version of tcl.

 In some cases a weaker relationship, such as Suggests or Recommends, will be more appropriate.
}}}}
##END:Lintian/Tags/tclsh-script-but-no-tclsh-dep

Self:Lintian/Tags/calls-suidperl-directly
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/calls-suidperl-directly.html|calls-suidperl-directly]]''':<<BR>>
 Since perl version 5.8.3-3, /usr/bin/suidperl shouldn't be called directly anymore (and doing so will lead to errors in most cases) but the script should just use /usr/bin/perl as interpreter which will call suidperl automatically if the script has the suid permission bit set.
}}}}
##END:Lintian/Tags/calls-suidperl-directly

Self:Lintian/Tags/shell-script-fails-syntax-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/shell-script-fails-syntax-check.html|shell-script-fails-syntax-check]]''':<<BR>>
 Running this shell script with the shell's -n option set fails, which means that the script has syntax errors. The most common cause of this problem is a script expecting {{{/bin/sh}}} to be bash checked on a system using dash as {{{/bin/sh}}}.

 Run e.g. {{{sh -n yourscript}}} to see the errors yourself.
}}}}
##END:Lintian/Tags/shell-script-fails-syntax-check

Self:Lintian/Tags/example-shell-script-fails-syntax-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/example-shell-script-fails-syntax-check.html|example-shell-script-fails-syntax-check]]''':<<BR>>
 Running this shell script with the shell's -n option set fails, which means that the script has syntax errors. The most common cause of this problem is a script expecting {{{/bin/sh}}} to be bash checked on a system using dash as {{{/bin/sh}}}.

 Run e.g. {{{sh -n yourscript}}} to see the errors yourself.
}}}}
##END:Lintian/Tags/example-shell-script-fails-syntax-check

Self:Lintian/Tags/maintainer-shell-script-fails-syntax-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-shell-script-fails-syntax-check.html|maintainer-shell-script-fails-syntax-check]]''':<<BR>>
 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. {{{sh -n yourscript}}} to see the errors yourself.
}}}}
##END:Lintian/Tags/maintainer-shell-script-fails-syntax-check

Self:Lintian/Tags/possibly-insecure-handling-of-tmp-files-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possibly-insecure-handling-of-tmp-files-in-maintainer-script.html|possibly-insecure-handling-of-tmp-files-in-maintainer-script]]''':<<BR>>
 The maintainer script seems to access a file in {{{/tmp}}} or some other temporary directory. Since creating temporary files in a world-writable directory is very dangerous, this is likely to be a security bug. Use the {{{tempfile}}} or {{{mktemp}}} utilities to create temporary files in these directories.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/possibly-insecure-handling-of-tmp-files-in-maintainer-script

Self:Lintian/Tags/killall-is-dangerous
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/killall-is-dangerous.html|killall-is-dangerous]]''':<<BR>>
 The maintainer script seems to call {{{killall}}}. Since this utility kills processes by name, it may well end up killing unrelated processes. Most uses of {{{killall}}} should use {{{invoke-rc.d}}} instead.
}}}}
##END:Lintian/Tags/killall-is-dangerous

Self:Lintian/Tags/mknod-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/mknod-in-maintainer-script.html|mknod-in-maintainer-script]]''':<<BR>>
 Maintainer scripts must not create device files directly. They should call {{{MAKEDEV}}} instead.

 If {{{mknod}}} is being used to create a FIFO (named pipe), use {{{mkfifo}}} instead to avoid triggering this tag.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.6]]
}}}}
##END:Lintian/Tags/mknod-in-maintainer-script

Self:Lintian/Tags/start-stop-daemon-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/start-stop-daemon-in-maintainer-script.html|start-stop-daemon-in-maintainer-script]]''':<<BR>>
 The maintainer script seems to call {{{start-stop-daemon}}} directly. Long-running daemons should be started and stopped via init scripts using {{{invoke-rc.d}}} rather than directly in maintainer scripts.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.2]]
}}}}
##END:Lintian/Tags/start-stop-daemon-in-maintainer-script

Self:Lintian/Tags/maintainer-script-removes-device-files
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-removes-device-files.html|maintainer-script-removes-device-files]]''':<<BR>>
 Maintainer scripts must not remove device files. This is left to the system administrator.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.6]]
}}}}
##END:Lintian/Tags/maintainer-script-removes-device-files

Self:Lintian/Tags/read-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/read-in-maintainer-script.html|read-in-maintainer-script]]''':<<BR>>
 This maintainer script appears to use read to get information from the user. Prompting in maintainer scripts must be done by communicating through a program such as debconf which conforms to the Debian Configuration management specification, version 2 or higher.

 This check can have false positives if read is used in a block with a redirection, in a function run in a pipe, or in other ways where standard input is provided in inobvious ways. If this is the case, please add an override for this tag.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.9.1]]
}}}}
##END:Lintian/Tags/read-in-maintainer-script

Self:Lintian/Tags/possible-bashism-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-bashism-in-maintainer-script.html|possible-bashism-in-maintainer-script]]''':<<BR>>
 This script is marked as running under {{{/bin/sh}}}, but it seems to use a feature found in bash but not in the SUSv3 or POSIX shell specification.

 Examples: '==' in a test, it should use '=' instead 'read' without a variable in the argument 'function' to define a function 'source' instead of '.' '. command args', passing arguments to commands via 'source' is not supported '{foo,bar}' instead of 'foo bar' '[[ test ]]' instead of '[ test ]' (requires a Korn shell) 'type' instead of 'which' or 'command -v'

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/possible-bashism-in-maintainer-script

Self:Lintian/Tags/suidregister-used-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/suidregister-used-in-maintainer-script.html|suidregister-used-in-maintainer-script]]''':<<BR>>
 This script calls suidregister, a long-obsolete program that has been replaced by dpkg-statoverride.
}}}}
##END:Lintian/Tags/suidregister-used-in-maintainer-script

Self:Lintian/Tags/maintainer-script-needs-depends-on-update-inetd
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-needs-depends-on-update-inetd.html|maintainer-script-needs-depends-on-update-inetd]]''':<<BR>>
 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".
}}}}
##END:Lintian/Tags/maintainer-script-needs-depends-on-update-inetd

Self:Lintian/Tags/maintainer-script-needs-depends-on-adduser
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-needs-depends-on-adduser.html|maintainer-script-needs-depends-on-adduser]]''':<<BR>>
 This script calls adduser, but the package does not depend or pre-depend on the adduser package.
}}}}
##END:Lintian/Tags/maintainer-script-needs-depends-on-adduser

Self:Lintian/Tags/maintainer-script-needs-depends-on-gconf2
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-needs-depends-on-gconf2.html|maintainer-script-needs-depends-on-gconf2]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/maintainer-script-needs-depends-on-gconf2

Self:Lintian/Tags/maintainer-script-needs-depends-on-ucf
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-needs-depends-on-ucf.html|maintainer-script-needs-depends-on-ucf]]''':<<BR>>
 This script calls ucf, but the package does not depend or pre-depend on the ucf package.
}}}}
##END:Lintian/Tags/maintainer-script-needs-depends-on-ucf

Self:Lintian/Tags/maintainer-script-needs-depends-on-xml-core
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-needs-depends-on-xml-core.html|maintainer-script-needs-depends-on-xml-core]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/maintainer-script-needs-depends-on-xml-core

Self:Lintian/Tags/update-alternatives-remove-called-in-postrm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/update-alternatives-remove-called-in-postrm.html|update-alternatives-remove-called-in-postrm]]''':<<BR>>
 {{{update-alternatives --remove <alternative> foo}}} is called in the postrm. This can be dangerous because at the time the postrm is executed foo has already been deleted and update-alternatives will ignore it while constructing its list of available alternatives. Then, if the /etc/alternatives symlink points at foo, update-alternatives won't recognize it and will mark the symlink as something site-specific. As such, the symlink will no longer be updated automatically and will be left dangling until {{{update-alternatives --auto <alternative>}}} is run by hand.

 {{{update-alternatives --remove}}} should be called in the prerm instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy F]], [[DebianMan:8/update-alternatives|update-alternatives(8)]]
}}}}
##END:Lintian/Tags/update-alternatives-remove-called-in-postrm

Self:Lintian/Tags/deprecated-chown-usage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/deprecated-chown-usage.html|deprecated-chown-usage]]''':<<BR>>
 {{{chown user.group}}} is called in one of the maintainer scripts. The correct syntax is {{{chown user:group}}}. 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.

Reference(s): [[DebianMan:1/chown|chown(1)]]
}}}}
##END:Lintian/Tags/deprecated-chown-usage

Self:Lintian/Tags/maintainer-script-hides-init-failure
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-hides-init-failure.html|maintainer-script-hides-init-failure]]''':<<BR>>
 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).
}}}}
##END:Lintian/Tags/maintainer-script-hides-init-failure

Self:Lintian/Tags/maintainer-script-calls-init-script-directly
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-calls-init-script-directly.html|maintainer-script-calls-init-script-directly]]''':<<BR>>
 This script apparently runs an init script directly rather than using invoke-rc.d. The use of invoke-rc.d to invoke the /etc/init.d/* initscripts instead of calling them directly is required. Maintainer scripts may call the init script directly only if invoke-rc.d is not available.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.2]]
}}}}
##END:Lintian/Tags/maintainer-script-calls-init-script-directly

Self:Lintian/Tags/script-calls-init-script-directly
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-calls-init-script-directly.html|script-calls-init-script-directly]]''':<<BR>>
 This script apparently runs an init script directly rather than using {{{invoke-rc.d}}}. While use of {{{invoke-rc.d}}} is only required for maintainer scripts, supporting the policy layer that it implements is a good idea in any script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.2]]
}}}}
##END:Lintian/Tags/script-calls-init-script-directly

Self:Lintian/Tags/gconftool-used-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/gconftool-used-in-maintainer-script.html|gconftool-used-in-maintainer-script]]''':<<BR>>
 This script apparently runs gconftool or gconftool-2. It should probably be calling gconf-schemas or update-gconf-defaults instead.
}}}}
##END:Lintian/Tags/gconftool-used-in-maintainer-script

Self:Lintian/Tags/fc-cache-used-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/fc-cache-used-in-maintainer-script.html|fc-cache-used-in-maintainer-script]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/fc-cache-used-in-maintainer-script

Self:Lintian/Tags/install-info-used-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/install-info-used-in-maintainer-script.html|install-info-used-in-maintainer-script]]''':<<BR>>
 This script apparently runs {{{install-info}}}. Updating the {{{/usr/share/info/dir}}} file is now handled automatically by triggers, so running {{{install-info}}} from maintainer scripts is no longer necessary.

 If debhelper generated the maintainer script fragment, rebuilding the package with debhelper 7.2.17 or later will fix this problem.
}}}}
##END:Lintian/Tags/install-info-used-in-maintainer-script

Self:Lintian/Tags/maintainer-script-uses-dpkg-status-directly
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-uses-dpkg-status-directly.html|maintainer-script-uses-dpkg-status-directly]]''':<<BR>>
 The file /var/lib/dpkg/status is internal to dpkg, may disappear or change formats, and is not always a correct and complete record of installed packages while dpkg is running. Maintainer scripts should use dpkg-query instead. For the most common case of retrieving conffile information, use:

  dpkg-query -W -f='${Conffiles}' <package>

 instead.

Reference(s): [[http://wiki.debian.org/DpkgConffileHandling]]
}}}}
##END:Lintian/Tags/maintainer-script-uses-dpkg-status-directly

Self:Lintian/Tags/maintainer-script-modifies-netbase-managed-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-modifies-netbase-managed-file.html|maintainer-script-modifies-netbase-managed-file]]''':<<BR>>
 The maintainer script modifies at least one of the files {{{/etc/services}}}, {{{/etc/protocols}}}, and {{{/etc/rpc}}}, which are managed by the netbase package. Instead of doing this, please file a wishlist bug against netbase to have an appropriate entry added.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.2]]
}}}}
##END:Lintian/Tags/maintainer-script-modifies-netbase-managed-file

Self:Lintian/Tags/maintainer-script-modifies-inetd-conf
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-modifies-inetd-conf.html|maintainer-script-modifies-inetd-conf]]''':<<BR>>
 The maintainer script modifies {{{/etc/inetd.conf}}} directly. This file must not be modified directly; instead, use the {{{update-inetd}}} script or the {{{DebianNet.pm}}} Perl module.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.2]]
}}}}
##END:Lintian/Tags/maintainer-script-modifies-inetd-conf

Self:Lintian/Tags/maintainer-script-modifies-ld-so-conf
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-modifies-ld-so-conf.html|maintainer-script-modifies-ld-so-conf]]''':<<BR>>
 This package appears to modify {{{/etc/ld.so.conf}}} 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 {{{/usr/lib}}} 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 {{{/usr/lib}}} except now conflicting library packages may cause random segfaults and difficult-to-debug problems instead of conflicts in the package manager.
}}}}
##END:Lintian/Tags/maintainer-script-modifies-ld-so-conf

Self:Lintian/Tags/install-sgmlcatalog-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/install-sgmlcatalog-deprecated.html|install-sgmlcatalog-deprecated]]''':<<BR>>
 The maintainer script apparently runs install-sgmlcatalog with flags other than {{{--quiet}}} and {{{--remove}}} or in a maintainer script other than postinst or prerm. install-sgmlcatalog is deprecated and should only be used in postinst or prerm to remove the entries from earlier packages. Given how long ago this transition was, consider removing it entirely.
}}}}
##END:Lintian/Tags/install-sgmlcatalog-deprecated

Self:Lintian/Tags/maintainer-script-empty
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-empty.html|maintainer-script-empty]]''':<<BR>>
 The maintainer script doesn't seem to contain any code other than comments and boilerplate (set -e, exit statements, and the case statement to parse options). While this is harmless in most cases, it is probably not what you wanted, may mean the package will leave unnecessary files behind until purged, and may even lead to problems in rare situations where dpkg would fail if no maintainer script was present.

 If the package currently doesn't need to do anything in this maintainer script, it shouldn't be included in the package.
}}}}
##END:Lintian/Tags/maintainer-script-empty

Self:Lintian/Tags/maintainer-script-ignores-errors
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-ignores-errors.html|maintainer-script-ignores-errors]]''':<<BR>>
 The maintainer script doesn't seem to set the {{{-e}}} flag which ensures that the script's execution is aborted when any executed command fails.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/maintainer-script-ignores-errors

Self:Lintian/Tags/maintainer-script-without-set-e
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-without-set-e.html|maintainer-script-without-set-e]]''':<<BR>>
 The maintainer script passes {{{-e}}} to the shell on the {{{#!}}} line rather than using {{{set -e}}} in the body of the script. This is fine for normal operation, but if the script is run by hand with {{{sh /path/to/script}}} (common in debugging), {{{-e}}} will not be in effect. It's therefore better to use {{{set -e}}} in the body of the script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.4]]
}}}}
##END:Lintian/Tags/maintainer-script-without-set-e

Self:Lintian/Tags/command-with-path-in-maintainer-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/command-with-path-in-maintainer-script.html|command-with-path-in-maintainer-script]]''':<<BR>>
 The indicated program run in a maintainer script has a prepended path. Programs called from maintainer scripts normally should not have a path prepended. dpkg ensures that the PATH is set to a reasonable value, and prepending a path may prevent the local administrator from using a replacement version of a command for some local reason.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 6.1]]
}}}}
##END:Lintian/Tags/command-with-path-in-maintainer-script

Self:Lintian/Tags/ancient-dpkg-predepends-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-dpkg-predepends-check.html|ancient-dpkg-predepends-check]]''':<<BR>>
 The package calls dpkg --assert-support-predepends in a maintainer script. This check is obsolete and has always returned true since dpkg 1.1.0, released 1996-02-11.
}}}}
##END:Lintian/Tags/ancient-dpkg-predepends-check

Self:Lintian/Tags/ancient-dpkg-epoch-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-dpkg-epoch-check.html|ancient-dpkg-epoch-check]]''':<<BR>>
 The package calls dpkg --assert-working-epoch in a maintainer script. This check is obsolete and has always returned true since dpkg 1.4.0.7, released 1997-01-25.
}}}}
##END:Lintian/Tags/ancient-dpkg-epoch-check

Self:Lintian/Tags/ancient-dpkg-long-filenames-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-dpkg-long-filenames-check.html|ancient-dpkg-long-filenames-check]]''':<<BR>>
 The package calls dpkg --assert-long-filenames in a maintainer script. This check is obsolete and has always returned true since dpkg 1.4.1.17, released 1999-10-21.
}}}}
##END:Lintian/Tags/ancient-dpkg-long-filenames-check

Self:Lintian/Tags/ancient-dpkg-multi-conrep-check
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-dpkg-multi-conrep-check.html|ancient-dpkg-multi-conrep-check]]''':<<BR>>
 The package calls dpkg --assert-multi-conrep in a maintainer script. This check is obsolete and has always returned true since dpkg 1.4.1.19, released 1999-10-30.
}}}}
##END:Lintian/Tags/ancient-dpkg-multi-conrep-check

Self:Lintian/Tags/package-uses-local-diversion
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-uses-local-diversion.html|package-uses-local-diversion]]''':<<BR>>
 The maintainer script calls dpkg-divert with {{{--local}}} or without {{{--package}}}. This option is reserved for local administrators and must never be used by a Debian package.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.9]]
}}}}
##END:Lintian/Tags/package-uses-local-diversion

Self:Lintian/Tags/diversion-for-unknown-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diversion-for-unknown-file.html|diversion-for-unknown-file]]''':<<BR>>
 The maintainer script adds a diversion for a file that is not provided by this package.
}}}}
##END:Lintian/Tags/diversion-for-unknown-file

Self:Lintian/Tags/orphaned-diversion
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/orphaned-diversion.html|orphaned-diversion]]''':<<BR>>
 A diversion was added for the file, but not removed. This means your package doesn't restore the previous state after removal.
}}}}
##END:Lintian/Tags/orphaned-diversion

Self:Lintian/Tags/remove-of-unknown-diversion
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/remove-of-unknown-diversion.html|remove-of-unknown-diversion]]''':<<BR>>
 The maintainer script removes a diversion that it didn't add. If you're cleaning up unnecessary diversions from older versions of the package, remove them in {{{preinst}}} or {{{postinst}}} instead of waiting for {{{postrm}}} to do it.
}}}}
##END:Lintian/Tags/remove-of-unknown-diversion

########################################################################
== menus ==
########################################################################

Self:Lintian/Tags/postinst-should-not-set-usr-doc-link
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-should-not-set-usr-doc-link.html|postinst-should-not-set-usr-doc-link]]''':<<BR>>
 The technical committee chose the symlink transition method to move from FSSTND to FHS. That transition has been completed with woody and thus this link is no longer required.
}}}}
##END:Lintian/Tags/postinst-should-not-set-usr-doc-link

Self:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-updatemenus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-does-not-check-for-existence-of-updatemenus.html|maintainer-script-does-not-check-for-existence-of-updatemenus]]''':<<BR>>
 The maintainer script calls the {{{update-menus}}} command without checking for existence first. (The {{{menu}}} package which provides the command is not marked as "essential" package.)

 For example, use the following code in your maintainer script: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi
}}}}
##END:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-updatemenus

Self:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-wm-menu-config
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-does-not-check-for-existence-of-wm-menu-config.html|maintainer-script-does-not-check-for-existence-of-wm-menu-config]]''':<<BR>>
 The maintainer script calls the {{{wm-menu-config}}} command without checking for existence first. (The {{{menu}}} package which provides the command is not marked as "essential" package.)

 For example, use the following code in your maintainer script: if [ -x /usr/sbin/wm-menu ]; then /usr/sbin/wm-menu-config; fi
}}}}
##END:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-wm-menu-config

Self:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-installdocs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-does-not-check-for-existence-of-installdocs.html|maintainer-script-does-not-check-for-existence-of-installdocs]]''':<<BR>>
 The maintainer script calls the {{{install-docs}}} command without checking for existence first. (The {{{doc-base}}} package which provides the command is not marked as "essential" package.)

 For example, use the following code in your maintainer script: if [ -x /usr/sbin/install-docs ]; then /usr/sbin/install-docs -i /usr/share/doc-base/<your-package> fi
}}}}
##END:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-installdocs

Self:Lintian/Tags/maintainer-script-calls-deprecated-wm-menu-config
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-calls-deprecated-wm-menu-config.html|maintainer-script-calls-deprecated-wm-menu-config]]''':<<BR>>
 The use of the wm-menu-config script is deprecated because its design had some serious flaws.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 5]]
}}}}
##END:Lintian/Tags/maintainer-script-calls-deprecated-wm-menu-config

Self:Lintian/Tags/preinst-calls-updatemenus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/preinst-calls-updatemenus.html|preinst-calls-updatemenus]]''':<<BR>>
 The preinst script calls the {{{update-menus}}} command. Usually, this command should be called from the {{{postinst}}} maintainer script.
}}}}
##END:Lintian/Tags/preinst-calls-updatemenus

Self:Lintian/Tags/preinst-calls-installdocs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/preinst-calls-installdocs.html|preinst-calls-installdocs]]''':<<BR>>
 The preinst script calls the {{{install-docs}}} command. Usually, this command should be called from the {{{postinst}}} maintainer script.
}}}}
##END:Lintian/Tags/preinst-calls-installdocs

Self:Lintian/Tags/prerm-calls-updatemenus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/prerm-calls-updatemenus.html|prerm-calls-updatemenus]]''':<<BR>>
 The prerm script calls the {{{update-menus}}} command. Usually, this command should be called from the {{{postrm}}} maintainer script.
}}}}
##END:Lintian/Tags/prerm-calls-updatemenus

Self:Lintian/Tags/postrm-calls-installdocs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-calls-installdocs.html|postrm-calls-installdocs]]''':<<BR>>
 The postrm script calls the {{{install-docs}}} command. Usually, this command should be called from the {{{prerm}}} maintainer script.
}}}}
##END:Lintian/Tags/postrm-calls-installdocs

Self:Lintian/Tags/executable-menu-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-menu-file.html|executable-menu-file]]''':<<BR>>
 Menu files should normally not be marked as executables. You only need to do this if your package has to generate menu entries dynamically.
}}}}
##END:Lintian/Tags/executable-menu-file

Self:Lintian/Tags/menu-file-in-usr-lib
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-file-in-usr-lib.html|menu-file-in-usr-lib]]''':<<BR>>
 As of menu, version 2.1.25, /usr/lib/menu as location for menu files is deprecated (but still works perfectly). Menu files should now be placed in /usr/share/menu instead. Only menu files that are actually binary executables still need to go to /usr/lib/menu.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 3.1]]
}}}}
##END:Lintian/Tags/menu-file-in-usr-lib

Self:Lintian/Tags/executable-in-usr-share-docbase
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/executable-in-usr-share-docbase.html|executable-in-usr-share-docbase]]''':<<BR>>
 Files in {{{/usr/share/doc-base}}} may not be marked as executables.
}}}}
##END:Lintian/Tags/executable-in-usr-share-docbase

Self:Lintian/Tags/postinst-does-not-call-updatemenus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-does-not-call-updatemenus.html|postinst-does-not-call-updatemenus]]''':<<BR>>
 Since the package installs a file in {{{/etc/menu-methods}}}, {{{/usr/share/menu}}}, or {{{/usr/lib/menu}}}, the package should probably call the {{{update-menus}}} command in it's {{{postinst}}} script.

 For example, use the following code in your maintainer script: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 4.2]]
}}}}
##END:Lintian/Tags/postinst-does-not-call-updatemenus

Self:Lintian/Tags/postrm-does-not-call-updatemenus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-does-not-call-updatemenus.html|postrm-does-not-call-updatemenus]]''':<<BR>>
 Since the package installs a file in {{{/etc/menu-methods}}}, {{{/usr/share/menu}}}, or {{{/usr/lib/menu}}}, the package should probably call the {{{update-menus}}} command in it's {{{postrm}}} script.

 For example, use the following code in your maintainer script: if [ -x /usr/bin/update-menus ] ; then update-menus ; fi

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 4.2]]
}}}}
##END:Lintian/Tags/postrm-does-not-call-updatemenus

Self:Lintian/Tags/postinst-has-useless-call-to-update-menus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-has-useless-call-to-update-menus.html|postinst-has-useless-call-to-update-menus]]''':<<BR>>
 The {{{postinst}}} script calls the {{{update-menus}}} program though no file is installed in {{{/etc/menu-methods}}}, {{{/usr/share/menu}}}, or {{{/usr/lib/menu}}}.
}}}}
##END:Lintian/Tags/postinst-has-useless-call-to-update-menus

Self:Lintian/Tags/postrm-has-useless-call-to-update-menus
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-has-useless-call-to-update-menus.html|postrm-has-useless-call-to-update-menus]]''':<<BR>>
 The {{{postrm}}} script calls the {{{update-menus}}} program though no file is installed in {{{/etc/menu-methods}}}, {{{/usr/share/menu}}}, or {{{/usr/lib/menu}}}.
}}}}
##END:Lintian/Tags/postrm-has-useless-call-to-update-menus

Self:Lintian/Tags/postinst-has-useless-call-to-install-docs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-has-useless-call-to-install-docs.html|postinst-has-useless-call-to-install-docs]]''':<<BR>>
 Explicitly calling {{{install-docs}}} in {{{postinst}}} is no longer required since doc-base file processing is handled by triggers. If the {{{install-docs}}} call was added by debhelper, rebuilding the package with debhelper 7.2.3 or later will fix this problem.
}}}}
##END:Lintian/Tags/postinst-has-useless-call-to-install-docs

Self:Lintian/Tags/prerm-has-useless-call-to-install-docs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/prerm-has-useless-call-to-install-docs.html|prerm-has-useless-call-to-install-docs]]''':<<BR>>
 Explicitly calling {{{install-docs}}} in {{{prerm}}} is no longer required since doc-base file processing is handled by triggers. If the {{{install-docs}}} call was added by debhelper, rebuilding the package with debhelper 7.2.3 or later will fix this problem.
}}}}
##END:Lintian/Tags/prerm-has-useless-call-to-install-docs

Self:Lintian/Tags/bad-menu-file-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-menu-file-name.html|bad-menu-file-name]]''':<<BR>>
 The package installs a file {{{/usr/lib/menu/menu}}}, which is already in use by the {{{menu}}} package itself. The menu file should be named after the package that installs it.
}}}}
##END:Lintian/Tags/bad-menu-file-name

Self:Lintian/Tags/doc-base-file-references-usr-doc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-references-usr-doc.html|doc-base-file-references-usr-doc]]''':<<BR>>
 Files in {{{/usr/share/doc-base}}} should only contain links to files in the {{{/usr/share/doc}}} directory.
}}}}
##END:Lintian/Tags/doc-base-file-references-usr-doc

Self:Lintian/Tags/doc-base-index-references-multiple-files
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-index-references-multiple-files.html|doc-base-index-references-multiple-files]]''':<<BR>>
 The Index field in a doc-base file should reference the single index file for that document. Any other files belonging to the same document should be listed in the Files field.

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-index-references-multiple-files

Self:Lintian/Tags/doc-base-file-references-missing-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-references-missing-file.html|doc-base-file-references-missing-file]]''':<<BR>>
 One of the files referenced in an Index or Files field in this doc-base control file does not exist in the package. The doc-base control files should be installed by the package that provides the documents they are registering.
}}}}
##END:Lintian/Tags/doc-base-file-references-missing-file

Self:Lintian/Tags/doc-base-file-unknown-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-unknown-format.html|doc-base-file-unknown-format]]''':<<BR>>
 The Format field in this doc-base control file declares a format that is not supported. Recognized formats are "HTML", "Text", "PDF", "PostScript", "Info", "DVI", and "DebianDoc-SGML" (case-insensitive).

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-unknown-format

Self:Lintian/Tags/doc-base-file-no-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-no-format.html|doc-base-file-no-format]]''':<<BR>>
 A format section of this doc-base control file didn't specify a format. Each section after the first must specify a format.

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-no-format

Self:Lintian/Tags/doc-base-file-no-format-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-no-format-section.html|doc-base-file-no-format-section]]''':<<BR>>
 This doc-base control file didn't specify any format section.

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-no-format-section

Self:Lintian/Tags/doc-base-file-no-index
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-no-index.html|doc-base-file-no-index]]''':<<BR>>
 Format sections in doc-base control files for HTML or Info documents must contain an Index field specifying the starting document for the documentation. Even if the documentation is a single file, this field must be present.

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-no-index

Self:Lintian/Tags/doc-base-document-field-ends-in-whitespace
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-document-field-ends-in-whitespace.html|doc-base-document-field-ends-in-whitespace]]''':<<BR>>
 The Document field in a doc-base file should not end in whitespace. doc-base (at least as of 0.8.5) cannot cope with such fields and debhelper 5.0.57 or earlier may create files ending in whitespace when installing such files.
}}}}
##END:Lintian/Tags/doc-base-document-field-ends-in-whitespace

Self:Lintian/Tags/doc-base-document-field-not-in-first-line
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-document-field-not-in-first-line.html|doc-base-document-field-not-in-first-line]]''':<<BR>>
 The Document field in doc-base control file must be located at first line of the file. While unregistering documents, doc-base 0.8 and later parses only the first line of the control file for performance reasons.

Reference(s): doc-base 2.3.2.1
}}}}
##END:Lintian/Tags/doc-base-document-field-not-in-first-line

Self:Lintian/Tags/doc-base-file-unknown-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-unknown-field.html|doc-base-file-unknown-field]]''':<<BR>>
 The doc-base control file contains field which is either unknown or not valid for the section where was found. Possible reasons for this error are: a typo in field name, missing empty line between control file sections, or an extra empty line separating sections.

Reference(s): doc-base 2.3.2.1, doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-unknown-field

Self:Lintian/Tags/doc-base-file-duplicated-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-duplicated-field.html|doc-base-file-duplicated-field]]''':<<BR>>
 The doc-base control file contains a duplicated field.
}}}}
##END:Lintian/Tags/doc-base-file-duplicated-field

Self:Lintian/Tags/doc-base-file-duplicated-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-duplicated-format.html|doc-base-file-duplicated-format]]''':<<BR>>
 The doc-base control file contains a duplicated format. Doc-base files must not register different documents in one control file.

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-duplicated-format

Self:Lintian/Tags/doc-base-file-lacks-required-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-lacks-required-field.html|doc-base-file-lacks-required-field]]''':<<BR>>
 The doc-base control file does not contain a required field for the appropriate section.

Reference(s): doc-base 2.3.2.1, doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-lacks-required-field

Self:Lintian/Tags/doc-base-invalid-document-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-invalid-document-field.html|doc-base-invalid-document-field]]''':<<BR>>
 The Document field should consists only of letters (a-z), digits (0-9), plus (+) or minus (-) signs, and dots (.). In particular, uppercase letters are not allowed.

Reference(s): doc-base 2.2
}}}}
##END:Lintian/Tags/doc-base-invalid-document-field

Self:Lintian/Tags/doc-base-abstract-field-is-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-abstract-field-is-template.html|doc-base-abstract-field-is-template]]''':<<BR>>
 The Abstract field of doc-base contains a "manage online manuals" phrase, which was copied verbatim from an example control file found in section 2.3.1 of the Debian doc-base Manual.
}}}}
##END:Lintian/Tags/doc-base-abstract-field-is-template

Self:Lintian/Tags/doc-base-abstract-might-contain-extra-leading-whitespaces
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-abstract-might-contain-extra-leading-whitespaces.html|doc-base-abstract-might-contain-extra-leading-whitespaces]]''':<<BR>>
 Continuation lines of the Abstract field of doc-base control file should start with only one space unless they are meant to be displayed verbatim by frontends.

Reference(s): doc-base 2.3.2
}}}}
##END:Lintian/Tags/doc-base-abstract-might-contain-extra-leading-whitespaces

Self:Lintian/Tags/doc-base-abstract-field-separator-extra-whitespaces
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-abstract-field-separator-extra-whitespaces.html|doc-base-abstract-field-separator-extra-whitespaces]]''':<<BR>>
 Unnecessary spaces were found in the paragraph separator line of the doc-base's Abstract field. The separator line should consist of a single space followed by a single dot.

Reference(s): doc-base 2.3.2
}}}}
##END:Lintian/Tags/doc-base-abstract-field-separator-extra-whitespaces

Self:Lintian/Tags/spelling-error-in-doc-base-title-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-doc-base-title-field.html|spelling-error-in-doc-base-title-field]]''':<<BR>>
 Lintian found a spelling or capitalization error in the Title field of this doc-base control file. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does.
}}}}
##END:Lintian/Tags/spelling-error-in-doc-base-title-field

Self:Lintian/Tags/spelling-error-in-doc-base-abstract-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-doc-base-abstract-field.html|spelling-error-in-doc-base-abstract-field]]''':<<BR>>
 Lintian found a spelling or capitalization error in the Abstract field of this doc-base control file. Lintian has a list of common misspellings that looks for. It does not have a dictionary like a spelling checker does.
}}}}
##END:Lintian/Tags/spelling-error-in-doc-base-abstract-field

Self:Lintian/Tags/doc-base-file-syntax-error
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-syntax-error.html|doc-base-file-syntax-error]]''':<<BR>>
 Lintian found a syntax error in the doc-base control file.

Reference(s): doc-base 2.3.2.2
}}}}
##END:Lintian/Tags/doc-base-file-syntax-error

Self:Lintian/Tags/doc-base-file-separator-extra-whitespaces
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-separator-extra-whitespaces.html|doc-base-file-separator-extra-whitespaces]]''':<<BR>>
 Unnecessary spaces were found in the doc-base file sections' separator. The section separator is an empty line and should not contain any whitespace.

Reference(s): doc-base 2.3.2
}}}}
##END:Lintian/Tags/doc-base-file-separator-extra-whitespaces

Self:Lintian/Tags/doc-base-file-uses-obsolete-national-encoding
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-file-uses-obsolete-national-encoding.html|doc-base-file-uses-obsolete-national-encoding]]''':<<BR>>
 doc-base files must be valid UTF-8, an encoding of the Unicode character set.

 There are many ways to convert a doc-base file from an obsolete encoding like ISO-8859-1. You may, for example, use "iconv" like:

  $ iconv -f ISO-8859-1 -t UTF-8 doc-base > doc-base.new $ mv doc-base.new doc-base

Reference(s): doc-base 2.3.2
}}}}
##END:Lintian/Tags/doc-base-file-uses-obsolete-national-encoding

Self:Lintian/Tags/doc-base-uses-applications-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-uses-applications-section.html|doc-base-uses-applications-section]]''':<<BR>>
 The section indicated in this doc-base control file has a top-level section of Apps or Applications. This section is only used in menu, not in doc-base. Simply removing the top-level section will lead to a valid doc-base section.

Reference(s): doc-base 2.3.3
}}}}
##END:Lintian/Tags/doc-base-uses-applications-section

Self:Lintian/Tags/doc-base-unknown-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/doc-base-unknown-section.html|doc-base-unknown-section]]''':<<BR>>
 The section indicated in this doc-base control file is not one of the standard doc-base sections. The doc-base sections are based on the menu sections but are not exactly the same.

Reference(s): doc-base 2.3.3
}}}}
##END:Lintian/Tags/doc-base-unknown-section

Self:Lintian/Tags/menu-method-should-include-menu-h
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/menu-method-should-include-menu-h.html|menu-method-should-include-menu-h]]''':<<BR>>
 A menu-method file must include the menu.h configuration file (using "!include menu.h").

Reference(s): [[http://www.debian.org/doc/packaging-manuals/menu.html/|menu 5]]
}}}}
##END:Lintian/Tags/menu-method-should-include-menu-h

Self:Lintian/Tags/possible-documentation-but-no-doc-base-registration
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-documentation-but-no-doc-base-registration.html|possible-documentation-but-no-doc-base-registration]]''':<<BR>>
 The package ships a {{{.html}}} or {{{.pdf}}} file under {{{/usr/share/doc/}}}, which are usually documentation, but it does not register anything in doc-base. (Files under an {{{examples}}} directory are excluded.)

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.10]]
}}}}
##END:Lintian/Tags/possible-documentation-but-no-doc-base-registration

########################################################################
== control-file ==
########################################################################

Self:Lintian/Tags/debian-control-file-uses-obsolete-national-encoding
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-control-file-uses-obsolete-national-encoding.html|debian-control-file-uses-obsolete-national-encoding]]''':<<BR>>
 The Debian control file should be valid UTF-8, an encoding of the Unicode character set.

 There are many ways to convert a control from an obsoleted encoding like ISO-8859-1; you may for example use "iconv" like this:

  $ iconv -f ISO-8859-1 -t UTF-8 control > control.new $ mv control.new control

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.1]]
}}}}
##END:Lintian/Tags/debian-control-file-uses-obsolete-national-encoding

Self:Lintian/Tags/build-info-in-binary-control-file-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/build-info-in-binary-control-file-section.html|build-info-in-binary-control-file-section]]''':<<BR>>
 The control file has a Build-Depends, Build-Depends-Indep, Build-Conflicts, or Build-Conflicts-Indep field in a binary section. These specify source package relationships, and should be in the source section of the control file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.2]]
}}}}
##END:Lintian/Tags/build-info-in-binary-control-file-section

Self:Lintian/Tags/debian-control-with-duplicate-fields
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-control-with-duplicate-fields.html|debian-control-with-duplicate-fields]]''':<<BR>>
 One of the paragraphs of your debian/control contains the same field more than once. This can lead to unexpected behaviour in {{{dpkg}}} and {{{apt}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.1]]
}}}}
##END:Lintian/Tags/debian-control-with-duplicate-fields

Self:Lintian/Tags/debian-control-has-unusual-field-spacing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-control-has-unusual-field-spacing.html|debian-control-has-unusual-field-spacing]]''':<<BR>>
 The field on this line of {{{debian/control}}} has whitespace other than a single space after the colon. This is explicitly permitted in the syntax of Debian control files, but as Policy says, it is conventional to put a single space after the colon.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.1]]
}}}}
##END:Lintian/Tags/debian-control-has-unusual-field-spacing

Self:Lintian/Tags/binary-control-field-duplicates-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-control-field-duplicates-source.html|binary-control-field-duplicates-source]]''':<<BR>>
 In {{{debian/control}}}, this field for a binary package duplicates the value inherited from the source package paragraph. This doesn't hurt anything, but you may want to take advantage of the inheritance and set the value in only one place. It prevents missing duplicate places that need to be fixed if the value ever changes.
}}}}
##END:Lintian/Tags/binary-control-field-duplicates-source

Self:Lintian/Tags/debian-control-file-is-a-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-control-file-is-a-symlink.html|debian-control-file-is-a-symlink]]''':<<BR>>
 The {{{debian/control}}} file is a symlink rather than a regular file. Using symlinks for required source package files is unnecessary and makes package checking and manipulation more difficult. If the control file should be available in the source package under multiple names, make {{{debian/control}}} the real file and the other names symlinks to it.
}}}}
##END:Lintian/Tags/debian-control-file-is-a-symlink

Self:Lintian/Tags/no-section-field-for-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-section-field-for-source.html|no-section-field-for-source]]''':<<BR>>
 The package does not have a "Section:" field in the source package section of its control file. The Section field is required for source packages at the request of the Debian ftp-masters.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.2]]
}}}}
##END:Lintian/Tags/no-section-field-for-source

Self:Lintian/Tags/section-area-mismatch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/section-area-mismatch.html|section-area-mismatch]]''':<<BR>>
 The {{{debian/control}}} file places the indicated binary package in a different archive area (main, contrib, non-free) than its source package or other binary packages built from the same source package. The source package and any binary packages it builds must be in the same area of the archive, with the single exception that source packages in main may also build binary packages in contrib.
}}}}
##END:Lintian/Tags/section-area-mismatch

Self:Lintian/Tags/xs-vcs-header-in-debian-control
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/xs-vcs-header-in-debian-control.html|xs-vcs-header-in-debian-control]]''':<<BR>>
 There is an XS-Vcs-* field in the {{{debian/control}}} file. As of dpkg 1.14.6, the XS- prefix is no longer necessary. dpkg now recognizes these headers and handles them correctly. Consider removing the XS- prefix for this field.
}}}}
##END:Lintian/Tags/xs-vcs-header-in-debian-control

Self:Lintian/Tags/xc-package-type-in-debian-control
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/xc-package-type-in-debian-control.html|xc-package-type-in-debian-control]]''':<<BR>>
 The {{{debian/control}}} file contains an XC-Package-Type field. As of dpkg-dev 1.15.7, the dpkg development utilities recognize Package-Type as an official field name and do not add it to binary packages (the previous concern with the dpkg-dev-supported Package-Type field). XC-Package-Type should generally now be replaced with Package-Type.
}}}}
##END:Lintian/Tags/xc-package-type-in-debian-control

Self:Lintian/Tags/stronger-dependency-implies-weaker
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/stronger-dependency-implies-weaker.html|stronger-dependency-implies-weaker]]''':<<BR>>
 In the {{{debian/control}}} stanza for the given package, a stronger dependency field implies one of the dependencies in a weaker dependency field. In other words, the Depends field of the package requires that one of the packages listed in Recommends or Suggests be installed, or a package is listed in Recommends as well as Suggests.

 Current versions of dpkg-gencontrol will silently fix this problem by removing the weaker dependency, but it may indicate a more subtle bug (misspelling or forgetting to remove the stronger dependency when it was moved to the weaker field).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.2]]
}}}}
##END:Lintian/Tags/stronger-dependency-implies-weaker

Self:Lintian/Tags/package-depends-on-itself
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-itself.html|package-depends-on-itself]]''':<<BR>>
 The given package declares a dependency on itself in its {{{debian/control}}} stanza. Current versions of dpkg-gencontrol will silently fix this problem by removing the dependency, but it may indicate a more subtle bug (misspelling or cutting and pasting the wrong package name).

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.2]]
}}}}
##END:Lintian/Tags/package-depends-on-itself

Self:Lintian/Tags/duplicate-short-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-short-description.html|duplicate-short-description]]''':<<BR>>
 The listed binary packages all share the same short description (the first line of the Description control field). The package names may provide enough additional information to distinguish between the packages, but it's common to also add a word or two to the short description to clarify the difference.
}}}}
##END:Lintian/Tags/duplicate-short-description

Self:Lintian/Tags/duplicate-long-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-long-description.html|duplicate-long-description]]''':<<BR>>
 The listed binary packages all share the same extended description. Some additional information in the extended description explaining what is in each package and how it differs from the other packages is useful, particularly for users who aren't familiar with Debian's package naming conventions.
}}}}
##END:Lintian/Tags/duplicate-long-description

Self:Lintian/Tags/duplicate-in-relation-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-in-relation-field.html|duplicate-in-relation-field]]''':<<BR>>
 The given field in the {{{debian/control}}} file contains relations that are either identical or imply each other. The less restrictive one can be removed. This is done automatically by {{{dpkg-source}}} and {{{dpkg-gencontrol}}}, so this does not affect the generated package.
}}}}
##END:Lintian/Tags/duplicate-in-relation-field

Self:Lintian/Tags/missing-separator-between-items
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-separator-between-items.html|missing-separator-between-items]]''':<<BR>>
 The given field in the {{{debian/control}}} file contains a list of items separated by commas and pipes. It appears a separator was missed between two items. This can lead to bogus or incomplete dependencies, conflicts etc.
}}}}
##END:Lintian/Tags/missing-separator-between-items

Self:Lintian/Tags/obsolete-relation-form-in-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/obsolete-relation-form-in-source.html|obsolete-relation-form-in-source]]''':<<BR>>
 The forms "<" and ">" mean "<=" and ">=", not "<<" and ">>" as one might expect. These forms were marked obsolete and should no longer be used. Use the longer forms instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.1]]
}}}}
##END:Lintian/Tags/obsolete-relation-form-in-source

Self:Lintian/Tags/package-depends-on-hardcoded-libc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-depends-on-hardcoded-libc.html|package-depends-on-hardcoded-libc]]''':<<BR>>
 The given package declares a dependency on libc directly instead of using ${shlibs:Depends} in its {{{debian/control}}} stanza.
}}}}
##END:Lintian/Tags/package-depends-on-hardcoded-libc

Self:Lintian/Tags/weak-library-dev-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/weak-library-dev-dependency.html|weak-library-dev-dependency]]''':<<BR>>
 The given package appears to be a shared library -dev package, but the dependency on what seems to be a corresponding shared library package does not force the same package version. To ensure that compiling and linking works properly, and that the symlinks in the -dev package point to the correct files in the shared library package, a -dev package should normally use {{{(= ${binary:Version})}}} for the dependency on the shared library package.

 Sometimes, such as for -dev packages that are architecture-independent to not break binNMUs or when one doesn't want to force a tight dependency, a weaker dependency is warranted. Something like {{{(>= ${source:Upstream-Version}), (<< ${source:Upstream-Version}+1~)}}}, possibly using {{{${source:Version} }}} instead, is the right apprach. The goal is to ensure that a new upstream version of the library package doesn't satisfy the -dev package dependency, since the minor version of the shared library may have changed, breaking the {{{*.so}}} links.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 8.5]]
}}}}
##END:Lintian/Tags/weak-library-dev-dependency

########################################################################
== patch-systems ==
########################################################################

Self:Lintian/Tags/dpatch-build-dep-but-no-patch-list
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dpatch-build-dep-but-no-patch-list.html|dpatch-build-dep-but-no-patch-list]]''':<<BR>>
 Using dpatch requires you to explicitly list all patches you want to apply in debian/patches/00list. This package build-depends on dpatch, but does not provide a patch list. You should either remove the dpatch build dependency or add a patch list.

 Note that an empty file cannot be represented in the Debian diff, so an empty patch list will disappear in the source package. If you intended for the series file to be empty, add a comment line.
}}}}
##END:Lintian/Tags/dpatch-build-dep-but-no-patch-list

Self:Lintian/Tags/dpatch-index-references-non-existent-patch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dpatch-index-references-non-existent-patch.html|dpatch-index-references-non-existent-patch]]''':<<BR>>
 In the 00list file listing all your dpatches, you referenced a file that does not exist. This will lead to a fatal error when calling dpatch.
}}}}
##END:Lintian/Tags/dpatch-index-references-non-existent-patch

Self:Lintian/Tags/dpatch-missing-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dpatch-missing-description.html|dpatch-missing-description]]''':<<BR>>
 dpatch files should carry a description of the included patch. Description lines start with "## DP:".

 As well as a description of the purpose and function of the patch, the description should ideally contain author information, a URL for the bug report (if any), Debian or upstream bugs fixed by it, upstream status, the Debian version and date the patch was first included, and any other information that would be useful if someone were investigating the patch and underlying problem. Please consider using the DEP-3 format for this information.

Reference(s): [[http://dep.debian.net/deps/dep3/]]
}}}}
##END:Lintian/Tags/dpatch-missing-description

Self:Lintian/Tags/quilt-build-dep-but-no-series-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/quilt-build-dep-but-no-series-file.html|quilt-build-dep-but-no-series-file]]''':<<BR>>
 Using quilt requires you to explicitly list all patches you want to apply in debian/patches/series. This package build-depends on quilt, but does not provide a patch list. You should either remove the quilt build dependency or add a series file.

 Note that an empty file cannot be represented in the Debian diff, so an empty series file will disappear in the source package. If you intended for the series file to be empty, add a comment line.
}}}}
##END:Lintian/Tags/quilt-build-dep-but-no-series-file

Self:Lintian/Tags/quilt-series-but-no-build-dep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/quilt-series-but-no-build-dep.html|quilt-series-but-no-build-dep]]''':<<BR>>
 The package contains a debian/patches/series file usually used by quilt to apply patches at build time, but quilt is not listed in the build dependencies.

 You should either remove the series file if it's effectively not useful or add quilt to the build-dependencies if quilt is used during the build process.

 If you don't need quilt during build but only during maintenance work, then you can override this warning.
}}}}
##END:Lintian/Tags/quilt-series-but-no-build-dep

Self:Lintian/Tags/quilt-patch-with-non-standard-options
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/quilt-patch-with-non-standard-options.html|quilt-patch-with-non-standard-options]]''':<<BR>>
 The quilt series file contains non-standard options to apply some of the listed patches. Quilt uses '-p1' by default if nothing is specified after the name of the patch and the current series file specify something else for some of the patches listed.

 For compatibility with the source "3.0 (quilt)" source package format, you should avoid using any option at all and make sure that your patches apply with "-p1". This can be done by refreshing all patches like this: quilt pop -a; while quilt push; do quilt refresh -pab; done
}}}}
##END:Lintian/Tags/quilt-patch-with-non-standard-options

Self:Lintian/Tags/quilt-series-references-non-existent-patch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/quilt-series-references-non-existent-patch.html|quilt-series-references-non-existent-patch]]''':<<BR>>
 In the series file listing all your quilt patches, you referenced a file that does not exist. This will lead to a fatal error when calling quilt.
}}}}
##END:Lintian/Tags/quilt-series-references-non-existent-patch

Self:Lintian/Tags/quilt-patch-missing-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/quilt-patch-missing-description.html|quilt-patch-missing-description]]''':<<BR>>
 quilt patch files should start with a description of patch. All lines before the start of the patch itself are considered part of the description. You can edit the description with {{{quilt header -e}}} when the patch is at the top of the stack.

 As well as a description of the purpose and function of the patch, the description should ideally contain author information, a URL for the bug report (if any), Debian or upstream bugs fixed by it, upstream status, the Debian version and date the patch was first included, and any other information that would be useful if someone were investigating the patch and underlying problem. Please consider using the DEP-3 format for this information.

Reference(s): [[http://dep.debian.net/deps/dep3/]]
}}}}
##END:Lintian/Tags/quilt-patch-missing-description

Self:Lintian/Tags/patch-modifying-debian-files
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/patch-modifying-debian-files.html|patch-modifying-debian-files]]''':<<BR>>
 A patch stored in debian/patches/ should never modify files in the debian directory (even when it's only creating new files) because the debian directory is always directly provided by the Debian packaging. And you shouldn't have to modify what you choose to provide in the first place.

 If the patch provides a new file (say a manual page), place that file in the upstream directory hierarchy as if it was ready to be submitted.
}}}}
##END:Lintian/Tags/patch-modifying-debian-files

Self:Lintian/Tags/patch-system-but-direct-changes-in-diff
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/patch-system-but-direct-changes-in-diff.html|patch-system-but-direct-changes-in-diff]]''':<<BR>>
 The package uses a patch system, but the Debian diff.gz contains changes to files or creation of additional files outside of the {{{debian}}} directory. This often indicates accidental changes that weren't meant to be in the package or changes that were supposed to be separated out into a patch. The package will also more easily support possible future source package formats if all changes outside the {{{debian}}} directory are stored as patches.
}}}}
##END:Lintian/Tags/patch-system-but-direct-changes-in-diff

Self:Lintian/Tags/more-than-one-patch-system
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/more-than-one-patch-system.html|more-than-one-patch-system]]''':<<BR>>
 Either the build-dependencies list more than one patch system or the package uses the {{{3.0 (quilt)}}} source format but also has a dependency on {{{dpatch}}}. 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.
}}}}
##END:Lintian/Tags/more-than-one-patch-system

Self:Lintian/Tags/direct-changes-in-diff-but-no-patch-system
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/direct-changes-in-diff-but-no-patch-system.html|direct-changes-in-diff-but-no-patch-system]]''':<<BR>>
 The Debian diff.gz contains changes to files or creation of additional files outside the {{{debian}}} directory. Keeping the changes as separate patches under the control of a patch system allows for more fine grained control over them. The package will also more easily support possible future source package formats if all changes outside the {{{debian}}} directory are stored as patches.

 If the diff only creates new files that can be copied into place by the package build rules, consider putting them in the {{{debian}}} directory rather than using a patch system.
}}}}
##END:Lintian/Tags/direct-changes-in-diff-but-no-patch-system

Self:Lintian/Tags/patch-system-but-no-source-readme
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/patch-system-but-no-source-readme.html|patch-system-but-no-source-readme]]''':<<BR>>
 This package build-depends on a patch system such as dpatch or quilt, but there is no {{{debian/README.source}}} file. This file is recommended for any package where {{{dpkg-source -x}}} does not result in the preferred form for making modifications to the package.

 If you are using quilt and the package needs no other special handling instructions, you may want to add a {{{debian/README.source}}} referring to {{{/usr/share/doc/quilt/README.source}}}. Similarly, you can refer to {{{/usr/share/doc/dpatch/README.source.gz}}} for dpatch.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.14]]
}}}}
##END:Lintian/Tags/patch-system-but-no-source-readme

########################################################################
== deb-format ==
########################################################################

Self:Lintian/Tags/malformed-deb-archive
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-deb-archive.html|malformed-deb-archive]]''':<<BR>>
 The binary package is not a correctly constructed archive. A binary Debian package must be an ar archive with exactly three members: {{{debian-binary}}}, {{{control.tar.gz}}}, and {{{data.tar.gz}}} or {{{data.tar.bz2}}} in exactly that order. The {{{debian-binary}}} member must start with a single line containing the version number, with a major revision of 2.

Reference(s): [[DebianMan:5/deb|deb(5)]]
}}}}
##END:Lintian/Tags/malformed-deb-archive

Self:Lintian/Tags/lzma-deb-archive
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/lzma-deb-archive.html|lzma-deb-archive]]''':<<BR>>
 The data portion of this binary package is compressed with lzma. This is supported by dpkg but not yet permitted in the Debian archive. Such a package will be rejected by DAK.
}}}}
##END:Lintian/Tags/lzma-deb-archive

Self:Lintian/Tags/tar-errors-from-control
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/tar-errors-from-control.html|tar-errors-from-control]]''':<<BR>>
 tar produced an error while listing the contents of the {{{control.tar.gz}}} member of this package. This probably means there's something broken or at least strange about the way the package was constructed.
}}}}
##END:Lintian/Tags/tar-errors-from-control

Self:Lintian/Tags/tar-errors-from-data
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/tar-errors-from-data.html|tar-errors-from-data]]''':<<BR>>
 tar produced an error while listing the contents of the data member of this package. This probably means there's something broken or at least strange about the way the package was constructed.
}}}}
##END:Lintian/Tags/tar-errors-from-data

########################################################################
== huge-usr-share ==
########################################################################

Self:Lintian/Tags/arch-dep-package-has-big-usr-share
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/arch-dep-package-has-big-usr-share.html|arch-dep-package-has-big-usr-share]]''':<<BR>>
 The package has a significant amount of architecture-independent data (over 4MB, or over 2MB and more than 50% of the package) in {{{/usr/share}}} but is an architecture-dependent package. This is wasteful of mirror space and bandwidth since it means distributing multiple copies of this data, one for each architecture.

 If the data in {{{/usr/share}}} is not architecture-independent, this is a Policy violation that should be fixed by moving the data elsewhere (usually {{{/usr/lib}}}).

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.7.5]]
}}}}
##END:Lintian/Tags/arch-dep-package-has-big-usr-share

########################################################################
== control-files ==
########################################################################

Self:Lintian/Tags/unknown-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-control-file.html|unknown-control-file]]''':<<BR>>
 The package contains an unknown control file. Policy says that putting additional files in the package control area is not generally a good idea.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy B.2]]
}}}}
##END:Lintian/Tags/unknown-control-file

Self:Lintian/Tags/not-allowed-control-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/not-allowed-control-file.html|not-allowed-control-file]]''':<<BR>>
 The package contains a control file that is not allowed in this type of package. Some control files are only allowed in either .deb or .udeb packages and must not be included in packages of the other type. You should probably just remove the file.
}}}}
##END:Lintian/Tags/not-allowed-control-file

Self:Lintian/Tags/control-file-is-empty
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/control-file-is-empty.html|control-file-is-empty]]''':<<BR>>
 The package contains an empty control file, which is most probably an error.
}}}}
##END:Lintian/Tags/control-file-is-empty

Self:Lintian/Tags/control-file-has-bad-permissions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/control-file-has-bad-permissions.html|control-file-has-bad-permissions]]''':<<BR>>
 The {{{config}}}, {{{postinst}}}, {{{postrm}}}, {{{preinst}}}, and {{{prerm}}} control files should use mode 0755; all other control files should use 0644.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/control-file-has-bad-permissions

Self:Lintian/Tags/control-file-has-bad-owner
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/control-file-has-bad-owner.html|control-file-has-bad-owner]]''':<<BR>>
 All control files should be owned by root/root.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 10.9]]
}}}}
##END:Lintian/Tags/control-file-has-bad-owner

########################################################################
== debhelper ==
########################################################################

Self:Lintian/Tags/maintainer-script-lacks-debhelper-token
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-script-lacks-debhelper-token.html|maintainer-script-lacks-debhelper-token]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/maintainer-script-lacks-debhelper-token

Self:Lintian/Tags/package-uses-debhelper-but-lacks-build-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-uses-debhelper-but-lacks-build-depends.html|package-uses-debhelper-but-lacks-build-depends]]''':<<BR>>
 If a package uses debhelper, it must declare a Build-Depends on debhelper.
}}}}
##END:Lintian/Tags/package-uses-debhelper-but-lacks-build-depends

Self:Lintian/Tags/package-lacks-versioned-build-depends-on-debhelper
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-lacks-versioned-build-depends-on-debhelper.html|package-lacks-versioned-build-depends-on-debhelper]]''':<<BR>>
 The package either doesn't declare a versioned build dependency on debhelper or does not declare a versioned build dependency on a new enough version of debhelper to satisfy the declared compatibility level.

 Recommended practice is to always declare an explicit versioned dependency on debhelper equal to or greater than the compatibility level used by the package, even if the versioned dependency isn't strictly necessary. Having a versioned dependency also helps with backports to older releases and correct builds on partially updated systems.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/package-lacks-versioned-build-depends-on-debhelper

Self:Lintian/Tags/dh-make-template-in-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh-make-template-in-source.html|dh-make-template-in-source]]''':<<BR>>
 This package contains debian/*.ex and/or debian/ex.* files installed by dh_make. These are intended to be filled in with the package's details and renamed for use by various debhelper commands. If they are not being used, they should be removed.
}}}}
##END:Lintian/Tags/dh-make-template-in-source

Self:Lintian/Tags/dh_dhelp-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh_dhelp-is-deprecated.html|dh_dhelp-is-deprecated]]''':<<BR>>
 This package calls dh_dhelp in its {{{debian/rules}}} file. dh_dhelp is deprecated as it is not part of the canonical debhelper suite and due to be removed since it supports only one single documentation system (dhelp).

 Simply use dh_installdocs, which creates doc-base files and supports all of the documentation systems that way.
}}}}
##END:Lintian/Tags/dh_dhelp-is-deprecated

Self:Lintian/Tags/dh_suidregister-is-obsolete
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh_suidregister-is-obsolete.html|dh_suidregister-is-obsolete]]''':<<BR>>
 suidregister is obsoleted by dpkg-statoverride, so registration of files in with dh_suidregister is unnecessary, and even harmful.

Reference(s): [[DebianMan:1/dh_suidregister|dh_suidregister(1)]]
}}}}
##END:Lintian/Tags/dh_suidregister-is-obsolete

Self:Lintian/Tags/dh_undocumented-is-obsolete
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh_undocumented-is-obsolete.html|dh_undocumented-is-obsolete]]''':<<BR>>
 This package calls dh_undocumented in its {{{debian/rules}}} file. The dh_undocumented command is obsolete and does nothing, since it's former behavior of adding symlinks to the undocumented(7) man page is now obsolete.

Reference(s): [[DebianMan:1/dh_undocumented|dh_undocumented(1)]]
}}}}
##END:Lintian/Tags/dh_undocumented-is-obsolete

Self:Lintian/Tags/dh_desktop-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh_desktop-is-deprecated.html|dh_desktop-is-deprecated]]''':<<BR>>
 This package calls dh_desktop in its {{{debian/rules}}} file. dh_desktop is deprecated and no longer does anything. The setup it used to handle is now done with triggers.

Reference(s): [[DebianMan:1/dh_desktop|dh_desktop(1)]]
}}}}
##END:Lintian/Tags/dh_desktop-is-deprecated

Self:Lintian/Tags/dh_scrollkeeper-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh_scrollkeeper-is-deprecated.html|dh_scrollkeeper-is-deprecated]]''':<<BR>>
 This package calls dh_scrollkeeper in its {{{debian/rules}}} file. dh_scrollkeeper is deprecated and no longer does anything. scrollkeeper has been replaced by rarian, which does not require the functionality dh_scrollkeeper used to provide.

Reference(s): [[DebianMan:1/dh_scrollkeeper|dh_scrollkeeper(1)]]
}}}}
##END:Lintian/Tags/dh_scrollkeeper-is-deprecated

Self:Lintian/Tags/dh-clean-k-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/dh-clean-k-is-deprecated.html|dh-clean-k-is-deprecated]]''':<<BR>>
 This package calls dh_clean -k in its {{{debian/rules}}} file and declares a debhelper compatibility version of at least 7.

 debhelper 7 deprecated dh_clean -k in favour of dh_prep.

Reference(s): [[DebianMan:1/dh_clean|dh_clean(1)]]
}}}}
##END:Lintian/Tags/dh-clean-k-is-deprecated

Self:Lintian/Tags/debhelper-compat-file-is-empty
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debhelper-compat-file-is-empty.html|debhelper-compat-file-is-empty]]''':<<BR>>
 The source package has an empty debian/compat file. This is an error, the compat level of debhelper should be in there. Note that only the first line of the file is relevant.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/debhelper-compat-file-is-empty

Self:Lintian/Tags/declares-possibly-conflicting-debhelper-compat-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/declares-possibly-conflicting-debhelper-compat-versions.html|declares-possibly-conflicting-debhelper-compat-versions]]''':<<BR>>
 The source package declares the debhelper compatibility version both in the {{{debian/compat}}} file and in the {{{debian/rules}}} file. If these ever get out of synchronisation, the package may not build as expected.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/declares-possibly-conflicting-debhelper-compat-versions

Self:Lintian/Tags/package-uses-deprecated-debhelper-compat-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/package-uses-deprecated-debhelper-compat-version.html|package-uses-deprecated-debhelper-compat-version]]''':<<BR>>
 The debhelper compatibility version used by this package is marked as deprecated by the debhelper developer. You should really consider using a newer compatibility version.

 The compatibility version can be set in (preferred) {{{debian/compat}}} or by setting and exporting DH_COMPAT in {{{debian/rules}}}. If it is not set in either place, debhelper defaults to the deprecated compatibility version 1.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/package-uses-deprecated-debhelper-compat-version

Self:Lintian/Tags/uses-dh-python-with-no-pycompat
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/uses-dh-python-with-no-pycompat.html|uses-dh-python-with-no-pycompat]]''':<<BR>>
 This package uses dh_python but apparently does not tell it to use the current Python policy by putting 2 in {{{debian/pycompat}}}. This may mean that the package has not been converted to the current Python policy, in which case it probably should be.
}}}}
##END:Lintian/Tags/uses-dh-python-with-no-pycompat

Self:Lintian/Tags/debhelper-but-no-misc-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debhelper-but-no-misc-depends.html|debhelper-but-no-misc-depends]]''':<<BR>>
 The source package uses debhelper, but it does not include ${misc:Depends} in the given binary package's debian/control entry. Any debhelper command may add dependencies to ${misc:Depends} that are required for the work that it does, so recommended best practice is to always add ${misc:Depends} to the dependencies of each binary package if debhelper is in use.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/debhelper-but-no-misc-depends

Self:Lintian/Tags/missing-build-dependency-for-dh_-command
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-build-dependency-for-dh_-command.html|missing-build-dependency-for-dh_-command]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/missing-build-dependency-for-dh_-command

Self:Lintian/Tags/debhelper-script-needs-versioned-build-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debhelper-script-needs-versioned-build-depends.html|debhelper-script-needs-versioned-build-depends]]''':<<BR>>
 The given debhelper script was introduced in a later version of debhelper than the package Build-Depends on. The package Build-Depends should be updated to require that version of debhelper. Giving the version followed by {{{~}}} is recommended so that backports will satisfy the dependency.

 etch was released with debhelper version 5.0.42, so every package that assumes a newer version should explicitly declare so for the sake of etch backports.
}}}}
##END:Lintian/Tags/debhelper-script-needs-versioned-build-depends

Self:Lintian/Tags/debhelper-overrides-need-versioned-build-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debhelper-overrides-need-versioned-build-depends.html|debhelper-overrides-need-versioned-build-depends]]''':<<BR>>
 The override targets facility in debhelper, involving debian/rules targets that begin with "override_dh_", was introduced in a later version of debhelper than the package Build-Depends on. The package Build-Depends should be updated to require at least debhelper 7.0.50. Giving the version followed by {{{~}}} is recommended so that backports will satisfy the dependency.

 lenny was released with debhelper version 7.0.15, so every package that assumes a newer version should explicitly declare so for the sake of lenny backports.

Reference(s): [[DebianMan:1/dh|dh(1)]]
}}}}
##END:Lintian/Tags/debhelper-overrides-need-versioned-build-depends

Self:Lintian/Tags/brace-expansion-in-debhelper-config-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/brace-expansion-in-debhelper-config-file.html|brace-expansion-in-debhelper-config-file]]''':<<BR>>
 This debhelper config file appears to use shell brace expansion (such as {{{{foo,bar} }}}) to specify files. This happens to work due to an accident of implementation but is not a supported feature. Only {{{?}}}, {{{*}}}, and {{{[...]}}} are supported.

Reference(s): [[DebianMan:1/debhelper|debhelper(1)]]
}}}}
##END:Lintian/Tags/brace-expansion-in-debhelper-config-file

Self:Lintian/Tags/weak-dependency-on-misc-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/weak-dependency-on-misc-depends.html|weak-dependency-on-misc-depends]]''':<<BR>>
 The source package declares a weak dependecy on ${misc:Depends} in the given binary package's debian/control entry. A stronger dependency, that is one that ensures the package's installation, is required so that the additional commands are available to the maintainer scripts when they are run.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/weak-dependency-on-misc-depends

Self:Lintian/Tags/debhelper-compat-not-a-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debhelper-compat-not-a-number.html|debhelper-compat-not-a-number]]''':<<BR>>
 The debhelper compatibility level specified in {{{debian/compat}}} is not a number.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/debhelper-compat-not-a-number

Self:Lintian/Tags/debhelper-compatibility-level-not-a-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debhelper-compatibility-level-not-a-number.html|debhelper-compatibility-level-not-a-number]]''':<<BR>>
 The debhelper compatibility level specified in {{{debian/rules}}} is not a number. If you're using make functions or other more complex methods to generate the compatibility level, write the output into {{{debian/compat}}} instead of setting DH_COMPAT. The latter should be available for a user to override temporarily.
}}}}
##END:Lintian/Tags/debhelper-compatibility-level-not-a-number

########################################################################
== cruft ==
########################################################################

Self:Lintian/Tags/native-package-with-dash-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/native-package-with-dash-version.html|native-package-with-dash-version]]''':<<BR>>
 Native packaging should only be used if a piece of software was written specifically to be turned into a Debian package. In this case, the version number should not contain a Debian revision part.

 Native source packages are sometimes created by accident. In most cases the reason is the location of the original source tarball. For version 1.0 source packages, dpkg-source determines whether they're non-native by looking for a file named {{{<package>_<version>.orig.tar.gz}}} in the parent directory, where <version> is the version from the most recent {{{debian/changelog}}} entry. For version 3.0 packages, check {{{debian/source/format}}} for an erroneous "(native)" package format.
}}}}
##END:Lintian/Tags/native-package-with-dash-version

Self:Lintian/Tags/non-native-package-with-native-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/non-native-package-with-native-version.html|non-native-package-with-native-version]]''':<<BR>>
 This package has a native version number (a version number without a dash and a Debian portion) but is built as a non-native package. Usually this is an error caused by a stray {{{*.orig.tar.gz}}} file in the parent directory fooling {{{dpkg-source}}} into thinking it was supposed to be a non-native package.
}}}}
##END:Lintian/Tags/non-native-package-with-native-version

Self:Lintian/Tags/documentation-package-not-architecture-independent
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/documentation-package-not-architecture-independent.html|documentation-package-not-architecture-independent]]''':<<BR>>
 Documentation packages usually shouldn't carry anything that requires recompiling on various architectures, in order to save space on mirrors.
}}}}
##END:Lintian/Tags/documentation-package-not-architecture-independent

Self:Lintian/Tags/debian-files-list-in-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-files-list-in-source.html|debian-files-list-in-source]]''':<<BR>>
 Leaving {{{debian/files}}} causes problems for the autobuilders, since that file will likely include the list of .deb files for another architecture, which will cause dpkg-buildpackage run by the buildd to fail.

 The clean rule for the package should remove this file.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.12]]
}}}}
##END:Lintian/Tags/debian-files-list-in-source

Self:Lintian/Tags/diff-contains-cmake-cache-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-cmake-cache-file.html|diff-contains-cmake-cache-file]]''':<<BR>>
 The Debian diff contains a CMake cache file. These files embed the full path of the source tree in which they're created and cause build failures if they exist when the source is built under a different path, so they will always cause errors on the buildds. The file was probably accidentally included. If it is present in the upstream source, don't modify it in the Debian diff; instead, delete it before the build in {{{debian/rules}}}.
}}}}
##END:Lintian/Tags/diff-contains-cmake-cache-file

Self:Lintian/Tags/diff-contains-cvs-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-cvs-control-dir.html|diff-contains-cvs-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in a CVS directory. These are usually artifacts of the revision control system used by the Debian maintainer and not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-cvs-control-dir

Self:Lintian/Tags/source-contains-cvs-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-cvs-control-dir.html|source-contains-cvs-control-dir]]''':<<BR>>
 The upstream source contains a CVS directory. It was most likely included by accident since CVS directories usually don't belong in releases. When packaging a CVS snapshot, export from CVS rather than use a checkout. If an upstream release tarball contains CVS directories, you usually should report this as a bug to upstream.
}}}}
##END:Lintian/Tags/source-contains-cvs-control-dir

Self:Lintian/Tags/diff-contains-svn-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-svn-control-dir.html|diff-contains-svn-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in an .svn directory. These are usually artifacts of the revision control system used by the Debian maintainer and not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-svn-control-dir

Self:Lintian/Tags/source-contains-svn-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-svn-control-dir.html|source-contains-svn-control-dir]]''':<<BR>>
 The upstream source contains an .svn directory. It was most likely included by accident since Subversion version control directories usually don't belong in releases. When packaging a Subversion snapshot, export from subversion rather than checkout. If an upstream release tarball contains .svn directories, this should be reported as a bug to upstream since it can double the size of the tarball to no purpose.
}}}}
##END:Lintian/Tags/source-contains-svn-control-dir

Self:Lintian/Tags/diff-contains-bzr-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-bzr-control-dir.html|diff-contains-bzr-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in a .bzr directory. These are usually artifacts of the revision control system used by the Debian maintainer and not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-bzr-control-dir

Self:Lintian/Tags/source-contains-bzr-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-bzr-control-dir.html|source-contains-bzr-control-dir]]''':<<BR>>
 The upstream source contains a .bzr directory. It was most likely included by accident since bazaar-ng version control directories usually don't belong in releases and may contain the entire repository. When packaging a bzr snapshot, use bzr export to create a clean tree. If an upstream release tarball contains .bzr directories, you should usually report this as a bug upstream.
}}}}
##END:Lintian/Tags/source-contains-bzr-control-dir

Self:Lintian/Tags/diff-contains-arch-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-arch-control-dir.html|diff-contains-arch-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in an {arch} or .arch-ids directory or a directory starting with {{{,,}}} (used by baz for debugging traces). These are usually artifacts of the revision control system used by the Debian maintainer and not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-arch-control-dir

Self:Lintian/Tags/source-contains-arch-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-arch-control-dir.html|source-contains-arch-control-dir]]''':<<BR>>
 The upstream source contains an {arch} or .arch-ids directory or a directory starting with {{{,,}}} (used by baz for debugging traces). It was most likely included by accident since Arch version control directories usually don't belong in releases. If an upstream release tarball contains these directories, you should usually report this as a bug upstream.
}}}}
##END:Lintian/Tags/source-contains-arch-control-dir

Self:Lintian/Tags/diff-contains-git-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-git-control-dir.html|diff-contains-git-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in a .git directory. These are usually artifacts of the revision control system used by the Debian maintainer and not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-git-control-dir

Self:Lintian/Tags/source-contains-git-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-git-control-dir.html|source-contains-git-control-dir]]''':<<BR>>
 The upstream source contains a .git directory. It was most likely included by accident since git version control directories usually don't belong in releases and may contain a complete copy of the repository. If an upstream release tarball contains .git directories, you should usually report this as a bug upstream.
}}}}
##END:Lintian/Tags/source-contains-git-control-dir

Self:Lintian/Tags/diff-contains-hg-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-hg-control-dir.html|diff-contains-hg-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in a .hg directory. These are usually artifacts of the revision control system used by the Debian maintainer and not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-hg-control-dir

Self:Lintian/Tags/source-contains-hg-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-hg-control-dir.html|source-contains-hg-control-dir]]''':<<BR>>
 The upstream source contains a .hg directory. It was most likely included by accident since hg version control directories usually don't belong in releases and may contain a complete copy of the repository. If an upstream release tarball contains .hg directories, you should usually report this as a bug upstream.
}}}}
##END:Lintian/Tags/source-contains-hg-control-dir

Self:Lintian/Tags/diff-contains-bts-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-bts-control-dir.html|diff-contains-bts-control-dir]]''':<<BR>>
 The Debian diff or native package contains files in a directory used by a bug tracking system, which are not useful in a diff or native package. Passing {{{-i}}} to {{{dpkg-buildpackage}}} or the equivalent will automatically exclude them.
}}}}
##END:Lintian/Tags/diff-contains-bts-control-dir

Self:Lintian/Tags/source-contains-bts-control-dir
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-bts-control-dir.html|source-contains-bts-control-dir]]''':<<BR>>
 The upstream source contains a directory used by a bug tracking system. It was most likely included by accident since bug tracking system directories usually don't belong in releases.
}}}}
##END:Lintian/Tags/source-contains-bts-control-dir

Self:Lintian/Tags/diff-contains-svn-commit-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-svn-commit-file.html|diff-contains-svn-commit-file]]''':<<BR>>
 The Debian diff or native package contains an {{{svn-commit(.NNN).tmp}}}, almost certainly a left-over from a failed Subversion commit by the Debian package maintainer.
}}}}
##END:Lintian/Tags/diff-contains-svn-commit-file

Self:Lintian/Tags/source-contains-svn-commit-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-svn-commit-file.html|source-contains-svn-commit-file]]''':<<BR>>
 The upstream source contains an {{{svn-commit(.NNN).tmp}}}, almost certainly a left-over from a failed Subversion commit. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/source-contains-svn-commit-file

Self:Lintian/Tags/diff-contains-svk-commit-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-svk-commit-file.html|diff-contains-svk-commit-file]]''':<<BR>>
 The Debian diff or native package contains an {{{svk-commitNNN.tmp}}}, almost certainly a left-over from a failed svk commit by the Debian package maintainer.
}}}}
##END:Lintian/Tags/diff-contains-svk-commit-file

Self:Lintian/Tags/source-contains-svk-commit-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-svk-commit-file.html|source-contains-svk-commit-file]]''':<<BR>>
 The upstream source contains an {{{svk-commitNNN.tmp}}}, almost certainly a left-over from a failed Subversion commit. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/source-contains-svk-commit-file

Self:Lintian/Tags/diff-contains-arch-inventory-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-arch-inventory-file.html|diff-contains-arch-inventory-file]]''':<<BR>>
 The Debian diff or native package contains an {{{.arch-inventory}}} file. This is Arch metadata that should normally not be distributed.
}}}}
##END:Lintian/Tags/diff-contains-arch-inventory-file

Self:Lintian/Tags/source-contains-arch-inventory-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-arch-inventory-file.html|source-contains-arch-inventory-file]]''':<<BR>>
 The upstream source contains an {{{.arch-inventory}}} file. This is Arch metadata that should normally not be distributed. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/source-contains-arch-inventory-file

Self:Lintian/Tags/diff-contains-hg-tags-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-hg-tags-file.html|diff-contains-hg-tags-file]]''':<<BR>>
 The Debian diff or native package contains an {{{.hgtags}}} file. This file is Mercurial metadata that should normally not be distributed. It stores hashes of tagged commits in a Mercurial repository and isn't therefore useful without the repository.
}}}}
##END:Lintian/Tags/diff-contains-hg-tags-file

Self:Lintian/Tags/source-contains-hg-tags-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-hg-tags-file.html|source-contains-hg-tags-file]]''':<<BR>>
 The upstream source contains an {{{.hgtags}}} file. This file is Mercurial metadata that should normally not be distributed. It stores hashes of tagged commits in a Mercurial repository and isn't therefore useful without the repository. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/source-contains-hg-tags-file

Self:Lintian/Tags/diff-contains-cvs-conflict-copy
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-cvs-conflict-copy.html|diff-contains-cvs-conflict-copy]]''':<<BR>>
 The Debian diff or native package contains a CVS conflict copy. These have file names like {{{.#file.version}}} and are generated by CVS when a conflict was detected when merging local changes with updates from a source repository. They're useful only while resolving the conflict and should not be included in the package.
}}}}
##END:Lintian/Tags/diff-contains-cvs-conflict-copy

Self:Lintian/Tags/source-contains-cvs-conflict-copy
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-cvs-conflict-copy.html|source-contains-cvs-conflict-copy]]''':<<BR>>
 The upstream source contains a CVS conflict copy. These have file names like {{{.#file.version}}} and are generated by CVS when a conflict was detected when merging local changes with updates from a source repository. They're useful only while resolving the conflict and were probably included by accident. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/source-contains-cvs-conflict-copy

Self:Lintian/Tags/diff-contains-svn-conflict-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-svn-conflict-file.html|diff-contains-svn-conflict-file]]''':<<BR>>
 The Debian diff or native package contains a file that looks like a Subversion conflict file. These are generated by Subversion when a conflict was detected while merging local changes with updates from a source repository. Use {{{svn resolved}}} to remove them and clear the Subversion conflict state after you have resolved the conflict.
}}}}
##END:Lintian/Tags/diff-contains-svn-conflict-file

Self:Lintian/Tags/source-contains-svn-conflict-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-svn-conflict-file.html|source-contains-svn-conflict-file]]''':<<BR>>
 The upstream source contains a file that looks like a Subversion conflict file. These are generated by Subversion when a conflict was detected while merging local changes with updates from a source repository. They're useful only while resolving the conflict and were probably included by accident. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/source-contains-svn-conflict-file

Self:Lintian/Tags/diff-contains-patch-failure-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-patch-failure-file.html|diff-contains-patch-failure-file]]''':<<BR>>
 The Debian diff or native package contains a file that looks like the files left behind by the {{{patch}}} utility when it cannot completely apply a diff. This may be left over from a patch applied by the maintainer. Normally such files should not be included in the package.
}}}}
##END:Lintian/Tags/diff-contains-patch-failure-file

Self:Lintian/Tags/diff-contains-editor-backup-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-editor-backup-file.html|diff-contains-editor-backup-file]]''':<<BR>>
 The Debian diff or native package contains a file ending in {{{~}}} or of the form {{{.xxx.swp}}}, which is normally either an Emacs or vim backup file or a backup file created by programs such as {{{autoheader}}} or {{{debconf-updatepo}}}. This usually causes no harm, but it's messy and bloats the size of the Debian diff to no useful purpose.
}}}}
##END:Lintian/Tags/diff-contains-editor-backup-file

Self:Lintian/Tags/diff-contains-substvars
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/diff-contains-substvars.html|diff-contains-substvars]]''':<<BR>>
 Lintian found a substvars file in the Debian diff for this source package. The debian/substvars file is usually generated and modified dynamically by debian/rules targets, in which case it must be removed by the clean target.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.9]]
}}}}
##END:Lintian/Tags/diff-contains-substvars

Self:Lintian/Tags/empty-debian-diff
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/empty-debian-diff.html|empty-debian-diff]]''':<<BR>>
 The Debian diff of this non-native package appears to be completely empty. This usually indicates a mistake when generating the upstream tarball, or it may mean that this was intended to be a native package and was built non-native by mistake.

 If the Debian packaging is maintained in conjunction with upstream, this may be intentional, but it's not recommended best practice. If the software is only for Debian, it should be a native package; otherwise, it's better to omit the {{{debian}}} directory from upstream releases and add it in the Debian diff. Otherwise, it can cause problems for some package updates in Debian (files can't be removed from the {{{debian}}} directory via the diff, for example).
}}}}
##END:Lintian/Tags/empty-debian-diff

Self:Lintian/Tags/configure-generated-file-in-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/configure-generated-file-in-source.html|configure-generated-file-in-source]]''':<<BR>>
 Leaving config.cache/status causes autobuilders problems. config.cache and config.status are produced by GNU autoconf's configure scripts. If they are left in the source package, autobuilders may pick up settings for the wrong architecture.

 The clean rule in {{{debian/rules}}} should remove this file. This should ideally be done by fixing the upstream build system to do it when you run the appropriate cleaning command (and don't forget to forward the fix to the upstream authors so it doesn't happen in the next release). If that is already implemented, then make sure you are indeed cleaning it in the clean rule. If all else fails, a simple rm -f should work.

 Note that Lintian cannot reliably detect the removal in the clean rule, so once you fix this, please ignore or override this warning.
}}}}
##END:Lintian/Tags/configure-generated-file-in-source

Self:Lintian/Tags/ancient-autotools-helper-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-autotools-helper-file.html|ancient-autotools-helper-file]]''':<<BR>>
 The referenced file has a time stamp older than year 2004 and the package does not build-depend on autotools-dev or automake and therefore apparently does not update it. This usually means that the source package will not build correctly on all currently released architectures.

 Read /usr/share/doc/autotools-dev/README.Debian.gz (from the autotools-dev package) for information on how to fix this problem. cdbs will automatically update these files if autotools-dev is installed during build, but the build dependency on autotools-dev is still necessary.
}}}}
##END:Lintian/Tags/ancient-autotools-helper-file

Self:Lintian/Tags/outdated-autotools-helper-file
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/outdated-autotools-helper-file.html|outdated-autotools-helper-file]]''':<<BR>>
 The referenced file has a time stamp older than June of 2006 and the package does not build-depend on autotools-dev or automake and therefore apparently does not update it. This usually means that the source package will not build correctly on AVR32, for which a Debian port is currently in progress, and may not support other newer architectures.

 Read /usr/share/doc/autotools-dev/README.Debian.gz (from the autotools-dev package) for information on how to fix this problem. cdbs will automatically update these files if autotools-dev is installed during build, but the build dependency on autotools-dev is still necessary.
}}}}
##END:Lintian/Tags/outdated-autotools-helper-file

Self:Lintian/Tags/ancient-libtool
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-libtool.html|ancient-libtool]]''':<<BR>>
 The referenced file seems to be from a libtool version older than 1.5.2-2. This might lead to build errors on some newer architectures not known to this libtool.

 Please ask your upstream maintainer to re-libtoolize the package or do it yourself if there is no active upstream. You will also need to run Autoconf to regenerate the configure script. Usually it is best to do this during the build by depending on autoconf, libtool, and automake if it is used, and then running:

  autoreconf -i --force

 before running configure. Depending on how old the package is, this may require additional modifications to {{{configure.ac}}} or {{{configure.in}}} or other work. If you do this during the build, determine which files it will add or update and be sure to remove those files in the clean target.

 If you have fixed architecture-specific issues with minimal patches, rather than updating libtool, and verified that it builds correctly, please override this tag. Lintian will not be able to verify that.
}}}}
##END:Lintian/Tags/ancient-libtool

Self:Lintian/Tags/source-contains-prebuilt-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-prebuilt-binary.html|source-contains-prebuilt-binary]]''':<<BR>>
 The source tarball contains a prebuilt ELF object. They are usually left by mistake when generating the tarball by not cleaning the source directory first. You may want to report this as an upstream bug, in case there is no sign that this was intended.
}}}}
##END:Lintian/Tags/source-contains-prebuilt-binary

Self:Lintian/Tags/source-contains-prebuilt-windows-binary
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-contains-prebuilt-windows-binary.html|source-contains-prebuilt-windows-binary]]''':<<BR>>
 The source tarball contains a prebuilt binary for Microsoft Windows. They are usually provided for the convenience of users. These files usually just take up space in the tarball and are of no use in Debian.

 Check if upstream also provides source-only tarballs that you can use as the upstream distribution instead. If not, you may want to ask upstream to provide source-only tarballs.
}}}}
##END:Lintian/Tags/source-contains-prebuilt-windows-binary

Self:Lintian/Tags/tar-errors-from-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/tar-errors-from-source.html|tar-errors-from-source]]''':<<BR>>
 tar produced an error while unpacking this source package. This probably means there's something broken or at least strange about the way the upstream tar file was constructed. You may want to report this as an upstream bug.
}}}}
##END:Lintian/Tags/tar-errors-from-source

Self:Lintian/Tags/control-file-with-CRLF-EOLs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/control-file-with-CRLF-EOLs.html|control-file-with-CRLF-EOLs]]''':<<BR>>
 The given control file uses {{{CRLF}}} as line terminator instead of the traditional UNIX {{{LF}}} terminator. Since some tools were only designed with the UNIX end-of-line terminators in mind, it is possible that they misbehave or lead to unexpected results.

 Running the following command against the given file removes any {{{CR}}} character in the file:

 {{{sed -i 's/\r//g' path/to/file}}}
}}}}
##END:Lintian/Tags/control-file-with-CRLF-EOLs

########################################################################
== debconf ==
########################################################################

Self:Lintian/Tags/missing-debconf-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-debconf-dependency.html|missing-debconf-dependency]]''':<<BR>>
 Packages using debconf should depend on it, since debconf is not an essential package.
}}}}
##END:Lintian/Tags/missing-debconf-dependency

Self:Lintian/Tags/missing-debconf-dependency-for-preinst
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-debconf-dependency-for-preinst.html|missing-debconf-dependency-for-preinst]]''':<<BR>>
 Packages using debconf in their preinst script must pre-depend on debconf, with appropriate discussion on &debdev;. Since debconf is almost always already installed, this is normally better than depending on it and falling back to a different configuration system.
}}}}
##END:Lintian/Tags/missing-debconf-dependency-for-preinst

Self:Lintian/Tags/duplicate-fields-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-fields-in-templates.html|duplicate-fields-in-templates]]''':<<BR>>
 A template contains two identical fields (with identical values or not). This is either an error in this template, or two templates are not properly separated by a lone newline.
}}}}
##END:Lintian/Tags/duplicate-fields-in-templates

Self:Lintian/Tags/unknown-field-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-field-in-templates.html|unknown-field-in-templates]]''':<<BR>>
 Valid fields are currently "Template:", "Type:", "Choices:", "Default:", and "Description:".

Reference(s): [[|debconf-spec aen45]], [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/unknown-field-in-templates

Self:Lintian/Tags/no-template-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-template-name.html|no-template-name]]''':<<BR>>
 The templates file contains a template without a "Template:" field.
}}}}
##END:Lintian/Tags/no-template-name

Self:Lintian/Tags/malformed-template-name
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-template-name.html|malformed-template-name]]''':<<BR>>
 The "Template:" field should contain more than one component, each separated by a slash ("/"). Each component may only consist of the alphanumeric characters, "+", "-", and ".".
}}}}
##END:Lintian/Tags/malformed-template-name

Self:Lintian/Tags/no-template-type
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-template-type.html|no-template-type]]''':<<BR>>
 The templates file contains a template without a "Type:" field.
}}}}
##END:Lintian/Tags/no-template-type

Self:Lintian/Tags/unknown-template-type
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-template-type.html|unknown-template-type]]''':<<BR>>
 A "Type:" field in a templates file provided by this package uses an unknown data type. Valid types are currently "string", "boolean", "select", "multiselect", "note", "text", and "password".
}}}}
##END:Lintian/Tags/unknown-template-type

Self:Lintian/Tags/empty-translated-choices
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/empty-translated-choices.html|empty-translated-choices]]''':<<BR>>
 When the translation of a Choices: field is empty, the whole question is skipped (and nothing is selected). Please verify that the translation you're using is valid.
}}}}
##END:Lintian/Tags/empty-translated-choices

Self:Lintian/Tags/mismatch-translated-choices
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/mismatch-translated-choices.html|mismatch-translated-choices]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/mismatch-translated-choices

Self:Lintian/Tags/select-without-choices
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/select-without-choices.html|select-without-choices]]''':<<BR>>
 Templates using the "select" or "multiselect" data types must provide a "Choices:" field listing the possible values of the template.

Reference(s): [[|debconf-spec aen45]], [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/select-without-choices

Self:Lintian/Tags/boolean-template-has-bogus-default
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/boolean-template-has-bogus-default.html|boolean-template-has-bogus-default]]''':<<BR>>
 The "boolean" type in a debconf template, can have only two values: true and false. The default has been set to something different.

Reference(s): [[|debconf-spec aen45]], [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/boolean-template-has-bogus-default

Self:Lintian/Tags/no-template-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-template-description.html|no-template-description]]''':<<BR>>
 The templates file contains a template without a "Description:" field.

Reference(s): [[|debconf-spec aen45]], [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/no-template-description

Self:Lintian/Tags/duplicate-long-description-in-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-long-description-in-template.html|duplicate-long-description-in-template]]''':<<BR>>
 The long description of one of the templates provided by this package is a duplicate of the short description. If you cannot provide a good extended description, it is better to leave it blank.
}}}}
##END:Lintian/Tags/duplicate-long-description-in-template

Self:Lintian/Tags/config-does-not-load-confmodule
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/config-does-not-load-confmodule.html|config-does-not-load-confmodule]]''':<<BR>>
 The config script must load one of the debconf libraries.
}}}}
##END:Lintian/Tags/config-does-not-load-confmodule

Self:Lintian/Tags/postinst-uses-db-input
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-uses-db-input.html|postinst-uses-db-input]]''':<<BR>>
 It is generally not a good idea for postinst scripts to use debconf commands like {{{db_input}}}. Typically, they should restrict themselves to {{{db_get}}} to request previously acquired information, and have the config script do the actual prompting.
}}}}
##END:Lintian/Tags/postinst-uses-db-input

Self:Lintian/Tags/postinst-does-not-load-confmodule
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postinst-does-not-load-confmodule.html|postinst-does-not-load-confmodule]]''':<<BR>>
 Even if your postinst does not involve debconf, you currently need to make sure it loads one of the debconf libraries. This will be changed in the future.
}}}}
##END:Lintian/Tags/postinst-does-not-load-confmodule

Self:Lintian/Tags/loads-obsolete-confmodule
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/loads-obsolete-confmodule.html|loads-obsolete-confmodule]]''':<<BR>>
 The maintainer script uses an obsolete name for a debconf confmodule. Shell scripts should source {{{/usr/share/debconf/confmodule}}}, while Perl scripts should use {{{Debconf::Client::ConfModule}}}.

Reference(s): [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/loads-obsolete-confmodule

Self:Lintian/Tags/postrm-does-not-purge-debconf
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-does-not-purge-debconf.html|postrm-does-not-purge-debconf]]''':<<BR>>
 Packages using debconf should call {{{db_purge}}} or its equivalent in their postrm. If the package uses debhelper, dh_installdebconf(1) should take care of this.
}}}}
##END:Lintian/Tags/postrm-does-not-purge-debconf

Self:Lintian/Tags/isdefault-flag-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/isdefault-flag-is-deprecated.html|isdefault-flag-is-deprecated]]''':<<BR>>
 The "isdefault" flag on debconf questions is deprecated as of debconf 0.5.00, and has been replaced by "seen" with the inverse meaning. From debconf 0.5 onwards there should be very few reasons to use isdefault/seen anyway, as backing up works much better now. See /usr/share/doc/debconf-doc/changelog.gz for more information.

 The misuse of isdefault often leads to questions being asked twice in one installation run, or, worse, on every upgrade. Please test your package carefully to make sure this does not happen.
}}}}
##END:Lintian/Tags/isdefault-flag-is-deprecated

Self:Lintian/Tags/debconf-config-not-executable
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debconf-config-not-executable.html|debconf-config-not-executable]]''':<<BR>>
 The debconf "config" script in the package control area must be executable.
}}}}
##END:Lintian/Tags/debconf-config-not-executable

Self:Lintian/Tags/no-debconf-config
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-debconf-config.html|no-debconf-config]]''':<<BR>>
 The package contains a "templates" file in its control area but has no corresponding "config" script. This is occasionally OK, but is usually an error.
}}}}
##END:Lintian/Tags/no-debconf-config

Self:Lintian/Tags/no-debconf-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-debconf-templates.html|no-debconf-templates]]''':<<BR>>
 The package contains a "config" script in its control area but has no corresponding "templates" file. This is occasionally OK, but is usually an error.
}}}}
##END:Lintian/Tags/no-debconf-templates

Self:Lintian/Tags/debconf-is-not-a-registry
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debconf-is-not-a-registry.html|debconf-is-not-a-registry]]''':<<BR>>
 In the Unix tradition, Debian packages should have human-readable and human-editable configuration files. This package uses debconf commands outside its maintainer scripts, which often indicates that it is taking configuration information directly from the debconf database. Typically, packages should use debconf-supplied information to generate configuration files, and -- to avoid losing configuration information on upgrades -- should parse these configuration files in the {{{config}}} script if it is necessary to ask the user for changes.

 Some standalone programs may legitimately use debconf to prompt the user for questions. If you maintain a package containing such a program, please install an override. Other exceptions to this check include configuration scripts called from the package's post-installation script.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.1]], [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/debconf-is-not-a-registry

Self:Lintian/Tags/malformed-prompt-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-prompt-in-templates.html|malformed-prompt-in-templates]]''':<<BR>>
 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.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.4.2]]
}}}}
##END:Lintian/Tags/malformed-prompt-in-templates

Self:Lintian/Tags/malformed-title-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-title-in-templates.html|malformed-title-in-templates]]''':<<BR>>
 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.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.4.2.4]]
}}}}
##END:Lintian/Tags/malformed-title-in-templates

Self:Lintian/Tags/malformed-question-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-question-in-templates.html|malformed-question-in-templates]]''':<<BR>>
 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.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.4.2.2]]
}}}}
##END:Lintian/Tags/malformed-question-in-templates

Self:Lintian/Tags/using-question-in-extended-description-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/using-question-in-extended-description-in-templates.html|using-question-in-extended-description-in-templates]]''':<<BR>>
 The extended description of a debconf template should never include a question.

 If this template is only used internally by the package and not displayed to the user, put "for internal use" in the short description.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.3.2]]
}}}}
##END:Lintian/Tags/using-question-in-extended-description-in-templates

Self:Lintian/Tags/using-imperative-form-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/using-imperative-form-in-templates.html|using-imperative-form-in-templates]]''':<<BR>>
 Do not use useless imperative constructions such as "Please choose...", "Enter...". The interface will make it obvious that the user needs to choose or enter something.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.4.2]]
}}}}
##END:Lintian/Tags/using-imperative-form-in-templates

Self:Lintian/Tags/using-first-person-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/using-first-person-in-templates.html|using-first-person-in-templates]]''':<<BR>>
 You should avoid the use of first person ("I will do this..." or "We recommend..."). The computer is not a person and the Debconf templates do not speak for the Debian developers. You should use neutral construction and often the passive form.

 If this template is only used internally by the package and not displayed to the user, put "for internal use" in the short description.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.2.5]]
}}}}
##END:Lintian/Tags/using-first-person-in-templates

Self:Lintian/Tags/making-assumptions-about-interfaces-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/making-assumptions-about-interfaces-in-templates.html|making-assumptions-about-interfaces-in-templates]]''':<<BR>>
 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.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.2.4]]
}}}}
##END:Lintian/Tags/making-assumptions-about-interfaces-in-templates

Self:Lintian/Tags/too-long-short-description-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/too-long-short-description-in-templates.html|too-long-short-description-in-templates]]''':<<BR>>
 The short description should be kept short (50 characters or so) so that it may be accommodated by most debconf interfaces. Keeping it short also helps translators, as usually translations tend to end up being longer than the original.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.3.2]]
}}}}
##END:Lintian/Tags/too-long-short-description-in-templates

Self:Lintian/Tags/too-long-extended-description-in-templates
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/too-long-extended-description-in-templates.html|too-long-extended-description-in-templates]]''':<<BR>>
 Some debconf interfaces cannot deal very well with descriptions of more than about 20 lines, so try to keep the extended description below this limit.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 6.5.3.2]]
}}}}
##END:Lintian/Tags/too-long-extended-description-in-templates

Self:Lintian/Tags/unknown-debconf-priority
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-debconf-priority.html|unknown-debconf-priority]]''':<<BR>>
 The given maintainer script calls db_input or or db_text with a first argument that doesn't match one of the known priorities. The supported priorities are low, medium, high, and critical.

Reference(s): [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/unknown-debconf-priority

Self:Lintian/Tags/possible-debconf-note-abuse
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/possible-debconf-note-abuse.html|possible-debconf-note-abuse]]''':<<BR>>
 Debconf notes should be used only for important notes that the user really should see, since debconf will go to great pains to make sure the user sees it.

 Displaying a note with a low priority is conflicting with this statement, since using a low or medium priority shows that the note is not important.

 The right fix is NOT to increase the priority of the note, but to move it somewhere else in the inline documentation, for example in a README.Debian file for notes about package usability or NEWS.Debian for changes in the package behavior, or to simply drop it if it is not needed (e.g. "welcome" notes). Changing the templates type to "error" can also be appropriate, such as for input validation errors.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 3.9.1]]
}}}}
##END:Lintian/Tags/possible-debconf-note-abuse

Self:Lintian/Tags/select-with-boolean-choices
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/select-with-boolean-choices.html|select-with-boolean-choices]]''':<<BR>>
 Select templates with only yes and no choices should use the boolean type instead.

Reference(s): [[DebianMan:7/debconf-devel|debconf-devel(7)]]
}}}}
##END:Lintian/Tags/select-with-boolean-choices

Self:Lintian/Tags/template-uses-unsplit-choices
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/template-uses-unsplit-choices.html|template-uses-unsplit-choices]]''':<<BR>>
 The use of _Choices in templates is deprecated. An _Choices field must be translated as a single string.

 Using __Choices allows each choice to be translated separately, easing translation and is therefore recommended.

 Instead of simply replacing all occurrences of "_Choices" by "__Choices", apply the method described in po-debconf(7) under "SPLITTING CHOICES LIST", to avoid breaking existing translations.

 If in doubt, please ask for help on the debian-i18n mailing list.

Reference(s): [[DebianMan:7/po-debconf|po-debconf(7)]]
}}}}
##END:Lintian/Tags/template-uses-unsplit-choices

Self:Lintian/Tags/unused-debconf-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unused-debconf-template.html|unused-debconf-template]]''':<<BR>>
 Templates which are not used by the package should be removed from the templates file.

 This will reduce the size of the templates database and prevent translators from unnecessarily translating the template's text.

 In some cases, the template is used but Lintian is unable to determine this. Common causes are:

 - the maintainer scripts embed a variable in the template name in order to allow a template to be selected from a range of similar templates (e.g. {{{db_input low start_$service_at_boot}}})

 - the template is not used by the maintainer scripts but is used by a program in the package

 - the maintainer scripts are written in perl. lintian currently only understands the shell script debconf functions.

 If any of the above apply, please install an override.
}}}}
##END:Lintian/Tags/unused-debconf-template

########################################################################
== manpages ==
########################################################################

Self:Lintian/Tags/bad-link-to-undocumented-manpage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-link-to-undocumented-manpage.html|bad-link-to-undocumented-manpage]]''':<<BR>>
 The symbolic link should reference "{{{../man[237]/undocumented.[237].gz}}}" for manual pages in {{{/usr/share/man}}} or "{{{../../../share/man/man[237]/undocumented.[237].gz}}}" for manual pages in {{{/usr/X11R6/man}}}.
}}}}
##END:Lintian/Tags/bad-link-to-undocumented-manpage

Self:Lintian/Tags/link-to-undocumented-manpage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/link-to-undocumented-manpage.html|link-to-undocumented-manpage]]''':<<BR>>
 Symbolic links to the undocumented(7) manual page may be provided if no manual page is available, but that is deprecated.

 The lack of a manual page is still a bug, and if at all possible you should write one yourself.

 For help with writing manual pages, refer to the Man-Page-HOWTO at http://www.schweikhardt.net/man_page_howto.html, the examples created by {{{debmake}}} or {{{dh_make}}}, or the {{{/usr/share/doc/man-db/examples}}} directory. If the package provides {{{--help}}} output, you might want to use the {{{help2man}}} utility to generate a simple manual page.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/link-to-undocumented-manpage

Self:Lintian/Tags/binary-without-manpage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-without-manpage.html|binary-without-manpage]]''':<<BR>>
 Each binary in {{{/usr/bin}}}, {{{/usr/sbin}}}, {{{/bin}}}, {{{/sbin}}} or {{{/usr/games}}} should have a manual page

 Note that though the man program has the capability to check for several program names in the NAMES section, each of these programs should have its own manual page (a symbolic link to the appropriate manual page is sufficient) because other manual page viewers such as xman or tkman don't support this.

 If the name of the man page differs from the binary by case, man may be able to find it anyway; however, it is still best practice to make the case of the man page match the case of the binary.

 If the man pages are provided by another package on which this package depends, lintian may not be able to determine that man pages are available. In this case, after confirming that all binaries do have man pages after this package and its dependencies are installed, please add a lintian override.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/binary-without-manpage

Self:Lintian/Tags/manpage-in-wrong-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-in-wrong-directory.html|manpage-in-wrong-directory]]''':<<BR>>
 The manual page should be installed in the correct directory below {{{/usr/share/man/}}} or {{{/usr/share/man/locale}}}. Only sections 1 through 9 should be used.

 The section number in the filename should correspond with the section number in the directory name.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/manpage-in-wrong-directory

Self:Lintian/Tags/manpage-has-wrong-extension
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-has-wrong-extension.html|manpage-has-wrong-extension]]''':<<BR>>
 The manual page has an extension other than "section[program].gz".

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/manpage-has-wrong-extension

Self:Lintian/Tags/manpage-not-compressed
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-not-compressed.html|manpage-not-compressed]]''':<<BR>>
 Manual pages have to be installed compressed (using "{{{gzip -9}}}").

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/manpage-not-compressed

Self:Lintian/Tags/x11-games-should-be-in-usr-games
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/x11-games-should-be-in-usr-games.html|x11-games-should-be-in-usr-games]]''':<<BR>>
 Since X11 games should be installed in {{{/usr/games}}} (and not in {{{/usr/X11R6/bin}}}) and the game's manual pages should be installed in {{{/usr/share/man/man6}}}, the directory {{{/usr/X11R6/man/man6}}} should be empty.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 11.11]]
}}}}
##END:Lintian/Tags/x11-games-should-be-in-usr-games

Self:Lintian/Tags/manpage-not-compressed-with-gzip
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-not-compressed-with-gzip.html|manpage-not-compressed-with-gzip]]''':<<BR>>
 Manual pages should be compressed with {{{gzip -9}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/manpage-not-compressed-with-gzip

Self:Lintian/Tags/manpage-not-compressed-with-max-compression
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-not-compressed-with-max-compression.html|manpage-not-compressed-with-max-compression]]''':<<BR>>
 Manual pages should be compressed with {{{gzip -9}}}.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/manpage-not-compressed-with-max-compression

Self:Lintian/Tags/manpage-has-bad-whatis-entry
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-has-bad-whatis-entry.html|manpage-has-bad-whatis-entry]]''':<<BR>>
 Each manual page should start with a "NAME" section, which lists the name and a brief description of the page separated by "\-". The "NAME" section is parsed by lexgrog and used to generate a database that's queried by commands like apropos and whatis. This tag indicates that lexgrog was unable to parse the NAME section of this manual page.

 For manual pages that document multiple programs, functions, files, or other things, the part before "\-" should list each separated by a comma and a space. Each thing listed must not contain spaces; a man page for a two-part command like "fs listacl" must use something like "fs_listacl" in the "NAME" section so that it can be parsed by lexgrog.

Reference(s): [[DebianMan:1/lexgrog|lexgrog(1)]], [[DebianMan:7/groff_man|groff_man(7)]], [[DebianMan:7/groff_mdoc|groff_mdoc(7)]]
}}}}
##END:Lintian/Tags/manpage-has-bad-whatis-entry

Self:Lintian/Tags/manpage-has-useless-whatis-entry
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-has-useless-whatis-entry.html|manpage-has-useless-whatis-entry]]''':<<BR>>
 The whatis entry for this manual page (the brief description found in the NAME section) is of the form:

  program - manual page for program

 This conveys no information about what the program is for and is repetitive. The short description should contain brief information about what the program is for to aid in searching with apropos and similar programs.

 If this manpage was generated by help2man, use the -n option to provide a more meaningful description.
}}}}
##END:Lintian/Tags/manpage-has-useless-whatis-entry

Self:Lintian/Tags/manpage-is-dh_make-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-is-dh_make-template.html|manpage-is-dh_make-template]]''':<<BR>>
 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.
}}}}
##END:Lintian/Tags/manpage-is-dh_make-template

Self:Lintian/Tags/manpage-has-errors-from-man
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-has-errors-from-man.html|manpage-has-errors-from-man]]''':<<BR>>
 This man page provokes warnings or errors from man.

 "cannot adjust" or "can't break" are trouble with paragraph filling, usually related to long lines. Adjustment can be helped by left justifying, breaks can be helped with hyphenation, see "Manipulating Filling and Adjusting" and "Manipulating Hyphenation" in the manual.

 "can't find numbered character" usually means latin1 etc in the input, and this warning indicates characters will be missing from the output. You can change to escapes like \[:a] described on the groff_char man page.

 Other warnings are often formatting typos, like missing quotes around a string argument to .IP. These are likely to result in lost or malformed output. See the groff_man (or groff_mdoc if using mdoc) man page for information on macros.

 This test uses {{{man}}}'s {{{--warnings}}} option to enable groff warnings that catch common mistakes, such as putting {{{.}}} or {{{'}}} characters at the start of a line when they are intended as literal text rather than groff commands. This can be fixed either by reformatting the paragraph so that these characters are not at the start of a line, or by adding a zero-width space ({{{\&}}}) immediately before them.

 At worst, warning messages can be disabled with the .warn directive, see "Debugging" in the groff manual.

 To test this for yourself you can use the following command: LANG=en_US.UTF-8 MANWIDTH=80 man --warnings -E UTF-8 -l <file> >/dev/null
}}}}
##END:Lintian/Tags/manpage-has-errors-from-man

Self:Lintian/Tags/manpage-has-errors-from-pod2man
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-has-errors-from-pod2man.html|manpage-has-errors-from-pod2man]]''':<<BR>>
 This man page contains a section "POD ERRORS" generated by pod2man. This sections lists errors in the POD syntax found by pod2man during the generation of the man page.
}}}}
##END:Lintian/Tags/manpage-has-errors-from-pod2man

Self:Lintian/Tags/manpage-for-x11-binary-in-wrong-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-for-x11-binary-in-wrong-directory.html|manpage-for-x11-binary-in-wrong-directory]]''':<<BR>>
 Manual pages for binaries which are located in {{{/usr/X11R6/bin}}} should be installed below {{{/usr/X11R6/man}}}.

 Note that normally only packages that are part of X itself and those that are using some arcane Imakefiles should actually install binaries into {{{/usr/X11R6/bin}}}.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs usrsharemanmanualpages]]
}}}}
##END:Lintian/Tags/manpage-for-x11-binary-in-wrong-directory

Self:Lintian/Tags/manpage-for-non-x11-binary-in-wrong-directory
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-for-non-x11-binary-in-wrong-directory.html|manpage-for-non-x11-binary-in-wrong-directory]]''':<<BR>>
 Manual pages for binaries that are not located in {{{/usr/X11R6/bin}}} should not be installed below {{{/usr/X11R6/man}}}, but below {{{/usr/share/man}}}.

 Note that moving a binary into {{{/usr/X11R6/bin}}} is almost never the proper solution for this problem; move the manual page instead.

Reference(s): [[http://www.debian.org/doc/packaging-manuals/fhs/|fhs usrsharemanmanualpages]]
}}}}
##END:Lintian/Tags/manpage-for-non-x11-binary-in-wrong-directory

Self:Lintian/Tags/bad-so-link-within-manual-page
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/bad-so-link-within-manual-page.html|bad-so-link-within-manual-page]]''':<<BR>>
 Manual files that use the .so links to include other pages should only point to a path relative to the top-level manual hierarchy, e.g.

 {{{.so man3/boo.1.gz}}}
}}}}
##END:Lintian/Tags/bad-so-link-within-manual-page

Self:Lintian/Tags/empty-manual-page
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/empty-manual-page.html|empty-manual-page]]''':<<BR>>
 The referenced manual page is empty.
}}}}
##END:Lintian/Tags/empty-manual-page

Self:Lintian/Tags/manpage-section-mismatch
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-section-mismatch.html|manpage-section-mismatch]]''':<<BR>>
 A man page usually should contain a {{{.TH}}} header, specifying the section. The section in this manpage doesn't match with the section in the filename.

Reference(s): [[DebianMan:7/groff_man|groff_man(7)]], [[DebianMan:1/man|man(1)]]
}}}}
##END:Lintian/Tags/manpage-section-mismatch

Self:Lintian/Tags/hyphen-used-as-minus-sign
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/hyphen-used-as-minus-sign.html|hyphen-used-as-minus-sign]]''':<<BR>>
 This manual page seems to contain a hyphen where a minus sign was intended. By default, "-" chars are interpreted as hyphens (U+2010) by groff, not as minus signs (U+002D). Since options to programs use minus signs (U+002D), this means for example in UTF-8 locales that you cannot cut and paste options, nor search for them easily. The Debian groff package currently forces "-" to be interpreted as a minus sign due to the number of manual pages with this problem, but this is a Debian-specific modification and hopefully eventually can be removed.

 "-" must be escaped ("\-") to be interpreted as minus. If you really intend a hyphen (normally you don't), write it as "\(hy" to emphasise that fact. See groff(7) and especially groff_char(7) for details, and also the thread starting with http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.html

 If you use some tool that converts your documentation to groff format, this tag may indicate a bug in the tool. Some tools convert dashes of any kind to hyphens. The safe way of converting dashes is to convert them to "\-".

 Because this error can occur <em>very</em> often, Lintian shows only the first 10 occurrences for each man page and give the number of suppressed occurrences. If you want to see all warnings, run Lintian with the -d/--debug option.

Reference(s): /usr/share/doc/groff-base/README.Debian, [[DebianMan:7/groff_char|groff_char(7)]]
}}}}
##END:Lintian/Tags/hyphen-used-as-minus-sign

Self:Lintian/Tags/FSSTND-dir-in-manual-page
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/FSSTND-dir-in-manual-page.html|FSSTND-dir-in-manual-page]]''':<<BR>>
 The manual page references a directory that is specified in the FSSTND but not in the FHS which is used by Debian. This can be an indicator of a mismatch of the location of files as installed for Debian and as described by the man page.

 If you have to change file locations to abide by Debian Policy please also patch the man page to mention these new locations.
}}}}
##END:Lintian/Tags/FSSTND-dir-in-manual-page

Self:Lintian/Tags/binary-without-english-manpage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-without-english-manpage.html|binary-without-english-manpage]]''':<<BR>>
 Each binary in {{{/usr/bin}}}, {{{/usr/sbin}}}, {{{/bin}}}, {{{/sbin}}} or {{{/usr/games}}} should have a manual page. You don't provide an english, only a translated manpage. Since english is fallback, shipping only a non-english man page leaves most users without a man page at all.
}}}}
##END:Lintian/Tags/binary-without-english-manpage

Self:Lintian/Tags/manpage-locale-dir-country-specific
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/manpage-locale-dir-country-specific.html|manpage-locale-dir-country-specific]]''':<<BR>>
 This package installs a manual page in a locale directory that includes the country name. A country name should not be included in the directory name unless it indicates a significant difference in the language. The known cases where country names are appropriate are pt_BR and zh_*. Please file a bug against Lintian if this is another case where a country name is appropriate.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 12.1]]
}}}}
##END:Lintian/Tags/manpage-locale-dir-country-specific

Self:Lintian/Tags/spelling-error-in-manpage
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-manpage.html|spelling-error-in-manpage]]''':<<BR>>
 Lintian found a spelling error in the manpage. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does.

 If the string containing the spelling error is translated with the help of gettext (with the help of po4a, for example) or a similar tool, please fix the error in the translations as well as the English text to avoid making the translations fuzzy. With gettext, for example, this means you should also fix the spelling mistake in the corresponding msgids in the *.po files.
}}}}
##END:Lintian/Tags/spelling-error-in-manpage

########################################################################
== version-substvars ==
########################################################################

Self:Lintian/Tags/not-binnmuable-any-depends-any
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/not-binnmuable-any-depends-any.html|not-binnmuable-any-depends-any]]''':<<BR>>
 The package is not safely binNMUable because an arch:any package depends on another arch:any package with a (= ${source:Version}) relationship. Please use (= ${binary:Version}) instead.
}}}}
##END:Lintian/Tags/not-binnmuable-any-depends-any

Self:Lintian/Tags/not-binnmuable-any-depends-all
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/not-binnmuable-any-depends-all.html|not-binnmuable-any-depends-all]]''':<<BR>>
 The package is not safely binNMUable because an arch:any package depends on an arch:all package with a (= ${Source-Version}) or (= ${binary:Version}) relationship. Please use (= ${source:Version}) instead.
}}}}
##END:Lintian/Tags/not-binnmuable-any-depends-all

Self:Lintian/Tags/not-binnmuable-all-depends-any
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/not-binnmuable-all-depends-any.html|not-binnmuable-all-depends-any]]''':<<BR>>
 The package is not safely binNMUable because an arch:all package depends on an arch:any package with a strict (= ${Source-Version}), or similar, relationship.

 It is not possible for arch:all packages to depend so strictly on arch:any packages while having the package binNMUable, so please use one of these, whichever is more appropriate:

   Depends: arch_any (>= ${source:Version}) Depends: arch_any (>= ${source:Version}), arch_any (<< ${source:Version}.1~)
}}}}
##END:Lintian/Tags/not-binnmuable-all-depends-any

Self:Lintian/Tags/version-substvar-for-external-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/version-substvar-for-external-package.html|version-substvar-for-external-package]]''':<<BR>>
 The first package has a dependency on the second package that uses (= ${binary:Version}), (= ${source:Version}), or (= ${Source-Version}), but the second package is not built from this source package. Usually this means there is a mistake in the package name in this dependency.
}}}}
##END:Lintian/Tags/version-substvar-for-external-package

Self:Lintian/Tags/substvar-source-version-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/substvar-source-version-is-deprecated.html|substvar-source-version-is-deprecated]]''':<<BR>>
 The package uses the now deprecated ${Source-Version} substvar, which has misleading semantics. Please switch to ${binary:Version} or ${source:Version} as appropriate (introduced in dpkg 1.13.19, released with etch). Support for ${Source-Version} may be removed from dpkg-dev in the future.
}}}}
##END:Lintian/Tags/substvar-source-version-is-deprecated

########################################################################
== watch-file ==
########################################################################

Self:Lintian/Tags/debian-watch-file-is-missing
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-is-missing.html|debian-watch-file-is-missing]]''':<<BR>>
 This source package is not Debian-native but it does not have a {{{debian/watch}}} file. This file is used for automatic detection of new upstream versions by the Debian External Health Status project and other project infrastructure. If this package is maintained upstream, please consider adding a {{{debian/watch}}} file to detect new releases.

 If the package is not maintained upstream or if upstream uses a distribution mechanism that cannot be meaningfully monitored by uscan and the Debian External Health Status project, please consider adding a {{{debian/watch}}} file containing only comments documenting the situation.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.11]], [[DebianMan:1/uscan|uscan(1)]]
}}}}
##END:Lintian/Tags/debian-watch-file-is-missing

Self:Lintian/Tags/debian-watch-file-declares-multiple-versions
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-declares-multiple-versions.html|debian-watch-file-declares-multiple-versions]]''':<<BR>>
 The {{{debian/watch}}} file in this package contains multiple lines starting with {{{version=}}}. There should be only one version declaration in a watch file, on the first non-comment line of the file.

Reference(s): [[DebianMan:1/uscan|uscan(1)]]
}}}}
##END:Lintian/Tags/debian-watch-file-declares-multiple-versions

Self:Lintian/Tags/debian-watch-file-unknown-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-unknown-version.html|debian-watch-file-unknown-version]]''':<<BR>>
 The {{{version=}}} line in the {{{debian/watch}}} file in this package declares an unknown version. The currently known watch file versions are 2 and 3.

Reference(s): [[DebianMan:1/uscan|uscan(1)]]
}}}}
##END:Lintian/Tags/debian-watch-file-unknown-version

Self:Lintian/Tags/debian-watch-file-missing-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-missing-version.html|debian-watch-file-missing-version]]''':<<BR>>
 The {{{debian/watch}}} file in this package doesn't start a {{{version=}}} line. The first non-comment line of {{{debian/watch}}} should be a {{{version=}}} declaration. This may mean that this is an old version one watch file that should be updated to the current version.

Reference(s): [[DebianMan:1/uscan|uscan(1)]]
}}}}
##END:Lintian/Tags/debian-watch-file-missing-version

Self:Lintian/Tags/debian-watch-file-should-mangle-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-should-mangle-version.html|debian-watch-file-should-mangle-version]]''':<<BR>>
 The version of this package contains {{{dfsg}}}, {{{ds}}}, or {{{debian}}}, which normally indicates that the upstream source has been repackaged to comply with the Debian Free Software Guidelines (or similar reason), but there is no version mangling in the {{{debian/watch}}} file. Since the {{{dfsg}}} string is not part of the upstream version, the {{{debian/watch}}} file should use the dversionmangle option to remove the {{{dfsg}}} before version number comparison.

Reference(s): [[DebianMan:1/uscan|uscan(1)]], [[http://wiki.debian.org/DEHS]]
}}}}
##END:Lintian/Tags/debian-watch-file-should-mangle-version

Self:Lintian/Tags/debian-watch-file-should-dversionmangle-not-uversionmangle
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-should-dversionmangle-not-uversionmangle.html|debian-watch-file-should-dversionmangle-not-uversionmangle]]''':<<BR>>
 The version of this package contains {{{dfsg}}}, {{{ds}}}, or {{{debian}}}, but a misleading upstream version mangling occurs in the {{{debian/watch}}} file. Since the {{{dfsg}}} string is not part of the upstream version and its addition is Debian-specific, the the {{{debian/watch}}} file should use the dversionmangle option to remove, instead of adding in uversionmangle, the {{{dfsg}}} before comparing version numbers.

Reference(s): [[http://wiki.debian.org/DEHS]]
}}}}
##END:Lintian/Tags/debian-watch-file-should-dversionmangle-not-uversionmangle

Self:Lintian/Tags/debian-watch-file-should-uversionmangle-not-dversionmangle
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-should-uversionmangle-not-dversionmangle.html|debian-watch-file-should-uversionmangle-not-dversionmangle]]''':<<BR>>
 The version of this package contains {{{alpha}}}, {{{beta}}}, or {{{rc}}}, but a misleading Debian version mangling occurs in the {{{debian/watch}}} file. You should use the uversionmangle option instead of dversionmangle so that the prerelease is sorted by uscan before a possible future final release.

Reference(s): [[http://wiki.debian.org/DEHS]]
}}}}
##END:Lintian/Tags/debian-watch-file-should-uversionmangle-not-dversionmangle

Self:Lintian/Tags/debian-watch-file-in-native-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-in-native-package.html|debian-watch-file-in-native-package]]''':<<BR>>
 The package ships a watch file although it is a Debian native package. DEHS does not process watch files in native packages based on the reasoning that native packages do not have upstreams to check for new releases.

Reference(s): [[http://wiki.debian.org/DEHS]]
}}}}
##END:Lintian/Tags/debian-watch-file-in-native-package

Self:Lintian/Tags/debian-watch-file-uses-deprecated-sf-redirector-method
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-uses-deprecated-sf-redirector-method.html|debian-watch-file-uses-deprecated-sf-redirector-method]]''':<<BR>>
 The watch file seems to be passing arguments to the redirector other than a path. Calling the SourceForge redirector with parameters like {{{project}}} prevents uscan from generating working URIs to the files and thus has been deprecated and is no longer supported by the redirector.
}}}}
##END:Lintian/Tags/debian-watch-file-uses-deprecated-sf-redirector-method

Self:Lintian/Tags/debian-watch-file-should-use-sf-redirector
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-should-use-sf-redirector.html|debian-watch-file-should-use-sf-redirector]]''':<<BR>>
 The watch file specifies a SourceForge download server directly. This is not recommended; SourceForge changes their download servers periodically, requiring watch files to be modified every time. Instead, use the qa.debian.org redirector by using the magic URL:

   http://sf.net/<project>/<tar-name>-(.+)\.tar\.gz

 replacing {{{<project>}}} with the name of the SourceForge project and {{{<tar-name>}}} with the name of the tarball distributed within that project.

Reference(s): [[DebianMan:1/uscan|uscan(1)]]
}}}}
##END:Lintian/Tags/debian-watch-file-should-use-sf-redirector

Self:Lintian/Tags/debian-watch-file-specifies-wrong-upstream-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-specifies-wrong-upstream-version.html|debian-watch-file-specifies-wrong-upstream-version]]''':<<BR>>
 The watch file specifies an upstream version which exactly matches the version of a {{{debian/changelog}}} entry, this is not a native package, and no version mangling is being done. The version field in a watch file should specify the expected upstream version, not the version of the Debian package. Any epochs and Debian revisions should be removed first or mangled away.

Reference(s): [[DebianMan:1/uscan|uscan(1)]]
}}}}
##END:Lintian/Tags/debian-watch-file-specifies-wrong-upstream-version

Self:Lintian/Tags/debian-watch-file-specifies-old-upstream-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-watch-file-specifies-old-upstream-version.html|debian-watch-file-specifies-old-upstream-version]]''':<<BR>>
 The watch file specifies an upstream version number which matches the upstream portion of an old {{{debian/changelog}}} entry, and the current {{{debian/changelog}}} entry specifies a newer upstream version. The version number in the watch file is very likely to be incorrect and probably should be replaced with the current expected upstream version. Otherwise, DEHS and similar projects will think the package is out of date even when it may not be.
}}}}
##END:Lintian/Tags/debian-watch-file-specifies-old-upstream-version

########################################################################
== rules ==
########################################################################

Self:Lintian/Tags/debian-rules-is-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-is-symlink.html|debian-rules-is-symlink]]''':<<BR>>
 The file {{{debian/rules}}} is a symlink instead of a regular file. This is unnecessary and makes package checking and manipulation more difficult. If the rules file should be available in the source package under multiple names, make {{{debian/rules}}} the real file and the other names symlinks to it.

 This problem may have prevented lintian from performing other checks, leading to undetected changelog errors.
}}}}
##END:Lintian/Tags/debian-rules-is-symlink

Self:Lintian/Tags/debian-rules-not-a-makefile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-not-a-makefile.html|debian-rules-not-a-makefile]]''':<<BR>>
 The {{{debian/rules}}} file for this package does not appear to be a makefile or does not start with the required line. {{{debian/rules}}} must be a valid makefile and must have "{{{#!/usr/bin/make -f}}}" as its first line.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.9]]
}}}}
##END:Lintian/Tags/debian-rules-not-a-makefile

Self:Lintian/Tags/debian-rules-missing-required-target
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-missing-required-target.html|debian-rules-missing-required-target]]''':<<BR>>
 The {{{debian/rules}}} file for this package does not provide one of the required targets. All of build, binary, binary-arch, binary-indep, and clean must be provided, even if they don't do anything for this package.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.9]]
}}}}
##END:Lintian/Tags/debian-rules-missing-required-target

Self:Lintian/Tags/debian-rules-uses-pwd
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-uses-pwd.html|debian-rules-uses-pwd]]''':<<BR>>
 The {{{debian/rules}}} file for this package appears to use the variable $(PWD) to refer to the current directory. This variable is not set by GNU make and therefore will have whatever value it has in the environment, which may not be the actual current directory. Some ways of building Debian packages (such as through sudo) will clear the PWD environment variable.

 Instead of $(PWD), use $(CURDIR), which is set by GNU make, ignores the environment, and is guaranteed to always be set.
}}}}
##END:Lintian/Tags/debian-rules-uses-pwd

Self:Lintian/Tags/debian-rules-ignores-make-clean-error
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-ignores-make-clean-error.html|debian-rules-ignores-make-clean-error]]''':<<BR>>
 A rule in the {{{debian/rules}}} file for this package calls the package's clean or distclean target with a line like:

  -$(MAKE) distclean or $(MAKE) -i distclean

 The leading "-" or the option -i tells make to ignore all errors. Normally this is done for packages using Autoconf since Makefile may not exist. However, this line ignores all other error messages, not just the missing Makefile error. It's better to use:

  [ ! -f Makefile ] || $(MAKE) distclean

 so that other error messages from the clean or distclean rule will still be caught (or just remove the "-" if the package uses a static makefile).
}}}}
##END:Lintian/Tags/debian-rules-ignores-make-clean-error

Self:Lintian/Tags/debian-rules-uses-DEB_BUILD_OPTS
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-uses-DEB_BUILD_OPTS.html|debian-rules-uses-DEB_BUILD_OPTS]]''':<<BR>>
 The standard environment variable for build options is DEB_BUILD_OPTIONS. Usually, referring to DEB_BUILD_OPTS is a mistake and DEB_BUILD_OPTIONS was intended instead.
}}}}
##END:Lintian/Tags/debian-rules-uses-DEB_BUILD_OPTS

Self:Lintian/Tags/debian-rules-automatically-updates-control
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-automatically-updates-control.html|debian-rules-automatically-updates-control]]''':<<BR>>
 DEB_AUTO_UPDATE_DEBIAN_CONTROL appears to be set to {{{yes}}} in the {{{debian/rules}}} file. This activates a feature of CDBS which may not be used in packages uploaded to the Debian archive.

Reference(s): [[http://ftp-master.debian.org/REJECT-FAQ.html]]
}}}}
##END:Lintian/Tags/debian-rules-automatically-updates-control

Self:Lintian/Tags/debian-rules-sets-DH_COMPAT
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-sets-DH_COMPAT.html|debian-rules-sets-DH_COMPAT]]''':<<BR>>
 As of debhelper version 4, the DH_COMPAT environment variable is only to be used for temporarily overriding {{{debian/compat}}}. Any line in {{{debian/rules}}} that sets it globally should be deleted and a separate {{{debian/compat}}} file created if needed.

Reference(s): [[DebianMan:7/debhelper|debhelper(7)]]
}}}}
##END:Lintian/Tags/debian-rules-sets-DH_COMPAT

Self:Lintian/Tags/binary-arch-rules-but-pkg-is-arch-indep
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/binary-arch-rules-but-pkg-is-arch-indep.html|binary-arch-rules-but-pkg-is-arch-indep]]''':<<BR>>
 It looks like you try to run code in the binary-arch target of {{{debian/rules}}}, even though your package is architecture- independent.
}}}}
##END:Lintian/Tags/binary-arch-rules-but-pkg-is-arch-indep

Self:Lintian/Tags/debian-rules-calls-debhelper-in-odd-order
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-calls-debhelper-in-odd-order.html|debian-rules-calls-debhelper-in-odd-order]]''':<<BR>>
 One of the targets in the {{{debian/rules}}} file for this package calls debhelper programs in an odd order. Normally, dh_makeshlibs should be run before dh_shlibdeps or dh_installdeb, and dh_shlibdeps should be run before dh_gencontrol. dh_builddeb should be the last debhelper action when building the package, after any of the other programs mentioned. Calling these programs in the wrong order may cause incorrect or missing package files and metadata.
}}}}
##END:Lintian/Tags/debian-rules-calls-debhelper-in-odd-order

Self:Lintian/Tags/missing-build-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-build-dependency.html|missing-build-dependency]]''':<<BR>>
 The package doesn't specify a build dependency on a package that is used in {{{debian/rules}}}.

 lintian intentionally does not take into account transitive dependencies. Even if the package build-depends on some package that in turn depends on the needed package, an explicit build dependency should be added. Otherwise, a latent bug is created that will appear without warning if the other package is ever updated to change its dependencies. Even if this seems unlikely, please always add explicit build dependencies on every non-essential, non-build-essential package that is used directly during the build.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.2]]
}}}}
##END:Lintian/Tags/missing-build-dependency

Self:Lintian/Tags/missing-python-build-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-python-build-dependency.html|missing-python-build-dependency]]''':<<BR>>
 The package appears to use Python as part of its build process in {{{debian/rules}}} but doesn't depend on Python.

 Normally, packages that use Python as part of the build process should build-depend on one of python, python-all, python-dev, or python-all-dev depending on whether they support multiple versions of Python and whether they're building modules or only using Python as part of the package build process. Packages that depend on a specific version of Python may build-depend on the appropriate pythonX.Y or pythonX.Y-dev package instead.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 4.2]]
}}}}
##END:Lintian/Tags/missing-python-build-dependency

Self:Lintian/Tags/missing-dh_python-build-dependency
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-dh_python-build-dependency.html|missing-dh_python-build-dependency]]''':<<BR>>
 The package runs dh_python in {{{debian/rules}}} but doesn't build-depend on python or python-dev. dh_python requires {{{/usr/bin/python}}} to run, so packages using dh_python must build-depend on python (or python-dev or python-all-dev, which in turn depend on python), even if they don't otherwise need Python to build.

Reference(s): [[DebianMan:1/dh_python|dh_python(1)]]
}}}}
##END:Lintian/Tags/missing-dh_python-build-dependency

Self:Lintian/Tags/clean-should-be-satisfied-by-build-depends
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/clean-should-be-satisfied-by-build-depends.html|clean-should-be-satisfied-by-build-depends]]''':<<BR>>
 The specified package is required to run the clean target of {{{debian/rules}}} and therefore must be listed in Build-Depends, not Build-Depends-Indep, even if no architecture-dependent packages are built.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 7.7]]
}}}}
##END:Lintian/Tags/clean-should-be-satisfied-by-build-depends

Self:Lintian/Tags/debian-rules-makemaker-prefix-is-deprecated
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/debian-rules-makemaker-prefix-is-deprecated.html|debian-rules-makemaker-prefix-is-deprecated]]''':<<BR>>
 The package appears to use an {{{ExtUtils::MakeMaker}}} (Makefile.PL) build system and sets the temporary installation path by overriding {{{PREFIX}}} when calling {{{make install}}}. This only works because of a Debian-specific change to {{{ExtUtils::MakeMaker}}} that the maintainers of the Debian perl package intend to remove.

 The correct way to set the installation directory is with DESTDIR. Setting PREFIX should not be necessary at all.

 For example, the line make install PREFIX=$(TMP)/usr # WRONG should be replaced with make install DESTDIR=$(TMP) # RIGHT

Reference(s): [[http://www.debian.org/doc/packaging-manuals/perl-policy/|perl-policy 4.3]]
}}}}
##END:Lintian/Tags/debian-rules-makemaker-prefix-is-deprecated

########################################################################
== debian-source-dir ==
########################################################################

Self:Lintian/Tags/missing-debian-source-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/missing-debian-source-format.html|missing-debian-source-format]]''':<<BR>>
 Explicitly selecting a source format by putting the format in {{{debian/source/format}}} 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.

Reference(s): [[DebianMan:1/dpkg-source|dpkg-source(1)]], [[http://wiki.debian.org/Projects/DebSrc3.0]]
}}}}
##END:Lintian/Tags/missing-debian-source-format

Self:Lintian/Tags/unknown-source-format
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-source-format.html|unknown-source-format]]''':<<BR>>
 {{{debian/source/format}}} contains an unknown source format. The formats officially supported by Debian are "3.0 (quilt)", "3.0 (native)" and "1.0". dpkg-source additionnaly supports "2.0", "3.0 (git)" and "3.0 (bzr)".

Reference(s): [[DebianMan:1/dpkg-source|dpkg-source(1)]]
}}}}
##END:Lintian/Tags/unknown-source-format

Self:Lintian/Tags/unknown-file-in-debian-source
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unknown-file-in-debian-source.html|unknown-file-in-debian-source]]''':<<BR>>
 The source package contains a file in debian/source/ that lintian doesn't know about. Currently the following files are recognized:

  * format * include-binaries * lintian-overrides * options * patch-header

 This tag is emitted in case you mistyped the name of one of the above files. If that's not the case and if the file can be legitimately be expected in source packages, please file a bug against lintian asking for the file to be recognized.
}}}}
##END:Lintian/Tags/unknown-file-in-debian-source

########################################################################
== standards-version ==
########################################################################

Self:Lintian/Tags/no-standards-version-field
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/no-standards-version-field.html|no-standards-version-field]]''':<<BR>>
 The source package does not have a Standards-Version control field. Please update your package to latest Policy and set this control field appropriately.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 5.6.11]]
}}}}
##END:Lintian/Tags/no-standards-version-field

Self:Lintian/Tags/invalid-standards-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/invalid-standards-version.html|invalid-standards-version]]''':<<BR>>
 The source package refers to a Standards-Version which never existed. Please update your package to latest Policy and set this control field appropriately.
}}}}
##END:Lintian/Tags/invalid-standards-version

Self:Lintian/Tags/newer-standards-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/newer-standards-version.html|newer-standards-version]]''':<<BR>>
 The source package refers to a Standards-Version which is newer than the highest one lintian is programmed to check. If the source package is correct, then please upgrade lintian to the newest version. (If there is no newer lintian version, then please bug &maint; to make one.)
}}}}
##END:Lintian/Tags/newer-standards-version

Self:Lintian/Tags/ancient-standards-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ancient-standards-version.html|ancient-standards-version]]''':<<BR>>
 The source package refers to a Standards-Version that has been obsolete for more than two years. Please update your package to latest Policy and set this control field appropriately.

 If the package is already compliant with the current standards, you don't have to re-upload the package just to adjust the Standards-Version control field. However, please remember to update this field next time you upload the package.

 See {{{/usr/share/doc/debian-policy/upgrading-checklist.txt.gz}}} in the debian-policy package for a summary of changes in newer versions of Policy.
}}}}
##END:Lintian/Tags/ancient-standards-version

Self:Lintian/Tags/out-of-date-standards-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/out-of-date-standards-version.html|out-of-date-standards-version]]''':<<BR>>
 The source package refers to a Standards-Version older than the one that was current at the time the package was created (according to the timestamp of the latest {{{debian/changelog}}} entry). Please consider updating the package to current Policy and setting this control field appropriately.

 If the package is already compliant with the current standards, you don't have to re-upload the package just to adjust the Standards-Version control field. However, please remember to update this field next time you upload the package.

 See {{{/usr/share/doc/debian-policy/upgrading-checklist.txt.gz}}} in the debian-policy package for a summary of changes in newer versions of Policy.
}}}}
##END:Lintian/Tags/out-of-date-standards-version

Self:Lintian/Tags/timewarp-standards-version
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/timewarp-standards-version.html|timewarp-standards-version]]''':<<BR>>
 The source package refers to a Standards-Version that was released after the date of the most recent {{{debian/changelog}}} entry. Perhaps you forgot to update the timestamp in {{{debian/changelog}}} before building the package?
}}}}
##END:Lintian/Tags/timewarp-standards-version

########################################################################
== debian-readme ==
########################################################################

Self:Lintian/Tags/readme-debian-mentions-usr-doc
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/readme-debian-mentions-usr-doc.html|readme-debian-mentions-usr-doc]]''':<<BR>>
 The README.Debian file installed by this package apparently points users at /usr/doc. /usr/doc has been retired and all documentation migrated to /usr/share/doc. This reference should probably also be updated.
}}}}
##END:Lintian/Tags/readme-debian-mentions-usr-doc

Self:Lintian/Tags/readme-debian-contains-debmake-template
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/readme-debian-contains-debmake-template.html|readme-debian-contains-debmake-template]]''':<<BR>>
 The README.Debian file installed by this package contains one of the template phrases from the README.Debian provided by deb-make or dh_make:

  Comments regarding the package So far nothing to say <possible notes regarding this package - if none, delete this file>

 If there is real information in the file, please delete any generic template phrases. If there is nothing to say in the file, it is best removed.
}}}}
##END:Lintian/Tags/readme-debian-contains-debmake-template

Self:Lintian/Tags/readme-debian-contains-debmake-default-email-address
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/readme-debian-contains-debmake-default-email-address.html|readme-debian-contains-debmake-default-email-address]]''':<<BR>>
 The README.Debian file contains an email address (<..@unknown>) that was not updated to the maintainer's real address.
}}}}
##END:Lintian/Tags/readme-debian-contains-debmake-default-email-address

Self:Lintian/Tags/spelling-error-in-readme-debian
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/spelling-error-in-readme-debian.html|spelling-error-in-readme-debian]]''':<<BR>>
 Lintian found a spelling error in the README.Debian file. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does.
}}}}
##END:Lintian/Tags/spelling-error-in-readme-debian

########################################################################
== ocaml ==
########################################################################

Self:Lintian/Tags/ocaml-dangling-cmxa
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-dangling-cmxa.html|ocaml-dangling-cmxa]]''':<<BR>>
 This package provides a {{{.cmxa}}} library without its implementation ({{{.a}}} static library).
}}}}
##END:Lintian/Tags/ocaml-dangling-cmxa

Self:Lintian/Tags/ocaml-dangling-cmx
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-dangling-cmx.html|ocaml-dangling-cmx]]''':<<BR>>
 This package provides a {{{.cmx}}} module without its implementation ({{{.o}}} object file which may be embedded in a {{{.a}}} static library installed in the same directory).
}}}}
##END:Lintian/Tags/ocaml-dangling-cmx

Self:Lintian/Tags/ocaml-dangling-cmxs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-dangling-cmxs.html|ocaml-dangling-cmxs]]''':<<BR>>
 This package seems to be a library package, and provides a native plugin ({{{.cmxs}}}). If the plugin is meant to be used as a library for other plugins, it should be shipped as bytecode ({{{.cma}}} or {{{.cmo}}}) as well.
}}}}
##END:Lintian/Tags/ocaml-dangling-cmxs

Self:Lintian/Tags/ocaml-dev-file-not-in-usr-lib-ocaml
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-dev-file-not-in-usr-lib-ocaml.html|ocaml-dev-file-not-in-usr-lib-ocaml]]''':<<BR>>
 This development package installs OCaml development files ({{{.cmi}}}, {{{.cmx}}} or {{{.cmxa}}}) outside {{{/usr/lib/ocaml}}}. Such files are used only by compilation and should be in a subdirectory of OCaml standard library path.
}}}}
##END:Lintian/Tags/ocaml-dev-file-not-in-usr-lib-ocaml

Self:Lintian/Tags/ocaml-stray-cmo
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-stray-cmo.html|ocaml-stray-cmo]]''':<<BR>>
 This package installs a {{{.cma}}} file and a {{{.cmo}}} file with the same base name. Most of the time, the module provided by the {{{.cmo}}} file is also linked in the {{{.cma}}} file, so the {{{.cmo}}} file is useless.
}}}}
##END:Lintian/Tags/ocaml-stray-cmo

Self:Lintian/Tags/ocaml-dangling-cmi
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-dangling-cmi.html|ocaml-dangling-cmi]]''':<<BR>>
 This package installs a compiled interface ({{{.cmi}}}) without its text version ({{{.mli}}}). The text version should also be installed for documentation purpose. If the module involved doesn't have a {{{.mli}}}, its source code ({{{.ml}}}) should be installed instead.
}}}}
##END:Lintian/Tags/ocaml-dangling-cmi

Self:Lintian/Tags/ocaml-dev-file-in-nondev-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-dev-file-in-nondev-package.html|ocaml-dev-file-in-nondev-package]]''':<<BR>>
 This package doesn't appear to be a development package, but installs OCaml development files ({{{.cmi}}}, {{{.cmx}}} or {{{.cmxa}}}). These files should be moved to a development package.
}}}}
##END:Lintian/Tags/ocaml-dev-file-in-nondev-package

Self:Lintian/Tags/ocaml-meta-without-suggesting-findlib
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/ocaml-meta-without-suggesting-findlib.html|ocaml-meta-without-suggesting-findlib]]''':<<BR>>
 This development package installs a META file but doesn't depend on ocaml-findlib. Libraries with META file are easier to use with findlib. The package should at least suggest ocaml-findlib.
}}}}
##END:Lintian/Tags/ocaml-meta-without-suggesting-findlib

########################################################################
== init ==
########################################################################

Self:Lintian/Tags/duplicate-updaterc.d-calls-in-postinst
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-updaterc.d-calls-in-postinst.html|duplicate-updaterc.d-calls-in-postinst]]''':<<BR>>
 The {{{postinst}}} script calls {{{update-rc.d}}} several times for the same {{{/etc/init.d}}} script.
}}}}
##END:Lintian/Tags/duplicate-updaterc.d-calls-in-postinst

Self:Lintian/Tags/output-of-updaterc.d-not-redirected-to-dev-null
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/output-of-updaterc.d-not-redirected-to-dev-null.html|output-of-updaterc.d-not-redirected-to-dev-null]]''':<<BR>>
 The output messages of the {{{update-rc.d}}} command should be redirected to {{{/dev/null}}} because it is currently very chatty per default.
}}}}
##END:Lintian/Tags/output-of-updaterc.d-not-redirected-to-dev-null

Self:Lintian/Tags/preinst-calls-updaterc.d
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/preinst-calls-updaterc.d.html|preinst-calls-updaterc.d]]''':<<BR>>
 The {{{preinst}}} package calls {{{update-rc.d}}}. Instead, you should call it in the {{{postinst}}} script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.1]]
}}}}
##END:Lintian/Tags/preinst-calls-updaterc.d

Self:Lintian/Tags/duplicate-updaterc.d-calls-in-postrm
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/duplicate-updaterc.d-calls-in-postrm.html|duplicate-updaterc.d-calls-in-postrm]]''':<<BR>>
 The {{{postrm}}} script calls {{{update-rc.d}}} several times for the same {{{/etc/init.d}}} script.
}}}}
##END:Lintian/Tags/duplicate-updaterc.d-calls-in-postrm

Self:Lintian/Tags/prerm-calls-updaterc.d
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/prerm-calls-updaterc.d.html|prerm-calls-updaterc.d]]''':<<BR>>
 The {{{prerm}}} package calls {{{update-rc.d}}}. Instead, you should call it in the {{{postrm}}} script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.1]]
}}}}
##END:Lintian/Tags/prerm-calls-updaterc.d

Self:Lintian/Tags/postrm-does-not-call-updaterc.d-for-init.d-script
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-does-not-call-updaterc.d-for-init.d-script.html|postrm-does-not-call-updaterc.d-for-init.d-script]]''':<<BR>>
 An {{{/etc/init.d}}} script which has been registered in the {{{postinst}}} script is not de-registered in the {{{postrm}}} script.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.1]]
}}}}
##END:Lintian/Tags/postrm-does-not-call-updaterc.d-for-init.d-script

Self:Lintian/Tags/postrm-contains-additional-updaterc.d-calls
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/postrm-contains-additional-updaterc.d-calls.html|postrm-contains-additional-updaterc.d-calls]]''':<<BR>>
 The {{{postrm}}} de-registers an {{{/etc/init.d}}} script which has not been registered in the {{{postinst}}} script before.
}}}}
##END:Lintian/Tags/postrm-contains-additional-updaterc.d-calls

Self:Lintian/Tags/file-in-etc-rc.d-marked-as-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/file-in-etc-rc.d-marked-as-conffile.html|file-in-etc-rc.d-marked-as-conffile]]''':<<BR>>
 The symbolic links in {{{/etc/rc?.d}}} may not be marked as conffiles.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3]]
}}}}
##END:Lintian/Tags/file-in-etc-rc.d-marked-as-conffile

Self:Lintian/Tags/init.d-script-not-marked-as-conffile
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-not-marked-as-conffile.html|init.d-script-not-marked-as-conffile]]''':<<BR>>
 {{{/etc/init.d}}} scripts should be marked as conffiles.

 This is usually an error, but the Policy allows for managing these files manually in maintainer scripts and Lintian cannot reliably detect that.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.2]]
}}}}
##END:Lintian/Tags/init.d-script-not-marked-as-conffile

Self:Lintian/Tags/init.d-script-does-not-implement-required-option
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-does-not-implement-required-option.html|init.d-script-does-not-implement-required-option]]''':<<BR>>
 The {{{/etc/init.d}}} scripts have to support the following command line arguments: start, stop, restart, force-reload.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.2]]
}}}}
##END:Lintian/Tags/init.d-script-does-not-implement-required-option

Self:Lintian/Tags/init.d-script-not-included-in-package
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-not-included-in-package.html|init.d-script-not-included-in-package]]''':<<BR>>
 The {{{/etc/init.d}}} script is registered in the {{{postinst}}} script, but is not included in the package.
}}}}
##END:Lintian/Tags/init.d-script-not-included-in-package

Self:Lintian/Tags/script-in-etc-init.d-not-registered-via-update-rc.d
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/script-in-etc-init.d-not-registered-via-update-rc.d.html|script-in-etc-init.d-not-registered-via-update-rc.d]]''':<<BR>>
 The package installs an {{{/etc/init.d}}} script which is not registered in the {{{postinst}}} script. This is usually a bug, unless you omit the links intentionally for some reason or create the links some other way.
}}}}
##END:Lintian/Tags/script-in-etc-init.d-not-registered-via-update-rc.d

Self:Lintian/Tags/init.d-script-has-duplicate-lsb-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-duplicate-lsb-section.html|init.d-script-has-duplicate-lsb-section]]''':<<BR>>
 This {{{/etc/init.d}}} script has more than one LSB keyword section. These sections start with {{{### BEGIN INIT INFO}}} and end with {{{### END INIT INFO}}}. There should be only one such section per init script.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-duplicate-lsb-section

Self:Lintian/Tags/init.d-script-has-unterminated-lsb-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-unterminated-lsb-section.html|init.d-script-has-unterminated-lsb-section]]''':<<BR>>
 This {{{/etc/init.d}}} script has an LSB keyword section starting with {{{### BEGIN INIT INFO}}} but either has no matching {{{### END INIT INFO}}} or has lines between those two markers that are not comments. The line number given is the first line that doesn't look like part of an LSB keyword section. There must be an end marker after all the keyword settings and there must not be any lines between those markers that do not begin with {{{#}}}.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-unterminated-lsb-section

Self:Lintian/Tags/init.d-script-has-duplicate-lsb-keyword
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-duplicate-lsb-keyword.html|init.d-script-has-duplicate-lsb-keyword]]''':<<BR>>
 The given keyword was set twice in the LSB keyword section in this {{{/etc/init.d}}} script. This is probably a mistake; the behavior of setting the same keyword twice is undefined.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-duplicate-lsb-keyword

Self:Lintian/Tags/init.d-script-has-unknown-lsb-keyword
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-unknown-lsb-keyword.html|init.d-script-has-unknown-lsb-keyword]]''':<<BR>>
 The given keyword was set in the LSB keyword section in this {{{/etc/init.d}}} script but isn't one of the known LSB keywords and doesn't begin with {{{X-}}}. One of the standard keywords may have been misspelled.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-unknown-lsb-keyword

Self:Lintian/Tags/init.d-script-has-bad-lsb-line
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-bad-lsb-line.html|init.d-script-has-bad-lsb-line]]''':<<BR>>
 This line in the LSB keyword section of an {{{/etc/init.d}}} script doesn't match the required formatting of that section. Note that keyword settings must start with {{{#}}}, a single space, the keyword, a colon, and some whitespace, followed by the value (if any). Only the Description keyword allows continuation lines, and continuation lines must begin with {{{#}}} and either a tab or two or more spaces.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-bad-lsb-line

Self:Lintian/Tags/init.d-script-missing-lsb-section
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-missing-lsb-section.html|init.d-script-missing-lsb-section]]''':<<BR>>
 This {{{/etc/init.d}}} script does not have an LSB keyword section (or the {{{### BEGIN INIT INFO}}} tag is incorrect). This section provides description and runlevel information in a standard format and provides dependency information that can be used to parallelize the boot process. Please consider adding it.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-missing-lsb-section

Self:Lintian/Tags/init.d-script-missing-lsb-keyword
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-missing-lsb-keyword.html|init.d-script-missing-lsb-keyword]]''':<<BR>>
 This {{{/etc/init.d}}} script has an LSB keyword section, but it is missing the given required LSB keyword. If the value of this keyword should be empty, please still include it in the LSB keyword section with an empty value.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-missing-lsb-keyword

Self:Lintian/Tags/init.d-script-missing-lsb-short-description
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-missing-lsb-short-description.html|init.d-script-missing-lsb-short-description]]''':<<BR>>
 This {{{/etc/init.d}}} script has an LSB keyword section, but it is missing a Short-Description LSB keyword. This field isn't directly used currently, but adding it is still a good idea for documentation purposes.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-missing-lsb-short-description

Self:Lintian/Tags/init.d-script-has-bad-start-runlevel
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-bad-start-runlevel.html|init.d-script-has-bad-start-runlevel]]''':<<BR>>
 The given runlevel specified in the Default-Start keyword of the LSB keyword section of this {{{/etc/init.d}}} script isn't one of the recognized standard runlevels (S, 0, 1, 2, 3, 4, 5, and 6).

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-bad-start-runlevel

Self:Lintian/Tags/init.d-script-has-bad-stop-runlevel
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-bad-stop-runlevel.html|init.d-script-has-bad-stop-runlevel]]''':<<BR>>
 The given runlevel specified in the Default-Stop keyword of the LSB keyword section of this {{{/etc/init.d}}} script isn't one of the recognized standard runlevels (0, 1, 2, 3, 4, 5, and 6).

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-bad-stop-runlevel

Self:Lintian/Tags/init.d-script-has-conflicting-start-stop
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-has-conflicting-start-stop.html|init.d-script-has-conflicting-start-stop]]''':<<BR>>
 The given runlevel was included in both the Default-Start and Default-Stop keywords of the LSB keyword section of this {{{/etc/init.d}}} script. Since it doesn't make sense to both start and stop a service in the same runlevel, there is probably an error in one or the other of these keywords.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-has-conflicting-start-stop

Self:Lintian/Tags/init-d-script-stops-in-s-runlevel
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init-d-script-stops-in-s-runlevel.html|init-d-script-stops-in-s-runlevel]]''':<<BR>>
 This {{{/etc/init.d}}} script specifies the S runlevel in Default-Stop in its LSB keyword section. The S runlevel is not a real runlevel and is only used during boot. There is no way to switch to it and hence no use for stop scripts for it, so S should be removed from Default-Stop.
}}}}
##END:Lintian/Tags/init-d-script-stops-in-s-runlevel

Self:Lintian/Tags/init.d-script-uses-usr-interpreter
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-uses-usr-interpreter.html|init.d-script-uses-usr-interpreter]]''':<<BR>>
 The given {{{/etc/init.d}}} script specifies an interpreter in its shebang located under {{{/usr}}}. This means the init script will fail if run at a point in the boot sequence before the {{{/usr}}} partition has been mounted.

 It also indicates that the init script may be using a non-essential interpreter. Since init scripts are configuration files, they may be left on the system after their package has been removed but not purged. At that point, the package dependencies are not guaranteed to exist and the interpreter may therefore not be available.

 It's generally best to write init scripts using {{{/bin/sh}}} or {{{/bin/bash}}} where possible, since they are guaranteed to always be available.
}}}}
##END:Lintian/Tags/init.d-script-uses-usr-interpreter

Self:Lintian/Tags/init.d-script-sourcing-without-test
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-sourcing-without-test.html|init.d-script-sourcing-without-test]]''':<<BR>>
 The given {{{/etc/init.d}}} script seems to be sourcing an {{{/etc/default/}}} file without checking for its existence first. Files in {{{/etc/default/}}} can be deleted by the administrator at any time, and init scripts are required to handle the situation gracefully.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.2]]
}}}}
##END:Lintian/Tags/init.d-script-sourcing-without-test

Self:Lintian/Tags/init.d-script-starts-in-stop-runlevel
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-starts-in-stop-runlevel.html|init.d-script-starts-in-stop-runlevel]]''':<<BR>>
 This {{{/etc/init.d}}} script specifies the 0 or 6 runlevels in Default-Start in its LSB keyword section. The 0 and 6 runlevels are meant to only stop services, not to start them. Even if the init script is doing something that isn't exactly stopping a service, the run-level should be listed in Default-Stop, not Default-Start, and the script should perform those actions when passed the {{{stop}}} argument.
}}}}
##END:Lintian/Tags/init.d-script-starts-in-stop-runlevel

Self:Lintian/Tags/init.d-script-provides-virtual-facility
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-provides-virtual-facility.html|init.d-script-provides-virtual-facility]]''':<<BR>>
 This {{{/etc/init.d}}} script indicates in its LSB headers that it provides a virtual facility, denoted by the dollar sign in front of the name.

 This is not the correct way to provide a virtual facility. Instead, the package should include a file in {{{/etc/insserv.conf.d}}}, usually named after the package, containing:

  $virtual_facility_name +init-script-name

 to declare that the named init script provides the named virtual facility.

Reference(s): [[http://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities]]
}}}}
##END:Lintian/Tags/init.d-script-provides-virtual-facility

Self:Lintian/Tags/init.d-script-does-not-provide-itself
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-does-not-provide-itself.html|init.d-script-does-not-provide-itself]]''':<<BR>>
 This {{{/etc/init.d}}} script indicates it provides one or more facilities, but none of the provided facilities match the name of the init script. In certain cases, it may be necessary to not follow that convention, but normally init scripts should always provide a facility matching the name of the init script.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-does-not-provide-itself

Self:Lintian/Tags/init.d-script-should-depend-on-virtual-facility
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-should-depend-on-virtual-facility.html|init.d-script-should-depend-on-virtual-facility]]''':<<BR>>
 The given {{{/etc/init.d}}} script depends on a non-virtual facility that should probably be replaced by a virtual facility. For example, init scripts should depend on the virtual facility {{{$network}}} rather than the facility {{{networking}}}, and the virtual facility {{{$named}}} rather than the specific facility {{{bind9}}}.

 Properly using virtual facilities allows multiple implementations of the same facility and accommodates systems where that specific facility may not be enough to provide everything the script expects.
}}}}
##END:Lintian/Tags/init.d-script-should-depend-on-virtual-facility

Self:Lintian/Tags/init.d-script-possible-missing-stop
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-possible-missing-stop.html|init.d-script-possible-missing-stop]]''':<<BR>>
 The given {{{/etc/init.d}}} script indicates it should be stopped at one of the runlevels 0, 1, or 6 but not at all of them. This is usually a mistake. Normally, facilities that need to be stopped at any of those runlevels need to be stopped at all of them.

 For example, if it is safe for the facility provided by this init script to be stopped by {{{sendsigs}}} at runlevels 0 and 6, there should be no reason to special case runlevel 1, where {{{killprocs}}} would stop it. If the facility needs special shutdown handling when rebooting the system (runlevel 6), it probably needs the same handling when halting the system (runlevel 0) or switching to single-user mode (runlevel 1).
}}}}
##END:Lintian/Tags/init.d-script-possible-missing-stop

Self:Lintian/Tags/init.d-script-missing-start
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-missing-start.html|init.d-script-missing-start]]''':<<BR>>
 The given {{{/etc/init.d}}} script indicates it should be started at one of the runlevels 2-5 but not at all of them. This is a mistake. The system administrators should be given the opportunity to customize the runlevels at their will.

Reference(s): [[http://www.debian.org/doc/debian-policy/|policy 9.3.3.1]]
}}}}
##END:Lintian/Tags/init.d-script-missing-start

Self:Lintian/Tags/init.d-script-missing-dependency-on-remote_fs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-missing-dependency-on-remote_fs.html|init.d-script-missing-dependency-on-remote_fs]]''':<<BR>>
 The given init script seems to refer to {{{/usr}}}, possibly using a file or binary from there. Without a dependency on {{{$remote_fs}}} in Required-Start or Required-Stop, as appropriate, the init script might be run before {{{/usr}}} is mounted or after it's unmounted.

 Using Should-Start or Should-Stop to declare the dependency is conceptually incorrect since the $remote_fs facility is always available. Required-Start or Required-Stop should be used instead. Also, please note that $all should not be used in Required-Stop, only Required-Start.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-missing-dependency-on-remote_fs

Self:Lintian/Tags/init.d-script-missing-dependency-on-local_fs
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-missing-dependency-on-local_fs.html|init.d-script-missing-dependency-on-local_fs]]''':<<BR>>
 The given init script seems to refer to {{{/var}}}, possibly using a file from there. Without a dependency on {{{$local_fs}}} in Required-Start or Required-Stop, as appropriate, the init script might be run before {{{/var}}} is mounted or after it's unmounted.

 Using Should-Start or Should-Stop to declare the dependency is conceptually incorrect since the $local_fs facility is always available. Required-Start or Required-Stop should be used instead.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-missing-dependency-on-local_fs

Self:Lintian/Tags/init.d-script-depends-on-unknown-virtual-facility
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/init.d-script-depends-on-unknown-virtual-facility.html|init.d-script-depends-on-unknown-virtual-facility]]''':<<BR>>
 The given init script declares a dependency on a virtual facility that is not known to be provided by any init.d script in the archive. If the dependency can not be satisfied upon the package's installation, insserv will refuse the activation of the init.d script.

Reference(s): [[http://wiki.debian.org/LSBInitScripts]]
}}}}
##END:Lintian/Tags/init.d-script-depends-on-unknown-virtual-facility

########################################################################
== nmu ==
########################################################################

Self:Lintian/Tags/orphaned-package-should-not-have-uploaders
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/orphaned-package-should-not-have-uploaders.html|orphaned-package-should-not-have-uploaders]]''':<<BR>>
 Packages with their maintainer set to packages@qa.debian.org, i.e. orphaned packages, should not have uploaders. Adopt the package properly if you want to resume its maintenance.
}}}}
##END:Lintian/Tags/orphaned-package-should-not-have-uploaders

Self:Lintian/Tags/qa-upload-has-incorrect-version-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/qa-upload-has-incorrect-version-number.html|qa-upload-has-incorrect-version-number]]''':<<BR>>
 A QA upload (uploading an orphaned package without adopting it) is always a maintainer upload: it should not get a NMU revision number.
}}}}
##END:Lintian/Tags/qa-upload-has-incorrect-version-number

Self:Lintian/Tags/team-upload-has-incorrect-version-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/team-upload-has-incorrect-version-number.html|team-upload-has-incorrect-version-number]]''':<<BR>>
 A team upload (uploading a package from the same team without adding oneself as maintainer or uploader) is a maintainer upload: it should not get a NMU revision number. Team uploads are recognized by the string "team upload" on the first line of the changelog file.
}}}}
##END:Lintian/Tags/team-upload-has-incorrect-version-number

Self:Lintian/Tags/source-nmu-has-incorrect-version-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/source-nmu-has-incorrect-version-number.html|source-nmu-has-incorrect-version-number]]''':<<BR>>
 A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a native package). This is to prevent stealing version numbers from the maintainer.

 Maybe you didn't intend this upload to be a NMU, in that case, please doublecheck that the most recent entry in the changelog is byte-for-byte identical to the maintainer or one of the uploaders. If this is a local package (not intended for Debian), you can suppress this warning by putting "local" in the version number or "local package" on the first line of the changelog entry.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.11.2]]
}}}}
##END:Lintian/Tags/source-nmu-has-incorrect-version-number

Self:Lintian/Tags/maintainer-upload-has-incorrect-version-number
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/maintainer-upload-has-incorrect-version-number.html|maintainer-upload-has-incorrect-version-number]]''':<<BR>>
 A maintainer upload should have a Debian revision without dots. Revisions with dots are reserved for Non-Maintainer Uploads (NMU's), if you do a maintainer-upload with dots, a potential NMU'er has problems choosing a correct version number.
}}}}
##END:Lintian/Tags/maintainer-upload-has-incorrect-version-number

Self:Lintian/Tags/changelog-should-mention-qa
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-should-mention-qa.html|changelog-should-mention-qa]]''':<<BR>>
 If this upload is to orphan this package, please mention this fact on the first line of the changelog. If this is a QA upload, please mention "QA (group) upload" there.
}}}}
##END:Lintian/Tags/changelog-should-mention-qa

Self:Lintian/Tags/changelog-should-mention-nmu
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-should-mention-nmu.html|changelog-should-mention-nmu]]''':<<BR>>
 When you NMU a package, that fact should be mentioned on the first line in the changelog entry. Use the words "NMU" or "Non-maintainer upload" (case insensitive).

 Maybe you didn't intend this upload to be a NMU, in that case, please doublecheck that the most recent entry in the changelog is byte-for-byte identical to the maintainer or one of the uploaders. If this is a local package (not intended for Debian), you can suppress this warning by putting "local" in the version number or "local package" on the first line of the changelog entry.

Reference(s): [[http://www.debian.org/doc/manuals/developers-reference/|devref 5.11.3]]
}}}}
##END:Lintian/Tags/changelog-should-mention-nmu

Self:Lintian/Tags/changelog-should-not-mention-nmu
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-should-not-mention-nmu.html|changelog-should-not-mention-nmu]]''':<<BR>>
 The first line of the changelog entry for this package appears to indicate it is a non-maintainer upload (by including either that string or the string "NMU" and not saying that it's an acknowledgement), but the changelog indicates the person making this release is one of the maintainers.

 If this was intended to be an NMU, do not add yourself as a maintainer or uploader. Otherwise, please rephrase your changelog entry to not cause confusion.
}}}}
##END:Lintian/Tags/changelog-should-not-mention-nmu

Self:Lintian/Tags/changelog-is-symlink
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/changelog-is-symlink.html|changelog-is-symlink]]''':<<BR>>
 The file {{{debian/changelog}}} is a symlink instead of a regular file. This is unnecessary and makes package checking and manipulation more difficult. If the changelog should be available in the source package under multiple names, make {{{debian/changelog}}} the real file and the other names symlinks to it.

 This problem may have prevented lintian from performing other checks, leading to undetected changelog errors.
}}}}
##END:Lintian/Tags/changelog-is-symlink

########################################################################
== lintian ==
########################################################################

Self:Lintian/Tags/unused-override
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/unused-override.html|unused-override]]''':<<BR>>
 Lintian discovered an unused override entry in its database. Please remove it from the overrides file if it is not needed anymore.
}}}}
##END:Lintian/Tags/unused-override

Self:Lintian/Tags/malformed-override
{{{{#!wiki note
Lintian tag '''[[http://lintian.debian.org/tags/malformed-override.html|malformed-override]]''':<<BR>>
 Lintian discovered an override entry with an invalid format. An override entry should have the format:

   <package>[ <type>]: <tag>[ <extra> ...]

 where <package> is the package name, the optional <type> parameter specifies the package type (binary is the default), <tag> is the tag to suppress, and <extra> is any specific information for the particular tag to suppress.
}}}}
##END:Lintian/Tags/malformed-override

##START:TOC
=== debconf ===
 * [[Self:Lintian/Tags/missing-debconf-dependency|missing-debconf-dependency]]
 * [[Self:Lintian/Tags/missing-debconf-dependency-for-preinst|missing-debconf-dependency-for-preinst]]
 * [[Self:Lintian/Tags/duplicate-fields-in-templates|duplicate-fields-in-templates]]
 * [[Self:Lintian/Tags/unknown-field-in-templates|unknown-field-in-templates]]
 * [[Self:Lintian/Tags/no-template-name|no-template-name]]
 * [[Self:Lintian/Tags/malformed-template-name|malformed-template-name]]
 * [[Self:Lintian/Tags/no-template-type|no-template-type]]
 * [[Self:Lintian/Tags/unknown-template-type|unknown-template-type]]
 * [[Self:Lintian/Tags/empty-translated-choices|empty-translated-choices]]
 * [[Self:Lintian/Tags/mismatch-translated-choices|mismatch-translated-choices]]
 * [[Self:Lintian/Tags/select-without-choices|select-without-choices]]
 * [[Self:Lintian/Tags/boolean-template-has-bogus-default|boolean-template-has-bogus-default]]
 * [[Self:Lintian/Tags/no-template-description|no-template-description]]
 * [[Self:Lintian/Tags/duplicate-long-description-in-template|duplicate-long-description-in-template]]
 * [[Self:Lintian/Tags/config-does-not-load-confmodule|config-does-not-load-confmodule]]
 * [[Self:Lintian/Tags/postinst-uses-db-input|postinst-uses-db-input]]
 * [[Self:Lintian/Tags/postinst-does-not-load-confmodule|postinst-does-not-load-confmodule]]
 * [[Self:Lintian/Tags/loads-obsolete-confmodule|loads-obsolete-confmodule]]
 * [[Self:Lintian/Tags/postrm-does-not-purge-debconf|postrm-does-not-purge-debconf]]
 * [[Self:Lintian/Tags/isdefault-flag-is-deprecated|isdefault-flag-is-deprecated]]
 * [[Self:Lintian/Tags/debconf-config-not-executable|debconf-config-not-executable]]
 * [[Self:Lintian/Tags/no-debconf-config|no-debconf-config]]
 * [[Self:Lintian/Tags/no-debconf-templates|no-debconf-templates]]
 * [[Self:Lintian/Tags/debconf-is-not-a-registry|debconf-is-not-a-registry]]
 * [[Self:Lintian/Tags/malformed-prompt-in-templates|malformed-prompt-in-templates]]
 * [[Self:Lintian/Tags/malformed-title-in-templates|malformed-title-in-templates]]
 * [[Self:Lintian/Tags/malformed-question-in-templates|malformed-question-in-templates]]
 * [[Self:Lintian/Tags/using-question-in-extended-description-in-templates|using-question-in-extended-description-in-templates]]
 * [[Self:Lintian/Tags/using-imperative-form-in-templates|using-imperative-form-in-templates]]
 * [[Self:Lintian/Tags/using-first-person-in-templates|using-first-person-in-templates]]
 * [[Self:Lintian/Tags/making-assumptions-about-interfaces-in-templates|making-assumptions-about-interfaces-in-templates]]
 * [[Self:Lintian/Tags/too-long-short-description-in-templates|too-long-short-description-in-templates]]
 * [[Self:Lintian/Tags/too-long-extended-description-in-templates|too-long-extended-description-in-templates]]
 * [[Self:Lintian/Tags/unknown-debconf-priority|unknown-debconf-priority]]
 * [[Self:Lintian/Tags/possible-debconf-note-abuse|possible-debconf-note-abuse]]
 * [[Self:Lintian/Tags/select-with-boolean-choices|select-with-boolean-choices]]
 * [[Self:Lintian/Tags/template-uses-unsplit-choices|template-uses-unsplit-choices]]
 * [[Self:Lintian/Tags/unused-debconf-template|unused-debconf-template]]

=== infofiles ===
 * [[Self:Lintian/Tags/info-document-not-compressed|info-document-not-compressed]]
 * [[Self:Lintian/Tags/info-document-not-compressed-with-gzip|info-document-not-compressed-with-gzip]]
 * [[Self:Lintian/Tags/info-document-not-compressed-with-max-compression|info-document-not-compressed-with-max-compression]]
 * [[Self:Lintian/Tags/info-document-has-wrong-extension|info-document-has-wrong-extension]]
 * [[Self:Lintian/Tags/info-document-missing-dir-section|info-document-missing-dir-section]]
 * [[Self:Lintian/Tags/info-document-missing-dir-entry|info-document-missing-dir-entry]]
 * [[Self:Lintian/Tags/missing-dependency-on-install-info|missing-dependency-on-install-info]]

=== control-file ===
 * [[Self:Lintian/Tags/debian-control-file-uses-obsolete-national-encoding|debian-control-file-uses-obsolete-national-encoding]]
 * [[Self:Lintian/Tags/build-info-in-binary-control-file-section|build-info-in-binary-control-file-section]]
 * [[Self:Lintian/Tags/debian-control-with-duplicate-fields|debian-control-with-duplicate-fields]]
 * [[Self:Lintian/Tags/debian-control-has-unusual-field-spacing|debian-control-has-unusual-field-spacing]]
 * [[Self:Lintian/Tags/binary-control-field-duplicates-source|binary-control-field-duplicates-source]]
 * [[Self:Lintian/Tags/debian-control-file-is-a-symlink|debian-control-file-is-a-symlink]]
 * [[Self:Lintian/Tags/no-section-field-for-source|no-section-field-for-source]]
 * [[Self:Lintian/Tags/section-area-mismatch|section-area-mismatch]]
 * [[Self:Lintian/Tags/xs-vcs-header-in-debian-control|xs-vcs-header-in-debian-control]]
 * [[Self:Lintian/Tags/xc-package-type-in-debian-control|xc-package-type-in-debian-control]]
 * [[Self:Lintian/Tags/stronger-dependency-implies-weaker|stronger-dependency-implies-weaker]]
 * [[Self:Lintian/Tags/package-depends-on-itself|package-depends-on-itself]]
 * [[Self:Lintian/Tags/duplicate-short-description|duplicate-short-description]]
 * [[Self:Lintian/Tags/duplicate-long-description|duplicate-long-description]]
 * [[Self:Lintian/Tags/duplicate-in-relation-field|duplicate-in-relation-field]]
 * [[Self:Lintian/Tags/missing-separator-between-items|missing-separator-between-items]]
 * [[Self:Lintian/Tags/obsolete-relation-form-in-source|obsolete-relation-form-in-source]]
 * [[Self:Lintian/Tags/package-depends-on-hardcoded-libc|package-depends-on-hardcoded-libc]]
 * [[Self:Lintian/Tags/weak-library-dev-dependency|weak-library-dev-dependency]]

=== shared-libs ===
 * [[Self:Lintian/Tags/shlib-with-executable-bit|shlib-with-executable-bit]]
 * [[Self:Lintian/Tags/shlib-with-bad-permissions|shlib-with-bad-permissions]]
 * [[Self:Lintian/Tags/shlib-with-non-pic-code|shlib-with-non-pic-code]]
 * [[Self:Lintian/Tags/shlib-without-versioned-soname|shlib-without-versioned-soname]]
 * [[Self:Lintian/Tags/ldconfig-symlink-missing-for-shlib|ldconfig-symlink-missing-for-shlib]]
 * [[Self:Lintian/Tags/ldconfig-symlink-before-shlib-in-deb|ldconfig-symlink-before-shlib-in-deb]]
 * [[Self:Lintian/Tags/dev-pkg-without-shlib-symlink|dev-pkg-without-shlib-symlink]]
 * [[Self:Lintian/Tags/non-dev-pkg-with-shlib-symlink|non-dev-pkg-with-shlib-symlink]]
 * [[Self:Lintian/Tags/preinst-calls-ldconfig|preinst-calls-ldconfig]]
 * [[Self:Lintian/Tags/prerm-calls-ldconfig|prerm-calls-ldconfig]]
 * [[Self:Lintian/Tags/postrm-unsafe-ldconfig|postrm-unsafe-ldconfig]]
 * [[Self:Lintian/Tags/no-shlibs-control-file|no-shlibs-control-file]]
 * [[Self:Lintian/Tags/pkg-has-shlibs-control-file-but-no-actual-shared-libs|pkg-has-shlibs-control-file-but-no-actual-shared-libs]]
 * [[Self:Lintian/Tags/duplicate-entry-in-shlibs-control-file|duplicate-entry-in-shlibs-control-file]]
 * [[Self:Lintian/Tags/shlib-missing-in-control-file|shlib-missing-in-control-file]]
 * [[Self:Lintian/Tags/unused-shlib-entry-in-control-file|unused-shlib-entry-in-control-file]]
 * [[Self:Lintian/Tags/shlibs-declares-dependency-on-other-package|shlibs-declares-dependency-on-other-package]]
 * [[Self:Lintian/Tags/ldconfig-symlink-referencing-wrong-file|ldconfig-symlink-referencing-wrong-file]]
 * [[Self:Lintian/Tags/ldconfig-symlink-is-not-a-symlink|ldconfig-symlink-is-not-a-symlink]]
 * [[Self:Lintian/Tags/postinst-has-useless-call-to-ldconfig|postinst-has-useless-call-to-ldconfig]]
 * [[Self:Lintian/Tags/udeb-postinst-must-not-call-ldconfig|udeb-postinst-must-not-call-ldconfig]]
 * [[Self:Lintian/Tags/postrm-has-useless-call-to-ldconfig|postrm-has-useless-call-to-ldconfig]]
 * [[Self:Lintian/Tags/postinst-must-call-ldconfig|postinst-must-call-ldconfig]]
 * [[Self:Lintian/Tags/postrm-should-call-ldconfig|postrm-should-call-ldconfig]]
 * [[Self:Lintian/Tags/sharedobject-in-library-directory-missing-soname|sharedobject-in-library-directory-missing-soname]]
 * [[Self:Lintian/Tags/shlib-without-PT_GNU_STACK-section|shlib-without-PT_GNU_STACK-section]]
 * [[Self:Lintian/Tags/shlib-with-executable-stack|shlib-with-executable-stack]]
 * [[Self:Lintian/Tags/symbols-file-contains-current-version-with-debian-revision|symbols-file-contains-current-version-with-debian-revision]]
 * [[Self:Lintian/Tags/symbols-file-contains-debian-revision|symbols-file-contains-debian-revision]]
 * [[Self:Lintian/Tags/syntax-error-in-symbols-file|syntax-error-in-symbols-file]]
 * [[Self:Lintian/Tags/duplicate-entry-in-symbols-control-file|duplicate-entry-in-symbols-control-file]]
 * [[Self:Lintian/Tags/no-symbols-control-file|no-symbols-control-file]]
 * [[Self:Lintian/Tags/pkg-has-symbols-control-file-but-no-shared-libs|pkg-has-symbols-control-file-but-no-shared-libs]]
 * [[Self:Lintian/Tags/shlib-missing-in-symbols-control-file|shlib-missing-in-symbols-control-file]]
 * [[Self:Lintian/Tags/unused-shlib-entry-in-symbols-control-file|unused-shlib-entry-in-symbols-control-file]]
 * [[Self:Lintian/Tags/symbols-declares-dependency-on-other-package|symbols-declares-dependency-on-other-package]]
 * [[Self:Lintian/Tags/invalid-template-id-in-symbols-file|invalid-template-id-in-symbols-file]]
 * [[Self:Lintian/Tags/unknown-meta-field-in-symbols-file|unknown-meta-field-in-symbols-file]]
 * [[Self:Lintian/Tags/symbols-declared-but-not-shlib|symbols-declared-but-not-shlib]]
 * [[Self:Lintian/Tags/shlib-calls-exit|shlib-calls-exit]]
 * [[Self:Lintian/Tags/incorrect-libdir-in-la-file|incorrect-libdir-in-la-file]]

=== debian-source-dir ===
 * [[Self:Lintian/Tags/missing-debian-source-format|missing-debian-source-format]]
 * [[Self:Lintian/Tags/unknown-source-format|unknown-source-format]]
 * [[Self:Lintian/Tags/unknown-file-in-debian-source|unknown-file-in-debian-source]]

=== version-substvars ===
 * [[Self:Lintian/Tags/not-binnmuable-any-depends-any|not-binnmuable-any-depends-any]]
 * [[Self:Lintian/Tags/not-binnmuable-any-depends-all|not-binnmuable-any-depends-all]]
 * [[Self:Lintian/Tags/not-binnmuable-all-depends-any|not-binnmuable-all-depends-any]]
 * [[Self:Lintian/Tags/version-substvar-for-external-package|version-substvar-for-external-package]]
 * [[Self:Lintian/Tags/substvar-source-version-is-deprecated|substvar-source-version-is-deprecated]]

=== deb-format ===
 * [[Self:Lintian/Tags/malformed-deb-archive|malformed-deb-archive]]
 * [[Self:Lintian/Tags/lzma-deb-archive|lzma-deb-archive]]
 * [[Self:Lintian/Tags/tar-errors-from-control|tar-errors-from-control]]
 * [[Self:Lintian/Tags/tar-errors-from-data|tar-errors-from-data]]

=== debian-readme ===
 * [[Self:Lintian/Tags/readme-debian-mentions-usr-doc|readme-debian-mentions-usr-doc]]
 * [[Self:Lintian/Tags/readme-debian-contains-debmake-template|readme-debian-contains-debmake-template]]
 * [[Self:Lintian/Tags/readme-debian-contains-debmake-default-email-address|readme-debian-contains-debmake-default-email-address]]
 * [[Self:Lintian/Tags/spelling-error-in-readme-debian|spelling-error-in-readme-debian]]

=== patch-systems ===
 * [[Self:Lintian/Tags/dpatch-build-dep-but-no-patch-list|dpatch-build-dep-but-no-patch-list]]
 * [[Self:Lintian/Tags/dpatch-index-references-non-existent-patch|dpatch-index-references-non-existent-patch]]
 * [[Self:Lintian/Tags/dpatch-missing-description|dpatch-missing-description]]
 * [[Self:Lintian/Tags/quilt-build-dep-but-no-series-file|quilt-build-dep-but-no-series-file]]
 * [[Self:Lintian/Tags/quilt-series-but-no-build-dep|quilt-series-but-no-build-dep]]
 * [[Self:Lintian/Tags/quilt-patch-with-non-standard-options|quilt-patch-with-non-standard-options]]
 * [[Self:Lintian/Tags/quilt-series-references-non-existent-patch|quilt-series-references-non-existent-patch]]
 * [[Self:Lintian/Tags/quilt-patch-missing-description|quilt-patch-missing-description]]
 * [[Self:Lintian/Tags/patch-modifying-debian-files|patch-modifying-debian-files]]
 * [[Self:Lintian/Tags/patch-system-but-direct-changes-in-diff|patch-system-but-direct-changes-in-diff]]
 * [[Self:Lintian/Tags/more-than-one-patch-system|more-than-one-patch-system]]
 * [[Self:Lintian/Tags/direct-changes-in-diff-but-no-patch-system|direct-changes-in-diff-but-no-patch-system]]
 * [[Self:Lintian/Tags/patch-system-but-no-source-readme|patch-system-but-no-source-readme]]

=== huge-usr-share ===
 * [[Self:Lintian/Tags/arch-dep-package-has-big-usr-share|arch-dep-package-has-big-usr-share]]

=== etcfiles ===
 * [[Self:Lintian/Tags/file-in-etc-not-marked-as-conffile|file-in-etc-not-marked-as-conffile]]

=== lintian ===
 * [[Self:Lintian/Tags/unused-override|unused-override]]
 * [[Self:Lintian/Tags/malformed-override|malformed-override]]

=== cruft ===
 * [[Self:Lintian/Tags/native-package-with-dash-version|native-package-with-dash-version]]
 * [[Self:Lintian/Tags/non-native-package-with-native-version|non-native-package-with-native-version]]
 * [[Self:Lintian/Tags/documentation-package-not-architecture-independent|documentation-package-not-architecture-independent]]
 * [[Self:Lintian/Tags/debian-files-list-in-source|debian-files-list-in-source]]
 * [[Self:Lintian/Tags/diff-contains-cmake-cache-file|diff-contains-cmake-cache-file]]
 * [[Self:Lintian/Tags/diff-contains-cvs-control-dir|diff-contains-cvs-control-dir]]
 * [[Self:Lintian/Tags/source-contains-cvs-control-dir|source-contains-cvs-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-svn-control-dir|diff-contains-svn-control-dir]]
 * [[Self:Lintian/Tags/source-contains-svn-control-dir|source-contains-svn-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-bzr-control-dir|diff-contains-bzr-control-dir]]
 * [[Self:Lintian/Tags/source-contains-bzr-control-dir|source-contains-bzr-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-arch-control-dir|diff-contains-arch-control-dir]]
 * [[Self:Lintian/Tags/source-contains-arch-control-dir|source-contains-arch-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-git-control-dir|diff-contains-git-control-dir]]
 * [[Self:Lintian/Tags/source-contains-git-control-dir|source-contains-git-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-hg-control-dir|diff-contains-hg-control-dir]]
 * [[Self:Lintian/Tags/source-contains-hg-control-dir|source-contains-hg-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-bts-control-dir|diff-contains-bts-control-dir]]
 * [[Self:Lintian/Tags/source-contains-bts-control-dir|source-contains-bts-control-dir]]
 * [[Self:Lintian/Tags/diff-contains-svn-commit-file|diff-contains-svn-commit-file]]
 * [[Self:Lintian/Tags/source-contains-svn-commit-file|source-contains-svn-commit-file]]
 * [[Self:Lintian/Tags/diff-contains-svk-commit-file|diff-contains-svk-commit-file]]
 * [[Self:Lintian/Tags/source-contains-svk-commit-file|source-contains-svk-commit-file]]
 * [[Self:Lintian/Tags/diff-contains-arch-inventory-file|diff-contains-arch-inventory-file]]
 * [[Self:Lintian/Tags/source-contains-arch-inventory-file|source-contains-arch-inventory-file]]
 * [[Self:Lintian/Tags/diff-contains-hg-tags-file|diff-contains-hg-tags-file]]
 * [[Self:Lintian/Tags/source-contains-hg-tags-file|source-contains-hg-tags-file]]
 * [[Self:Lintian/Tags/diff-contains-cvs-conflict-copy|diff-contains-cvs-conflict-copy]]
 * [[Self:Lintian/Tags/source-contains-cvs-conflict-copy|source-contains-cvs-conflict-copy]]
 * [[Self:Lintian/Tags/diff-contains-svn-conflict-file|diff-contains-svn-conflict-file]]
 * [[Self:Lintian/Tags/source-contains-svn-conflict-file|source-contains-svn-conflict-file]]
 * [[Self:Lintian/Tags/diff-contains-patch-failure-file|diff-contains-patch-failure-file]]
 * [[Self:Lintian/Tags/diff-contains-editor-backup-file|diff-contains-editor-backup-file]]
 * [[Self:Lintian/Tags/diff-contains-substvars|diff-contains-substvars]]
 * [[Self:Lintian/Tags/empty-debian-diff|empty-debian-diff]]
 * [[Self:Lintian/Tags/configure-generated-file-in-source|configure-generated-file-in-source]]
 * [[Self:Lintian/Tags/ancient-autotools-helper-file|ancient-autotools-helper-file]]
 * [[Self:Lintian/Tags/outdated-autotools-helper-file|outdated-autotools-helper-file]]
 * [[Self:Lintian/Tags/ancient-libtool|ancient-libtool]]
 * [[Self:Lintian/Tags/source-contains-prebuilt-binary|source-contains-prebuilt-binary]]
 * [[Self:Lintian/Tags/source-contains-prebuilt-windows-binary|source-contains-prebuilt-windows-binary]]
 * [[Self:Lintian/Tags/tar-errors-from-source|tar-errors-from-source]]
 * [[Self:Lintian/Tags/control-file-with-CRLF-EOLs|control-file-with-CRLF-EOLs]]

=== menus ===
 * [[Self:Lintian/Tags/postinst-should-not-set-usr-doc-link|postinst-should-not-set-usr-doc-link]]
 * [[Self:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-updatemenus|maintainer-script-does-not-check-for-existence-of-updatemenus]]
 * [[Self:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-wm-menu-config|maintainer-script-does-not-check-for-existence-of-wm-menu-config]]
 * [[Self:Lintian/Tags/maintainer-script-does-not-check-for-existence-of-installdocs|maintainer-script-does-not-check-for-existence-of-installdocs]]
 * [[Self:Lintian/Tags/maintainer-script-calls-deprecated-wm-menu-config|maintainer-script-calls-deprecated-wm-menu-config]]
 * [[Self:Lintian/Tags/preinst-calls-updatemenus|preinst-calls-updatemenus]]
 * [[Self:Lintian/Tags/preinst-calls-installdocs|preinst-calls-installdocs]]
 * [[Self:Lintian/Tags/prerm-calls-updatemenus|prerm-calls-updatemenus]]
 * [[Self:Lintian/Tags/postrm-calls-installdocs|postrm-calls-installdocs]]
 * [[Self:Lintian/Tags/executable-menu-file|executable-menu-file]]
 * [[Self:Lintian/Tags/menu-file-in-usr-lib|menu-file-in-usr-lib]]
 * [[Self:Lintian/Tags/executable-in-usr-share-docbase|executable-in-usr-share-docbase]]
 * [[Self:Lintian/Tags/postinst-does-not-call-updatemenus|postinst-does-not-call-updatemenus]]
 * [[Self:Lintian/Tags/postrm-does-not-call-updatemenus|postrm-does-not-call-updatemenus]]
 * [[Self:Lintian/Tags/postinst-has-useless-call-to-update-menus|postinst-has-useless-call-to-update-menus]]
 * [[Self:Lintian/Tags/postrm-has-useless-call-to-update-menus|postrm-has-useless-call-to-update-menus]]
 * [[Self:Lintian/Tags/postinst-has-useless-call-to-install-docs|postinst-has-useless-call-to-install-docs]]
 * [[Self:Lintian/Tags/prerm-has-useless-call-to-install-docs|prerm-has-useless-call-to-install-docs]]
 * [[Self:Lintian/Tags/bad-menu-file-name|bad-menu-file-name]]
 * [[Self:Lintian/Tags/doc-base-file-references-usr-doc|doc-base-file-references-usr-doc]]
 * [[Self:Lintian/Tags/doc-base-index-references-multiple-files|doc-base-index-references-multiple-files]]
 * [[Self:Lintian/Tags/doc-base-file-references-missing-file|doc-base-file-references-missing-file]]
 * [[Self:Lintian/Tags/doc-base-file-unknown-format|doc-base-file-unknown-format]]
 * [[Self:Lintian/Tags/doc-base-file-no-format|doc-base-file-no-format]]
 * [[Self:Lintian/Tags/doc-base-file-no-format-section|doc-base-file-no-format-section]]
 * [[Self:Lintian/Tags/doc-base-file-no-index|doc-base-file-no-index]]
 * [[Self:Lintian/Tags/doc-base-document-field-ends-in-whitespace|doc-base-document-field-ends-in-whitespace]]
 * [[Self:Lintian/Tags/doc-base-document-field-not-in-first-line|doc-base-document-field-not-in-first-line]]
 * [[Self:Lintian/Tags/doc-base-file-unknown-field|doc-base-file-unknown-field]]
 * [[Self:Lintian/Tags/doc-base-file-duplicated-field|doc-base-file-duplicated-field]]
 * [[Self:Lintian/Tags/doc-base-file-duplicated-format|doc-base-file-duplicated-format]]
 * [[Self:Lintian/Tags/doc-base-file-lacks-required-field|doc-base-file-lacks-required-field]]
 * [[Self:Lintian/Tags/doc-base-invalid-document-field|doc-base-invalid-document-field]]
 * [[Self:Lintian/Tags/doc-base-abstract-field-is-template|doc-base-abstract-field-is-template]]
 * [[Self:Lintian/Tags/doc-base-abstract-might-contain-extra-leading-whitespaces|doc-base-abstract-might-contain-extra-leading-whitespaces]]
 * [[Self:Lintian/Tags/doc-base-abstract-field-separator-extra-whitespaces|doc-base-abstract-field-separator-extra-whitespaces]]
 * [[Self:Lintian/Tags/spelling-error-in-doc-base-title-field|spelling-error-in-doc-base-title-field]]
 * [[Self:Lintian/Tags/spelling-error-in-doc-base-abstract-field|spelling-error-in-doc-base-abstract-field]]
 * [[Self:Lintian/Tags/doc-base-file-syntax-error|doc-base-file-syntax-error]]
 * [[Self:Lintian/Tags/doc-base-file-separator-extra-whitespaces|doc-base-file-separator-extra-whitespaces]]
 * [[Self:Lintian/Tags/doc-base-file-uses-obsolete-national-encoding|doc-base-file-uses-obsolete-national-encoding]]
 * [[Self:Lintian/Tags/doc-base-uses-applications-section|doc-base-uses-applications-section]]
 * [[Self:Lintian/Tags/doc-base-unknown-section|doc-base-unknown-section]]
 * [[Self:Lintian/Tags/menu-method-should-include-menu-h|menu-method-should-include-menu-h]]
 * [[Self:Lintian/Tags/possible-documentation-but-no-doc-base-registration|possible-documentation-but-no-doc-base-registration]]

=== init ===
 * [[Self:Lintian/Tags/duplicate-updaterc.d-calls-in-postinst|duplicate-updaterc.d-calls-in-postinst]]
 * [[Self:Lintian/Tags/output-of-updaterc.d-not-redirected-to-dev-null|output-of-updaterc.d-not-redirected-to-dev-null]]
 * [[Self:Lintian/Tags/preinst-calls-updaterc.d|preinst-calls-updaterc.d]]
 * [[Self:Lintian/Tags/duplicate-updaterc.d-calls-in-postrm|duplicate-updaterc.d-calls-in-postrm]]
 * [[Self:Lintian/Tags/prerm-calls-updaterc.d|prerm-calls-updaterc.d]]
 * [[Self:Lintian/Tags/postrm-does-not-call-updaterc.d-for-init.d-script|postrm-does-not-call-updaterc.d-for-init.d-script]]
 * [[Self:Lintian/Tags/postrm-contains-additional-updaterc.d-calls|postrm-contains-additional-updaterc.d-calls]]
 * [[Self:Lintian/Tags/file-in-etc-rc.d-marked-as-conffile|file-in-etc-rc.d-marked-as-conffile]]
 * [[Self:Lintian/Tags/init.d-script-not-marked-as-conffile|init.d-script-not-marked-as-conffile]]
 * [[Self:Lintian/Tags/init.d-script-does-not-implement-required-option|init.d-script-does-not-implement-required-option]]
 * [[Self:Lintian/Tags/init.d-script-not-included-in-package|init.d-script-not-included-in-package]]
 * [[Self:Lintian/Tags/script-in-etc-init.d-not-registered-via-update-rc.d|script-in-etc-init.d-not-registered-via-update-rc.d]]
 * [[Self:Lintian/Tags/init.d-script-has-duplicate-lsb-section|init.d-script-has-duplicate-lsb-section]]
 * [[Self:Lintian/Tags/init.d-script-has-unterminated-lsb-section|init.d-script-has-unterminated-lsb-section]]
 * [[Self:Lintian/Tags/init.d-script-has-duplicate-lsb-keyword|init.d-script-has-duplicate-lsb-keyword]]
 * [[Self:Lintian/Tags/init.d-script-has-unknown-lsb-keyword|init.d-script-has-unknown-lsb-keyword]]
 * [[Self:Lintian/Tags/init.d-script-has-bad-lsb-line|init.d-script-has-bad-lsb-line]]
 * [[Self:Lintian/Tags/init.d-script-missing-lsb-section|init.d-script-missing-lsb-section]]
 * [[Self:Lintian/Tags/init.d-script-missing-lsb-keyword|init.d-script-missing-lsb-keyword]]
 * [[Self:Lintian/Tags/init.d-script-missing-lsb-short-description|init.d-script-missing-lsb-short-description]]
 * [[Self:Lintian/Tags/init.d-script-has-bad-start-runlevel|init.d-script-has-bad-start-runlevel]]
 * [[Self:Lintian/Tags/init.d-script-has-bad-stop-runlevel|init.d-script-has-bad-stop-runlevel]]
 * [[Self:Lintian/Tags/init.d-script-has-conflicting-start-stop|init.d-script-has-conflicting-start-stop]]
 * [[Self:Lintian/Tags/init-d-script-stops-in-s-runlevel|init-d-script-stops-in-s-runlevel]]
 * [[Self:Lintian/Tags/init.d-script-uses-usr-interpreter|init.d-script-uses-usr-interpreter]]
 * [[Self:Lintian/Tags/init.d-script-sourcing-without-test|init.d-script-sourcing-without-test]]
 * [[Self:Lintian/Tags/init.d-script-starts-in-stop-runlevel|init.d-script-starts-in-stop-runlevel]]
 * [[Self:Lintian/Tags/init.d-script-provides-virtual-facility|init.d-script-provides-virtual-facility]]
 * [[Self:Lintian/Tags/init.d-script-does-not-provide-itself|init.d-script-does-not-provide-itself]]
 * [[Self:Lintian/Tags/init.d-script-should-depend-on-virtual-facility|init.d-script-should-depend-on-virtual-facility]]
 * [[Self:Lintian/Tags/init.d-script-possible-missing-stop|init.d-script-possible-missing-stop]]
 * [[Self:Lintian/Tags/init.d-script-missing-start|init.d-script-missing-start]]
 * [[Self:Lintian/Tags/init.d-script-missing-dependency-on-remote_fs|init.d-script-missing-dependency-on-remote_fs]]
 * [[Self:Lintian/Tags/init.d-script-missing-dependency-on-local_fs|init.d-script-missing-dependency-on-local_fs]]
 * [[Self:Lintian/Tags/init.d-script-depends-on-unknown-virtual-facility|init.d-script-depends-on-unknown-virtual-facility]]

=== standards-version ===
 * [[Self:Lintian/Tags/no-standards-version-field|no-standards-version-field]]
 * [[Self:Lintian/Tags/invalid-standards-version|invalid-standards-version]]
 * [[Self:Lintian/Tags/newer-standards-version|newer-standards-version]]
 * [[Self:Lintian/Tags/ancient-standards-version|ancient-standards-version]]
 * [[Self:Lintian/Tags/out-of-date-standards-version|out-of-date-standards-version]]
 * [[Self:Lintian/Tags/timewarp-standards-version|timewarp-standards-version]]

=== files ===
 * [[Self:Lintian/Tags/package-contains-ancient-file|package-contains-ancient-file]]
 * [[Self:Lintian/Tags/old-app-defaults-directory|old-app-defaults-directory]]
 * [[Self:Lintian/Tags/package-installs-font-to-usr-x11r6|package-installs-font-to-usr-x11r6]]
 * [[Self:Lintian/Tags/package-installs-file-to-usr-x11r6-bin|package-installs-file-to-usr-x11r6-bin]]
 * [[Self:Lintian/Tags/package-installs-file-to-usr-x11r6|package-installs-file-to-usr-x11r6]]
 * [[Self:Lintian/Tags/config-file-reserved|config-file-reserved]]
 * [[Self:Lintian/Tags/package-uses-obsolete-file|package-uses-obsolete-file]]
 * [[Self:Lintian/Tags/FSSTND-dir-in-usr|FSSTND-dir-in-usr]]
 * [[Self:Lintian/Tags/FSSTND-dir-in-var|FSSTND-dir-in-var]]
 * [[Self:Lintian/Tags/package-installs-into-etc-gconf-schemas|package-installs-into-etc-gconf-schemas]]
 * [[Self:Lintian/Tags/package-installs-into-etc-rc.d|package-installs-into-etc-rc.d]]
 * [[Self:Lintian/Tags/package-installs-into-etc-rc.boot|package-installs-into-etc-rc.boot]]
 * [[Self:Lintian/Tags/non-standard-file-permissions-for-etc-init.d-script|non-standard-file-permissions-for-etc-init.d-script]]
 * [[Self:Lintian/Tags/file-directly-in-usr-share|file-directly-in-usr-share]]
 * [[Self:Lintian/Tags/file-in-usr-local|file-in-usr-local]]
 * [[Self:Lintian/Tags/stray-directory-in-manpage-directory|stray-directory-in-manpage-directory]]
 * [[Self:Lintian/Tags/executable-manpage|executable-manpage]]
 * [[Self:Lintian/Tags/dir-in-usr-local|dir-in-usr-local]]
 * [[Self:Lintian/Tags/non-standard-dir-perm|non-standard-dir-perm]]
 * [[Self:Lintian/Tags/executable-is-not-world-readable|executable-is-not-world-readable]]
 * [[Self:Lintian/Tags/non-standard-executable-perm|non-standard-executable-perm]]
 * [[Self:Lintian/Tags/non-standard-game-executable-perm|non-standard-game-executable-perm]]
 * [[Self:Lintian/Tags/non-standard-setuid-executable-perm|non-standard-setuid-executable-perm]]
 * [[Self:Lintian/Tags/setuid-binary|setuid-binary]]
 * [[Self:Lintian/Tags/setgid-binary|setgid-binary]]
 * [[Self:Lintian/Tags/setuid-gid-binary|setuid-gid-binary]]
 * [[Self:Lintian/Tags/non-standard-file-perm|non-standard-file-perm]]
 * [[Self:Lintian/Tags/special-file|special-file]]
 * [[Self:Lintian/Tags/old-style-example-dir|old-style-example-dir]]
 * [[Self:Lintian/Tags/compressed-symlink-with-wrong-ext|compressed-symlink-with-wrong-ext]]
 * [[Self:Lintian/Tags/symlink-has-double-slash|symlink-has-double-slash]]
 * [[Self:Lintian/Tags/symlink-ends-with-slash|symlink-ends-with-slash]]
 * [[Self:Lintian/Tags/symlink-should-be-relative|symlink-should-be-relative]]
 * [[Self:Lintian/Tags/symlink-should-be-absolute|symlink-should-be-absolute]]
 * [[Self:Lintian/Tags/udeb-contains-documentation-file|udeb-contains-documentation-file]]
 * [[Self:Lintian/Tags/executable-in-usr-share-doc|executable-in-usr-share-doc]]
 * [[Self:Lintian/Tags/script-in-usr-share-doc|script-in-usr-share-doc]]
 * [[Self:Lintian/Tags/symlink-has-too-many-up-segments|symlink-has-too-many-up-segments]]
 * [[Self:Lintian/Tags/lengthy-symlink|lengthy-symlink]]
 * [[Self:Lintian/Tags/symlink-is-self-recursive|symlink-is-self-recursive]]
 * [[Self:Lintian/Tags/symlink-contains-spurious-segments|symlink-contains-spurious-segments]]
 * [[Self:Lintian/Tags/run-parts-cron-filename-contains-full-stop|run-parts-cron-filename-contains-full-stop]]
 * [[Self:Lintian/Tags/bad-permissions-for-etc-cron.d-script|bad-permissions-for-etc-cron.d-script]]
 * [[Self:Lintian/Tags/bad-permissions-for-etc-emacs-script|bad-permissions-for-etc-emacs-script]]
 * [[Self:Lintian/Tags/image-file-in-usr-lib|image-file-in-usr-lib]]
 * [[Self:Lintian/Tags/file-directly-in-usr-share-doc|file-directly-in-usr-share-doc]]
 * [[Self:Lintian/Tags/bad-owner-for-doc-file|bad-owner-for-doc-file]]
 * [[Self:Lintian/Tags/dir-or-file-in-var-lock|dir-or-file-in-var-lock]]
 * [[Self:Lintian/Tags/dir-or-file-in-var-run|dir-or-file-in-var-run]]
 * [[Self:Lintian/Tags/dir-or-file-in-var-www|dir-or-file-in-var-www]]
 * [[Self:Lintian/Tags/dir-or-file-in-tmp|dir-or-file-in-tmp]]
 * [[Self:Lintian/Tags/dir-or-file-in-mnt|dir-or-file-in-mnt]]
 * [[Self:Lintian/Tags/dir-or-file-in-opt|dir-or-file-in-opt]]
 * [[Self:Lintian/Tags/dir-or-file-in-srv|dir-or-file-in-srv]]
 * [[Self:Lintian/Tags/third-party-package-in-python-dir|third-party-package-in-python-dir]]
 * [[Self:Lintian/Tags/perl-module-in-core-directory|perl-module-in-core-directory]]
 * [[Self:Lintian/Tags/backup-file-in-package|backup-file-in-package]]
 * [[Self:Lintian/Tags/nfs-temporary-file-in-package|nfs-temporary-file-in-package]]
 * [[Self:Lintian/Tags/windows-thumbnail-database-in-package|windows-thumbnail-database-in-package]]
 * [[Self:Lintian/Tags/macos-ds-store-file-in-package|macos-ds-store-file-in-package]]
 * [[Self:Lintian/Tags/macos-resource-fork-file-in-package|macos-resource-fork-file-in-package]]
 * [[Self:Lintian/Tags/package-installs-perllocal-pod|package-installs-perllocal-pod]]
 * [[Self:Lintian/Tags/extra-license-file|extra-license-file]]
 * [[Self:Lintian/Tags/non-standard-toplevel-dir|non-standard-toplevel-dir]]
 * [[Self:Lintian/Tags/subdir-in-bin|subdir-in-bin]]
 * [[Self:Lintian/Tags/subdir-in-usr-bin|subdir-in-usr-bin]]
 * [[Self:Lintian/Tags/non-standard-dir-in-usr|non-standard-dir-in-usr]]
 * [[Self:Lintian/Tags/non-standard-dir-in-var|non-standard-dir-in-var]]
 * [[Self:Lintian/Tags/use-of-compat-symlink|use-of-compat-symlink]]
 * [[Self:Lintian/Tags/file-in-unusual-dir|file-in-unusual-dir]]
 * [[Self:Lintian/Tags/package-installs-packlist|package-installs-packlist]]
 * [[Self:Lintian/Tags/zero-byte-file-in-doc-directory|zero-byte-file-in-doc-directory]]
 * [[Self:Lintian/Tags/override-file-in-wrong-location|override-file-in-wrong-location]]
 * [[Self:Lintian/Tags/package-contains-upstream-install-documentation|package-contains-upstream-install-documentation]]
 * [[Self:Lintian/Tags/package-contains-hardlink|package-contains-hardlink]]
 * [[Self:Lintian/Tags/package-contains-bts-control-dir|package-contains-bts-control-dir]]
 * [[Self:Lintian/Tags/package-contains-vcs-control-dir|package-contains-vcs-control-dir]]
 * [[Self:Lintian/Tags/package-contains-xvpics-dir|package-contains-xvpics-dir]]
 * [[Self:Lintian/Tags/package-contains-vcs-control-file|package-contains-vcs-control-file]]
 * [[Self:Lintian/Tags/svn-commit-file-in-package|svn-commit-file-in-package]]
 * [[Self:Lintian/Tags/svk-commit-file-in-package|svk-commit-file-in-package]]
 * [[Self:Lintian/Tags/nested-examples-directory|nested-examples-directory]]
 * [[Self:Lintian/Tags/package-installs-nonbinary-perl-in-usr-lib-perl5|package-installs-nonbinary-perl-in-usr-lib-perl5]]
 * [[Self:Lintian/Tags/file-in-usr-lib-site-python|file-in-usr-lib-site-python]]
 * [[Self:Lintian/Tags/package-installs-python-pyc|package-installs-python-pyc]]
 * [[Self:Lintian/Tags/bad-permissions-for-ali-file|bad-permissions-for-ali-file]]
 * [[Self:Lintian/Tags/package-contains-readme-for-other-platform-or-distro|package-contains-readme-for-other-platform-or-distro]]
 * [[Self:Lintian/Tags/desktop-file-in-wrong-dir|desktop-file-in-wrong-dir]]
 * [[Self:Lintian/Tags/script-with-language-extension|script-with-language-extension]]
 * [[Self:Lintian/Tags/file-in-usr-lib-sgml|file-in-usr-lib-sgml]]
 * [[Self:Lintian/Tags/file-name-ends-in-whitespace|file-name-ends-in-whitespace]]
 * [[Self:Lintian/Tags/package-contains-empty-directory|package-contains-empty-directory]]
 * [[Self:Lintian/Tags/package-section-games-but-contains-no-game|package-section-games-but-contains-no-game]]
 * [[Self:Lintian/Tags/package-section-games-but-has-usr-bin|package-section-games-but-has-usr-bin]]
 * [[Self:Lintian/Tags/games-package-should-be-section-games|games-package-should-be-section-games]]
 * [[Self:Lintian/Tags/package-contains-devhelp-file-without-symlink|package-contains-devhelp-file-without-symlink]]
 * [[Self:Lintian/Tags/debug-package-should-be-named-dbg|debug-package-should-be-named-dbg]]
 * [[Self:Lintian/Tags/package-contains-linda-override|package-contains-linda-override]]
 * [[Self:Lintian/Tags/wrong-file-owner-uid-or-gid|wrong-file-owner-uid-or-gid]]
 * [[Self:Lintian/Tags/embedded-javascript-library|embedded-javascript-library]]
 * [[Self:Lintian/Tags/embedded-feedparser-library|embedded-feedparser-library]]
 * [[Self:Lintian/Tags/embedded-pear-module|embedded-pear-module]]
 * [[Self:Lintian/Tags/embedded-php-library|embedded-php-library]]
 * [[Self:Lintian/Tags/windows-devel-file-in-package|windows-devel-file-in-package]]
 * [[Self:Lintian/Tags/font-in-non-font-package|font-in-non-font-package]]
 * [[Self:Lintian/Tags/duplicate-font-file|duplicate-font-file]]
 * [[Self:Lintian/Tags/icon-size-and-directory-name-mismatch|icon-size-and-directory-name-mismatch]]
 * [[Self:Lintian/Tags/gz-file-not-gzip|gz-file-not-gzip]]
 * [[Self:Lintian/Tags/non-free-flash|non-free-flash]]
 * [[Self:Lintian/Tags/non-conf-file-in-modprobe.d|non-conf-file-in-modprobe.d]]
 * [[Self:Lintian/Tags/file-in-discouraged-x11-font-directory|file-in-discouraged-x11-font-directory]]
 * [[Self:Lintian/Tags/file-in-unknown-x11-font-directory|file-in-unknown-x11-font-directory]]
 * [[Self:Lintian/Tags/package-contains-multiple-dpi-fonts|package-contains-multiple-dpi-fonts]]
 * [[Self:Lintian/Tags/package-mixes-misc-and-dpi-fonts|package-mixes-misc-and-dpi-fonts]]
 * [[Self:Lintian/Tags/package-contains-info-dir-file|package-contains-info-dir-file]]
 * [[Self:Lintian/Tags/package-contains-mime-cache-file|package-contains-mime-cache-file]]
 * [[Self:Lintian/Tags/package-contains-mimeinfo.cache-file|package-contains-mimeinfo.cache-file]]
 * [[Self:Lintian/Tags/package-modifies-ld.so-search-path|package-modifies-ld.so-search-path]]
 * [[Self:Lintian/Tags/global-data-in-games-directory|global-data-in-games-directory]]
 * [[Self:Lintian/Tags/duplicated-compressed-file|duplicated-compressed-file]]
 * [[Self:Lintian/Tags/udev-rule-in-etc|udev-rule-in-etc]]
 * [[Self:Lintian/Tags/obsolete-comments-style-in-php-ini|obsolete-comments-style-in-php-ini]]
 * [[Self:Lintian/Tags/triplet-dir-and-architecture-mismatch|triplet-dir-and-architecture-mismatch]]
 * [[Self:Lintian/Tags/empty-binary-package|empty-binary-package]]
 * [[Self:Lintian/Tags/star-file|star-file]]
 * [[Self:Lintian/Tags/incorrect-locale-code|incorrect-locale-code]]
 * [[Self:Lintian/Tags/unknown-locale-code|unknown-locale-code]]

=== nmu ===
 * [[Self:Lintian/Tags/orphaned-package-should-not-have-uploaders|orphaned-package-should-not-have-uploaders]]
 * [[Self:Lintian/Tags/qa-upload-has-incorrect-version-number|qa-upload-has-incorrect-version-number]]
 * [[Self:Lintian/Tags/team-upload-has-incorrect-version-number|team-upload-has-incorrect-version-number]]
 * [[Self:Lintian/Tags/source-nmu-has-incorrect-version-number|source-nmu-has-incorrect-version-number]]
 * [[Self:Lintian/Tags/maintainer-upload-has-incorrect-version-number|maintainer-upload-has-incorrect-version-number]]
 * [[Self:Lintian/Tags/changelog-should-mention-qa|changelog-should-mention-qa]]
 * [[Self:Lintian/Tags/changelog-should-mention-nmu|changelog-should-mention-nmu]]
 * [[Self:Lintian/Tags/changelog-should-not-mention-nmu|changelog-should-not-mention-nmu]]
 * [[Self:Lintian/Tags/changelog-is-symlink|changelog-is-symlink]]

=== description ===
 * [[Self:Lintian/Tags/package-has-no-description|package-has-no-description]]
 * [[Self:Lintian/Tags/description-synopsis-is-empty|description-synopsis-is-empty]]
 * [[Self:Lintian/Tags/extended-description-is-empty|extended-description-is-empty]]
 * [[Self:Lintian/Tags/extended-description-is-probably-too-short|extended-description-is-probably-too-short]]
 * [[Self:Lintian/Tags/description-contains-invalid-control-statement|description-contains-invalid-control-statement]]
 * [[Self:Lintian/Tags/description-too-long|description-too-long]]
 * [[Self:Lintian/Tags/description-starts-with-package-name|description-starts-with-package-name]]
 * [[Self:Lintian/Tags/description-contains-tabs|description-contains-tabs]]
 * [[Self:Lintian/Tags/description-starts-with-leading-spaces|description-starts-with-leading-spaces]]
 * [[Self:Lintian/Tags/possible-unindented-list-in-extended-description|possible-unindented-list-in-extended-description]]
 * [[Self:Lintian/Tags/description-is-debmake-template|description-is-debmake-template]]
 * [[Self:Lintian/Tags/description-is-dh_make-template|description-is-dh_make-template]]
 * [[Self:Lintian/Tags/description-contains-dh-make-perl-template|description-contains-dh-make-perl-template]]
 * [[Self:Lintian/Tags/description-synopsis-might-not-be-phrased-properly|description-synopsis-might-not-be-phrased-properly]]
 * [[Self:Lintian/Tags/description-synopsis-is-duplicated|description-synopsis-is-duplicated]]
 * [[Self:Lintian/Tags/extended-description-line-too-long|extended-description-line-too-long]]
 * [[Self:Lintian/Tags/description-contains-homepage|description-contains-homepage]]
 * [[Self:Lintian/Tags/spelling-error-in-description|spelling-error-in-description]]
 * [[Self:Lintian/Tags/capitalization-error-in-description|capitalization-error-in-description]]
 * [[Self:Lintian/Tags/description-contains-duplicated-word|description-contains-duplicated-word]]
 * [[Self:Lintian/Tags/using-first-person-in-description|using-first-person-in-description]]
 * [[Self:Lintian/Tags/description-possibly-contains-homepage|description-possibly-contains-homepage]]

=== rules ===
 * [[Self:Lintian/Tags/debian-rules-is-symlink|debian-rules-is-symlink]]
 * [[Self:Lintian/Tags/debian-rules-not-a-makefile|debian-rules-not-a-makefile]]
 * [[Self:Lintian/Tags/debian-rules-missing-required-target|debian-rules-missing-required-target]]
 * [[Self:Lintian/Tags/debian-rules-uses-pwd|debian-rules-uses-pwd]]
 * [[Self:Lintian/Tags/debian-rules-ignores-make-clean-error|debian-rules-ignores-make-clean-error]]
 * [[Self:Lintian/Tags/debian-rules-uses-DEB_BUILD_OPTS|debian-rules-uses-DEB_BUILD_OPTS]]
 * [[Self:Lintian/Tags/debian-rules-automatically-updates-control|debian-rules-automatically-updates-control]]
 * [[Self:Lintian/Tags/debian-rules-sets-DH_COMPAT|debian-rules-sets-DH_COMPAT]]
 * [[Self:Lintian/Tags/binary-arch-rules-but-pkg-is-arch-indep|binary-arch-rules-but-pkg-is-arch-indep]]
 * [[Self:Lintian/Tags/debian-rules-calls-debhelper-in-odd-order|debian-rules-calls-debhelper-in-odd-order]]
 * [[Self:Lintian/Tags/missing-build-dependency|missing-build-dependency]]
 * [[Self:Lintian/Tags/missing-python-build-dependency|missing-python-build-dependency]]
 * [[Self:Lintian/Tags/missing-dh_python-build-dependency|missing-dh_python-build-dependency]]
 * [[Self:Lintian/Tags/clean-should-be-satisfied-by-build-depends|clean-should-be-satisfied-by-build-depends]]
 * [[Self:Lintian/Tags/debian-rules-makemaker-prefix-is-deprecated|debian-rules-makemaker-prefix-is-deprecated]]

=== conffiles ===
 * [[Self:Lintian/Tags/file-in-usr-marked-as-conffile|file-in-usr-marked-as-conffile]]
 * [[Self:Lintian/Tags/non-etc-file-marked-as-conffile|non-etc-file-marked-as-conffile]]
 * [[Self:Lintian/Tags/relative-conffile|relative-conffile]]
 * [[Self:Lintian/Tags/duplicate-conffile|duplicate-conffile]]

=== debhelper ===
 * [[Self:Lintian/Tags/maintainer-script-lacks-debhelper-token|maintainer-script-lacks-debhelper-token]]
 * [[Self:Lintian/Tags/package-uses-debhelper-but-lacks-build-depends|package-uses-debhelper-but-lacks-build-depends]]
 * [[Self:Lintian/Tags/package-lacks-versioned-build-depends-on-debhelper|package-lacks-versioned-build-depends-on-debhelper]]
 * [[Self:Lintian/Tags/dh-make-template-in-source|dh-make-template-in-source]]
 * [[Self:Lintian/Tags/dh_dhelp-is-deprecated|dh_dhelp-is-deprecated]]
 * [[Self:Lintian/Tags/dh_suidregister-is-obsolete|dh_suidregister-is-obsolete]]
 * [[Self:Lintian/Tags/dh_undocumented-is-obsolete|dh_undocumented-is-obsolete]]
 * [[Self:Lintian/Tags/dh_desktop-is-deprecated|dh_desktop-is-deprecated]]
 * [[Self:Lintian/Tags/dh_scrollkeeper-is-deprecated|dh_scrollkeeper-is-deprecated]]
 * [[Self:Lintian/Tags/dh-clean-k-is-deprecated|dh-clean-k-is-deprecated]]
 * [[Self:Lintian/Tags/debhelper-compat-file-is-empty|debhelper-compat-file-is-empty]]
 * [[Self:Lintian/Tags/declares-possibly-conflicting-debhelper-compat-versions|declares-possibly-conflicting-debhelper-compat-versions]]
 * [[Self:Lintian/Tags/package-uses-deprecated-debhelper-compat-version|package-uses-deprecated-debhelper-compat-version]]
 * [[Self:Lintian/Tags/uses-dh-python-with-no-pycompat|uses-dh-python-with-no-pycompat]]
 * [[Self:Lintian/Tags/debhelper-but-no-misc-depends|debhelper-but-no-misc-depends]]
 * [[Self:Lintian/Tags/missing-build-dependency-for-dh_-command|missing-build-dependency-for-dh_-command]]
 * [[Self:Lintian/Tags/debhelper-script-needs-versioned-build-depends|debhelper-script-needs-versioned-build-depends]]
 * [[Self:Lintian/Tags/debhelper-overrides-need-versioned-build-depends|debhelper-overrides-need-versioned-build-depends]]
 * [[Self:Lintian/Tags/brace-expansion-in-debhelper-config-file|brace-expansion-in-debhelper-config-file]]
 * [[Self:Lintian/Tags/weak-dependency-on-misc-depends|weak-dependency-on-misc-depends]]
 * [[Self:Lintian/Tags/debhelper-compat-not-a-number|debhelper-compat-not-a-number]]
 * [[Self:Lintian/Tags/debhelper-compatibility-level-not-a-number|debhelper-compatibility-level-not-a-number]]

=== manpages ===
 * [[Self:Lintian/Tags/bad-link-to-undocumented-manpage|bad-link-to-undocumented-manpage]]
 * [[Self:Lintian/Tags/link-to-undocumented-manpage|link-to-undocumented-manpage]]
 * [[Self:Lintian/Tags/binary-without-manpage|binary-without-manpage]]
 * [[Self:Lintian/Tags/manpage-in-wrong-directory|manpage-in-wrong-directory]]
 * [[Self:Lintian/Tags/manpage-has-wrong-extension|manpage-has-wrong-extension]]
 * [[Self:Lintian/Tags/manpage-not-compressed|manpage-not-compressed]]
 * [[Self:Lintian/Tags/x11-games-should-be-in-usr-games|x11-games-should-be-in-usr-games]]
 * [[Self:Lintian/Tags/manpage-not-compressed-with-gzip|manpage-not-compressed-with-gzip]]
 * [[Self:Lintian/Tags/manpage-not-compressed-with-max-compression|manpage-not-compressed-with-max-compression]]
 * [[Self:Lintian/Tags/manpage-has-bad-whatis-entry|manpage-has-bad-whatis-entry]]
 * [[Self:Lintian/Tags/manpage-has-useless-whatis-entry|manpage-has-useless-whatis-entry]]
 * [[Self:Lintian/Tags/manpage-is-dh_make-template|manpage-is-dh_make-template]]
 * [[Self:Lintian/Tags/manpage-has-errors-from-man|manpage-has-errors-from-man]]
 * [[Self:Lintian/Tags/manpage-has-errors-from-pod2man|manpage-has-errors-from-pod2man]]
 * [[Self:Lintian/Tags/manpage-for-x11-binary-in-wrong-directory|manpage-for-x11-binary-in-wrong-directory]]
 * [[Self:Lintian/Tags/manpage-for-non-x11-binary-in-wrong-directory|manpage-for-non-x11-binary-in-wrong-directory]]
 * [[Self:Lintian/Tags/bad-so-link-within-manual-page|bad-so-link-within-manual-page]]
 * [[Self:Lintian/Tags/empty-manual-page|empty-manual-page]]
 * [[Self:Lintian/Tags/manpage-section-mismatch|manpage-section-mismatch]]
 * [[Self:Lintian/Tags/hyphen-used-as-minus-sign|hyphen-used-as-minus-sign]]
 * [[Self:Lintian/Tags/FSSTND-dir-in-manual-page|FSSTND-dir-in-manual-page]]
 * [[Self:Lintian/Tags/binary-without-english-manpage|binary-without-english-manpage]]
 * [[Self:Lintian/Tags/manpage-locale-dir-country-specific|manpage-locale-dir-country-specific]]
 * [[Self:Lintian/Tags/spelling-error-in-manpage|spelling-error-in-manpage]]

=== scripts ===
 * [[Self:Lintian/Tags/script-without-interpreter|script-without-interpreter]]
 * [[Self:Lintian/Tags/example-script-without-interpreter|example-script-without-interpreter]]
 * [[Self:Lintian/Tags/executable-not-elf-or-script|executable-not-elf-or-script]]
 * [[Self:Lintian/Tags/script-not-executable|script-not-executable]]
 * [[Self:Lintian/Tags/interpreter-not-absolute|interpreter-not-absolute]]
 * [[Self:Lintian/Tags/example-interpreter-not-absolute|example-interpreter-not-absolute]]
 * [[Self:Lintian/Tags/unusual-interpreter|unusual-interpreter]]
 * [[Self:Lintian/Tags/example-unusual-interpreter|example-unusual-interpreter]]
 * [[Self:Lintian/Tags/script-uses-bin-env|script-uses-bin-env]]
 * [[Self:Lintian/Tags/example-script-uses-bin-env|example-script-uses-bin-env]]
 * [[Self:Lintian/Tags/forbidden-config-interpreter|forbidden-config-interpreter]]
 * [[Self:Lintian/Tags/forbidden-postrm-interpreter|forbidden-postrm-interpreter]]
 * [[Self:Lintian/Tags/unusual-control-interpreter|unusual-control-interpreter]]
 * [[Self:Lintian/Tags/unknown-control-interpreter|unknown-control-interpreter]]
 * [[Self:Lintian/Tags/interpreter-in-usr-local|interpreter-in-usr-local]]
 * [[Self:Lintian/Tags/example-interpreter-in-usr-local|example-interpreter-in-usr-local]]
 * [[Self:Lintian/Tags/control-interpreter-in-usr-local|control-interpreter-in-usr-local]]
 * [[Self:Lintian/Tags/preinst-interpreter-without-predepends|preinst-interpreter-without-predepends]]
 * [[Self:Lintian/Tags/control-interpreter-without-depends|control-interpreter-without-depends]]
 * [[Self:Lintian/Tags/missing-dep-for-interpreter|missing-dep-for-interpreter]]
 * [[Self:Lintian/Tags/csh-considered-harmful|csh-considered-harmful]]
 * [[Self:Lintian/Tags/suid-perl-script-but-no-perl-suid-dep|suid-perl-script-but-no-perl-suid-dep]]
 * [[Self:Lintian/Tags/wrong-path-for-interpreter|wrong-path-for-interpreter]]
 * [[Self:Lintian/Tags/example-wrong-path-for-interpreter|example-wrong-path-for-interpreter]]
 * [[Self:Lintian/Tags/gawk-script-but-no-gawk-dep|gawk-script-but-no-gawk-dep]]
 * [[Self:Lintian/Tags/mawk-script-but-no-mawk-dep|mawk-script-but-no-mawk-dep]]
 * [[Self:Lintian/Tags/php-script-but-no-phpX-cli-dep|php-script-but-no-phpX-cli-dep]]
 * [[Self:Lintian/Tags/python-script-but-no-python-dep|python-script-but-no-python-dep]]
 * [[Self:Lintian/Tags/ruby-script-but-no-ruby-dep|ruby-script-but-no-ruby-dep]]
 * [[Self:Lintian/Tags/wish-script-but-no-wish-dep|wish-script-but-no-wish-dep]]
 * [[Self:Lintian/Tags/tclsh-script-but-no-tclsh-dep|tclsh-script-but-no-tclsh-dep]]
 * [[Self:Lintian/Tags/calls-suidperl-directly|calls-suidperl-directly]]
 * [[Self:Lintian/Tags/shell-script-fails-syntax-check|shell-script-fails-syntax-check]]
 * [[Self:Lintian/Tags/example-shell-script-fails-syntax-check|example-shell-script-fails-syntax-check]]
 * [[Self:Lintian/Tags/maintainer-shell-script-fails-syntax-check|maintainer-shell-script-fails-syntax-check]]
 * [[Self:Lintian/Tags/possibly-insecure-handling-of-tmp-files-in-maintainer-script|possibly-insecure-handling-of-tmp-files-in-maintainer-script]]
 * [[Self:Lintian/Tags/killall-is-dangerous|killall-is-dangerous]]
 * [[Self:Lintian/Tags/mknod-in-maintainer-script|mknod-in-maintainer-script]]
 * [[Self:Lintian/Tags/start-stop-daemon-in-maintainer-script|start-stop-daemon-in-maintainer-script]]
 * [[Self:Lintian/Tags/maintainer-script-removes-device-files|maintainer-script-removes-device-files]]
 * [[Self:Lintian/Tags/read-in-maintainer-script|read-in-maintainer-script]]
 * [[Self:Lintian/Tags/possible-bashism-in-maintainer-script|possible-bashism-in-maintainer-script]]
 * [[Self:Lintian/Tags/suidregister-used-in-maintainer-script|suidregister-used-in-maintainer-script]]
 * [[Self:Lintian/Tags/maintainer-script-needs-depends-on-update-inetd|maintainer-script-needs-depends-on-update-inetd]]
 * [[Self:Lintian/Tags/maintainer-script-needs-depends-on-adduser|maintainer-script-needs-depends-on-adduser]]
 * [[Self:Lintian/Tags/maintainer-script-needs-depends-on-gconf2|maintainer-script-needs-depends-on-gconf2]]
 * [[Self:Lintian/Tags/maintainer-script-needs-depends-on-ucf|maintainer-script-needs-depends-on-ucf]]
 * [[Self:Lintian/Tags/maintainer-script-needs-depends-on-xml-core|maintainer-script-needs-depends-on-xml-core]]
 * [[Self:Lintian/Tags/update-alternatives-remove-called-in-postrm|update-alternatives-remove-called-in-postrm]]
 * [[Self:Lintian/Tags/deprecated-chown-usage|deprecated-chown-usage]]
 * [[Self:Lintian/Tags/maintainer-script-hides-init-failure|maintainer-script-hides-init-failure]]
 * [[Self:Lintian/Tags/maintainer-script-calls-init-script-directly|maintainer-script-calls-init-script-directly]]
 * [[Self:Lintian/Tags/script-calls-init-script-directly|script-calls-init-script-directly]]
 * [[Self:Lintian/Tags/gconftool-used-in-maintainer-script|gconftool-used-in-maintainer-script]]
 * [[Self:Lintian/Tags/fc-cache-used-in-maintainer-script|fc-cache-used-in-maintainer-script]]
 * [[Self:Lintian/Tags/install-info-used-in-maintainer-script|install-info-used-in-maintainer-script]]
 * [[Self:Lintian/Tags/maintainer-script-uses-dpkg-status-directly|maintainer-script-uses-dpkg-status-directly]]
 * [[Self:Lintian/Tags/maintainer-script-modifies-netbase-managed-file|maintainer-script-modifies-netbase-managed-file]]
 * [[Self:Lintian/Tags/maintainer-script-modifies-inetd-conf|maintainer-script-modifies-inetd-conf]]
 * [[Self:Lintian/Tags/maintainer-script-modifies-ld-so-conf|maintainer-script-modifies-ld-so-conf]]
 * [[Self:Lintian/Tags/install-sgmlcatalog-deprecated|install-sgmlcatalog-deprecated]]
 * [[Self:Lintian/Tags/maintainer-script-empty|maintainer-script-empty]]
 * [[Self:Lintian/Tags/maintainer-script-ignores-errors|maintainer-script-ignores-errors]]
 * [[Self:Lintian/Tags/maintainer-script-without-set-e|maintainer-script-without-set-e]]
 * [[Self:Lintian/Tags/command-with-path-in-maintainer-script|command-with-path-in-maintainer-script]]
 * [[Self:Lintian/Tags/ancient-dpkg-predepends-check|ancient-dpkg-predepends-check]]
 * [[Self:Lintian/Tags/ancient-dpkg-epoch-check|ancient-dpkg-epoch-check]]
 * [[Self:Lintian/Tags/ancient-dpkg-long-filenames-check|ancient-dpkg-long-filenames-check]]
 * [[Self:Lintian/Tags/ancient-dpkg-multi-conrep-check|ancient-dpkg-multi-conrep-check]]
 * [[Self:Lintian/Tags/package-uses-local-diversion|package-uses-local-diversion]]
 * [[Self:Lintian/Tags/diversion-for-unknown-file|diversion-for-unknown-file]]
 * [[Self:Lintian/Tags/orphaned-diversion|orphaned-diversion]]
 * [[Self:Lintian/Tags/remove-of-unknown-diversion|remove-of-unknown-diversion]]

=== changes-file ===
 * [[Self:Lintian/Tags/malformed-changes-file|malformed-changes-file]]
 * [[Self:Lintian/Tags/no-description-in-changes-file|no-description-in-changes-file]]
 * [[Self:Lintian/Tags/bad-distribution-in-changes-file|bad-distribution-in-changes-file]]
 * [[Self:Lintian/Tags/bad-ubuntu-distribution-in-changes-file|bad-ubuntu-distribution-in-changes-file]]
 * [[Self:Lintian/Tags/multiple-distributions-in-changes-file|multiple-distributions-in-changes-file]]
 * [[Self:Lintian/Tags/no-urgency-in-changes-file|no-urgency-in-changes-file]]
 * [[Self:Lintian/Tags/bad-urgency-in-changes-file|bad-urgency-in-changes-file]]
 * [[Self:Lintian/Tags/file-size-mismatch-in-changes-file|file-size-mismatch-in-changes-file]]
 * [[Self:Lintian/Tags/checksum-mismatch-in-changes-file|checksum-mismatch-in-changes-file]]
 * [[Self:Lintian/Tags/bad-section-in-changes-file|bad-section-in-changes-file]]
 * [[Self:Lintian/Tags/changed-by-name-missing|changed-by-name-missing]]
 * [[Self:Lintian/Tags/changed-by-address-missing|changed-by-address-missing]]
 * [[Self:Lintian/Tags/changed-by-address-malformed|changed-by-address-malformed]]
 * [[Self:Lintian/Tags/changed-by-address-looks-weird|changed-by-address-looks-weird]]
 * [[Self:Lintian/Tags/changed-by-address-is-on-localhost|changed-by-address-is-on-localhost]]

=== control-files ===
 * [[Self:Lintian/Tags/unknown-control-file|unknown-control-file]]
 * [[Self:Lintian/Tags/not-allowed-control-file|not-allowed-control-file]]
 * [[Self:Lintian/Tags/control-file-is-empty|control-file-is-empty]]
 * [[Self:Lintian/Tags/control-file-has-bad-permissions|control-file-has-bad-permissions]]
 * [[Self:Lintian/Tags/control-file-has-bad-owner|control-file-has-bad-owner]]

=== menu-format ===
 * [[Self:Lintian/Tags/old-format-menu-file|old-format-menu-file]]
 * [[Self:Lintian/Tags/whitespace-after-continuation-character|whitespace-after-continuation-character]]
 * [[Self:Lintian/Tags/bad-test-in-menu-item|bad-test-in-menu-item]]
 * [[Self:Lintian/Tags/unparsable-menu-item|unparsable-menu-item]]
 * [[Self:Lintian/Tags/pkg-not-in-package-test|pkg-not-in-package-test]]
 * [[Self:Lintian/Tags/duplicated-tag-in-menu-item|duplicated-tag-in-menu-item]]
 * [[Self:Lintian/Tags/menu-item-missing-required-tag|menu-item-missing-required-tag]]
 * [[Self:Lintian/Tags/menu-item-contains-unknown-tag|menu-item-contains-unknown-tag]]
 * [[Self:Lintian/Tags/menu-item-uses-icon-none|menu-item-uses-icon-none]]
 * [[Self:Lintian/Tags/menu-item-needs-tag-has-unknown-value|menu-item-needs-tag-has-unknown-value]]
 * [[Self:Lintian/Tags/menu-item-uses-apps-games-section|menu-item-uses-apps-games-section]]
 * [[Self:Lintian/Tags/menu-item-uses-apps-section|menu-item-uses-apps-section]]
 * [[Self:Lintian/Tags/menu-item-uses-windowmanagers-section|menu-item-uses-windowmanagers-section]]
 * [[Self:Lintian/Tags/menu-item-creates-new-section|menu-item-creates-new-section]]
 * [[Self:Lintian/Tags/menu-item-creates-new-root-section|menu-item-creates-new-root-section]]
 * [[Self:Lintian/Tags/menu-icon-not-in-xpm-format|menu-icon-not-in-xpm-format]]
 * [[Self:Lintian/Tags/menu-icon-missing|menu-icon-missing]]
 * [[Self:Lintian/Tags/menu-icon-too-big|menu-icon-too-big]]
 * [[Self:Lintian/Tags/menu-icon-cannot-be-parsed|menu-icon-cannot-be-parsed]]
 * [[Self:Lintian/Tags/su-wrapper-without--c|su-wrapper-without--c]]
 * [[Self:Lintian/Tags/su-to-root-with-usr-sbin|su-to-root-with-usr-sbin]]
 * [[Self:Lintian/Tags/su-wrapper-not-su-to-root|su-wrapper-not-su-to-root]]
 * [[Self:Lintian/Tags/menu-item-needs-dwww|menu-item-needs-dwww]]
 * [[Self:Lintian/Tags/non-wm-in-windowmanager-menu-section|non-wm-in-windowmanager-menu-section]]
 * [[Self:Lintian/Tags/non-wm-module-in-wm-modules-menu-section|non-wm-module-in-wm-modules-menu-section]]
 * [[Self:Lintian/Tags/unquoted-string-in-menu-item|unquoted-string-in-menu-item]]
 * [[Self:Lintian/Tags/menu-command-not-in-package|menu-command-not-in-package]]
 * [[Self:Lintian/Tags/executable-desktop-file|executable-desktop-file]]
 * [[Self:Lintian/Tags/desktop-entry-file-has-crs|desktop-entry-file-has-crs]]
 * [[Self:Lintian/Tags/duplicated-key-in-desktop-entry|duplicated-key-in-desktop-entry]]
 * [[Self:Lintian/Tags/desktop-entry-missing-required-key|desktop-entry-missing-required-key]]
 * [[Self:Lintian/Tags/desktop-entry-contains-unknown-key|desktop-entry-contains-unknown-key]]
 * [[Self:Lintian/Tags/desktop-entry-contains-deprecated-key|desktop-entry-contains-deprecated-key]]
 * [[Self:Lintian/Tags/desktop-entry-contains-encoding-key|desktop-entry-contains-encoding-key]]
 * [[Self:Lintian/Tags/desktop-entry-lacks-main-category|desktop-entry-lacks-main-category]]
 * [[Self:Lintian/Tags/desktop-entry-uses-reserved-category|desktop-entry-uses-reserved-category]]
 * [[Self:Lintian/Tags/desktop-entry-invalid-category|desktop-entry-invalid-category]]
 * [[Self:Lintian/Tags/desktop-command-not-in-package|desktop-command-not-in-package]]
 * [[Self:Lintian/Tags/desktop-contains-deprecated-header|desktop-contains-deprecated-header]]
 * [[Self:Lintian/Tags/deprecated-kdelnk-file|deprecated-kdelnk-file]]
 * [[Self:Lintian/Tags/desktop-entry-limited-to-environments|desktop-entry-limited-to-environments]]

=== watch-file ===
 * [[Self:Lintian/Tags/debian-watch-file-is-missing|debian-watch-file-is-missing]]
 * [[Self:Lintian/Tags/debian-watch-file-declares-multiple-versions|debian-watch-file-declares-multiple-versions]]
 * [[Self:Lintian/Tags/debian-watch-file-unknown-version|debian-watch-file-unknown-version]]
 * [[Self:Lintian/Tags/debian-watch-file-missing-version|debian-watch-file-missing-version]]
 * [[Self:Lintian/Tags/debian-watch-file-should-mangle-version|debian-watch-file-should-mangle-version]]
 * [[Self:Lintian/Tags/debian-watch-file-should-dversionmangle-not-uversionmangle|debian-watch-file-should-dversionmangle-not-uversionmangle]]
 * [[Self:Lintian/Tags/debian-watch-file-should-uversionmangle-not-dversionmangle|debian-watch-file-should-uversionmangle-not-dversionmangle]]
 * [[Self:Lintian/Tags/debian-watch-file-in-native-package|debian-watch-file-in-native-package]]
 * [[Self:Lintian/Tags/debian-watch-file-uses-deprecated-sf-redirector-method|debian-watch-file-uses-deprecated-sf-redirector-method]]
 * [[Self:Lintian/Tags/debian-watch-file-should-use-sf-redirector|debian-watch-file-should-use-sf-redirector]]
 * [[Self:Lintian/Tags/debian-watch-file-specifies-wrong-upstream-version|debian-watch-file-specifies-wrong-upstream-version]]
 * [[Self:Lintian/Tags/debian-watch-file-specifies-old-upstream-version|debian-watch-file-specifies-old-upstream-version]]

=== fields ===
 * [[Self:Lintian/Tags/unsupported-source-format|unsupported-source-format]]
 * [[Self:Lintian/Tags/no-package-name|no-package-name]]
 * [[Self:Lintian/Tags/bad-package-name|bad-package-name]]
 * [[Self:Lintian/Tags/package-not-lowercase|package-not-lowercase]]
 * [[Self:Lintian/Tags/bad-provided-package-name|bad-provided-package-name]]
 * [[Self:Lintian/Tags/no-version-field|no-version-field]]
 * [[Self:Lintian/Tags/bad-version-number|bad-version-number]]
 * [[Self:Lintian/Tags/upstream-version-not-numeric|upstream-version-not-numeric]]
 * [[Self:Lintian/Tags/debian-revision-not-well-formed|debian-revision-not-well-formed]]
 * [[Self:Lintian/Tags/debian-revision-should-not-be-zero|debian-revision-should-not-be-zero]]
 * [[Self:Lintian/Tags/no-architecture-field|no-architecture-field]]
 * [[Self:Lintian/Tags/magic-arch-in-arch-list|magic-arch-in-arch-list]]
 * [[Self:Lintian/Tags/unknown-architecture|unknown-architecture]]
 * [[Self:Lintian/Tags/too-many-architectures|too-many-architectures]]
 * [[Self:Lintian/Tags/arch-wildcard-in-binary-package|arch-wildcard-in-binary-package]]
 * [[Self:Lintian/Tags/aspell-package-not-arch-all|aspell-package-not-arch-all]]
 * [[Self:Lintian/Tags/no-maintainer-field|no-maintainer-field]]
 * [[Self:Lintian/Tags/maintainer-name-missing|maintainer-name-missing]]
 * [[Self:Lintian/Tags/maintainer-address-missing|maintainer-address-missing]]
 * [[Self:Lintian/Tags/maintainer-address-malformed|maintainer-address-malformed]]
 * [[Self:Lintian/Tags/maintainer-not-full-name|maintainer-not-full-name]]
 * [[Self:Lintian/Tags/maintainer-address-looks-weird|maintainer-address-looks-weird]]
 * [[Self:Lintian/Tags/maintainer-address-is-on-localhost|maintainer-address-is-on-localhost]]
 * [[Self:Lintian/Tags/uploader-name-missing|uploader-name-missing]]
 * [[Self:Lintian/Tags/uploader-address-missing|uploader-address-missing]]
 * [[Self:Lintian/Tags/uploader-address-malformed|uploader-address-malformed]]
 * [[Self:Lintian/Tags/uploader-not-full-name|uploader-not-full-name]]
 * [[Self:Lintian/Tags/uploader-address-looks-weird|uploader-address-looks-weird]]
 * [[Self:Lintian/Tags/uploader-address-is-on-localhost|uploader-address-is-on-localhost]]
 * [[Self:Lintian/Tags/wrong-debian-qa-address-set-as-maintainer|wrong-debian-qa-address-set-as-maintainer]]
 * [[Self:Lintian/Tags/wrong-debian-qa-group-name|wrong-debian-qa-group-name]]
 * [[Self:Lintian/Tags/no-human-maintainers|no-human-maintainers]]
 * [[Self:Lintian/Tags/no-source-field|no-source-field]]
 * [[Self:Lintian/Tags/source-field-does-not-match-pkg-name|source-field-does-not-match-pkg-name]]
 * [[Self:Lintian/Tags/source-field-malformed|source-field-malformed]]
 * [[Self:Lintian/Tags/essential-in-source-package|essential-in-source-package]]
 * [[Self:Lintian/Tags/essential-no-not-needed|essential-no-not-needed]]
 * [[Self:Lintian/Tags/unknown-essential-value|unknown-essential-value]]
 * [[Self:Lintian/Tags/no-section-field|no-section-field]]
 * [[Self:Lintian/Tags/unknown-section|unknown-section]]
 * [[Self:Lintian/Tags/section-is-dh_make-template|section-is-dh_make-template]]
 * [[Self:Lintian/Tags/wrong-section-for-udeb|wrong-section-for-udeb]]
 * [[Self:Lintian/Tags/no-priority-field|no-priority-field]]
 * [[Self:Lintian/Tags/unknown-priority|unknown-priority]]
 * [[Self:Lintian/Tags/superfluous-clutter-in-homepage|superfluous-clutter-in-homepage]]
 * [[Self:Lintian/Tags/bad-homepage|bad-homepage]]
 * [[Self:Lintian/Tags/no-homepage-field|no-homepage-field]]
 * [[Self:Lintian/Tags/homepage-for-cpan-package-contains-version|homepage-for-cpan-package-contains-version]]
 * [[Self:Lintian/Tags/obsolete-field|obsolete-field]]
 * [[Self:Lintian/Tags/unknown-field-in-dsc|unknown-field-in-dsc]]
 * [[Self:Lintian/Tags/unknown-field-in-control|unknown-field-in-control]]
 * [[Self:Lintian/Tags/multiline-field|multiline-field]]
 * [[Self:Lintian/Tags/alternates-not-allowed|alternates-not-allowed]]
 * [[Self:Lintian/Tags/versioned-provides|versioned-provides]]
 * [[Self:Lintian/Tags/obsolete-relation-form|obsolete-relation-form]]
 * [[Self:Lintian/Tags/bad-version-in-relation|bad-version-in-relation]]
 * [[Self:Lintian/Tags/package-relation-with-self|package-relation-with-self]]
 * [[Self:Lintian/Tags/bad-relation|bad-relation]]
 * [[Self:Lintian/Tags/new-essential-package|new-essential-package]]
 * [[Self:Lintian/Tags/doc-package-depends-on-main-package|doc-package-depends-on-main-package]]
 * [[Self:Lintian/Tags/depends-on-obsolete-package|depends-on-obsolete-package]]
 * [[Self:Lintian/Tags/ored-depends-on-obsolete-package|ored-depends-on-obsolete-package]]
 * [[Self:Lintian/Tags/build-depends-on-obsolete-package|build-depends-on-obsolete-package]]
 * [[Self:Lintian/Tags/ored-build-depends-on-obsolete-package|ored-build-depends-on-obsolete-package]]
 * [[Self:Lintian/Tags/depends-on-old-emacs|depends-on-old-emacs]]
 * [[Self:Lintian/Tags/depends-on-metapackage|depends-on-metapackage]]
 * [[Self:Lintian/Tags/build-depends-on-metapackage|build-depends-on-metapackage]]
 * [[Self:Lintian/Tags/depends-on-essential-package-without-using-version|depends-on-essential-package-without-using-version]]
 * [[Self:Lintian/Tags/build-depends-on-essential-package-without-using-version|build-depends-on-essential-package-without-using-version]]
 * [[Self:Lintian/Tags/build-depends-on-non-build-package|build-depends-on-non-build-package]]
 * [[Self:Lintian/Tags/virtual-package-depends-without-real-package-depends|virtual-package-depends-without-real-package-depends]]
 * [[Self:Lintian/Tags/invalid-arch-string-in-source-relation|invalid-arch-string-in-source-relation]]
 * [[Self:Lintian/Tags/conflicting-negation-in-source-relation|conflicting-negation-in-source-relation]]
 * [[Self:Lintian/Tags/depends-on-build-essential-package-without-using-version|depends-on-build-essential-package-without-using-version]]
 * [[Self:Lintian/Tags/package-depends-on-an-x-font-package|package-depends-on-an-x-font-package]]
 * [[Self:Lintian/Tags/build-depends-indep-without-arch-indep|build-depends-indep-without-arch-indep]]
 * [[Self:Lintian/Tags/build-conflicts-with-build-dependency|build-conflicts-with-build-dependency]]
 * [[Self:Lintian/Tags/package-has-a-duplicate-build-relation|package-has-a-duplicate-build-relation]]
 * [[Self:Lintian/Tags/build-depends-on-1-revision|build-depends-on-1-revision]]
 * [[Self:Lintian/Tags/needlessly-depends-on-awk|needlessly-depends-on-awk]]
 * [[Self:Lintian/Tags/package-depends-on-multiple-libstdc-versions|package-depends-on-multiple-libstdc-versions]]
 * [[Self:Lintian/Tags/package-depends-on-multiple-tcl-versions|package-depends-on-multiple-tcl-versions]]
 * [[Self:Lintian/Tags/package-depends-on-multiple-tclx-versions|package-depends-on-multiple-tclx-versions]]
 * [[Self:Lintian/Tags/package-depends-on-multiple-tk-versions|package-depends-on-multiple-tk-versions]]
 * [[Self:Lintian/Tags/package-depends-on-multiple-tkx-versions|package-depends-on-multiple-tkx-versions]]
 * [[Self:Lintian/Tags/package-depends-on-multiple-libpng-versions|package-depends-on-multiple-libpng-versions]]
 * [[Self:Lintian/Tags/depends-on-libdb1-compat|depends-on-libdb1-compat]]
 * [[Self:Lintian/Tags/depends-on-python-minimal|depends-on-python-minimal]]
 * [[Self:Lintian/Tags/depends-exclusively-on-makedev|depends-exclusively-on-makedev]]
 * [[Self:Lintian/Tags/dbg-package-missing-depends|dbg-package-missing-depends]]
 * [[Self:Lintian/Tags/conflicts-with-dependency|conflicts-with-dependency]]
 * [[Self:Lintian/Tags/breaks-without-version|breaks-without-version]]
 * [[Self:Lintian/Tags/conflicts-with-version|conflicts-with-version]]
 * [[Self:Lintian/Tags/bad-menu-item|bad-menu-item]]
 * [[Self:Lintian/Tags/redundant-origin-field|redundant-origin-field]]
 * [[Self:Lintian/Tags/binary-nmu-uses-old-version-style|binary-nmu-uses-old-version-style]]
 * [[Self:Lintian/Tags/binary-nmu-debian-revision-in-source|binary-nmu-debian-revision-in-source]]
 * [[Self:Lintian/Tags/dfsg-version-in-native-package|dfsg-version-in-native-package]]
 * [[Self:Lintian/Tags/dfsg-version-with-period|dfsg-version-with-period]]
 * [[Self:Lintian/Tags/dfsg-version-misspelled|dfsg-version-misspelled]]
 * [[Self:Lintian/Tags/redundant-bugs-field|redundant-bugs-field]]
 * [[Self:Lintian/Tags/build-depends-on-build-essential|build-depends-on-build-essential]]
 * [[Self:Lintian/Tags/malformed-python-version|malformed-python-version]]
 * [[Self:Lintian/Tags/old-versioned-python-dependency|old-versioned-python-dependency]]
 * [[Self:Lintian/Tags/malformed-dm-upload-allowed|malformed-dm-upload-allowed]]
 * [[Self:Lintian/Tags/wrong-section-according-to-package-name|wrong-section-according-to-package-name]]
 * [[Self:Lintian/Tags/debug-package-should-be-priority-extra|debug-package-should-be-priority-extra]]
 * [[Self:Lintian/Tags/maintainer-also-in-uploaders|maintainer-also-in-uploaders]]
 * [[Self:Lintian/Tags/duplicate-uploader|duplicate-uploader]]
 * [[Self:Lintian/Tags/versioned-dependency-satisfied-by-perl|versioned-dependency-satisfied-by-perl]]
 * [[Self:Lintian/Tags/package-superseded-by-perl|package-superseded-by-perl]]
 * [[Self:Lintian/Tags/vcs-field-uses-not-recommended-uri-format|vcs-field-uses-not-recommended-uri-format]]
 * [[Self:Lintian/Tags/vcs-field-uses-unknown-uri-format|vcs-field-uses-unknown-uri-format]]
 * [[Self:Lintian/Tags/lib-recommends-documentation|lib-recommends-documentation]]
 * [[Self:Lintian/Tags/build-depends-on-python-dev-with-no-arch-any|build-depends-on-python-dev-with-no-arch-any]]

=== ocaml ===
 * [[Self:Lintian/Tags/ocaml-dangling-cmxa|ocaml-dangling-cmxa]]
 * [[Self:Lintian/Tags/ocaml-dangling-cmx|ocaml-dangling-cmx]]
 * [[Self:Lintian/Tags/ocaml-dangling-cmxs|ocaml-dangling-cmxs]]
 * [[Self:Lintian/Tags/ocaml-dev-file-not-in-usr-lib-ocaml|ocaml-dev-file-not-in-usr-lib-ocaml]]
 * [[Self:Lintian/Tags/ocaml-stray-cmo|ocaml-stray-cmo]]
 * [[Self:Lintian/Tags/ocaml-dangling-cmi|ocaml-dangling-cmi]]
 * [[Self:Lintian/Tags/ocaml-dev-file-in-nondev-package|ocaml-dev-file-in-nondev-package]]
 * [[Self:Lintian/Tags/ocaml-meta-without-suggesting-findlib|ocaml-meta-without-suggesting-findlib]]

=== md5sums ===
 * [[Self:Lintian/Tags/no-md5sums-control-file|no-md5sums-control-file]]
 * [[Self:Lintian/Tags/malformed-md5sums-control-file|malformed-md5sums-control-file]]
 * [[Self:Lintian/Tags/md5sum-mismatch|md5sum-mismatch]]
 * [[Self:Lintian/Tags/md5sums-lists-nonexisting-file|md5sums-lists-nonexisting-file]]
 * [[Self:Lintian/Tags/file-missing-in-md5sums|file-missing-in-md5sums]]

=== binaries ===
 * [[Self:Lintian/Tags/arch-independent-package-contains-binary-or-object|arch-independent-package-contains-binary-or-object]]
 * [[Self:Lintian/Tags/unstripped-binary-or-object|unstripped-binary-or-object]]
 * [[Self:Lintian/Tags/library-in-debug-or-profile-should-not-be-stripped|library-in-debug-or-profile-should-not-be-stripped]]
 * [[Self:Lintian/Tags/statically-linked-binary|statically-linked-binary]]
 * [[Self:Lintian/Tags/library-not-linked-against-libc|library-not-linked-against-libc]]
 * [[Self:Lintian/Tags/program-not-linked-against-libc|program-not-linked-against-libc]]
 * [[Self:Lintian/Tags/binary-or-shlib-defines-rpath|binary-or-shlib-defines-rpath]]
 * [[Self:Lintian/Tags/binary-has-unneeded-section|binary-has-unneeded-section]]
 * [[Self:Lintian/Tags/missing-depends-line|missing-depends-line]]
 * [[Self:Lintian/Tags/shared-lib-without-dependency-information|shared-lib-without-dependency-information]]
 * [[Self:Lintian/Tags/arch-dependent-file-in-usr-share|arch-dependent-file-in-usr-share]]
 * [[Self:Lintian/Tags/binary-in-etc|binary-in-etc]]
 * [[Self:Lintian/Tags/binary-compiled-with-profiling-enabled|binary-compiled-with-profiling-enabled]]
 * [[Self:Lintian/Tags/binary-file-compressed-with-upx|binary-file-compressed-with-upx]]
 * [[Self:Lintian/Tags/package-name-doesnt-match-sonames|package-name-doesnt-match-sonames]]
 * [[Self:Lintian/Tags/binary-with-bad-dynamic-table|binary-with-bad-dynamic-table]]
 * [[Self:Lintian/Tags/apparently-corrupted-elf-binary|apparently-corrupted-elf-binary]]
 * [[Self:Lintian/Tags/apparently-truncated-elf-binary|apparently-truncated-elf-binary]]
 * [[Self:Lintian/Tags/missing-dependency-on-libc|missing-dependency-on-libc]]
 * [[Self:Lintian/Tags/missing-dependency-on-perlapi|missing-dependency-on-perlapi]]
 * [[Self:Lintian/Tags/missing-dependency-on-phpapi|missing-dependency-on-phpapi]]
 * [[Self:Lintian/Tags/debug-file-should-use-detached-symbols|debug-file-should-use-detached-symbols]]
 * [[Self:Lintian/Tags/binary-from-other-architecture|binary-from-other-architecture]]
 * [[Self:Lintian/Tags/spelling-error-in-binary|spelling-error-in-binary]]
 * [[Self:Lintian/Tags/embedded-zlib|embedded-zlib]]
 * [[Self:Lintian/Tags/embedded-libpng|embedded-libpng]]
 * [[Self:Lintian/Tags/embedded-libjpeg|embedded-libjpeg]]
 * [[Self:Lintian/Tags/embedded-libopenjpeg|embedded-libopenjpeg]]
 * [[Self:Lintian/Tags/embedded-library|embedded-library]]
 * [[Self:Lintian/Tags/debug-symbols-directly-in-usr-lib-debug|debug-symbols-directly-in-usr-lib-debug]]
 * [[Self:Lintian/Tags/ocaml-custom-executable|ocaml-custom-executable]]

=== copyright-file ===
 * [[Self:Lintian/Tags/no-copyright-file|no-copyright-file]]
 * [[Self:Lintian/Tags/copyright-refers-to-old-directory|copyright-refers-to-old-directory]]
 * [[Self:Lintian/Tags/copyright-file-compressed|copyright-file-compressed]]
 * [[Self:Lintian/Tags/copyright-file-is-symlink|copyright-file-is-symlink]]
 * [[Self:Lintian/Tags/copyright-file-contains-full-gpl-license|copyright-file-contains-full-gpl-license]]
 * [[Self:Lintian/Tags/copyright-file-contains-full-gfdl-license|copyright-file-contains-full-gfdl-license]]
 * [[Self:Lintian/Tags/copyright-file-contains-full-apache-2-license|copyright-file-contains-full-apache-2-license]]
 * [[Self:Lintian/Tags/usr-share-doc-symlink-without-dependency|usr-share-doc-symlink-without-dependency]]
 * [[Self:Lintian/Tags/usr-share-doc-symlink-to-foreign-package|usr-share-doc-symlink-to-foreign-package]]
 * [[Self:Lintian/Tags/cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package|cannot-check-whether-usr-share-doc-symlink-points-to-foreign-package]]
 * [[Self:Lintian/Tags/old-style-copyright-file|old-style-copyright-file]]
 * [[Self:Lintian/Tags/old-fsf-address-in-copyright-file|old-fsf-address-in-copyright-file]]
 * [[Self:Lintian/Tags/helper-templates-in-copyright|helper-templates-in-copyright]]
 * [[Self:Lintian/Tags/copyright-refers-to-compressed-license|copyright-refers-to-compressed-license]]
 * [[Self:Lintian/Tags/usr-share-doc-symlink-points-outside-of-usr-share-doc|usr-share-doc-symlink-points-outside-of-usr-share-doc]]
 * [[Self:Lintian/Tags/copyright-does-not-refer-to-common-license-file|copyright-does-not-refer-to-common-license-file]]
 * [[Self:Lintian/Tags/copyright-refers-to-incorrect-directory|copyright-refers-to-incorrect-directory]]
 * [[Self:Lintian/Tags/copyright-file-lacks-pointer-to-perl-license|copyright-file-lacks-pointer-to-perl-license]]
 * [[Self:Lintian/Tags/copyright-should-refer-to-common-license-file-for-gpl|copyright-should-refer-to-common-license-file-for-gpl]]
 * [[Self:Lintian/Tags/copyright-should-refer-to-common-license-file-for-gfdl|copyright-should-refer-to-common-license-file-for-gfdl]]
 * [[Self:Lintian/Tags/copyright-should-refer-to-common-license-file-for-lgpl|copyright-should-refer-to-common-license-file-for-lgpl]]
 * [[Self:Lintian/Tags/copyright-has-url-from-dh_make-boilerplate|copyright-has-url-from-dh_make-boilerplate]]
 * [[Self:Lintian/Tags/debian-copyright-file-uses-obsolete-national-encoding|debian-copyright-file-uses-obsolete-national-encoding]]
 * [[Self:Lintian/Tags/copyright-contains-dh_make-todo-boilerplate|copyright-contains-dh_make-todo-boilerplate]]
 * [[Self:Lintian/Tags/copyright-contains-dh-make-perl-boilerplate|copyright-contains-dh-make-perl-boilerplate]]
 * [[Self:Lintian/Tags/copyright-with-old-dh-make-debian-copyright|copyright-with-old-dh-make-debian-copyright]]
 * [[Self:Lintian/Tags/copyright-refers-to-bad-php-license|copyright-refers-to-bad-php-license]]
 * [[Self:Lintian/Tags/copyright-refers-to-problematic-php-license|copyright-refers-to-problematic-php-license]]
 * [[Self:Lintian/Tags/copyright-without-copyright-notice|copyright-without-copyright-notice]]
 * [[Self:Lintian/Tags/spelling-error-in-copyright|spelling-error-in-copyright]]
 * [[Self:Lintian/Tags/possible-gpl-code-linked-with-openssl|possible-gpl-code-linked-with-openssl]]
 * [[Self:Lintian/Tags/copyright-refers-to-symlink-license|copyright-refers-to-symlink-license]]
 * [[Self:Lintian/Tags/copyright-refers-to-versionless-license-file|copyright-refers-to-versionless-license-file]]
 * [[Self:Lintian/Tags/copyright-refers-to-nonexistent-license-file|copyright-refers-to-nonexistent-license-file]]
 * [[Self:Lintian/Tags/copyright-refers-to-deprecated-bsd-license-file|copyright-refers-to-deprecated-bsd-license-file]]

=== po-debconf ===
 * [[Self:Lintian/Tags/not-using-po-debconf|not-using-po-debconf]]
 * [[Self:Lintian/Tags/stray-translated-debconf-templates|stray-translated-debconf-templates]]
 * [[Self:Lintian/Tags/missing-potfiles-in|missing-potfiles-in]]
 * [[Self:Lintian/Tags/missing-file-from-potfiles-in|missing-file-from-potfiles-in]]
 * [[Self:Lintian/Tags/missing-templates-pot|missing-templates-pot]]
 * [[Self:Lintian/Tags/unknown-encoding-in-po-file|unknown-encoding-in-po-file]]
 * [[Self:Lintian/Tags/invalid-po-file|invalid-po-file]]
 * [[Self:Lintian/Tags/misnamed-po-file|misnamed-po-file]]
 * [[Self:Lintian/Tags/newer-debconf-templates|newer-debconf-templates]]
 * [[Self:Lintian/Tags/translated-default-field|translated-default-field]]
 * [[Self:Lintian/Tags/no-complete-debconf-translation|no-complete-debconf-translation]]

=== changelog-file ===
 * [[Self:Lintian/Tags/html-changelog-without-text-version|html-changelog-without-text-version]]
 * [[Self:Lintian/Tags/changelog-file-not-compressed|changelog-file-not-compressed]]
 * [[Self:Lintian/Tags/debian-news-file-not-compressed|debian-news-file-not-compressed]]
 * [[Self:Lintian/Tags/changelog-not-compressed-with-max-compression|changelog-not-compressed-with-max-compression]]
 * [[Self:Lintian/Tags/wrong-name-for-changelog-of-native-package|wrong-name-for-changelog-of-native-package]]
 * [[Self:Lintian/Tags/changelog-file-missing-in-native-package|changelog-file-missing-in-native-package]]
 * [[Self:Lintian/Tags/wrong-name-for-upstream-changelog|wrong-name-for-upstream-changelog]]
 * [[Self:Lintian/Tags/no-upstream-changelog|no-upstream-changelog]]
 * [[Self:Lintian/Tags/wrong-name-for-debian-changelog-file|wrong-name-for-debian-changelog-file]]
 * [[Self:Lintian/Tags/wrong-name-for-debian-news-file|wrong-name-for-debian-news-file]]
 * [[Self:Lintian/Tags/debian-changelog-file-missing|debian-changelog-file-missing]]
 * [[Self:Lintian/Tags/debian-changelog-file-is-a-symlink|debian-changelog-file-is-a-symlink]]
 * [[Self:Lintian/Tags/debian-changelog-file-missing-or-wrong-name|debian-changelog-file-missing-or-wrong-name]]
 * [[Self:Lintian/Tags/debian-changelog-file-contains-obsolete-user-emacs-settings|debian-changelog-file-contains-obsolete-user-emacs-settings]]
 * [[Self:Lintian/Tags/debian-changelog-file-contains-debmake-default-email-address|debian-changelog-file-contains-debmake-default-email-address]]
 * [[Self:Lintian/Tags/debian-changelog-file-contains-invalid-email-address|debian-changelog-file-contains-invalid-email-address]]
 * [[Self:Lintian/Tags/debian-changelog-file-uses-obsolete-national-encoding|debian-changelog-file-uses-obsolete-national-encoding]]
 * [[Self:Lintian/Tags/debian-news-file-uses-obsolete-national-encoding|debian-news-file-uses-obsolete-national-encoding]]
 * [[Self:Lintian/Tags/latest-debian-changelog-entry-without-new-date|latest-debian-changelog-entry-without-new-date]]
 * [[Self:Lintian/Tags/latest-debian-changelog-entry-without-new-version|latest-debian-changelog-entry-without-new-version]]
 * [[Self:Lintian/Tags/latest-debian-changelog-entry-changed-to-native|latest-debian-changelog-entry-changed-to-native]]
 * [[Self:Lintian/Tags/possible-new-upstream-release-without-new-version|possible-new-upstream-release-without-new-version]]
 * [[Self:Lintian/Tags/experimental-to-unstable-without-comment|experimental-to-unstable-without-comment]]
 * [[Self:Lintian/Tags/syntax-error-in-debian-changelog|syntax-error-in-debian-changelog]]
 * [[Self:Lintian/Tags/syntax-error-in-debian-news-file|syntax-error-in-debian-news-file]]
 * [[Self:Lintian/Tags/improbable-bug-number-in-closes|improbable-bug-number-in-closes]]
 * [[Self:Lintian/Tags/wrong-bug-number-in-closes|wrong-bug-number-in-closes]]
 * [[Self:Lintian/Tags/possible-missing-colon-in-closes|possible-missing-colon-in-closes]]
 * [[Self:Lintian/Tags/debian-news-entry-has-strange-distribution|debian-news-entry-has-strange-distribution]]
 * [[Self:Lintian/Tags/debian-news-entry-uses-asterisk|debian-news-entry-uses-asterisk]]
 * [[Self:Lintian/Tags/debian-news-entry-has-unknown-version|debian-news-entry-has-unknown-version]]
 * [[Self:Lintian/Tags/spelling-error-in-changelog|spelling-error-in-changelog]]
 * [[Self:Lintian/Tags/spelling-error-in-news-debian|spelling-error-in-news-debian]]
 * [[Self:Lintian/Tags/new-package-should-close-itp-bug|new-package-should-close-itp-bug]]
 * [[Self:Lintian/Tags/debian-changelog-line-too-long|debian-changelog-line-too-long]]
 * [[Self:Lintian/Tags/changelog-news-debian-mismatch|changelog-news-debian-mismatch]]
 * [[Self:Lintian/Tags/version-refers-to-distribution|version-refers-to-distribution]]

##END:TOC
}}}}}


== Extraction script ==
{{{#!python
#!/usr/bin/env python
# Copyright 2010, Frank lin Piat. Licensed under GPLv2 or later.

import sys, os, re, string, gzip

debug = False

tags_url = "http://lintian.debian.org/tags/%s.html"
wikipage_header = """#language en
#format wiki

This page contains some data that are automatically imported, and
used in pages:
 * [[Lintian/Tags]]

To refresh this page with the latest lintian tags, simply grab the
python script below. The script will generate this wiki page using
your local copy of lintian. Just copy and paste the generated page
into this page.
"""

manpages_re = re.compile('(\S+)\((\S+)\)')
manpages_url = "DebianMan:$section/$name"
manpage_template = string.Template(manpages_url)

lintian_changelog = "/usr/share/doc/lintian/changelog.gz"

refs_urls = {
    'debconf-spec': '',
    'devref': 'http://www.debian.org/doc/manuals/developers-reference/',
    #'doc-base': '',
    'fhs': 'http://www.debian.org/doc/packaging-manuals/fhs/',
    #'libpkg-guide': '',
    'lintian': 'http://lintian.debian.org/manual/',
    'menu': 'http://www.debian.org/doc/packaging-manuals/menu.html/',
    'menu-policy': 'http://www.debian.org/doc/packaging-manuals/menu-policy/',
    'perl-policy': 'http://www.debian.org/doc/packaging-manuals/perl-policy/',
    'policy': 'http://www.debian.org/doc/debian-policy/',
    'python-policy': 'http://www.debian.org/doc/packaging-manuals/python-policy/'}



def wiki_url(target, label):
    if label == "":
        return "[[%s]]" % (target)
    else:
        return "[[%s|%s]]" % (target, label)

def manpage(s):
    m = manpages_re.match(s)
    t = manpage_template.substitute({'section': m.group(2), 'name': m.group(1)})
    return wiki_url(t, s)

def process_ref(refs):
    out=[]
    for ref in refs.split(","):
        ref = ref.strip()
        k = ref.split(" ")[0]
        if k in refs_urls:
            out.append(wiki_url(refs_urls[k], ref))
        elif manpages_re.match(ref):
            out.append(manpage(ref))
        elif ref.startswith('http://'):
            out.append(wiki_url(ref, ''))
        else:
            out.append(ref)
    return ", ".join(out)

def process_tag(tag, info, ref):
    print "Self:Lintian/Tags/%s" % tag
    print "%s#!wiki note" % ('{' * 4)
    url = tags_url % tag
    print "Lintian tag '''[[%s|%s]]''':<<BR>>" % (url, tag)
    if info != False:
        s = "\n\n".join(info).replace("<tt>","{" * 3)
        s = s.replace("}</tt>","} %s" % ("}" * 3) )
        s = s.replace("</tt>","}" * 3)
        s = s.replace("<i>","") # Moin don't support italics in bloc quotes.
        s = s.replace("</i>","")
        s = s.replace("&lt;", "<").replace("&gt;", ">")
        print " %s" % s
        if ref:
            print ""
            print "Reference(s): %s" % process_ref(ref)
    print ('}' * 4)
    print "##END:Lintian/Tags/%s" % tag
    print ""

def show_toc(toc):
    print "##START:TOC"
    for categ, tags in toc.iteritems():
        print "=== %s ===" % categ
        for tag in tags:
            print " * [[Self:Lintian/Tags/%s|%s]]" % (tag, tag)
        print ""
    print "##END:TOC"

def show_source():
    for l in open(sys.argv[0]):
        print l.rstrip()

def get_descs(descs_dir):
    toc = {}
    for path in os.listdir(descs_dir):
        name = path[:path.find(".")]
        if not path.endswith(".desc"):
            continue
        print "########################################################################"
        print "== %s ==" % name
        print "########################################################################"
        print ""

        toc[name] = []

        tag = False
        info = False
        ref = False
        for l in open(os.path.join(descs_dir,path)).xreadlines():
            l = l.rstrip()
            if l.find(":"):
                k = l[:l.find(":")].lower()
                v = l[l.find(":")+1:].lstrip()
            else:
                k,v = "",""
            if debug:
                print "<%s" % l

            if l == "" or k == "tag":
                if tag != False:
                    process_tag(tag, info, ref)
                if k == "tag":
                    tag = v
                    toc[name].append(tag)
                else:
                    tag = False
                info = False
                ref = False
            elif tag:
                if k == "ref":
                    ref = l[l.find(" ")+1:]
                elif k == "info":
                    info = []
                    info.append(l[l.find(" ")+1:])
                elif l == " .":
                    if info != False:
                        info.append("")
                elif l.startswith(" "):
                    if info != False:
                        info[-1] += l

        if tag != False:
            process_tag(tag, info, ref)

    show_toc(toc)

def changelog_get_version(f):
    h = gzip.open(f)
    for l in h:
        return l.strip()

def generate_wikipage():
    print wikipage_header
    print ""
    print "Last updated with:"
    print " %s" % ('{' * 3)
    print changelog_get_version(lintian_changelog)
    print "%s" % ('}' * 3)
    # Curly braces are escape code in MoinMoin markup.
    print "%s#!wiki comment" % ( '{' * 5 )
    get_descs("/usr/share/lintian/checks")
    print "%s" % ( '}' * 5 )
    print ""
    print ""
    print "== Extraction script =="
    print "%s#!python" % ( '{' * 3 )
    show_source()
    print "%s" % ( '}' * 3 )

generate_wikipage()

}}}