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