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