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