W: grub2-themes-ubuntustudio source: package-needs-versioned-debhelper-build-depends 12 N: N: The package either doesn't declare a versioned build dependency on N: debhelper or does not declare a versioned build dependency on a new N: enough version of debhelper to satisfy the declared compatibility level. N: N: The required version of debhelper is not guaranteed to be satisfied in N: all supported releases of Debian and therefore this may lead to a build N: failure. N: N: The recommended practice is to always declare an explicit versioned N: dependency on debhelper equal to or greater than the compatibility level N: used by the package, even if the versioned dependency isn't strictly N: necessary. Having a versioned dependency also helps with backports to N: older releases and correct builds on partially updated systems. N: N: Packages not using an experimental or beta compatibility level may N: alternatively Build-Depend on the debhelper-compat virtual package, for N: example: N: N: Build-Depends: debhelper-compat (= 12) N: N: Note if you are using a compat level marked as experimental (such as N: compat 12 in debhelper 11.4~) please explicitly override this tag. N: N: Refer to the debhelper(7) manual page for details. N: N: Severity: minor, Certainty: certain N: N: Check: debhelper, Type: source N: W: grub2-themes-ubuntustudio source: binary-nmu-debian-revision-in-source 0.1-0~201903030148~ubuntu19.04.1 N: N: The version number of your source package ends in +b and a number or has N: a Debian revision containing three parts. These version numbers are used N: by binary NMUs and should not be used as the source version. (The +b N: form is the current standard; the three-part version number now N: obsolete.) N: N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or N: binary-only NMU) for details. N: N: Severity: normal, Certainty: certain N: N: Check: fields, Type: binary, udeb, source N: W: grub2-themes-ubuntustudio source: hyphen-in-native-debian-changelog-version 0.1-0~201903030148~ubuntu19.04.1 N: N: Native packaging should only be used if a piece of software was written N: specifically to be turned into a Debian package. In this case, the N: version number should not contain a Debian revision part. N: N: Native source packages are sometimes created by accident. In most cases N: the reason is the location of the original source tarball. For version N: 1.0 source packages, dpkg-source determines whether they're non-native N: by looking for a file named _.orig.tar.gz in the N: parent directory, where is the upstream version from the N: most recent debian/changelog entry. For version 3.0 packages, check N: debian/source/format for an erroneous "(native)" package format. N: N: Severity: normal, Certainty: certain N: N: Check: source-changelog, Type: source N: P: grub2-themes-ubuntustudio source: insecure-copyright-format-uri http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ N: N: Format URI of the machine-readable copyright file uses the plain HTTP N: unencrypted transport protocol. Using HTTPS is preferred since policy N: 4.0.0. N: N: Please use N: https://www.debian.org/doc/packaging-manuals/copyright-format// N: as the format URI instead. N: N: Refer to N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for N: details. N: N: Severity: pedantic, Certainty: certain N: N: Check: source-copyright, Type: source N: W: grub2-themes-ubuntustudio source: field-name-typo-in-dep5-copyright licence -> license (line 23) N: N: The listed field name is a likely misspelling of one of the documented N: DEP 5 fields. N: N: Lintian will continue by using the "misspelled" variant, but other N: parsers are unlikely to do so. N: N: Implementation detail: The typo is detected by using "Levenshtein edit N: distance". Therefore, if the typo involve several characters, Lintian N: may not detect it. N: N: Severity: normal, Certainty: possible N: N: Check: source-copyright, Type: source N: I: grub2-themes-ubuntustudio source: testsuite-autopkgtest-missing N: N: This package does not declare a test suite. N: N: Having a test suite aids with automated quality assurance of the archive N: outside of your package. For example, if your package has a test suite N: it is possible to re-run that test suite when any of your package's N: dependencies have a new version and check whether that update causes N: problems for your package. N: N: In addition, since May 2018 such tests now influence migration from N: unstable to testing: N: N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html N: N: Please add a debian/tests/control file to your package to declare a N: testsuite, but please make sure to only add autopkgtests if they provide N: meaningful coverage of your package. N: N: Refer to https://ci.debian.net/doc/ for details. N: N: Severity: wishlist, Certainty: certain N: N: Check: testsuite, Type: source N: