1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-r1o8t0h4/twin-style-crystal-trinity_14.1.6~pre6-0ubuntu20.04.0+1.dsc' '/tmp/debusine-fetch-exec-upload-r1o8t0h4/twin-style-crystal-trinity_14.1.6~pre6-0ubuntu20.04.0+1_amd64.deb' 2output (contains stderr only, stdout was captured): 3Use of uninitialized value $1 in ucfirst at /usr/share/perl5/Lintian/Inspect/Changelog.pm line 158. 4 5Files in working directory: 6lintian.txt 7-------------------- 8E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/ 9N: 10N: Debian packages should not install into /opt, because it is reserved for 11N: add-on software. 12N: 13N: Refer to Filesystem Hierarchy Standard (/opt : Add-on application 14N: software packages) for details. 15N: 16N: Severity: error 17N: 18N: Check: files/hierarchy-standard 19N: 20E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/lib/ 21E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/ 22E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/twin3_crystal.la 23E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/twin3_crystal.so 24E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/twin_crystal_config.la 25E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/lib/trinity/twin_crystal_config.so 26E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/ 27E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/apps/ 28E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/apps/twin/ 29E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/apps/twin/crystal.desktop 30E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ 31E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/ 32E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/LC_MESSAGES/ 33E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/LC_MESSAGES/twin-style-crystal.mo 34E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/ 35E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/ 36E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/twin-style-crystal.mo 37E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/ 38E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/ 39E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/twin-style-crystal.mo 40E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/pt_BR/ 41E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/pt_BR/LC_MESSAGES/ 42E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/pt_BR/LC_MESSAGES/twin-style-crystal.mo 43E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/ 44E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/ 45E: twin-style-crystal-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/twin-style-crystal.mo 46E: twin-style-crystal-trinity source: epoch-changed-but-upstream-version-did-not-go-backwards 1.0.5-0ubuntu3 -> 4:14.1.6~pre6-0ubuntu20.04.0+1 47N: 48N: The previous version of this package had a different version epoch to 49N: the current version but the upstream version did not go "backwards". For 50N: example, the previous package version was "1:1.0-1" and the current 51N: version is "2:2.0-1". 52N: 53N: This was likely an accidental bump or addition of an epoch. 54N: 55N: Epochs exist to cope with changes to the upstream version numbering 56N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 57N: has many downsides including causing issues with versioned dependencies, 58N: being misleading to users and being aesthetically unappealing. Whilst 59N: they should be avoided, valid reasons to add or increment the epoch 60N: include: 61N: 62N: - Upstream changed their versioning scheme in a way that makes the 63N: latest version lower than the previous one. 64N: - You need to permanently revert to a lower upstream version. 65N: 66N: Temporary revertions (eg. after an NMU) should use not modify or 67N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 68N: upload the latest version again. 69N: 70N: If you are unsure whether you need to increase the epoch for a package, 71N: please consult the debian-devel mailing list. 72N: 73N: Severity: error 74N: 75N: Check: debian/changelog 76N: 77E: twin-style-crystal-trinity source: missing-build-dependency cdbs 78N: 79N: The package doesn't specify a build dependency on a package that is used 80N: in debian/rules. 81N: 82N: Lintian intentionally does not take into account transitive 83N: dependencies. Even if the package build-depends on some package that in 84N: turn depends on the needed package, an explicit build dependency should 85N: be added. Otherwise, a latent bug is created that will appear without 86N: warning if the other package is ever updated to change its dependencies. 87N: Even if this seems unlikely, please always add explicit build 88N: dependencies on every non-essential, non-build-essential package that is 89N: used directly during the build. 90N: 91N: Refer to Debian Policy Manual section 4.2 (Package relationships) for 92N: details. 93N: 94N: Severity: error 95N: 96N: Check: debian/rules 97N: 98W: twin-style-crystal-trinity source: ancient-standards-version 3.8.4 (released 2010-01-27) (current is 4.5.0) 99N: 100N: The source package refers to a Standards-Version that has been obsolete 101N: for more than two years. Please update your package to latest Policy and 102N: set this control field appropriately. 103N: 104N: If the package is already compliant with the current standards, you 105N: don't have to re-upload the package just to adjust the Standards-Version 106N: control field. However, please remember to update this field next time 107N: you upload the package. 108N: 109N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 110N: debian-policy package for a summary of changes in newer versions of 111N: Policy. 112N: 113N: Refer to 114N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 115N: details. 116N: 117N: Severity: warning 118N: 119N: Check: fields/standards-version 120N: 121W: twin-style-crystal-trinity source: binary-nmu-debian-revision-in-source 4:14.1.6~pre6-0ubuntu20.04.0+1 122N: 123N: The version number of your source package ends in +b and a number or has 124N: a Debian revision containing three parts. These version numbers are used 125N: by binary NMUs and should not be used as the source version. (The +b 126N: form is the current standard; the three-part version number now 127N: obsolete.) 128N: 129N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or 130N: binary-only NMU) for details. 131N: 132N: Severity: warning 133N: 134N: Check: fields/version 135N: 136W: twin-style-crystal-trinity source: debian-source-options-has-custom-compression-settings compression = "xz" (line 2) 137N: 138N: The debian/source/options file for this package specifies a custom 139N: compression level or algorithm. 140N: 141N: Whilst higher levels may reduce the size of big files, they have the 142N: side effect of consuming a lot of memory during both compression and 143N: extraction. This can not only also waste time unnecessarily, it can 144N: cause packages to FTBFS or even fail to install in resource-constrained 145N: environments or architectures. 146N: 147N: Please remove the call and let dpkg-deb(1) select suitable defaults. 148N: 149N: Refer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page 150N: for details. 151N: 152N: Severity: warning 153N: 154N: Check: debian/source-dir 155N: 156W: twin-style-crystal-trinity source: debian-source-options-has-custom-compression-settings compression-level = 9 (line 3) 157W: twin-style-crystal-trinity source: epoch-change-without-comment 1.0.5-0ubuntu3 -> 4:14.1.6~pre6-0ubuntu20.04.0+1 158N: 159N: The previous version of this package had a different version epoch (eg. 160N: 2:1.0-1) to the current version but there's no reference to this in the 161N: changelog entry. 162N: 163N: Epochs exist to cope with changes to the upstream version numbering 164N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 165N: has many downsides including causing issues with versioned dependencies, 166N: being misleading to users and being aesthetically unappealing. Whilst 167N: they should be avoided, valid reasons to add or increment the epoch 168N: include: 169N: 170N: - Upstream changed their versioning scheme in a way that makes the 171N: latest version lower than the previous one. 172N: - You need to permanently revert to a lower upstream version. 173N: 174N: Temporary revertions (eg. after an NMU) should use not modify or 175N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 176N: upload the latest version again. 177N: 178N: If you are unsure whether you need to increase the epoch for a package, 179N: please consult the debian-devel mailing list. 180N: 181N: Lintian looks in this version's changelog entry for the phrase "epoch". 182N: 183N: Severity: warning 184N: 185N: Check: debian/changelog 186N: 187W: twin-style-crystal-trinity: hardening-no-relro opt/trinity/lib/trinity/twin3_crystal.so 188N: 189N: This package provides an ELF binary that lacks the "read-only 190N: relocation" link flag. This package was likely not built with the 191N: default Debian compiler flags defined by dpkg-buildflags. If built using 192N: dpkg-buildflags directly, be sure to import LDFLAGS. 193N: 194N: Refer to https://wiki.debian.org/Hardening for details. 195N: 196N: Severity: warning 197N: 198N: Check: binaries 199N: 200W: twin-style-crystal-trinity: hardening-no-relro opt/trinity/lib/trinity/twin_crystal_config.so 201W: twin-style-crystal-trinity: package-has-unnecessary-activation-of-ldconfig-trigger 202N: 203N: The package activates the ldconfig trigger even though no shared 204N: libraries are installed in a directory controlled by the dynamic library 205N: loader. 206N: 207N: Note this may be triggered by a bug in debhelper, that causes it to 208N: auto-generate an ldconfig trigger for packages that do not need it. 209N: 210N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) and 211N: https://bugs.debian.org/204975 for details. 212N: 213N: Severity: warning 214N: 215N: Check: shared-libs 216N: 217W: twin-style-crystal-trinity: spelling-error-in-description Transparancy Transparency 218N: 219N: Lintian found a spelling error in the package description. Lintian has a 220N: list of common misspellings that it looks for. It does not have a 221N: dictionary like a spelling checker does. It is particularly picky about 222N: spelling and capitalization in package descriptions since they're very 223N: visible to end users. 224N: 225N: Severity: warning 226N: 227N: Check: fields/description 228N: 229W: twin-style-crystal-trinity: spelling-error-in-description-synopsis transparant transparent 230N: 231N: Lintian found a spelling error in the package synopsis. Lintian has a 232N: list of common misspellings that it looks for. It does not have a 233N: dictionary like a spelling checker does. It is particularly picky about 234N: spelling and capitalization in package descriptions since they're very 235N: visible to end users. 236N: 237N: Severity: warning 238N: 239N: Check: fields/description 240N: 241W: twin-style-crystal-trinity: syntax-error-in-debian-changelog line 83 "bad key-value after `;': `urge ncy=low'" 242N: 243N: While parsing the Debian changelog, a syntax error was found. If you 244N: have old changelog entries that don't follow the current syntax but that 245N: you want to keep as-is for the historical record, add the line: 246N: 247N: Old Changelog: 248N: 249N: with no leading whitespace before the legacy entries. This line and 250N: everything after it will be ignored. 251N: 252N: Refer to Debian Policy Manual section 4.4 (Debian changelog: 253N: debian/changelog) for details. 254N: 255N: Severity: warning 256N: 257N: Check: debian/changelog 258N: 259W: twin-style-crystal-trinity: syntax-error-in-debian-changelog line 83 "unknown key-value key - copying to XS-" 260W: twin-style-crystal-trinity: unknown-section tde 261N: 262N: The "Section:" field in this package's control file is not one of the 263N: sections in use on the ftp archive. Valid sections are currently admin, 264N: comm, cli-mono, database, debug, devel, doc, editors, electronics, 265N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, 266N: haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, 267N: lisp, localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, 268N: otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex, 269N: text, utils, vcs, video, web, x11, xfce, zope. 270N: 271N: The section name should be preceded by "non-free/" if the package is in 272N: the non-free archive area, and by "contrib/" if the package is in the 273N: contrib archive area. 274N: 275N: Refer to Debian Policy Manual section 2.4 (Sections) for details. 276N: 277N: Severity: warning 278N: 279N: Check: fields/section 280N: 281I: twin-style-crystal-trinity source: debian-watch-file-is-missing 282N: 283N: This source package is not Debian-native but it does not have a 284N: debian/watch file. This file is used for automatic detection of new 285N: upstream versions by the Debian External Health Status project and other 286N: project infrastructure. If this package is maintained upstream, please 287N: consider adding a debian/watch file to detect new releases. 288N: 289N: If the package is not maintained upstream or if upstream uses a 290N: distribution mechanism that cannot be meaningfully monitored by uscan 291N: and the Debian External Health Status project, please consider adding a 292N: debian/watch file containing only comments documenting the situation. 293N: 294N: Refer to Debian Policy Manual section 4.11 (Optional upstream source 295N: location: debian/watch) and the uscan(1) manual page for details. 296N: 297N: Severity: info 298N: 299N: Check: debian/watch 300N: 301I: twin-style-crystal-trinity: hardening-no-bindnow opt/trinity/lib/trinity/twin3_crystal.so 302N: 303N: This package provides an ELF binary that lacks the "bindnow" linker 304N: flag. 305N: 306N: This is needed (together with "relro") to make the "Global Offset Table" 307N: (GOT) fully read-only. The bindnow feature trades startup time for 308N: improved security. Please consider enabling this feature or consider 309N: overriding the tag (possibly with a comment about why). 310N: 311N: If you use dpkg-buildflags, you may have to add hardening=+bindnow or 312N: hardening=+all to DEB_BUILD_MAINT_OPTIONS. 313N: 314N: The relevant compiler flags are set in LDFLAGS. 315N: 316N: Refer to https://wiki.debian.org/Hardening for details. 317N: 318N: Severity: info 319N: 320N: Check: binaries 321N: 322I: twin-style-crystal-trinity: hardening-no-bindnow opt/trinity/lib/trinity/twin_crystal_config.so 323I: twin-style-crystal-trinity source: no-dh-sequencer 324N: 325N: This package does not use the dh sequencer in debian/rules. 326N: 327N: While maintainers may use a variety of build systems, this one is by far 328N: the most popular. 329N: 330N: Maintainers are strongly encouraged to use the dh sequencer in new 331N: packages and convert existing ones when appropriate. 332N: 333N: Severity: info 334N: 335N: Check: debian/rules/dh-sequencer 336N: 337I: twin-style-crystal-trinity: spelling-error-in-binary opt/trinity/lib/trinity/twin_crystal_config.so independend independent 338N: 339N: Lintian found a spelling error in the given binary. Lintian has a list 340N: of common misspellings that it looks for. It does not have a dictionary 341N: like a spelling checker does. 342N: 343N: If the string containing the spelling error is translated with the help 344N: of gettext or a similar tool, please fix the error in the translations 345N: as well as the English text to avoid making the translations fuzzy. With 346N: gettext, for example, this means you should also fix the spelling 347N: mistake in the corresponding msgids in the *.po files. 348N: 349N: You can often find the word in the source code by running: 350N: 351N: grep -rw <word> <source-tree> 352N: 353N: This tag may produce false positives for words that contain non-ASCII 354N: characters due to limitations in strings. 355N: 356N: Severity: info 357N: 358N: Check: binaries 359N: 360I: twin-style-crystal-trinity source: testsuite-autopkgtest-missing 361N: 362N: This package does not declare a test suite. 363N: 364N: Having a test suite aids with automated quality assurance of the archive 365N: outside of your package. For example, if your package has a test suite 366N: it is possible to re-run that test suite when any of your package's 367N: dependencies have a new version and check whether that update causes 368N: problems for your package. 369N: 370N: In addition, since May 2018 these tests now influence migration from 371N: unstable to testing: 372N: 373N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html 374N: 375N: Please add a debian/tests/control file to your package to declare a 376N: testsuite, but please make sure to only add autopkgtests if they provide 377N: meaningful coverage of your package. 378N: 379N: Refer to https://ci.debian.net/doc/ for details. 380N: 381N: Severity: info 382N: 383N: Check: testsuite 384N: 385P: twin-style-crystal-trinity: copyright-refers-to-symlink-license usr/share/common-licenses/GPL 386N: 387N: The copyright file refers to the versionless symlink in 388N: /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL 389N: license. This symlink is updated to point to the latest version of the 390N: license when a new one is released. The package appears to allow 391N: relicensing under later versions of its license, so this is legally 392N: consistent, but it implies that Debian will relicense the package under 393N: later versions of those licenses as they're released. It is normally 394N: better to point to the version of the license the package references in 395N: its license statement. 396N: 397N: For example, if the package says something like "you may redistribute it 398N: and/or modify it under the terms of the GNU General Public License as 399N: published by the Free Software Foundation; either version 2, or (at your 400N: option) any later version", the debian/copyright file should refer to 401N: /usr/share/common-licenses/GPL-2, not /GPL. 402N: 403N: For packages released under the same terms as Perl, Perl references the 404N: GPL version 1, so point to /usr/share/common-licenses/GPL-1. 405N: 406N: Severity: pedantic 407N: 408N: Check: debian/copyright 409N: 410P: twin-style-crystal-trinity source: file-contains-trailing-whitespace debian/changelog (line 124) 411N: 412N: This file appears to contain one or more lines with trailing whitespace 413N: characters. 414N: 415N: Whilst typically harmless and merely unsightly, they can often cause 416N: difficult-to-spot issues where tools interpret the whitespace characters 417N: literally as well as introduce unnecessary diff(1) noise. They are thus 418N: best avoided in their entirity. 419N: 420N: Whitespace at the end of lines may be removed with the following: 421N: 422N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 423N: 424N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 425N: 426N: However, if you wish to only remove trailing spaces and leave trailing 427N: tabs (eg. for Makefiles), you can use the following code snippet: 428N: 429N: $ sed -i -e 's@[ ]*$@@g' debian/rules 430N: 431N: To remove empty lines from the end of a file, you can use: 432N: 433N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 434N: 435N: Severity: pedantic 436N: 437N: Check: cruft 438N: 439P: twin-style-crystal-trinity source: file-contains-trailing-whitespace debian/changelog (line 131) 440P: twin-style-crystal-trinity source: file-contains-trailing-whitespace debian/changelog (line 142) 441P: twin-style-crystal-trinity source: file-contains-trailing-whitespace debian/changelog (line 73) 442P: twin-style-crystal-trinity source: file-contains-trailing-whitespace debian/changelog (line 97) 443P: twin-style-crystal-trinity source: file-contains-trailing-whitespace debian/changelog (line 98) 444P: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-trinity: package-is-maintained-by-individual 598C: twin-style-crystal-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: twin-style-crystal-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: twin-style-crystal-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: 629 630--------------------