diff options
Diffstat (limited to 'tags/n')
78 files changed, 790 insertions, 0 deletions
diff --git a/tags/n/named-copyright-for-single-installable.tag b/tags/n/named-copyright-for-single-installable.tag new file mode 100644 index 0000000..1b939ff --- /dev/null +++ b/tags/n/named-copyright-for-single-installable.tag @@ -0,0 +1,10 @@ +Tag: named-copyright-for-single-installable +Severity: warning +Check: debian/copyright +See-Also: debian-policy 12.5 +Explanation: Every package must include the file <code>/usr/share/doc/*pkg*/copyright</code>. + A copy of this file should be in <code>debian/copyright</code> in the source package. + . + These sources ship a copyright file named according to debhelper convention + <code>debian/$package.copyright</code> but build only one installable. Please move + the copyright file to <code>debian/copyright</code>. diff --git a/tags/n/national-encoding.tag b/tags/n/national-encoding.tag new file mode 100644 index 0000000..40c5eb5 --- /dev/null +++ b/tags/n/national-encoding.tag @@ -0,0 +1,23 @@ +Tag: national-encoding +Severity: warning +Check: files/encoding +Renamed-From: + national-encoding-in-text-file + debian-changelog-file-uses-obsolete-national-encoding + debian-control-file-uses-obsolete-national-encoding + debian-copyright-file-uses-obsolete-national-encoding + debian-news-file-uses-obsolete-national-encoding + debian-tests-control-uses-national-encoding + doc-base-file-uses-obsolete-national-encoding + national-encoding-in-debconf-template + national-encoding-in-manpage +Explanation: A file is not valid UTF-8. + . + Debian has used UTF-8 for many years. Support for national encodings + is being phased out. This file probably appears to users in mangled + characters (also called mojibake). + . + Packaging control files must be encoded in valid UTF-8. + . + Please convert the file to UTF-8 using <code>iconv</code> or a similar + tool. diff --git a/tags/n/native-source-file-without-utf8-name.tag b/tags/n/native-source-file-without-utf8-name.tag new file mode 100644 index 0000000..f40fc4f --- /dev/null +++ b/tags/n/native-source-file-without-utf8-name.tag @@ -0,0 +1,10 @@ +Tag: native-source-file-without-utf8-name +Severity: error +Check: files/names +See-Also: debian-policy 10.10 +Explanation: The file name in the native source tree is not valid UTF-8. + File names must decode as valid UTF-8. Please rename the file. + . + Unlike other file names in Lintian, which are printed in UTF-8, the + attached reference shows the bytes used by the file system. + Unprintable characters may have been replaced. diff --git a/tags/n/needless-dependency-on-jre.tag b/tags/n/needless-dependency-on-jre.tag new file mode 100644 index 0000000..a62caec --- /dev/null +++ b/tags/n/needless-dependency-on-jre.tag @@ -0,0 +1,15 @@ +Tag: needless-dependency-on-jre +Severity: warning +Check: fields/package-relations +Explanation: The package appear to be a Java library and depending on one + or more JRE/JDK packages. As of 05 Apr 2010, the Java Policy no + longer mandates that Java libraries depend on Java Runtimes. + . + If the library package ships executables along with the library, + then please consider making this an application package or move the + binaries to a (new) application package. + . + If there is otherwise a valid reason for this dependency, please override + the tag. +See-Also: https://lists.debian.org/debian-devel-changes/2010/04/msg00774.html, + Bug#227587 diff --git a/tags/n/needless-suggest-recommend-libservlet-java.tag b/tags/n/needless-suggest-recommend-libservlet-java.tag new file mode 100644 index 0000000..601a624 --- /dev/null +++ b/tags/n/needless-suggest-recommend-libservlet-java.tag @@ -0,0 +1,12 @@ +Tag: needless-suggest-recommend-libservlet-java +Severity: warning +Check: fields/package-relations +Explanation: Package should not suggest or recommend libservlet-java + Java servlets are only used in the context of a server (example: Tomcat or + Jetty). This server will have this dependency and will take care of the + loading of this package with the right libservlet. + . + Removing this dependency will fix this warning. + . + If there is otherwise a valid reason for this suggestion or recommendation, + please override the tag. diff --git a/tags/n/needlessly-depends-on-awk.tag b/tags/n/needlessly-depends-on-awk.tag new file mode 100644 index 0000000..87ccc8f --- /dev/null +++ b/tags/n/needlessly-depends-on-awk.tag @@ -0,0 +1,8 @@ +Tag: needlessly-depends-on-awk +Severity: error +Check: fields/package-relations +Explanation: 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. diff --git a/tags/n/nested-examples-directory.tag b/tags/n/nested-examples-directory.tag new file mode 100644 index 0000000..411842d --- /dev/null +++ b/tags/n/nested-examples-directory.tag @@ -0,0 +1,6 @@ +Tag: nested-examples-directory +Severity: error +Check: documentation/examples +Explanation: Package contains a <code>usr/share/doc/something/examples/examples</code> + directory. It was most likely installed by accident, since one examples/ + directory should be enough for everybody(tm). diff --git a/tags/n/new-essential-package.tag b/tags/n/new-essential-package.tag new file mode 100644 index 0000000..6d518bc --- /dev/null +++ b/tags/n/new-essential-package.tag @@ -0,0 +1,7 @@ +Tag: new-essential-package +Severity: error +Check: fields/essential +Explanation: 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. +See-Also: debian-policy 3.8 diff --git a/tags/n/new-package-should-not-package-python2-module.tag b/tags/n/new-package-should-not-package-python2-module.tag new file mode 100644 index 0000000..39fa255 --- /dev/null +++ b/tags/n/new-package-should-not-package-python2-module.tag @@ -0,0 +1,24 @@ +Tag: new-package-should-not-package-python2-module +Severity: warning +Check: languages/python +Explanation: This package appears to be the initial packaging of a new upstream + software package (ie. it contains a single changelog entry). However, it + ships the specified module for Python 2. + . + Python 2.x modules should not be packaged unless strictly necessary (such + as being explicitly requested by an end-user or required as part of a + dependency chain) as the 2.x series of Python is due for deprecation and + will not be maintained by upstream past 2020 and will likely be dropped + after the release of Debian <code>buster</code>. + . + If upstream have not yet moved to Python 3, please be certain that Debian + would benefit from the inclusion, continued maintenance burden and eventual + removal of this package before you upload. + . + This warning can be ignored if the package is not intended for Debian or + if it is a split of an existing Debian package. This warning can also be + ignored if viewed on https://lintian.debian.org/. + . + Please do not override this warning. Instead, add a justification to your + changelog entry. Lintian will detect your comment in the changelog. It ensures + that your rationale is preserved for posterity. diff --git a/tags/n/new-package-uses-date-based-version-number.tag b/tags/n/new-package-uses-date-based-version-number.tag new file mode 100644 index 0000000..8babd9d --- /dev/null +++ b/tags/n/new-package-uses-date-based-version-number.tag @@ -0,0 +1,11 @@ +Tag: new-package-uses-date-based-version-number +Severity: warning +Check: debian/changelog +Explanation: This package appears to be the first packaging of a new upstream + software package (there is only one changelog entry and the Debian + revision is 1) and uses a date-based versioning scheme such as + YYYYMMDD-1. + . + Packages using date-based version numbering should use a "0~" prefix + (eg. 0~20201612-1 or similar) to avoid having to introduce an epoch if + upstream starts tagging releases in a more conventional manner. diff --git a/tags/n/newer-debconf-templates.tag b/tags/n/newer-debconf-templates.tag new file mode 100644 index 0000000..4bc4305 --- /dev/null +++ b/tags/n/newer-debconf-templates.tag @@ -0,0 +1,13 @@ +Tag: newer-debconf-templates +Severity: warning +Check: debian/po-debconf +Explanation: 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 <code>debian/rules</code>. PO files will then always be up-to-date when + building the source package. diff --git a/tags/n/newer-standards-version.tag b/tags/n/newer-standards-version.tag new file mode 100644 index 0000000..12d6e19 --- /dev/null +++ b/tags/n/newer-standards-version.tag @@ -0,0 +1,8 @@ +Tag: newer-standards-version +Severity: warning +Check: fields/standards-version +Explanation: 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, please upgrade Lintian to the newest + version. diff --git a/tags/n/nfs-temporary-file-in-package.tag b/tags/n/nfs-temporary-file-in-package.tag new file mode 100644 index 0000000..9a27e15 --- /dev/null +++ b/tags/n/nfs-temporary-file-in-package.tag @@ -0,0 +1,7 @@ +Tag: nfs-temporary-file-in-package +Severity: warning +Check: files/unwanted +Explanation: 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. diff --git a/tags/n/nmu-in-changelog.tag b/tags/n/nmu-in-changelog.tag new file mode 100644 index 0000000..7c4d754 --- /dev/null +++ b/tags/n/nmu-in-changelog.tag @@ -0,0 +1,13 @@ +Tag: nmu-in-changelog +Severity: warning +Check: nmu +Renamed-From: changelog-should-not-mention-nmu +Explanation: 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. diff --git a/tags/n/no-changelog.tag b/tags/n/no-changelog.tag new file mode 100644 index 0000000..3835def --- /dev/null +++ b/tags/n/no-changelog.tag @@ -0,0 +1,18 @@ +Tag: no-changelog +Severity: error +Check: debian/changelog +Renamed-From: + changelog-file-missing-in-native-package + debian-changelog-file-missing +Explanation: A Debian package that provides a <code>/usr/share/doc/*pkg*</code> + directory must install a changelog file. + . + For native packages the best name is + <code>/usr/share/doc/*pkg*/changelog.gz</code>. + . + For non-native packages the best name is + <code>/usr/share/doc/*pkg*/changelog.Debian.gz</code>. + . + This tag may also be emitted when the changelog exists but does not + otherwise resemble a Debian changelog. +See-Also: debian-policy 12.7 diff --git a/tags/n/no-code-sections.tag b/tags/n/no-code-sections.tag new file mode 100644 index 0000000..cfeb6db --- /dev/null +++ b/tags/n/no-code-sections.tag @@ -0,0 +1,11 @@ +Tag: no-code-sections +Severity: error +Check: libraries/static/no-code +Explanation: + The named members of the static library have no usable code sections. + . + It happens when shared objects are built with <code>-flto=auto</code> but + without <code>-ffat-lto-objects</code>. <code>dh_strip</code> strips the + LTO sections but may leave the static library without any usable code. +See-Also: + Bug#977596 diff --git a/tags/n/no-complete-debconf-translation.tag b/tags/n/no-complete-debconf-translation.tag new file mode 100644 index 0000000..521f72a --- /dev/null +++ b/tags/n/no-complete-debconf-translation.tag @@ -0,0 +1,13 @@ +Tag: no-complete-debconf-translation +Severity: info +Check: debian/po-debconf +Explanation: 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 +See-Also: developer-reference 6.5.2.2 diff --git a/tags/n/no-copyright-file.tag b/tags/n/no-copyright-file.tag new file mode 100644 index 0000000..8f46204 --- /dev/null +++ b/tags/n/no-copyright-file.tag @@ -0,0 +1,6 @@ +Tag: no-copyright-file +Severity: error +Check: debian/copyright +Explanation: Each binary package has to include a plain file + /usr/share/doc/*pkg*/copyright +See-Also: debian-policy 12.5 diff --git a/tags/n/no-ctrl-scripts.tag b/tags/n/no-ctrl-scripts.tag new file mode 100644 index 0000000..656f177 --- /dev/null +++ b/tags/n/no-ctrl-scripts.tag @@ -0,0 +1,5 @@ +Tag: no-ctrl-scripts +Severity: classification +Check: control-files +Explanation: The package does not rely on any maintainer scripts (or other + executable control files). diff --git a/tags/n/no-debconf-config.tag b/tags/n/no-debconf-config.tag new file mode 100644 index 0000000..be17ef7 --- /dev/null +++ b/tags/n/no-debconf-config.tag @@ -0,0 +1,6 @@ +Tag: no-debconf-config +Severity: error +Check: debian/debconf +Explanation: 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. diff --git a/tags/n/no-debconf-templates.tag b/tags/n/no-debconf-templates.tag new file mode 100644 index 0000000..2657b25 --- /dev/null +++ b/tags/n/no-debconf-templates.tag @@ -0,0 +1,6 @@ +Tag: no-debconf-templates +Severity: warning +Check: debian/debconf +Explanation: 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. diff --git a/tags/n/no-debian-changes.tag b/tags/n/no-debian-changes.tag new file mode 100644 index 0000000..61b84c0 --- /dev/null +++ b/tags/n/no-debian-changes.tag @@ -0,0 +1,19 @@ +Tag: no-debian-changes +Severity: warning +Check: files/artifact +Renamed-From: + empty-debian-diff +Explanation: This non-native package makes no changes to the upstream sources + in the Debian-related files. + . + Maybe a mistake was made when the upstream tarball was created, or maybe this + package is really a native package but was built non-native by mistake. + . + Debian packaging is sometimes maintained as part of upstream, but that is not + recommended as best practice. Please make this package native, if the software + is only for Debian. Otherwise, please remove the <code>debian</code> directory + from upstream releases and add it in the Debian packaging. + . + Format 1.0 packages are subject to the restriction that the diff cannot remove + files from the <code>debian</code> directory. For Format 3.0 packages, the + <code>debian</code> directory is automatically purged during unpacking. diff --git a/tags/n/no-debian-copyright-in-source.tag b/tags/n/no-debian-copyright-in-source.tag new file mode 100644 index 0000000..4be0876 --- /dev/null +++ b/tags/n/no-debian-copyright-in-source.tag @@ -0,0 +1,7 @@ +Tag: no-debian-copyright-in-source +Severity: warning +Check: debian/copyright +Renamed-From: no-debian-copyright +See-Also: debian-policy 12.5 +Explanation: Every package must include the file <code>/usr/share/doc/*pkg*/copyright</code>. + A copy of this file should be in <code>debian/copyright</code> in the source package. diff --git a/tags/n/no-dep5-copyright.tag b/tags/n/no-dep5-copyright.tag new file mode 100644 index 0000000..b16c56e --- /dev/null +++ b/tags/n/no-dep5-copyright.tag @@ -0,0 +1,8 @@ +Tag: no-dep5-copyright +Severity: pedantic +Check: debian/copyright/dep5 +Explanation: This package does not use a machine-readable debian/copyright file. + . + This format makes it easier to review licenses and can be easily parsed + by Lintian. +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff --git a/tags/n/no-dh-sequencer.tag b/tags/n/no-dh-sequencer.tag new file mode 100644 index 0000000..900a60e --- /dev/null +++ b/tags/n/no-dh-sequencer.tag @@ -0,0 +1,10 @@ +Tag: no-dh-sequencer +Severity: info +Check: debian/rules/dh-sequencer +Explanation: This package does not use the <code>dh</code> sequencer in <code>debian/rules</code>. + . + While maintainers may use a variety of build systems, this one + is by far the most popular. + . + Maintainers are strongly encouraged to use the <code>dh</code> sequencer + in new packages and convert existing ones when appropriate. diff --git a/tags/n/no-english-manual-page.tag b/tags/n/no-english-manual-page.tag new file mode 100644 index 0000000..6b9ce09 --- /dev/null +++ b/tags/n/no-english-manual-page.tag @@ -0,0 +1,10 @@ +Tag: no-english-manual-page +Severity: warning +Check: documentation/manual +Renamed-From: binary-without-english-manpage +Explanation: Each binary in <code>/usr/bin</code>, <code>/usr/sbin</code>, <code>/bin</code>, + <code>/sbin</code> or <code>/usr/games</code> should have a manual page. You do + not provide an English manual page, but only a translated one. + . + Since the English language serves as a fallback option, the lack of an + English page leaves most users without any kind of manual page at all. diff --git a/tags/n/no-homepage-field.tag b/tags/n/no-homepage-field.tag new file mode 100644 index 0000000..2c034ab --- /dev/null +++ b/tags/n/no-homepage-field.tag @@ -0,0 +1,8 @@ +Tag: no-homepage-field +Severity: pedantic +Check: fields/homepage +Explanation: This non-native package lacks a <code>Homepage</code> field. If the + package has an upstream home page that contains useful information or + resources for the end user, consider adding a <code>Homepage</code> control + field to <code>debian/control</code>. +See-Also: debian-policy 5.6.23 diff --git a/tags/n/no-human-maintainers.tag b/tags/n/no-human-maintainers.tag new file mode 100644 index 0000000..e252a33 --- /dev/null +++ b/tags/n/no-human-maintainers.tag @@ -0,0 +1,7 @@ +Tag: no-human-maintainers +Severity: error +Check: fields/maintainer +Explanation: The Maintainer address for this package is a mailing list and there + are no Uploaders listed. Team-maintained packages must list the human + maintainers in the Uploaders field. +See-Also: debian-policy 3.3, developer-reference 5.12 diff --git a/tags/n/no-manual-page.tag b/tags/n/no-manual-page.tag new file mode 100644 index 0000000..c540ef8 --- /dev/null +++ b/tags/n/no-manual-page.tag @@ -0,0 +1,23 @@ +Tag: no-manual-page +Severity: warning +Check: documentation/manual +Renamed-From: binary-without-manpage +Explanation: Each binary in <code>/usr/bin</code>, <code>/usr/sbin</code>, <code>/bin</code>, + <code>/sbin</code> or <code>/usr/games</code> should have a manual page + . + Note that though the <code>man</code> 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 manual page differs from the binary by case, <code>man</code> + may be able to find it anyway; however, it is still best practice to match + the exact capitalization of the executable in the manual page. + . + If the manual pages are provided by another package on which this package + depends, Lintian may not be able to determine that manual pages are + available. In this case, after confirming that all binaries do have + manual pages after this package and its dependencies are installed, please + add a Lintian override. +See-Also: debian-policy 12.1 diff --git a/tags/n/no-md5sums-control-file.tag b/tags/n/no-md5sums-control-file.tag new file mode 100644 index 0000000..b342b37 --- /dev/null +++ b/tags/n/no-md5sums-control-file.tag @@ -0,0 +1,12 @@ +Tag: no-md5sums-control-file +Severity: info +Check: md5sums +Explanation: 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 + <code>dh_md5sums</code> at the end of your binary-indep or binary-arch + target, right before <code>dh_builddeb</code>. diff --git a/tags/n/no-newline-at-end.tag b/tags/n/no-newline-at-end.tag new file mode 100644 index 0000000..b2fa29d --- /dev/null +++ b/tags/n/no-newline-at-end.tag @@ -0,0 +1,7 @@ +Tag: no-newline-at-end +Severity: warning +Check: debian/trailing-whitespace +Explanation: The named text file does not end with a newline. + . + Git considers it a whitespace error. Emacs will offer to add it. + It is usually a good idea to do so. diff --git a/tags/n/no-nmu-in-changelog.tag b/tags/n/no-nmu-in-changelog.tag new file mode 100644 index 0000000..5ea5d55 --- /dev/null +++ b/tags/n/no-nmu-in-changelog.tag @@ -0,0 +1,15 @@ +Tag: no-nmu-in-changelog +Severity: warning +Check: nmu +Renamed-From: changelog-should-mention-nmu +Explanation: 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 + double-check 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. +See-Also: developer-reference 5.11.3 diff --git a/tags/n/no-op-testsuite.tag b/tags/n/no-op-testsuite.tag new file mode 100644 index 0000000..82fec57 --- /dev/null +++ b/tags/n/no-op-testsuite.tag @@ -0,0 +1,15 @@ +Tag: no-op-testsuite +Severity: warning +Check: testsuite +Explanation: This package declares a single autopkgtest which will always + pass as it uses a "no-op" command such as <code>/bin/true</code>. + . + As the results of autopkgtests influence migration from unstable + to testing this is undesirable and could be even considered an + unfair or unwarranted "advantage". Installability of packages is + better tested with piuparts which is also used to influence + testing migration. + . + Please update your autopkgtest to actually test the binary package(s) + when installed. +See-Also: https://ci.debian.net/doc/ diff --git a/tags/n/no-phrase.tag b/tags/n/no-phrase.tag new file mode 100644 index 0000000..2ec8f47 --- /dev/null +++ b/tags/n/no-phrase.tag @@ -0,0 +1,13 @@ +Tag: no-phrase +Severity: error +Check: fields/mail-address +Renamed-From: + maintainer-name-missing + changed-by-name-missing +Explanation: The named contact includes an email address, but no name + (which email folks call the *phrase*). + . + The contact information must contain both a name and a mail address. +See-Also: debian-policy 5.6.2, + debian-policy 5.6.3, + debian-policy 5.6.4 diff --git a/tags/n/no-qa-in-changelog.tag b/tags/n/no-qa-in-changelog.tag new file mode 100644 index 0000000..3e78559 --- /dev/null +++ b/tags/n/no-qa-in-changelog.tag @@ -0,0 +1,7 @@ +Tag: no-qa-in-changelog +Severity: warning +Check: nmu +Renamed-From: changelog-should-mention-qa +Explanation: 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. diff --git a/tags/n/no-shlibs.tag b/tags/n/no-shlibs.tag new file mode 100644 index 0000000..ed10b1b --- /dev/null +++ b/tags/n/no-shlibs.tag @@ -0,0 +1,9 @@ +Tag: no-shlibs +Severity: error +Check: debian/shlibs +Renamed-From: + no-shlibs-control-file +Explanation: Although the package includes a shared library, the package does not + have a shlibs control file. If this is intentional, please override this + error. +See-Also: debian-policy 8.6 diff --git a/tags/n/no-source-section.tag b/tags/n/no-source-section.tag new file mode 100644 index 0000000..fe018fa --- /dev/null +++ b/tags/n/no-source-section.tag @@ -0,0 +1,5 @@ +Tag: no-source-section +Severity: classification +Check: debian/control/field/section +Explanation: The <code>debian/control</code> file does not declare a + <code>Section</code> field in the source stanza. diff --git a/tags/n/no-strong-digests-in-dsc.tag b/tags/n/no-strong-digests-in-dsc.tag new file mode 100644 index 0000000..375f1a3 --- /dev/null +++ b/tags/n/no-strong-digests-in-dsc.tag @@ -0,0 +1,15 @@ +Tag: no-strong-digests-in-dsc +Severity: error +Check: fields/checksums +Explanation: This <code>.dsc</code> file contains no + <code>Checksum-Sha256</code> field and hence only weak digests. + . + This tag should show up only for source packages built with + <code>dpkg-source</code> older than version 1.14.17 (from March 2008). + It will probably not show up when you run Lintian locally but may be + seen on + https://lintian.debian.org/ for legacy source packages in the archive. + . + This tags can be fixed by rebuilding the source package + with a more recent version of <code>dpkg-source</code>, i.e. by making + a new upload. diff --git a/tags/n/no-symbols-control-file.tag b/tags/n/no-symbols-control-file.tag new file mode 100644 index 0000000..9910b44 --- /dev/null +++ b/tags/n/no-symbols-control-file.tag @@ -0,0 +1,10 @@ +Tag: no-symbols-control-file +Severity: info +Check: debian/shlibs +Explanation: 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. +See-Also: dpkg-gensymbols(1), https://wiki.debian.org/UsingSymbolsFiles diff --git a/tags/n/no-template-description.tag b/tags/n/no-template-description.tag new file mode 100644 index 0000000..ac79ff3 --- /dev/null +++ b/tags/n/no-template-description.tag @@ -0,0 +1,8 @@ +Tag: no-template-description +Severity: error +Check: debian/debconf +Explanation: The templates file contains a template without a + <code>Description</code> field. +See-Also: + debconf-specification 3, + debconf-devel(7) diff --git a/tags/n/no-template-name.tag b/tags/n/no-template-name.tag new file mode 100644 index 0000000..e784df0 --- /dev/null +++ b/tags/n/no-template-name.tag @@ -0,0 +1,4 @@ +Tag: no-template-name +Severity: error +Check: debian/debconf +Explanation: The templates file contains a template without a "Template:" field. diff --git a/tags/n/no-template-type.tag b/tags/n/no-template-type.tag new file mode 100644 index 0000000..9d1f4ae --- /dev/null +++ b/tags/n/no-template-type.tag @@ -0,0 +1,4 @@ +Tag: no-template-type +Severity: error +Check: debian/debconf +Explanation: The templates file contains a template without a "Type:" field. diff --git a/tags/n/no-tests.tag b/tags/n/no-tests.tag new file mode 100644 index 0000000..9145e2f --- /dev/null +++ b/tags/n/no-tests.tag @@ -0,0 +1,7 @@ +Tag: no-tests +Severity: warning +Check: testsuite +Explanation: The autopackage test suite does not define any tests via + either the <code>Tests</code> field or the <code>Test-Command</code> + field. +See-Also: https://salsa.debian.org/ci-team/autopkgtest/tree/master/doc/README.package-tests.rst diff --git a/tags/n/no-versioned-debhelper-prerequisite.tag b/tags/n/no-versioned-debhelper-prerequisite.tag new file mode 100644 index 0000000..90dfa9d --- /dev/null +++ b/tags/n/no-versioned-debhelper-prerequisite.tag @@ -0,0 +1,28 @@ +Tag: no-versioned-debhelper-prerequisite +Severity: warning +Check: debhelper +Renamed-From: + package-needs-versioned-debhelper-build-depends + package-lacks-versioned-build-depends-on-debhelper +Explanation: 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. + . + The required version of debhelper is not guaranteed to be satisfied + in all supported releases of Debian and therefore this may lead to + a build failure. + . + The 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. + . + Packages not using an experimental or beta compatibility level may + alternatively Build-Depend on the debhelper-compat virtual package, for + example: + . + Build-Depends: debhelper-compat (= 13) + . + Note if you are using a compat level marked as experimental (such as + compat 12 in debhelper 11.4~) please explicitly override this tag. diff --git a/tags/n/node-package-install-in-nodejs-rootdir.tag b/tags/n/node-package-install-in-nodejs-rootdir.tag new file mode 100644 index 0000000..804998a --- /dev/null +++ b/tags/n/node-package-install-in-nodejs-rootdir.tag @@ -0,0 +1,5 @@ +Tag: node-package-install-in-nodejs-rootdir +Severity: error +Check: languages/javascript/nodejs +Explanation: This package contains a file under /usr/*/nodejs + instead of /usr/*/nodejs/${package}. diff --git a/tags/n/nodejs-lock-file.tag b/tags/n/nodejs-lock-file.tag new file mode 100644 index 0000000..105eda7 --- /dev/null +++ b/tags/n/nodejs-lock-file.tag @@ -0,0 +1,16 @@ +Tag: nodejs-lock-file +Severity: error +Check: languages/javascript/nodejs +Explanation: package-lock.json is automatically generated for any operations where + npm modifies either the node_modules tree, or package.json. It + describes the exact tree that was generated, such that subsequent + installs are able to generate identical trees, regardless of + intermediate dependency updates. + . + These information are useless from a debian point of view, because + version are managed by dpkg. + . + Moreover, package-lock.json feature to pin to some version + dependencies is a anti feature of the debian way of managing package, + and could lead to security problems in the likely case of debian + solving security problems by patching instead of upgrading. diff --git a/tags/n/nodejs-missing-version-override.tag b/tags/n/nodejs-missing-version-override.tag new file mode 100644 index 0000000..3987570 --- /dev/null +++ b/tags/n/nodejs-missing-version-override.tag @@ -0,0 +1,6 @@ +Tag: nodejs-missing-version-override +Severity: error +Check: languages/javascript/nodejs +Explanation: This package installs the specified nodejs module with a + wrong version. Upstream probably uses semantic-release to publish its + module. You must override this version field in related package.json. diff --git a/tags/n/nodejs-module-installed-in-bad-directory.tag b/tags/n/nodejs-module-installed-in-bad-directory.tag new file mode 100644 index 0000000..3c0847f --- /dev/null +++ b/tags/n/nodejs-module-installed-in-bad-directory.tag @@ -0,0 +1,9 @@ +Tag: nodejs-module-installed-in-bad-directory +Severity: warning +Check: languages/javascript/nodejs +Explanation: This package installs the specified nodejs module in a location that + does not match its name declared in package.json. This renders this module + unusable using a simple <code>require()</code>. + . + You can use pkg-js-tools auto installer to avoid this, see + <code>/usr/share/doc/pkg-js-tools/README.md.gz</code> diff --git a/tags/n/nodejs-module-installed-in-usr-lib.tag b/tags/n/nodejs-module-installed-in-usr-lib.tag new file mode 100644 index 0000000..3585495 --- /dev/null +++ b/tags/n/nodejs-module-installed-in-usr-lib.tag @@ -0,0 +1,11 @@ +Tag: nodejs-module-installed-in-usr-lib +Severity: warning +Check: languages/javascript/nodejs +Explanation: This package installs the specified file under <code>/usr/lib/nodejs</code>. + Since the release of Buster, these files should be installed under + <code>/usr/share/nodejs</code> (for arch *independent* modules) or + <code>/usr/lib/$DEB_HOST_MULTIARCH/nodejs</code> (for arch *dependent* modules) + instead. + . + You can use pkg-js-tools auto installer to avoid this, see + <code>/usr/share/doc/pkg-js-tools/README.md.gz</code> diff --git a/tags/n/nodejs-module-not-declared.tag b/tags/n/nodejs-module-not-declared.tag new file mode 100644 index 0000000..a15c0a1 --- /dev/null +++ b/tags/n/nodejs-module-not-declared.tag @@ -0,0 +1,8 @@ +Tag: nodejs-module-not-declared +Severity: warning +Check: languages/javascript/nodejs +Explanation: This package installs the specified nodejs module in a nodejs root + directory without declaring it in "Provides:" field in debian/control. + . + You can use <code>Provides: ${nodejs:Provides}</code> provided by pkg-js-tools + to fix this. See <code>/usr/share/doc/pkg-js-tools/README.md.gz</code> for more. diff --git a/tags/n/nodejs-module.tag b/tags/n/nodejs-module.tag new file mode 100644 index 0000000..76a28f5 --- /dev/null +++ b/tags/n/nodejs-module.tag @@ -0,0 +1,4 @@ +Tag: nodejs-module +Severity: classification +Check: languages/javascript/nodejs +Explanation: Display nodejs module name, version and path diff --git a/tags/n/non-conf-file-in-modprobe.d.tag b/tags/n/non-conf-file-in-modprobe.d.tag new file mode 100644 index 0000000..887d75d --- /dev/null +++ b/tags/n/non-conf-file-in-modprobe.d.tag @@ -0,0 +1,11 @@ +Tag: non-conf-file-in-modprobe.d +Severity: error +Check: modprobe +See-Also: https://lists.debian.org/debian-devel/2009/03/msg00119.html +Explanation: Files in <code>/etc/modprobe.d</code> should use filenames ending in + <code>.conf</code>. modprobe silently ignores all files which do not match + this convention. + . + If the file is an example containing only comments, consider installing + it in another location as files in <code>/etc/modprobe.d</code> are + read each time modprobe is run (which is often at boot time). diff --git a/tags/n/non-consecutive-debian-revision.tag b/tags/n/non-consecutive-debian-revision.tag new file mode 100644 index 0000000..08d73a6 --- /dev/null +++ b/tags/n/non-consecutive-debian-revision.tag @@ -0,0 +1,8 @@ +Tag: non-consecutive-debian-revision +Severity: pedantic +Check: debian/changelog +Experimental: yes +Explanation: The latest changelog entry refers to a Debian revision (eg. + <code>1.2-3</code>) that is not consecutive to the previous changelog entry + (eg. <code>1.2-2</code>). Please use a consecutive Debian revision or use a + UNRELEASED version instead. diff --git a/tags/n/non-debug-file-in-debug-package.tag b/tags/n/non-debug-file-in-debug-package.tag new file mode 100644 index 0000000..aded7d5 --- /dev/null +++ b/tags/n/non-debug-file-in-debug-package.tag @@ -0,0 +1,9 @@ +Tag: non-debug-file-in-debug-package +Severity: error +Check: files/debug-packages +Explanation: This auto-generated package (eg. <code>-dbgsym</code>) contains the + specified file that is not a <code>.debug</code> file. + . + This may be due to the upstream build system miscalculating + installation paths. +See-Also: Bug#958945 diff --git a/tags/n/non-empty-dependency_libs-in-la-file.tag b/tags/n/non-empty-dependency_libs-in-la-file.tag new file mode 100644 index 0000000..988f774 --- /dev/null +++ b/tags/n/non-empty-dependency_libs-in-la-file.tag @@ -0,0 +1,15 @@ +Tag: non-empty-dependency_libs-in-la-file +Severity: error +Check: build-systems/libtool/la-file +Explanation: The dependency_libs field in the .la file has not been cleared. It has + long been a release goal to get rid of unneeded .la files and clearing the + dependency_libs field from the rest of them. + . + A non-empty dependency_libs field will also stall the Multi-Arch + conversion. + . + The .la file in itself may be useful if the library is loaded dynamically + via libltdl. +See-Also: https://wiki.debian.org/ReleaseGoals/LAFileRemoval, + https://lists.debian.org/debian-devel/2011/05/msg01003.html, + https://lists.debian.org/debian-devel/2011/05/msg01146.html diff --git a/tags/n/non-etc-file-marked-as-conffile.tag b/tags/n/non-etc-file-marked-as-conffile.tag new file mode 100644 index 0000000..4744f8d --- /dev/null +++ b/tags/n/non-etc-file-marked-as-conffile.tag @@ -0,0 +1,7 @@ +Tag: non-etc-file-marked-as-conffile +Severity: error +Check: conffiles +Explanation: A file installed in some other directory than <code>/etc</code> + is marked as conffile. A conffile typically implies a configuration + file, and Policy mandates such files to be in <code>/etc</code>. +See-Also: debian-policy 10.7.2 diff --git a/tags/n/non-free-flash.tag b/tags/n/non-free-flash.tag new file mode 100644 index 0000000..777da0c --- /dev/null +++ b/tags/n/non-free-flash.tag @@ -0,0 +1,5 @@ +Tag: non-free-flash +Severity: error +Check: files/non-free +Explanation: 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. diff --git a/tags/n/non-multi-arch-lib-dir.tag b/tags/n/non-multi-arch-lib-dir.tag new file mode 100644 index 0000000..382f48b --- /dev/null +++ b/tags/n/non-multi-arch-lib-dir.tag @@ -0,0 +1,7 @@ +Tag: non-multi-arch-lib-dir +Severity: warning +Check: files/hierarchy/standard +Explanation: The following library use an old path (like /lib64 or /lib32) + instead of using multi-arch path (like for instance + /lib/x86_64-linux-gnu/ or /lib/i386-linux-gnu/). +See-Also: https://wiki.debian.org/Multiarch diff --git a/tags/n/non-standard-apache2-configuration-name.tag b/tags/n/non-standard-apache2-configuration-name.tag new file mode 100644 index 0000000..46e1ad2 --- /dev/null +++ b/tags/n/non-standard-apache2-configuration-name.tag @@ -0,0 +1,7 @@ +Tag: non-standard-apache2-configuration-name +Severity: warning +Check: apache2 +Explanation: The package appears to be a web application which is installing a + configuration file for the Apache2 HTTPD server. To avoid name clashes, any file + installed to <code>/etc/apache2/{sites,conf}-available</code> should match the binary package + name and must not start with <code>local-</code>. diff --git a/tags/n/non-standard-apache2-module-package-name.tag b/tags/n/non-standard-apache2-module-package-name.tag new file mode 100644 index 0000000..4a87400 --- /dev/null +++ b/tags/n/non-standard-apache2-module-package-name.tag @@ -0,0 +1,7 @@ +Tag: non-standard-apache2-module-package-name +Severity: warning +Check: apache2 +Explanation: The package appears to be an Apache2 HTTPD server module but it + does not follow the module naming scheme. Apache2 HTTPD modules should + be called <code>libapache2-mod-name</code> with <code>mod-name</code> being the + actual <code>mod_name.so</code> equivalent. diff --git a/tags/n/non-standard-dir-in-usr.tag b/tags/n/non-standard-dir-in-usr.tag new file mode 100644 index 0000000..c87390e --- /dev/null +++ b/tags/n/non-standard-dir-in-usr.tag @@ -0,0 +1,8 @@ +Tag: non-standard-dir-in-usr +Severity: warning +Check: files/hierarchy/standard +Explanation: The FHS says "No large software packages should use a direct + subdirectory under the <code>/usr</code> hierarchy". This package contains + a directory in <code>/usr</code> that is not mentioned in the Filesystem + Hierarchy Standard. +See-Also: filesystem-hierarchy theusrhierarchy diff --git a/tags/n/non-standard-dir-in-var.tag b/tags/n/non-standard-dir-in-var.tag new file mode 100644 index 0000000..bfa3543 --- /dev/null +++ b/tags/n/non-standard-dir-in-var.tag @@ -0,0 +1,8 @@ +Tag: non-standard-dir-in-var +Severity: error +Check: files/hierarchy/standard +Explanation: The FHS says "Applications should generally not add directories to + the top level of <code>/var</code>. Such directories should only be added + if they have some system-wide implication, and in consultation with the + FHS mailing list." +See-Also: filesystem-hierarchy thevarhierarchy diff --git a/tags/n/non-standard-dir-perm.tag b/tags/n/non-standard-dir-perm.tag new file mode 100644 index 0000000..013aa82 --- /dev/null +++ b/tags/n/non-standard-dir-perm.tag @@ -0,0 +1,6 @@ +Tag: non-standard-dir-perm +Severity: warning +Check: files/permissions +Explanation: The directory has a mode different from 0755, and it's not one of the + known exceptions. +See-Also: debian-policy 10.9 diff --git a/tags/n/non-standard-executable-perm.tag b/tags/n/non-standard-executable-perm.tag new file mode 100644 index 0000000..119271f --- /dev/null +++ b/tags/n/non-standard-executable-perm.tag @@ -0,0 +1,8 @@ +Tag: non-standard-executable-perm +Severity: warning +Check: files/permissions +Explanation: 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. +See-Also: debian-policy 10.9 diff --git a/tags/n/non-standard-file-perm.tag b/tags/n/non-standard-file-perm.tag new file mode 100644 index 0000000..72465a6 --- /dev/null +++ b/tags/n/non-standard-file-perm.tag @@ -0,0 +1,32 @@ +Tag: non-standard-file-perm +Severity: warning +Check: files/permissions +Explanation: The file has a mode different from 0644. In some cases this is + intentional, but in other cases this is a bug. +See-Also: debian-policy 10.9 + +Screen: toolchain/gnat/ali-read-only +Advocates: Nicolas Boulenguez <nicolas@debian.org> +Reason: In GNAT, the compiler also deals with dependencies and rebuild order. + The <code>.ali</code> files contain the dependency information required to detect + if a <code>.o</code> is more recent than the closure of all sources it depends + upon, or if it should be rebuilt. + . + By convention, a read-only <code>.ali</code> file tells <code>GNAT</code> to fail if + the <code>.o</code> is obsolete or unavailable, instead of attempting to rebuild. + This is recommended for packaged libraries (the <code>.so</code> or <code>.a</code> + are available but not the <code>.o</code> files). + . + This convention may seem bizarre according to modern standards, but it + has been in use for 25 years, so Adacore would probably need a + compelling reason to break it. + . + See also Debian Policy 8.4, which explicitly requires this: + . + If the package provides Ada Library Information (<code>*.ali</code>) files for use + with <code>GNAT</code>, these files must be installed read-only (mode 0444) so that + <code>GNAT</code> will not attempt to recompile them. This overrides the normal + file mode requirements given in "Permissions and owners." +See-Also: + debian-policy 8.4, + Bug#986400 diff --git a/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag b/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag new file mode 100644 index 0000000..ed449d9 --- /dev/null +++ b/tags/n/non-standard-file-permissions-for-etc-init.d-script.tag @@ -0,0 +1,5 @@ +Tag: non-standard-file-permissions-for-etc-init.d-script +Severity: error +Check: files/init +Explanation: Usually, scripts in the <code>/etc/init.d</code> directory should have + mode 0755. diff --git a/tags/n/non-standard-game-executable-perm.tag b/tags/n/non-standard-game-executable-perm.tag new file mode 100644 index 0000000..f113c7a --- /dev/null +++ b/tags/n/non-standard-game-executable-perm.tag @@ -0,0 +1,8 @@ +Tag: non-standard-game-executable-perm +Severity: warning +Check: files/permissions +Explanation: 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. +See-Also: debian-policy 11.11 diff --git a/tags/n/non-standard-setuid-executable-perm.tag b/tags/n/non-standard-setuid-executable-perm.tag new file mode 100644 index 0000000..57c42d0 --- /dev/null +++ b/tags/n/non-standard-setuid-executable-perm.tag @@ -0,0 +1,10 @@ +Tag: non-standard-setuid-executable-perm +Severity: warning +Check: files/permissions +Explanation: 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. +See-Also: debian-policy 10.9 diff --git a/tags/n/non-standard-toplevel-dir.tag b/tags/n/non-standard-toplevel-dir.tag new file mode 100644 index 0000000..5db8e4c --- /dev/null +++ b/tags/n/non-standard-toplevel-dir.tag @@ -0,0 +1,6 @@ +Tag: non-standard-toplevel-dir +Severity: error +Check: files/hierarchy/standard +Explanation: The Filesystem Hierarchy Standard forbids the installation of new + files or directories in the root directory. +See-Also: filesystem-hierarchy therootfilesystem diff --git a/tags/n/non-virtual-facility-in-initd-script.tag b/tags/n/non-virtual-facility-in-initd-script.tag new file mode 100644 index 0000000..bf1a4b4 --- /dev/null +++ b/tags/n/non-virtual-facility-in-initd-script.tag @@ -0,0 +1,14 @@ +Tag: non-virtual-facility-in-initd-script +Severity: error +Check: init-d +Renamed-From: init.d-script-should-depend-on-virtual-facility +Explanation: The given <code>/etc/init.d</code> 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 + <code>$network</code> rather than the facility <code>networking</code>, and the + virtual facility <code>$named</code> rather than the specific facility + <code>bind9</code>. + . + 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. diff --git a/tags/n/non-wm-in-windowmanager-menu-section.tag b/tags/n/non-wm-in-windowmanager-menu-section.tag new file mode 100644 index 0000000..8c27d27 --- /dev/null +++ b/tags/n/non-wm-in-windowmanager-menu-section.tag @@ -0,0 +1,8 @@ +Tag: non-wm-in-windowmanager-menu-section +Severity: error +Check: menu-format +Explanation: The <code>menu</code> item is in the <code>Window Manager</code> + section but does not specify <code>needs=wm</code>. + . + If the application is a window manager, it should specify <code>needs=wm</code>. + Otherwise, it should be moved to another section. diff --git a/tags/n/non-wm-module-in-wm-modules-menu-section.tag b/tags/n/non-wm-module-in-wm-modules-menu-section.tag new file mode 100644 index 0000000..8ffa83b --- /dev/null +++ b/tags/n/non-wm-module-in-wm-modules-menu-section.tag @@ -0,0 +1,10 @@ +Tag: non-wm-module-in-wm-modules-menu-section +Severity: error +Check: menu-format +Explanation: The <code>menu</code> item is in the section for <code>FVWM Modules</code> + or <code>Window Maker</code> but a window manager as a prerequisite via the + <code>needs</code> key in the <code>menu</code> file. + . + Modules for Fvwm should list <code>needs="fvwmmodule"</code>. + . + Modules for WindowMaker should list <code>needs="wmmaker"</code>. diff --git a/tags/n/not-allowed-control-file.tag b/tags/n/not-allowed-control-file.tag new file mode 100644 index 0000000..89056ce --- /dev/null +++ b/tags/n/not-allowed-control-file.tag @@ -0,0 +1,7 @@ +Tag: not-allowed-control-file +Severity: error +Check: control-files +Explanation: 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. diff --git a/tags/n/not-binnmuable-all-depends-any.tag b/tags/n/not-binnmuable-all-depends-any.tag new file mode 100644 index 0000000..32ee806 --- /dev/null +++ b/tags/n/not-binnmuable-all-depends-any.tag @@ -0,0 +1,14 @@ +Tag: not-binnmuable-all-depends-any +Severity: error +Check: debian/version-substvars +Explanation: 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~) diff --git a/tags/n/not-binnmuable-any-depends-all.tag b/tags/n/not-binnmuable-any-depends-all.tag new file mode 100644 index 0000000..41c53ce --- /dev/null +++ b/tags/n/not-binnmuable-any-depends-all.tag @@ -0,0 +1,9 @@ +Tag: not-binnmuable-any-depends-all +Severity: error +Check: debian/version-substvars +Explanation: The package is not safely binNMUable because an arch:any package + depends on an arch:all package with a (= ${binary:Version}) + relationship. Please use (= ${source:Version}) instead. + . + Note this is also triggered if the dependency uses (>= ${var}), + since that has the same issue. diff --git a/tags/n/not-binnmuable-any-depends-any.tag b/tags/n/not-binnmuable-any-depends-any.tag new file mode 100644 index 0000000..60b202b --- /dev/null +++ b/tags/n/not-binnmuable-any-depends-any.tag @@ -0,0 +1,6 @@ +Tag: not-binnmuable-any-depends-any +Severity: error +Check: debian/version-substvars +Explanation: 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. diff --git a/tags/n/not-using-po-debconf.tag b/tags/n/not-using-po-debconf.tag new file mode 100644 index 0000000..d620dda --- /dev/null +++ b/tags/n/not-using-po-debconf.tag @@ -0,0 +1,8 @@ +Tag: not-using-po-debconf +Severity: error +Check: debian/po-debconf +Explanation: This package seems to be using debconf templates, but it does not + use po-debconf to make translations possible (<code>debian/po</code> doesn't + exist). Debian Policy requires that all packages using debconf use a + gettext-based translation system. +See-Also: debian-policy 3.9.1 diff --git a/tags/n/number-of-patches.tag b/tags/n/number-of-patches.tag new file mode 100644 index 0000000..2402b4b --- /dev/null +++ b/tags/n/number-of-patches.tag @@ -0,0 +1,5 @@ +Tag: number-of-patches +Severity: classification +Check: debian/patches/count +Explanation: The number of patches according to the + <code>debian/patches/series</code> file. |