cmd-output.log

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