1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-kbw8lnjd/kommando-trinity_14.2.0~pre50-0ubuntu20.04.0+7.dsc' '/tmp/debusine-fetch-exec-upload-kbw8lnjd/kommando-trinity_14.2.0~pre50-0ubuntu20.04.0+7_arm64.deb' 2output (contains stderr only, stdout was captured): 3 4Files in working directory: 5lintian.txt 6-------------------- 7E: kommando-trinity: dir-or-file-in-opt opt/trinity/ 8N: 9N: Debian packages should not install into /opt, because it is reserved for 10N: add-on software. 11N: 12N: Refer to Filesystem Hierarchy Standard (/opt : Add-on application 13N: software packages) for details. 14N: 15N: Severity: error 16N: 17N: Check: files/hierarchy-standard 18N: 19E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/ 20E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/libkommando.la 21E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/libkommando.so 22E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/libkommando.so.1 23E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/libkommando.so.1.0.0 24E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/ 25E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/kcm_kommando.la 26E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/kcm_kommando.so 27E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/kded_kommandod.la 28E: kommando-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/kded_kommandod.so 29E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/ 30E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/applications/ 31E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/applications/tde/ 32E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/applications/tde/kommando.desktop 33E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/ 34E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/ 35E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/ 36E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ 37E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/kommando/ 38E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/kommando/common 39E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/kommando/index.cache.bz2 40E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/kommando/index.docbook 41E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/ 42E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/ 43E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/ 44E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/apps/ 45E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/apps/kommando.png 46E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/ 47E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/apps/ 48E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/apps/kommando.png 49E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/64x64/ 50E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/64x64/apps/ 51E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/64x64/apps/kommando.png 52E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ 53E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/it/ 54E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/it/LC_MESSAGES/ 55E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/it/LC_MESSAGES/kommando.mo 56E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/ 57E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/LC_MESSAGES/ 58E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/LC_MESSAGES/kommando.mo 59E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/ 60E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/ 61E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/kommando.mo 62E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/ 63E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/ 64E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/kommando.mo 65E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/ 66E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/ 67E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/kommando.mo 68E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/zh_Hans/ 69E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/zh_Hans/LC_MESSAGES/ 70E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/locale/zh_Hans/LC_MESSAGES/kommando.mo 71E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/man/ 72E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/man/man1/ 73E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/man/man1/kommando.1 74E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/services/ 75E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/services/kded/ 76E: kommando-trinity: dir-or-file-in-opt opt/trinity/share/services/kded/kommandod.desktop 77E: kommando-trinity source: epoch-changed-but-upstream-version-did-not-go-backwards 0.5.2-0 -> 4:14.2.0~pre50-0ubuntu20.04.0+7 78N: 79N: The previous version of this package had a different version epoch to 80N: the current version but the upstream version did not go "backwards". For 81N: example, the previous package version was "1:1.0-1" and the current 82N: version is "2:2.0-1". 83N: 84N: This was likely an accidental bump or addition of an epoch. 85N: 86N: Epochs exist to cope with changes to the upstream version numbering 87N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 88N: has many downsides including causing issues with versioned dependencies, 89N: being misleading to users and being aesthetically unappealing. Whilst 90N: they should be avoided, valid reasons to add or increment the epoch 91N: include: 92N: 93N: - Upstream changed their versioning scheme in a way that makes the 94N: latest version lower than the previous one. 95N: - You need to permanently revert to a lower upstream version. 96N: 97N: Temporary revertions (eg. after an NMU) should use not modify or 98N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 99N: upload the latest version again. 100N: 101N: If you are unsure whether you need to increase the epoch for a package, 102N: please consult the debian-devel mailing list. 103N: 104N: Severity: error 105N: 106N: Check: debian/changelog 107N: 108E: kommando-trinity source: missing-build-dependency cdbs 109N: 110N: The package doesn't specify a build dependency on a package that is used 111N: in debian/rules. 112N: 113N: Lintian intentionally does not take into account transitive 114N: dependencies. Even if the package build-depends on some package that in 115N: turn depends on the needed package, an explicit build dependency should 116N: be added. Otherwise, a latent bug is created that will appear without 117N: warning if the other package is ever updated to change its dependencies. 118N: Even if this seems unlikely, please always add explicit build 119N: dependencies on every non-essential, non-build-essential package that is 120N: used directly during the build. 121N: 122N: Refer to Debian Policy Manual section 4.2 (Package relationships) for 123N: details. 124N: 125N: Severity: error 126N: 127N: Check: debian/rules 128N: 129W: kommando-trinity source: ancient-standards-version 3.8.4 (released 2010-01-27) (current is 4.5.0) 130N: 131N: The source package refers to a Standards-Version that has been obsolete 132N: for more than two years. Please update your package to latest Policy and 133N: set this control field appropriately. 134N: 135N: If the package is already compliant with the current standards, you 136N: don't have to re-upload the package just to adjust the Standards-Version 137N: control field. However, please remember to update this field next time 138N: you upload the package. 139N: 140N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 141N: debian-policy package for a summary of changes in newer versions of 142N: Policy. 143N: 144N: Refer to 145N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 146N: details. 147N: 148N: Severity: warning 149N: 150N: Check: fields/standards-version 151N: 152W: kommando-trinity source: binary-nmu-debian-revision-in-source 4:14.2.0~pre50-0ubuntu20.04.0+7 153N: 154N: The version number of your source package ends in +b and a number or has 155N: a Debian revision containing three parts. These version numbers are used 156N: by binary NMUs and should not be used as the source version. (The +b 157N: form is the current standard; the three-part version number now 158N: obsolete.) 159N: 160N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or 161N: binary-only NMU) for details. 162N: 163N: Severity: warning 164N: 165N: Check: fields/version 166N: 167W: kommando-trinity source: debhelper-but-no-misc-depends kommando-trinity 168N: 169N: The source package uses debhelper, but it does not include 170N: ${misc:Depends} in the given binary package's debian/control entry. Any 171N: debhelper command may add dependencies to ${misc:Depends} that are 172N: required for the work that it does, so recommended best practice is to 173N: always add ${misc:Depends} to the dependencies of each binary package if 174N: debhelper is in use. 175N: 176N: Refer to the debhelper(7) manual page for details. 177N: 178N: Severity: warning 179N: 180N: Check: debhelper 181N: 182W: kommando-trinity source: debian-source-options-has-custom-compression-settings compression = "xz" (line 2) 183N: 184N: The debian/source/options file for this package specifies a custom 185N: compression level or algorithm. 186N: 187N: Whilst higher levels may reduce the size of big files, they have the 188N: side effect of consuming a lot of memory during both compression and 189N: extraction. This can not only also waste time unnecessarily, it can 190N: cause packages to FTBFS or even fail to install in resource-constrained 191N: environments or architectures. 192N: 193N: Please remove the call and let dpkg-deb(1) select suitable defaults. 194N: 195N: Refer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page 196N: for details. 197N: 198N: Severity: warning 199N: 200N: Check: debian/source-dir 201N: 202W: kommando-trinity source: debian-source-options-has-custom-compression-settings compression-level = 9 (line 3) 203W: kommando-trinity: description-synopsis-starts-with-article 204N: 205N: The first line of the "Description:" should omit any initial indefinite 206N: or definite article: "a", "an", or "the". A good heuristic is that it 207N: should be possible to substitute the package name and synopsis into this 208N: formula: 209N: 210N: The package name provides {a,an,the,some} synopsis. 211N: 212N: Refer to Debian Developer's Reference section 6.2.2 (The package 213N: synopsis, or short description) for details. 214N: 215N: Severity: warning 216N: 217N: Check: fields/description 218N: 219W: kommando-trinity source: epoch-change-without-comment 0.5.2-0 -> 4:14.2.0~pre50-0ubuntu20.04.0+7 220N: 221N: The previous version of this package had a different version epoch (eg. 222N: 2:1.0-1) to the current version but there's no reference to this in the 223N: changelog entry. 224N: 225N: Epochs exist to cope with changes to the upstream version numbering 226N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 227N: has many downsides including causing issues with versioned dependencies, 228N: being misleading to users and being aesthetically unappealing. Whilst 229N: they should be avoided, valid reasons to add or increment the epoch 230N: include: 231N: 232N: - Upstream changed their versioning scheme in a way that makes the 233N: latest version lower than the previous one. 234N: - You need to permanently revert to a lower upstream version. 235N: 236N: Temporary revertions (eg. after an NMU) should use not modify or 237N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 238N: upload the latest version again. 239N: 240N: If you are unsure whether you need to increase the epoch for a package, 241N: please consult the debian-devel mailing list. 242N: 243N: Lintian looks in this version's changelog entry for the phrase "epoch". 244N: 245N: Severity: warning 246N: 247N: Check: debian/changelog 248N: 249W: kommando-trinity: hardening-no-relro opt/trinity/lib/libkommando.so.1.0.0 250N: 251N: This package provides an ELF binary that lacks the "read-only 252N: relocation" link flag. This package was likely not built with the 253N: default Debian compiler flags defined by dpkg-buildflags. If built using 254N: dpkg-buildflags directly, be sure to import LDFLAGS. 255N: 256N: Refer to https://wiki.debian.org/Hardening for details. 257N: 258N: Severity: warning 259N: 260N: Check: binaries 261N: 262W: kommando-trinity: hardening-no-relro opt/trinity/lib/trinity/kcm_kommando.so 263W: kommando-trinity: hardening-no-relro opt/trinity/lib/trinity/kded_kommandod.so 264W: kommando-trinity: package-has-unnecessary-activation-of-ldconfig-trigger 265N: 266N: The package activates the ldconfig trigger even though no shared 267N: libraries are installed in a directory controlled by the dynamic library 268N: loader. 269N: 270N: Note this may be triggered by a bug in debhelper, that causes it to 271N: auto-generate an ldconfig trigger for packages that do not need it. 272N: 273N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) and 274N: https://bugs.debian.org/204975 for details. 275N: 276N: Severity: warning 277N: 278N: Check: shared-libs 279N: 280W: kommando-trinity: unknown-section tde 281N: 282N: The "Section:" field in this package's control file is not one of the 283N: sections in use on the ftp archive. Valid sections are currently admin, 284N: comm, cli-mono, database, debug, devel, doc, editors, electronics, 285N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, 286N: haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, 287N: lisp, localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, 288N: otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex, 289N: text, utils, vcs, video, web, x11, xfce, zope. 290N: 291N: The section name should be preceded by "non-free/" if the package is in 292N: the non-free archive area, and by "contrib/" if the package is in the 293N: contrib archive area. 294N: 295N: Refer to Debian Policy Manual section 2.4 (Sections) for details. 296N: 297N: Severity: warning 298N: 299N: Check: fields/section 300N: 301I: kommando-trinity source: debian-watch-file-is-missing 302N: 303N: This source package is not Debian-native but it does not have a 304N: debian/watch file. This file is used for automatic detection of new 305N: upstream versions by the Debian External Health Status project and other 306N: project infrastructure. If this package is maintained upstream, please 307N: consider adding a debian/watch file to detect new releases. 308N: 309N: If the package is not maintained upstream or if upstream uses a 310N: distribution mechanism that cannot be meaningfully monitored by uscan 311N: and the Debian External Health Status project, please consider adding a 312N: debian/watch file containing only comments documenting the situation. 313N: 314N: Refer to Debian Policy Manual section 4.11 (Optional upstream source 315N: location: debian/watch) and the uscan(1) manual page for details. 316N: 317N: Severity: info 318N: 319N: Check: debian/watch 320N: 321I: kommando-trinity: hardening-no-bindnow opt/trinity/lib/libkommando.so.1.0.0 322N: 323N: This package provides an ELF binary that lacks the "bindnow" linker 324N: flag. 325N: 326N: This is needed (together with "relro") to make the "Global Offset Table" 327N: (GOT) fully read-only. The bindnow feature trades startup time for 328N: improved security. Please consider enabling this feature or consider 329N: overriding the tag (possibly with a comment about why). 330N: 331N: If you use dpkg-buildflags, you may have to add hardening=+bindnow or 332N: hardening=+all to DEB_BUILD_MAINT_OPTIONS. 333N: 334N: The relevant compiler flags are set in LDFLAGS. 335N: 336N: Refer to https://wiki.debian.org/Hardening for details. 337N: 338N: Severity: info 339N: 340N: Check: binaries 341N: 342I: kommando-trinity: hardening-no-bindnow opt/trinity/lib/trinity/kcm_kommando.so 343I: kommando-trinity: hardening-no-bindnow opt/trinity/lib/trinity/kded_kommandod.so 344I: kommando-trinity source: no-dh-sequencer 345N: 346N: This package does not use the dh sequencer in debian/rules. 347N: 348N: While maintainers may use a variety of build systems, this one is by far 349N: the most popular. 350N: 351N: Maintainers are strongly encouraged to use the dh sequencer in new 352N: packages and convert existing ones when appropriate. 353N: 354N: Severity: info 355N: 356N: Check: debian/rules/dh-sequencer 357N: 358I: kommando-trinity source: testsuite-autopkgtest-missing 359N: 360N: This package does not declare a test suite. 361N: 362N: Having a test suite aids with automated quality assurance of the archive 363N: outside of your package. For example, if your package has a test suite 364N: it is possible to re-run that test suite when any of your package's 365N: dependencies have a new version and check whether that update causes 366N: problems for your package. 367N: 368N: In addition, since May 2018 these tests now influence migration from 369N: unstable to testing: 370N: 371N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html 372N: 373N: Please add a debian/tests/control file to your package to declare a 374N: testsuite, but please make sure to only add autopkgtests if they provide 375N: meaningful coverage of your package. 376N: 377N: Refer to https://ci.debian.net/doc/ for details. 378N: 379N: Severity: info 380N: 381N: Check: testsuite 382N: 383P: kommando-trinity: copyright-refers-to-symlink-license usr/share/common-licenses/GPL 384N: 385N: The copyright file refers to the versionless symlink in 386N: /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL 387N: license. This symlink is updated to point to the latest version of the 388N: license when a new one is released. The package appears to allow 389N: relicensing under later versions of its license, so this is legally 390N: consistent, but it implies that Debian will relicense the package under 391N: later versions of those licenses as they're released. It is normally 392N: better to point to the version of the license the package references in 393N: its license statement. 394N: 395N: For example, if the package says something like "you may redistribute it 396N: and/or modify it under the terms of the GNU General Public License as 397N: published by the Free Software Foundation; either version 2, or (at your 398N: option) any later version", the debian/copyright file should refer to 399N: /usr/share/common-licenses/GPL-2, not /GPL. 400N: 401N: For packages released under the same terms as Perl, Perl references the 402N: GPL version 1, so point to /usr/share/common-licenses/GPL-1. 403N: 404N: Severity: pedantic 405N: 406N: Check: debian/copyright 407N: 408P: kommando-trinity: copyright-with-old-dh-make-debian-copyright 409N: 410N: The copyright file contains the incomplete Debian packaging copyright 411N: boilerplate from older versions of dh_make. (C) alone is not considered 412N: a valid copyright notice in some countries. The word Copyright or the © 413N: symbol should be used instead or in addition to (C). 414N: 415N: Copyright notices like this are, in any country that's a signatory to 416N: the Berne Convention, not required to claim copyright on a work, but 417N: their presence may allow claiming additional damages should a copyright 418N: case go to court. If you provide a notice, you may as well provide one 419N: that's legally recognized in a broader range of countries. 420N: 421N: Severity: pedantic 422N: 423N: Check: debian/copyright 424N: 425P: kommando-trinity source: file-contains-trailing-whitespace debian/changelog (line 25) 426N: 427N: This file appears to contain one or more lines with trailing whitespace 428N: characters. 429N: 430N: Whilst typically harmless and merely unsightly, they can often cause 431N: difficult-to-spot issues where tools interpret the whitespace characters 432N: literally as well as introduce unnecessary diff(1) noise. They are thus 433N: best avoided in their entirity. 434N: 435N: Whitespace at the end of lines may be removed with the following: 436N: 437N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 438N: 439N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 440N: 441N: However, if you wish to only remove trailing spaces and leave trailing 442N: tabs (eg. for Makefiles), you can use the following code snippet: 443N: 444N: $ sed -i -e 's@[ ]*$@@g' debian/rules 445N: 446N: To remove empty lines from the end of a file, you can use: 447N: 448N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 449N: 450N: Severity: pedantic 451N: 452N: Check: cruft 453N: 454P: kommando-trinity source: file-contains-trailing-whitespace debian/changelog (line 26) 455P: kommando-trinity source: file-contains-trailing-whitespace debian/changelog (line 27) 456P: kommando-trinity source: file-contains-trailing-whitespace debian/changelog (line 74) 457P: kommando-trinity source: file-contains-trailing-whitespace debian/control (line 13) 458P: kommando-trinity source: file-contains-trailing-whitespace debian/control (line 14) 459P: kommando-trinity source: no-dep5-copyright 460N: 461N: This package does not use a machine-readable debian/copyright file. 462N: 463N: This format makes it easier to review licenses and can be easily parsed 464N: by Lintian. 465N: 466N: Refer to 467N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 468N: details. 469N: 470N: Severity: pedantic 471N: 472N: Check: debian/copyright 473N: 474P: kommando-trinity source: no-homepage-field 475N: 476N: This non-native package lacks a Homepage field. If the package has an 477N: upstream home page that contains useful information or resources for the 478N: end user, consider adding a Homepage control field to debian/control. 479N: 480N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. 481N: 482N: Severity: pedantic 483N: 484N: Check: fields/homepage 485N: 486P: kommando-trinity source: package-uses-old-debhelper-compat-version 10 487N: 488N: The debhelper compatibility version used by this package is marked as 489N: not recommended by the debhelper developer. You may consider using a 490N: recommended compatibility version. 491N: 492N: The compatibility version can be set by specifying debhelper-compat (= 493N: 12) in your package's Build-Depends, by the legacy debian/compat file or 494N: even by setting and exporting DH_COMPAT in debian/rules. If it is not 495N: set in either place, debhelper defaults to the deprecated compatibility 496N: version 1. 497N: 498N: Refer to the debhelper(7) manual page for details. 499N: 500N: Severity: pedantic 501N: 502N: Check: debhelper 503N: 504P: kommando-trinity source: rules-requires-root-missing 505N: 506N: The debian/control file is missing an explicit Rules-Requires-Root 507N: field. 508N: 509N: Traditionally, Debian packages have required root privileges for some 510N: debian/rules target requiring a split between build and binary targets. 511N: This makes the builds slower due to the increased amount of invocations 512N: as well as the overhead of fakeroot itself. 513N: 514N: Please specify (eg.) Rules-Requires-Root: no in the debian/control 515N: source stanza, but packagers should verify using diffoscope(1) that the 516N: binaries built with this field present are identical. 517N: 518N: Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy 519N: Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian 520N: Policy Manual section 5.6.31 (Rules-Requires-Root) for details. 521N: 522N: Severity: pedantic 523N: 524N: Check: debian/control 525N: 526X: kommando-trinity source: upstream-metadata-file-is-missing 527N: 528N: This source package is not Debian-native but it does not have a 529N: debian/upstream/metadata file. 530N: 531N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort 532N: to collect meta-information about upstream projects from any source 533N: package. This file is in YAML format and it is used in to feed the data 534N: in the UltimateDebianDatabase. For example, it can contains the way the 535N: authors want their software be cited in publications and some 536N: bibliographic references about the software. 537N: 538N: Please add a debian/upstream/metadata file. 539N: 540N: Refer to https://dep-team.pages.debian.net/deps/dep12/ and 541N: https://wiki.debian.org/UpstreamMetadata for details. 542N: 543N: Severity: pedantic 544N: 545N: Check: debian/upstream/metadata 546N: 547N: This tag is experimental. Please file a bug report if the tag seems 548N: wrong. 549N: 550C: kommando-trinity: control-tarball-compression-format xz 551N: 552N: This is the compressor format used for the control.tar tarball. 553N: 554N: Severity: classification 555N: 556N: Check: deb-format 557N: 558N: This tag is a classification. There is no issue in your package. 559N: 560C: kommando-trinity: data-tarball-compression-format xz 561N: 562N: This is the compressor format used for the data.tar tarball. 563N: 564N: Severity: classification 565N: 566N: Check: deb-format 567N: 568N: This tag is a classification. There is no issue in your package. 569N: 570C: kommando-trinity source: debhelper-compat-level 10 571N: 572N: This is the debhelper compat level used specified by this package. 573N: 574N: Severity: classification 575N: 576N: Check: debhelper 577N: 578N: This tag is a classification. There is no issue in your package. 579N: 580C: kommando-trinity source: debian-build-system cdbs-with-debhelper.mk 581N: 582N: This is the build system that Lintian believes the package is using. 583N: 584N: Severity: classification 585N: 586N: Check: debhelper 587N: 588N: This tag is a classification. There is no issue in your package. 589N: 590C: kommando-trinity: no-ctrl-scripts 591N: 592N: The package does not rely on any maintainer scripts (or other executable 593N: control files). 594N: 595N: Severity: classification 596N: 597N: Check: control-files 598N: 599N: This tag is a classification. There is no issue in your package. 600N: 601C: kommando-trinity source: package-is-maintained-by-individual 602N: 603N: The package is maintained by an individual according to the 604N: maintainer/uploaders fields in the debian/control file. 605N: 606N: Severity: classification 607N: 608N: Check: fields/vcs 609N: 610N: This tag is a classification. There is no issue in your package. 611N: 612C: kommando-trinity: package-is-maintained-by-individual 613C: kommando-trinity source: patch-system quilt 614N: 615N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 616N: 617N: Severity: classification 618N: 619N: Check: patch-systems 620N: 621N: This tag is a classification. There is no issue in your package. 622N: 623C: kommando-trinity source: source-format 3.0 (quilt) 624N: 625N: This is the source format declared in the package. 626N: 627N: Severity: classification 628N: 629N: Check: debian/source-dir 630N: 631N: This tag is a classification. There is no issue in your package. 632N: 633C: kommando-trinity source: standards-version 3.8.4 634N: 635N: The standards version of the package according to Standards-Version 636N: field in the debian/control file. 637N: 638N: Severity: classification 639N: 640N: Check: fields/standards-version 641N: 642N: This tag is a classification. There is no issue in your package. 643N: 644 645--------------------