1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-u1dt6zp9/compizconfig-backend-tdeconfig-trinity_14.2.0~pre10-0ubuntu20.04.0+9.dsc' '/tmp/debusine-fetch-exec-upload-u1dt6zp9/compizconfig-backend-tdeconfig-trinity_14.2.0~pre10-0ubuntu20.04.0+9_armhf.deb' 2output (contains stderr only, stdout was captured): 3 4Files in working directory: 5lintian.txt 6-------------------- 7E: compizconfig-backend-tdeconfig-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: compizconfig-backend-tdeconfig-trinity: dir-or-file-in-opt opt/trinity/lib/ 20E: compizconfig-backend-tdeconfig-trinity: dir-or-file-in-opt opt/trinity/lib/compizconfig/ 21E: compizconfig-backend-tdeconfig-trinity: dir-or-file-in-opt opt/trinity/lib/compizconfig/backends/ 22E: compizconfig-backend-tdeconfig-trinity: dir-or-file-in-opt opt/trinity/lib/compizconfig/backends/libtdeconfig.la 23E: compizconfig-backend-tdeconfig-trinity: dir-or-file-in-opt opt/trinity/lib/compizconfig/backends/libtdeconfig.so 24E: compizconfig-backend-tdeconfig-trinity source: epoch-changed-but-upstream-version-did-not-go-backwards 0.8.4-0ubuntu1 -> 4:14.2.0~pre10-0ubuntu20.04.0+9 25N: 26N: The previous version of this package had a different version epoch to 27N: the current version but the upstream version did not go "backwards". For 28N: example, the previous package version was "1:1.0-1" and the current 29N: version is "2:2.0-1". 30N: 31N: This was likely an accidental bump or addition of an epoch. 32N: 33N: Epochs exist to cope with changes to the upstream version numbering 34N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 35N: has many downsides including causing issues with versioned dependencies, 36N: being misleading to users and being aesthetically unappealing. Whilst 37N: they should be avoided, valid reasons to add or increment the epoch 38N: include: 39N: 40N: - Upstream changed their versioning scheme in a way that makes the 41N: latest version lower than the previous one. 42N: - You need to permanently revert to a lower upstream version. 43N: 44N: Temporary revertions (eg. after an NMU) should use not modify or 45N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 46N: upload the latest version again. 47N: 48N: If you are unsure whether you need to increase the epoch for a package, 49N: please consult the debian-devel mailing list. 50N: 51N: Severity: error 52N: 53N: Check: debian/changelog 54N: 55E: compizconfig-backend-tdeconfig-trinity source: missing-build-dependency cdbs 56N: 57N: The package doesn't specify a build dependency on a package that is used 58N: in debian/rules. 59N: 60N: Lintian intentionally does not take into account transitive 61N: dependencies. Even if the package build-depends on some package that in 62N: turn depends on the needed package, an explicit build dependency should 63N: be added. Otherwise, a latent bug is created that will appear without 64N: warning if the other package is ever updated to change its dependencies. 65N: Even if this seems unlikely, please always add explicit build 66N: dependencies on every non-essential, non-build-essential package that is 67N: used directly during the build. 68N: 69N: Refer to Debian Policy Manual section 4.2 (Package relationships) for 70N: details. 71N: 72N: Severity: error 73N: 74N: Check: debian/rules 75N: 76W: compizconfig-backend-tdeconfig-trinity source: ancient-standards-version 3.8.4 (released 2010-01-27) (current is 4.5.0) 77N: 78N: The source package refers to a Standards-Version that has been obsolete 79N: for more than two years. Please update your package to latest Policy and 80N: set this control field appropriately. 81N: 82N: If the package is already compliant with the current standards, you 83N: don't have to re-upload the package just to adjust the Standards-Version 84N: control field. However, please remember to update this field next time 85N: you upload the package. 86N: 87N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 88N: debian-policy package for a summary of changes in newer versions of 89N: Policy. 90N: 91N: Refer to 92N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 93N: details. 94N: 95N: Severity: warning 96N: 97N: Check: fields/standards-version 98N: 99W: compizconfig-backend-tdeconfig-trinity source: binary-nmu-debian-revision-in-source 4:14.2.0~pre10-0ubuntu20.04.0+9 100N: 101N: The version number of your source package ends in +b and a number or has 102N: a Debian revision containing three parts. These version numbers are used 103N: by binary NMUs and should not be used as the source version. (The +b 104N: form is the current standard; the three-part version number now 105N: obsolete.) 106N: 107N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or 108N: binary-only NMU) for details. 109N: 110N: Severity: warning 111N: 112N: Check: fields/version 113N: 114W: compizconfig-backend-tdeconfig-trinity source: debian-source-options-has-custom-compression-settings compression = "xz" (line 2) 115N: 116N: The debian/source/options file for this package specifies a custom 117N: compression level or algorithm. 118N: 119N: Whilst higher levels may reduce the size of big files, they have the 120N: side effect of consuming a lot of memory during both compression and 121N: extraction. This can not only also waste time unnecessarily, it can 122N: cause packages to FTBFS or even fail to install in resource-constrained 123N: environments or architectures. 124N: 125N: Please remove the call and let dpkg-deb(1) select suitable defaults. 126N: 127N: Refer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page 128N: for details. 129N: 130N: Severity: warning 131N: 132N: Check: debian/source-dir 133N: 134W: compizconfig-backend-tdeconfig-trinity source: debian-source-options-has-custom-compression-settings compression-level = 9 (line 3) 135W: compizconfig-backend-tdeconfig-trinity source: epoch-change-without-comment 0.8.4-0ubuntu1 -> 4:14.2.0~pre10-0ubuntu20.04.0+9 136N: 137N: The previous version of this package had a different version epoch (eg. 138N: 2:1.0-1) to the current version but there's no reference to this in the 139N: changelog entry. 140N: 141N: Epochs exist to cope with changes to the upstream version numbering 142N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 143N: has many downsides including causing issues with versioned dependencies, 144N: being misleading to users and being aesthetically unappealing. Whilst 145N: they should be avoided, valid reasons to add or increment the epoch 146N: include: 147N: 148N: - Upstream changed their versioning scheme in a way that makes the 149N: latest version lower than the previous one. 150N: - You need to permanently revert to a lower upstream version. 151N: 152N: Temporary revertions (eg. after an NMU) should use not modify or 153N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 154N: upload the latest version again. 155N: 156N: If you are unsure whether you need to increase the epoch for a package, 157N: please consult the debian-devel mailing list. 158N: 159N: Lintian looks in this version's changelog entry for the phrase "epoch". 160N: 161N: Severity: warning 162N: 163N: Check: debian/changelog 164N: 165W: compizconfig-backend-tdeconfig-trinity: hardening-no-relro opt/trinity/lib/compizconfig/backends/libtdeconfig.so 166N: 167N: This package provides an ELF binary that lacks the "read-only 168N: relocation" link flag. This package was likely not built with the 169N: default Debian compiler flags defined by dpkg-buildflags. If built using 170N: dpkg-buildflags directly, be sure to import LDFLAGS. 171N: 172N: Refer to https://wiki.debian.org/Hardening for details. 173N: 174N: Severity: warning 175N: 176N: Check: binaries 177N: 178W: compizconfig-backend-tdeconfig-trinity: package-contains-upstream-installation-documentation usr/share/doc/compizconfig-backend-tdeconfig-trinity/INSTALL 179N: 180N: Binary packages do not need to contain the instructions for building and 181N: installing the package as this info is not needed by package users. If 182N: the info contained is important for configuration perhaps it could be 183N: summarized in README.Debian, otherwise an override may be added. 184N: 185N: Refer to Debian Policy Manual section 12.3 (Additional documentation) 186N: for details. 187N: 188N: Severity: warning 189N: 190N: Check: documentation 191N: 192W: compizconfig-backend-tdeconfig-trinity: package-has-long-file-name 80 (89) > 80 193N: 194N: The package has a very long filename. This may complicate shipping the 195N: package on some media that put restrictions on the length of the 196N: filenames (such as CDs). 197N: 198N: For architecture dependent packages, the tag is emitted based on the 199N: length of the longest architecture name rather than the name of the 200N: current architecture. 201N: 202N: This length will be written in brackets after the actual length. 203N: 204N: Refer to https://lists.debian.org/debian-devel/2011/03/msg00943.html for 205N: details. 206N: 207N: Severity: warning 208N: 209N: Check: filename-length 210N: 211W: compizconfig-backend-tdeconfig-trinity: package-has-unnecessary-activation-of-ldconfig-trigger 212N: 213N: The package activates the ldconfig trigger even though no shared 214N: libraries are installed in a directory controlled by the dynamic library 215N: loader. 216N: 217N: Note this may be triggered by a bug in debhelper, that causes it to 218N: auto-generate an ldconfig trigger for packages that do not need it. 219N: 220N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) and 221N: https://bugs.debian.org/204975 for details. 222N: 223N: Severity: warning 224N: 225N: Check: shared-libs 226N: 227W: compizconfig-backend-tdeconfig-trinity: priority-extra-is-replaced-by-priority-optional 228N: 229N: Since Debian Policy version 4.0.1, the priority extra has been 230N: deprecated. 231N: 232N: Please update debian/control and replace all instances of Priority: 233N: extra with Priority: optional. 234N: 235N: Refer to Debian Policy Manual section 2.5 (Priorities) for details. 236N: 237N: Severity: warning 238N: 239N: Check: fields/priority 240N: 241W: compizconfig-backend-tdeconfig-trinity source: source-package-component-has-long-file-name 82 > 80 242N: 243N: The source package has a component with a very long filename. This may 244N: complicate shipping the package on some media that put restrictions on 245N: the length of the filenames (such as CDs). 246N: 247N: Lintian only checks emits this tag once per source package based on the 248N: component with the longest filename. 249N: 250N: Refer to https://lists.debian.org/debian-devel/2011/03/msg00943.html for 251N: details. 252N: 253N: Severity: warning 254N: 255N: Check: filename-length 256N: 257I: compizconfig-backend-tdeconfig-trinity source: debian-watch-file-is-missing 258N: 259N: This source package is not Debian-native but it does not have a 260N: debian/watch file. This file is used for automatic detection of new 261N: upstream versions by the Debian External Health Status project and other 262N: project infrastructure. If this package is maintained upstream, please 263N: consider adding a debian/watch file to detect new releases. 264N: 265N: If the package is not maintained upstream or if upstream uses a 266N: distribution mechanism that cannot be meaningfully monitored by uscan 267N: and the Debian External Health Status project, please consider adding a 268N: debian/watch file containing only comments documenting the situation. 269N: 270N: Refer to Debian Policy Manual section 4.11 (Optional upstream source 271N: location: debian/watch) and the uscan(1) manual page for details. 272N: 273N: Severity: info 274N: 275N: Check: debian/watch 276N: 277I: compizconfig-backend-tdeconfig-trinity: hardening-no-bindnow opt/trinity/lib/compizconfig/backends/libtdeconfig.so 278N: 279N: This package provides an ELF binary that lacks the "bindnow" linker 280N: flag. 281N: 282N: This is needed (together with "relro") to make the "Global Offset Table" 283N: (GOT) fully read-only. The bindnow feature trades startup time for 284N: improved security. Please consider enabling this feature or consider 285N: overriding the tag (possibly with a comment about why). 286N: 287N: If you use dpkg-buildflags, you may have to add hardening=+bindnow or 288N: hardening=+all to DEB_BUILD_MAINT_OPTIONS. 289N: 290N: The relevant compiler flags are set in LDFLAGS. 291N: 292N: Refer to https://wiki.debian.org/Hardening for details. 293N: 294N: Severity: info 295N: 296N: Check: binaries 297N: 298I: compizconfig-backend-tdeconfig-trinity source: no-dh-sequencer 299N: 300N: This package does not use the dh sequencer in debian/rules. 301N: 302N: While maintainers may use a variety of build systems, this one is by far 303N: the most popular. 304N: 305N: Maintainers are strongly encouraged to use the dh sequencer in new 306N: packages and convert existing ones when appropriate. 307N: 308N: Severity: info 309N: 310N: Check: debian/rules/dh-sequencer 311N: 312I: compizconfig-backend-tdeconfig-trinity source: testsuite-autopkgtest-missing 313N: 314N: This package does not declare a test suite. 315N: 316N: Having a test suite aids with automated quality assurance of the archive 317N: outside of your package. For example, if your package has a test suite 318N: it is possible to re-run that test suite when any of your package's 319N: dependencies have a new version and check whether that update causes 320N: problems for your package. 321N: 322N: In addition, since May 2018 these tests now influence migration from 323N: unstable to testing: 324N: 325N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html 326N: 327N: Please add a debian/tests/control file to your package to declare a 328N: testsuite, but please make sure to only add autopkgtests if they provide 329N: meaningful coverage of your package. 330N: 331N: Refer to https://ci.debian.net/doc/ for details. 332N: 333N: Severity: info 334N: 335N: Check: testsuite 336N: 337P: compizconfig-backend-tdeconfig-trinity: copyright-refers-to-symlink-license usr/share/common-licenses/GPL 338N: 339N: The copyright file refers to the versionless symlink in 340N: /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL 341N: license. This symlink is updated to point to the latest version of the 342N: license when a new one is released. The package appears to allow 343N: relicensing under later versions of its license, so this is legally 344N: consistent, but it implies that Debian will relicense the package under 345N: later versions of those licenses as they're released. It is normally 346N: better to point to the version of the license the package references in 347N: its license statement. 348N: 349N: For example, if the package says something like "you may redistribute it 350N: and/or modify it under the terms of the GNU General Public License as 351N: published by the Free Software Foundation; either version 2, or (at your 352N: option) any later version", the debian/copyright file should refer to 353N: /usr/share/common-licenses/GPL-2, not /GPL. 354N: 355N: For packages released under the same terms as Perl, Perl references the 356N: GPL version 1, so point to /usr/share/common-licenses/GPL-1. 357N: 358N: Severity: pedantic 359N: 360N: Check: debian/copyright 361N: 362P: compizconfig-backend-tdeconfig-trinity: copyright-with-old-dh-make-debian-copyright 363N: 364N: The copyright file contains the incomplete Debian packaging copyright 365N: boilerplate from older versions of dh_make. (C) alone is not considered 366N: a valid copyright notice in some countries. The word Copyright or the © 367N: symbol should be used instead or in addition to (C). 368N: 369N: Copyright notices like this are, in any country that's a signatory to 370N: the Berne Convention, not required to claim copyright on a work, but 371N: their presence may allow claiming additional damages should a copyright 372N: case go to court. If you provide a notice, you may as well provide one 373N: that's legally recognized in a broader range of countries. 374N: 375N: Severity: pedantic 376N: 377N: Check: debian/copyright 378N: 379P: compizconfig-backend-tdeconfig-trinity source: no-dep5-copyright 380N: 381N: This package does not use a machine-readable debian/copyright file. 382N: 383N: This format makes it easier to review licenses and can be easily parsed 384N: by Lintian. 385N: 386N: Refer to 387N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 388N: details. 389N: 390N: Severity: pedantic 391N: 392N: Check: debian/copyright 393N: 394P: compizconfig-backend-tdeconfig-trinity source: no-homepage-field 395N: 396N: This non-native package lacks a Homepage field. If the package has an 397N: upstream home page that contains useful information or resources for the 398N: end user, consider adding a Homepage control field to debian/control. 399N: 400N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. 401N: 402N: Severity: pedantic 403N: 404N: Check: fields/homepage 405N: 406P: compizconfig-backend-tdeconfig-trinity source: package-uses-old-debhelper-compat-version 10 407N: 408N: The debhelper compatibility version used by this package is marked as 409N: not recommended by the debhelper developer. You may consider using a 410N: recommended compatibility version. 411N: 412N: The compatibility version can be set by specifying debhelper-compat (= 413N: 12) in your package's Build-Depends, by the legacy debian/compat file or 414N: even by setting and exporting DH_COMPAT in debian/rules. If it is not 415N: set in either place, debhelper defaults to the deprecated compatibility 416N: version 1. 417N: 418N: Refer to the debhelper(7) manual page for details. 419N: 420N: Severity: pedantic 421N: 422N: Check: debhelper 423N: 424P: compizconfig-backend-tdeconfig-trinity source: rules-requires-root-missing 425N: 426N: The debian/control file is missing an explicit Rules-Requires-Root 427N: field. 428N: 429N: Traditionally, Debian packages have required root privileges for some 430N: debian/rules target requiring a split between build and binary targets. 431N: This makes the builds slower due to the increased amount of invocations 432N: as well as the overhead of fakeroot itself. 433N: 434N: Please specify (eg.) Rules-Requires-Root: no in the debian/control 435N: source stanza, but packagers should verify using diffoscope(1) that the 436N: binaries built with this field present are identical. 437N: 438N: Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy 439N: Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian 440N: Policy Manual section 5.6.31 (Rules-Requires-Root) for details. 441N: 442N: Severity: pedantic 443N: 444N: Check: debian/control 445N: 446X: compizconfig-backend-tdeconfig-trinity source: upstream-metadata-file-is-missing 447N: 448N: This source package is not Debian-native but it does not have a 449N: debian/upstream/metadata file. 450N: 451N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort 452N: to collect meta-information about upstream projects from any source 453N: package. This file is in YAML format and it is used in to feed the data 454N: in the UltimateDebianDatabase. For example, it can contains the way the 455N: authors want their software be cited in publications and some 456N: bibliographic references about the software. 457N: 458N: Please add a debian/upstream/metadata file. 459N: 460N: Refer to https://dep-team.pages.debian.net/deps/dep12/ and 461N: https://wiki.debian.org/UpstreamMetadata for details. 462N: 463N: Severity: pedantic 464N: 465N: Check: debian/upstream/metadata 466N: 467N: This tag is experimental. Please file a bug report if the tag seems 468N: wrong. 469N: 470C: compizconfig-backend-tdeconfig-trinity: control-tarball-compression-format xz 471N: 472N: This is the compressor format used for the control.tar tarball. 473N: 474N: Severity: classification 475N: 476N: Check: deb-format 477N: 478N: This tag is a classification. There is no issue in your package. 479N: 480C: compizconfig-backend-tdeconfig-trinity: data-tarball-compression-format xz 481N: 482N: This is the compressor format used for the data.tar tarball. 483N: 484N: Severity: classification 485N: 486N: Check: deb-format 487N: 488N: This tag is a classification. There is no issue in your package. 489N: 490C: compizconfig-backend-tdeconfig-trinity source: debhelper-compat-level 10 491N: 492N: This is the debhelper compat level used specified by this package. 493N: 494N: Severity: classification 495N: 496N: Check: debhelper 497N: 498N: This tag is a classification. There is no issue in your package. 499N: 500C: compizconfig-backend-tdeconfig-trinity source: debian-build-system cdbs-with-debhelper.mk 501N: 502N: This is the build system that Lintian believes the package is using. 503N: 504N: Severity: classification 505N: 506N: Check: debhelper 507N: 508N: This tag is a classification. There is no issue in your package. 509N: 510C: compizconfig-backend-tdeconfig-trinity: no-ctrl-scripts 511N: 512N: The package does not rely on any maintainer scripts (or other executable 513N: control files). 514N: 515N: Severity: classification 516N: 517N: Check: control-files 518N: 519N: This tag is a classification. There is no issue in your package. 520N: 521C: compizconfig-backend-tdeconfig-trinity source: package-is-maintained-by-individual 522N: 523N: The package is maintained by an individual according to the 524N: maintainer/uploaders fields in the debian/control file. 525N: 526N: Severity: classification 527N: 528N: Check: fields/vcs 529N: 530N: This tag is a classification. There is no issue in your package. 531N: 532C: compizconfig-backend-tdeconfig-trinity: package-is-maintained-by-individual 533C: compizconfig-backend-tdeconfig-trinity source: patch-system quilt 534N: 535N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 536N: 537N: Severity: classification 538N: 539N: Check: patch-systems 540N: 541N: This tag is a classification. There is no issue in your package. 542N: 543C: compizconfig-backend-tdeconfig-trinity source: source-format 3.0 (quilt) 544N: 545N: This is the source format declared in the package. 546N: 547N: Severity: classification 548N: 549N: Check: debian/source-dir 550N: 551N: This tag is a classification. There is no issue in your package. 552N: 553C: compizconfig-backend-tdeconfig-trinity source: standards-version 3.8.4 554N: 555N: The standards version of the package according to Standards-Version 556N: field in the debian/control file. 557N: 558N: Severity: classification 559N: 560N: Check: fields/standards-version 561N: 562N: This tag is a classification. There is no issue in your package. 563N: 564 565--------------------