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