lintian.txt

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