lintian.txt

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