diff options
Diffstat (limited to '')
-rw-r--r-- | tags/g/game-outside-section.tag | 7 | ||||
-rw-r--r-- | tags/g/gawk-script-but-no-gawk-dep.tag | 9 | ||||
-rw-r--r-- | tags/g/generated-file.tag | 12 | ||||
-rw-r--r-- | tags/g/gfortran-module-does-not-declare-version.tag | 9 | ||||
-rw-r--r-- | tags/g/gir-in-arch-all-package.tag | 8 | ||||
-rw-r--r-- | tags/g/gir-missing-typelib-dependency.tag | 25 | ||||
-rw-r--r-- | tags/g/gir-section-not-libdevel.tag | 10 | ||||
-rw-r--r-- | tags/g/git-patches-not-exported.tag | 15 | ||||
-rw-r--r-- | tags/g/global-data-in-games-directory.tag | 14 | ||||
-rw-r--r-- | tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag | 15 | ||||
-rw-r--r-- | tags/g/globbing-patterns-out-of-order.tag | 13 | ||||
-rw-r--r-- | tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag | 11 | ||||
-rw-r--r-- | tags/g/groff-message.tag | 39 | ||||
-rw-r--r-- | tags/g/gzip-file-is-not-multi-arch-same-safe.tag | 8 |
14 files changed, 195 insertions, 0 deletions
diff --git a/tags/g/game-outside-section.tag b/tags/g/game-outside-section.tag new file mode 100644 index 0000000..2a087e2 --- /dev/null +++ b/tags/g/game-outside-section.tag @@ -0,0 +1,7 @@ +Tag: game-outside-section +Severity: warning +Check: games +Renamed-From: games-package-should-be-section-games +Explanation: All the executables in this package are in <code>/usr/games</code>, but + the package is not in section games. This can be intentional but is + usually a mistake. diff --git a/tags/g/gawk-script-but-no-gawk-dep.tag b/tags/g/gawk-script-but-no-gawk-dep.tag new file mode 100644 index 0000000..81eaf4b --- /dev/null +++ b/tags/g/gawk-script-but-no-gawk-dep.tag @@ -0,0 +1,9 @@ +Tag: gawk-script-but-no-gawk-dep +Severity: error +Check: scripts +Explanation: 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. diff --git a/tags/g/generated-file.tag b/tags/g/generated-file.tag new file mode 100644 index 0000000..af3ef04 --- /dev/null +++ b/tags/g/generated-file.tag @@ -0,0 +1,12 @@ +Tag: generated-file +Severity: classification +Check: files/generated +Explanation: This file contains a common marker for generated files. + . + Some examples are: + . + - <code>DO NOT EDIT BY HAND</code> + - <code>file was autogenerated</code> + . + In general, Debian likes to ship only true source files. Please consider + asking upstream to generate the file during the build process instead. diff --git a/tags/g/gfortran-module-does-not-declare-version.tag b/tags/g/gfortran-module-does-not-declare-version.tag new file mode 100644 index 0000000..38ae3e0 --- /dev/null +++ b/tags/g/gfortran-module-does-not-declare-version.tag @@ -0,0 +1,9 @@ +Tag: gfortran-module-does-not-declare-version +Severity: warning +Check: languages/fortran/gfortran +Explanation: The installation package ships a GFORTRAN module which does not + declare a module version number. That number is needed to establish the + proper prerequisites for binary rebuilds. +See-Also: Bug#796352, + Bug#714730, + https://salsa.debian.org/science-team/dh-fortran-mod/blob/debian/master/dh_fortran_mod.in diff --git a/tags/g/gir-in-arch-all-package.tag b/tags/g/gir-in-arch-all-package.tag new file mode 100644 index 0000000..74276f6 --- /dev/null +++ b/tags/g/gir-in-arch-all-package.tag @@ -0,0 +1,8 @@ +Tag: gir-in-arch-all-package +Severity: warning +Check: desktop/gnome/gir +Explanation: GObject-Introspection XML files + (<code>/usr/share/gir-1.0/Foo-23.gir</code>) must be made available in + an architecture-dependent package of the same source. +See-Also: + /usr/share/doc/gobject-introspection/policy.txt diff --git a/tags/g/gir-missing-typelib-dependency.tag b/tags/g/gir-missing-typelib-dependency.tag new file mode 100644 index 0000000..1b467b8 --- /dev/null +++ b/tags/g/gir-missing-typelib-dependency.tag @@ -0,0 +1,25 @@ +Tag: gir-missing-typelib-dependency +Severity: warning +Check: desktop/gnome/gir +Explanation: Development packages that contain GObject-Introspection XML files + (<code>/usr/share/gir-1.0/Foo-23.gir</code>) must depend on the package + containing the corresponding binary typelib, which is conventionally named + <code>gir1.2-foo-23</code>. The dependency must be strictly versioned + (for example <code>gir1.2-foo-23 (= ${binary:Version})</code> when using + debhelper). + . + If multiple typelibs are shipped in the same package, then that package + should have versioned <code>Provides</code> for the names that would have been + used for separate packages. In this case, Lintian does not emit this tag + when a group of binary packages from the same source is checked together. + . + For example, <code>libgtk-3-dev</code> contains <code>Gtk-3.0.gir</code>, + <code>Gdk-3.0.gir</code> and <code>GdkX11-3.0.gir</code>. + <code>gir1.2-gtk-3.0</code> contains all three corresponding typelibs, + so it is sufficient for <code>libgtk-3-dev</code> to depend on + <code>gir1.2-gtk-3.0</code>. Giving <code>gir1.2-gtk-3.0</code> <code>Provides</code> + entries for <code>gir1.2-gdk-3.0 (= ${binary:Version})</code> + and <code>gir1.2-gdkx11-3.0 (= ${binary:Version})</code> signals this + situation to Lintian. +See-Also: + /usr/share/doc/gobject-introspection/policy.txt diff --git a/tags/g/gir-section-not-libdevel.tag b/tags/g/gir-section-not-libdevel.tag new file mode 100644 index 0000000..8e050ea --- /dev/null +++ b/tags/g/gir-section-not-libdevel.tag @@ -0,0 +1,10 @@ +Tag: gir-section-not-libdevel +Severity: warning +Check: desktop/gnome/gir +Explanation: GObject-Introspection XML files + (<code>/usr/share/gir-1.0/Foo-23.gir</code>) must be made available in + a development package in the <code>libdevel</code> section of the archive. + This is normally the same <code>libfoo-dev</code> package that contains + other development files. +See-Also: + /usr/share/doc/gobject-introspection/policy.txt diff --git a/tags/g/git-patches-not-exported.tag b/tags/g/git-patches-not-exported.tag new file mode 100644 index 0000000..deb14ad --- /dev/null +++ b/tags/g/git-patches-not-exported.tag @@ -0,0 +1,15 @@ +Tag: git-patches-not-exported +Severity: error +Check: debian/source-dir +Explanation: The source package contains files in + <code>debian/source/git-patches</code>. These patches should have been exported + via the <code>quilt-patches-deb-export-hook</code> of <code>gitpkg</code>. + . + It does not look like the patches were exported for this source package. + . + You will see this tag when you generate a source package without + <code>gitpkg</code> (or with a misconfigured version) unless the patches + were exported manually. + . + See the above mentioned hook file (in <code>/usr/share/gitpkg/hooks</code>) + for information on how to export patches manually. diff --git a/tags/g/global-data-in-games-directory.tag b/tags/g/global-data-in-games-directory.tag new file mode 100644 index 0000000..dabec16 --- /dev/null +++ b/tags/g/global-data-in-games-directory.tag @@ -0,0 +1,14 @@ +Tag: global-data-in-games-directory +Severity: error +Check: games +Explanation: This package contains files under <code>/usr/share/games</code>, 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 <code>/usr/share</code> 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 + <code>--datadir=/usr/share/games</code> argument to configure or an + equivalent and using the upstream installation rules. These files need + to be moved into the corresponding directories directly under + <code>/usr/share</code>. diff --git a/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag b/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag new file mode 100644 index 0000000..7f4e0b9 --- /dev/null +++ b/tags/g/global-files-wildcard-not-first-paragraph-in-dep5-copyright.tag @@ -0,0 +1,15 @@ +Tag: global-files-wildcard-not-first-paragraph-in-dep5-copyright +Severity: warning +Check: debian/copyright/dep5 +Explanation: The specified paragraph in the machine readable copyright file references + all possible files but is not the first paragraph. For example: + . + Files: filea + Copyright: 2009, ... + . + Files: * + Copyright: 2010, ... + . + As the paragraphs is matched on a "last match wins" principle, all proceeding + paragraphs are overridden. +See-Also: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff --git a/tags/g/globbing-patterns-out-of-order.tag b/tags/g/globbing-patterns-out-of-order.tag new file mode 100644 index 0000000..88237d2 --- /dev/null +++ b/tags/g/globbing-patterns-out-of-order.tag @@ -0,0 +1,13 @@ +Tag: globbing-patterns-out-of-order +Severity: warning +Check: debian/copyright/dep5 +Explanation: The <code>Files</code> sections in debian/copyright are out of order. + The relative directory depth should increase from one section to the next. + That is the general pattern of the specification, with * at the top. + . + When sections are in another order, some files may be associated + with the wrong license. + . + Please reorder the sections. +See-Also: Bug#905747, + https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ diff --git a/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag b/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag new file mode 100644 index 0000000..0cf432c --- /dev/null +++ b/tags/g/gobject-introspection-package-missing-depends-on-gir-depends.tag @@ -0,0 +1,11 @@ +Tag: gobject-introspection-package-missing-depends-on-gir-depends +Severity: error +Check: desktop/gnome/gir/substvars +Explanation: The package in <code>debian/control</code> is a GObject Introspection + installation package but does not declare its prerequisites using the + <code>${gir:Depends}</code> substvar. + . + Without proper runtime prerequisites, a program usually aborts. + . + This tag can often be fixed by adding the <code>--with=gir</code> Debhelper + sequence. diff --git a/tags/g/groff-message.tag b/tags/g/groff-message.tag new file mode 100644 index 0000000..767a486 --- /dev/null +++ b/tags/g/groff-message.tag @@ -0,0 +1,39 @@ +Tag: groff-message +Severity: warning +Check: documentation/manual +Renamed-From: manpage-has-errors-from-man +Explanation: A manual page provoked warnings or errors from the <code>man</code> + program. Here are some common ones: + . + "cannot adjust" or "can't break" are issues with paragraph filling. They + are usually related to long lines. Justifying text on the left hand side + can help with adjustments. Hyphenation can help with breaks. + . + For more information, please see "Manipulating Filling and Adjusting" + and "Manipulating Hyphenation" in the Groff manual (see <code>info groff</code>). + . + "can't find numbered character" usually means that the input was in a + national legacy encoding. The warning means that some characters were + dropped. Please use escapes such as <code>\[:a]</code> as described on the + <code>groff_char</code> manual page. + . + Other common warnings are formatting typos. String arguments to + <code>.IP</code> require quotes. Usually, some text is lost or mangled. See + the <code>groff_man</code> (or <code>groff_mdoc</code> if using <code>mdoc</code>) + manual page for details on macros. + . + The check for manual pages uses the <code>--warnings</code> option to + <code>man</code> to catch common problems, like a <code>.</code> or a <code>'</code> + at the beginning of a line as literal text. They are interpreted as + Groff commands. Just reformat the paragraph so the characters are not at + the beginning of a line. You can also add a zero-width space (<code>\&</code>) + in front of them. + . + Aside from overrides, warnings can be disabled with the <code>.warn</code> + directive. Please see "Debugging" in the Groff manual. + . + You can see the warnings yourself by running the command used by Lintian: + . + <code>LC_ALL=C.UTF-8 MANROFFSEQ='' MANWIDTH=80 \ + man --warnings -E UTF-8 -l -Tutf8 -Z <file> >/dev/null</code> +See-Also: groff_man(7), groff_mdoc(7) diff --git a/tags/g/gzip-file-is-not-multi-arch-same-safe.tag b/tags/g/gzip-file-is-not-multi-arch-same-safe.tag new file mode 100644 index 0000000..1c2f0d2 --- /dev/null +++ b/tags/g/gzip-file-is-not-multi-arch-same-safe.tag @@ -0,0 +1,8 @@ +Tag: gzip-file-is-not-multi-arch-same-safe +Severity: error +Check: files/compressed/gz +Explanation: The gzip file contains a timestamp that will differ between + architectures. Multi-Arch: same implies all shared files must be + byte-for-byte identical. + . + This can usually be fixed by passing -n to gzip. |