1{"tags": [{"severity": "error", "package": "kbarcode-trinity", "tag": "epoch-changed-but-upstream-version-did-not-go-backwards", "explanation": "The previous version of this package had a different version epoch to\nthe current version but the upstream version did not go \"backwards\". For\nexample, the previous package version was \"1:1.0-1\" and the current\nversion is \"2:2.0-1\".\n\nThis was likely an accidental bump or addition of an epoch.\n\nEpochs exist to cope with changes to the upstream version numbering\nscheme. Whilst they are a powerful tool, increasing or adding an epoch\nhas many downsides including causing issues with versioned dependencies,\nbeing misleading to users and being aesthetically unappealing. Whilst\nthey should be avoided, valid reasons to add or increment the epoch\ninclude:\n\n- Upstream changed their versioning scheme in a way that makes the\nlatest version lower than the previous one.\n- You need to permanently revert to a lower upstream version.\n\nTemporary revertions (eg. after an NMU) should use not modify or\nintroduce an epoch - please use the CURRENT+reallyFORMER until you can\nupload the latest version again.\n\nIf you are unsure whether you need to increase the epoch for a package,\nplease consult the debian-devel mailing list.\n\nSeverity: error\n\nCheck: debian/changelog", "comment": "", "note": "2.0.6-0ubuntu3 -> 4:14.2.0~pre47-0ubuntu20.04.0+7", "pointer": ""}, {"severity": "error", "package": "kbarcode-trinity", "tag": "missing-build-dependency", "explanation": "The package doesn't specify a build dependency on a package that is used\nin debian/rules.\n\nLintian intentionally does not take into account transitive\ndependencies. Even if the package build-depends on some package that in\nturn depends on the needed package, an explicit build dependency should\nbe added. Otherwise, a latent bug is created that will appear without\nwarning if the other package is ever updated to change its dependencies.\nEven if this seems unlikely, please always add explicit build\ndependencies on every non-essential, non-build-essential package that is\nused directly during the build.\n\nRefer to Debian Policy Manual section 4.2 (Package relationships) for\ndetails.\n\nSeverity: error\n\nCheck: debian/rules", "comment": "", "note": "cdbs", "pointer": ""}, {"severity": "warning", "package": "kbarcode-trinity", "tag": "ancient-standards-version", "explanation": "The source package refers to a Standards-Version that has been obsolete\nfor more than two years. Please update your package to latest Policy and\nset this control field appropriately.\n\nIf the package is already compliant with the current standards, you\ndon't have to re-upload the package just to adjust the Standards-Version\ncontrol field. However, please remember to update this field next time\nyou upload the package.\n\nSee /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the\ndebian-policy package for a summary of changes in newer versions of\nPolicy.\n\nRefer to\nhttps://www.debian.org/doc/debian-policy/upgrading-checklist.html for\ndetails.\n\nSeverity: warning\n\nCheck: fields/standards-version", "comment": "", "note": "3.8.4 (released 2010-01-27) (current is 4.5.0)", "pointer": ""}, {"severity": "warning", "package": "kbarcode-trinity", "tag": "binary-nmu-debian-revision-in-source", "explanation": "The version number of your source package ends in +b and a number or has\na Debian revision containing three parts. These version numbers are used\nby binary NMUs and should not be used as the source version. (The +b\nform is the current standard; the three-part version number now\nobsolete.)\n\nRefer to Debian Developer's Reference section 5.10.2.1 (Recompilation or\nbinary-only NMU) for details.\n\nSeverity: warning\n\nCheck: fields/version", "comment": "", "note": "4:14.2.0~pre47-0ubuntu20.04.0+7", "pointer": ""}, {"severity": "warning", "package": "kbarcode-trinity", "tag": "debian-source-options-has-custom-compression-settings", "explanation": "The debian/source/options file for this package specifies a custom\ncompression level or algorithm.\n\nWhilst higher levels may reduce the size of big files, they have the\nside effect of consuming a lot of memory during both compression and\nextraction. This can not only also waste time unnecessarily, it can\ncause packages to FTBFS or even fail to install in resource-constrained\nenvironments or architectures.\n\nPlease remove the call and let dpkg-deb(1) select suitable defaults.\n\nRefer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page\nfor details.\n\nSeverity: warning\n\nCheck: debian/source-dir", "comment": "", "note": "compression = \"xz\" (line 2)", "pointer": ""}, {"severity": "warning", "package": "kbarcode-trinity", "tag": "debian-source-options-has-custom-compression-settings", "explanation": "", "comment": "", "note": "compression-level = 9 (line 3)", "pointer": ""}, {"severity": "warning", "package": "kbarcode-trinity", "tag": "epoch-change-without-comment", "explanation": "The previous version of this package had a different version epoch (eg.\n2:1.0-1) to the current version but there's no reference to this in the\nchangelog entry.\n\nEpochs exist to cope with changes to the upstream version numbering\nscheme. Whilst they are a powerful tool, increasing or adding an epoch\nhas many downsides including causing issues with versioned dependencies,\nbeing misleading to users and being aesthetically unappealing. Whilst\nthey should be avoided, valid reasons to add or increment the epoch\ninclude:\n\n- Upstream changed their versioning scheme in a way that makes the\nlatest version lower than the previous one.\n- You need to permanently revert to a lower upstream version.\n\nTemporary revertions (eg. after an NMU) should use not modify or\nintroduce an epoch - please use the CURRENT+reallyFORMER until you can\nupload the latest version again.\n\nIf you are unsure whether you need to increase the epoch for a package,\nplease consult the debian-devel mailing list.\n\nLintian looks in this version's changelog entry for the phrase \"epoch\".\n\nSeverity: warning\n\nCheck: debian/changelog", "comment": "", "note": "2.0.6-0ubuntu3 -> 4:14.2.0~pre47-0ubuntu20.04.0+7", "pointer": ""}, {"severity": "info", "package": "kbarcode-trinity", "tag": "debian-watch-file-is-missing", "explanation": "This source package is not Debian-native but it does not have a\ndebian/watch file. This file is used for automatic detection of new\nupstream versions by the Debian External Health Status project and other\nproject infrastructure. If this package is maintained upstream, please\nconsider adding a debian/watch file to detect new releases.\n\nIf the package is not maintained upstream or if upstream uses a\ndistribution mechanism that cannot be meaningfully monitored by uscan\nand the Debian External Health Status project, please consider adding a\ndebian/watch file containing only comments documenting the situation.\n\nRefer to Debian Policy Manual section 4.11 (Optional upstream source\nlocation: debian/watch) and the uscan(1) manual page for details.\n\nSeverity: info\n\nCheck: debian/watch", "comment": "", "note": "", "pointer": ""}, {"severity": "info", "package": "kbarcode-trinity", "tag": "no-dh-sequencer", "explanation": "This package does not use the dh sequencer in debian/rules.\n\nWhile maintainers may use a variety of build systems, this one is by far\nthe most popular.\n\nMaintainers are strongly encouraged to use the dh sequencer in new\npackages and convert existing ones when appropriate.\n\nSeverity: info\n\nCheck: debian/rules/dh-sequencer", "comment": "", "note": "", "pointer": ""}, {"severity": "info", "package": "kbarcode-trinity", "tag": "testsuite-autopkgtest-missing", "explanation": "This package does not declare a test suite.\n\nHaving a test suite aids with automated quality assurance of the archive\noutside of your package. For example, if your package has a test suite\nit is possible to re-run that test suite when any of your package's\ndependencies have a new version and check whether that update causes\nproblems for your package.\n\nIn addition, since May 2018 these tests now influence migration from\nunstable to testing:\n\nhttps://lists.debian.org/debian-devel-announce/2018/05/msg00001.html\n\nPlease add a debian/tests/control file to your package to declare a\ntestsuite, but please make sure to only add autopkgtests if they provide\nmeaningful coverage of your package.\n\nRefer to https://ci.debian.net/doc/ for details.\n\nSeverity: info\n\nCheck: testsuite", "comment": "", "note": "", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "co-maintained-package-with-no-vcs-fields", "explanation": "Based on the content of the maintainer and uploader fields this package\nis co-maintained but there are no Vcs-* fields.\n\nIt is recommended that shared maintenance of packages are co-ordinated\nvia a revision control system.\n\nSeverity: pedantic\n\nCheck: fields/vcs", "comment": "", "note": "", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "file-contains-trailing-whitespace", "explanation": "This file appears to contain one or more lines with trailing whitespace\ncharacters.\n\nWhilst typically harmless and merely unsightly, they can often cause\ndifficult-to-spot issues where tools interpret the whitespace characters\nliterally as well as introduce unnecessary diff(1) noise. They are thus\nbest avoided in their entirity.\n\nWhitespace at the end of lines may be removed with the following:\n\n$ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog\n\nIf you use Emacs, you can also use \"M-x wh-cl\" (whitespace-cleanup).\n\nHowever, if you wish to only remove trailing spaces and leave trailing\ntabs (eg. for Makefiles), you can use the following code snippet:\n\n$ sed -i -e 's@[ ]*$@@g' debian/rules\n\nTo remove empty lines from the end of a file, you can use:\n\n$ sed -i -e :a -e '/^\\n*$/{$d;N;};/\\n$/ba' debian/rules\n\nSeverity: pedantic\n\nCheck: cruft", "comment": "", "note": "debian/changelog (line 148)", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "file-contains-trailing-whitespace", "explanation": "", "comment": "", "note": "debian/changelog (line 170)", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "no-dep5-copyright", "explanation": "This package does not use a machine-readable debian/copyright file.\n\nThis format makes it easier to review licenses and can be easily parsed\nby Lintian.\n\nRefer to\nhttps://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for\ndetails.\n\nSeverity: pedantic\n\nCheck: debian/copyright", "comment": "", "note": "", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "no-homepage-field", "explanation": "This non-native package lacks a Homepage field. If the package has an\nupstream home page that contains useful information or resources for the\nend user, consider adding a Homepage control field to debian/control.\n\nRefer to Debian Policy Manual section 5.6.23 (Homepage) for details.\n\nSeverity: pedantic\n\nCheck: fields/homepage", "comment": "", "note": "", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "package-uses-old-debhelper-compat-version", "explanation": "The debhelper compatibility version used by this package is marked as\nnot recommended by the debhelper developer. You may consider using a\nrecommended compatibility version.\n\nThe compatibility version can be set by specifying debhelper-compat (=\n12) in your package's Build-Depends, by the legacy debian/compat file or\neven by setting and exporting DH_COMPAT in debian/rules. If it is not\nset in either place, debhelper defaults to the deprecated compatibility\nversion 1.\n\nRefer to the debhelper(7) manual page for details.\n\nSeverity: pedantic\n\nCheck: debhelper", "comment": "", "note": "10", "pointer": ""}, {"severity": "pedantic", "package": "kbarcode-trinity", "tag": "rules-requires-root-missing", "explanation": "The debian/control file is missing an explicit Rules-Requires-Root\nfield.\n\nTraditionally, Debian packages have required root privileges for some\ndebian/rules target requiring a split between build and binary targets.\nThis makes the builds slower due to the increased amount of invocations\nas well as the overhead of fakeroot itself.\n\nPlease specify (eg.) Rules-Requires-Root: no in the debian/control\nsource stanza, but packagers should verify using diffoscope(1) that the\nbinaries built with this field present are identical.\n\nRefer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy\nManual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian\nPolicy Manual section 5.6.31 (Rules-Requires-Root) for details.\n\nSeverity: pedantic\n\nCheck: debian/control", "comment": "", "note": "", "pointer": ""}, {"severity": "experimental", "package": "kbarcode-trinity", "tag": "upstream-metadata-file-is-missing", "explanation": "This source package is not Debian-native but it does not have a\ndebian/upstream/metadata file.\n\nThe Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort\nto collect meta-information about upstream projects from any source\npackage. This file is in YAML format and it is used in to feed the data\nin the UltimateDebianDatabase. For example, it can contains the way the\nauthors want their software be cited in publications and some\nbibliographic references about the software.\n\nPlease add a debian/upstream/metadata file.\n\nRefer to https://dep-team.pages.debian.net/deps/dep12/ and\nhttps://wiki.debian.org/UpstreamMetadata for details.\n\nSeverity: pedantic\n\nCheck: debian/upstream/metadata\n\nThis tag is experimental. Please file a bug report if the tag seems\nwrong.", "comment": "", "note": "", "pointer": ""}, {"severity": "classification", "package": "kbarcode-trinity", "tag": "debhelper-compat-level", "explanation": "This is the debhelper compat level used specified by this package.\n\nSeverity: classification\n\nCheck: debhelper\n\nThis tag is a classification. There is no issue in your package.", "comment": "", "note": "10", "pointer": ""}, {"severity": "classification", "package": "kbarcode-trinity", "tag": "debian-build-system", "explanation": "This is the build system that Lintian believes the package is using.\n\nSeverity: classification\n\nCheck: debhelper\n\nThis tag is a classification. There is no issue in your package.", "comment": "", "note": "cdbs-with-debhelper.mk", "pointer": ""}, {"severity": "classification", "package": "kbarcode-trinity", "tag": "package-is-co-maintained", "explanation": "The package is co-maintained but not team-maintained according to the\nmaintainer/uploaders fields in the debian/control file.\n\nSeverity: classification\n\nCheck: fields/vcs\n\nThis tag is a classification. There is no issue in your package.", "comment": "", "note": "2", "pointer": ""}, {"severity": "classification", "package": "kbarcode-trinity", "tag": "patch-system", "explanation": "This package uses the specified patch system (eg. \"quilt\" or \"dpatch\").\n\nSeverity: classification\n\nCheck: patch-systems\n\nThis tag is a classification. There is no issue in your package.", "comment": "", "note": "quilt", "pointer": ""}, {"severity": "classification", "package": "kbarcode-trinity", "tag": "source-format", "explanation": "This is the source format declared in the package.\n\nSeverity: classification\n\nCheck: debian/source-dir\n\nThis tag is a classification. There is no issue in your package.", "comment": "", "note": "3.0 (quilt)", "pointer": ""}, {"severity": "classification", "package": "kbarcode-trinity", "tag": "standards-version", "explanation": "The standards version of the package according to Standards-Version\nfield in the debian/control file.\n\nSeverity: classification\n\nCheck: fields/standards-version\n\nThis tag is a classification. There is no issue in your package.", "comment": "", "note": "3.8.4", "pointer": ""}], "summary": {"tags_count_by_severity": {"error": 2, "warning": 5, "info": 3, "pedantic": 7, "experimental": 1, "overridden": 0, "classification": 6}, "package_filename": {"kbarcode-trinity": "kbarcode-trinity_14.2.0~pre47-0ubuntu20.04.0+7.dsc"}, "tags_found": ["ancient-standards-version", "binary-nmu-debian-revision-in-source", "co-maintained-package-with-no-vcs-fields", "debhelper-compat-level", "debian-build-system", "debian-source-options-has-custom-compression-settings", "debian-watch-file-is-missing", "epoch-change-without-comment", "epoch-changed-but-upstream-version-did-not-go-backwards", "file-contains-trailing-whitespace", "missing-build-dependency", "no-dep5-copyright", "no-dh-sequencer", "no-homepage-field", "package-is-co-maintained", "package-uses-old-debhelper-compat-version", "patch-system", "rules-requires-root-missing", "source-format", "standards-version", "testsuite-autopkgtest-missing", "upstream-metadata-file-is-missing"], "overridden_tags_found": [], "lintian_version": "2.62.0", "distribution": "debian:focal"}, "version": 1}