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