1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-dijs8sl_/ksystemlog-trinity_14.2.0~pre39-0ubuntu20.04.0+7.dsc' '/tmp/debusine-fetch-exec-upload-dijs8sl_/ksystemlog-trinity_14.2.0~pre39-0ubuntu20.04.0+7_arm64.deb' 2output (contains stderr only, stdout was captured): 3 4Files in working directory: 5lintian.txt 6-------------------- 7E: ksystemlog-trinity: copyright-file-contains-full-gfdl-license 8N: 9N: The copyright file /usr/share/doc/<pkg>/copyright contains the complete 10N: text of the GFDL v1.2. It should refer to the file 11N: /usr/share/common-licenses/GFDL-1.2 instead. 12N: 13N: Refer to Debian Policy Manual section 12.5 (Copyright information) for 14N: details. 15N: 16N: Severity: error 17N: 18N: Check: debian/copyright 19N: 20E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/ 21N: 22N: Debian packages should not install into /opt, because it is reserved for 23N: add-on software. 24N: 25N: Refer to Filesystem Hierarchy Standard (/opt : Add-on application 26N: software packages) for details. 27N: 28N: Severity: error 29N: 30N: Check: files/hierarchy-standard 31N: 32E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/bin/ 33E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/bin/ksystemlog 34E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/ 35E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/applications/ 36E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/applications/tde/ 37E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/applications/tde/ksystemlog.desktop 38E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/apps/ 39E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksystemlog/ 40E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksystemlog/ksystemlogui.rc 41E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/config.kcfg/ 42E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/config.kcfg/ksystemlog.kcfg 43E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/ 44E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/ 45E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/ 46E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ 47E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksystemlog/ 48E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksystemlog/common 49E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksystemlog/index.cache.bz2 50E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksystemlog/index.docbook 51E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/ 52E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/ 53E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/128x128/ 54E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/128x128/apps/ 55E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/128x128/apps/ksystemlog.png 56E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/ 57E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/apps/ 58E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/apps/ksystemlog.png 59E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/22x22/ 60E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/22x22/apps/ 61E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/22x22/apps/ksystemlog.png 62E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/ 63E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/apps/ 64E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/apps/ksystemlog.png 65E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/48x48/ 66E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/48x48/apps/ 67E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/48x48/apps/ksystemlog.png 68E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/64x64/ 69E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/64x64/apps/ 70E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/64x64/apps/ksystemlog.png 71E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/scalable/ 72E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/scalable/apps/ 73E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/scalable/apps/ksystemlog.svgz 74E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ 75E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/br/ 76E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/br/LC_MESSAGES/ 77E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/br/LC_MESSAGES/ksystemlog.mo 78E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/da/ 79E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/da/LC_MESSAGES/ 80E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/da/LC_MESSAGES/ksystemlog.mo 81E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/de/ 82E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/de/LC_MESSAGES/ 83E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/de/LC_MESSAGES/ksystemlog.mo 84E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/el/ 85E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/el/LC_MESSAGES/ 86E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/el/LC_MESSAGES/ksystemlog.mo 87E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/en_GB/ 88E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/en_GB/LC_MESSAGES/ 89E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/en_GB/LC_MESSAGES/ksystemlog.mo 90E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/es/ 91E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/es/LC_MESSAGES/ 92E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/es/LC_MESSAGES/ksystemlog.mo 93E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/et/ 94E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/et/LC_MESSAGES/ 95E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/et/LC_MESSAGES/ksystemlog.mo 96E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/fr/ 97E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/fr/LC_MESSAGES/ 98E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/fr/LC_MESSAGES/ksystemlog.mo 99E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ga/ 100E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ga/LC_MESSAGES/ 101E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ga/LC_MESSAGES/ksystemlog.mo 102E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/it/ 103E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/it/LC_MESSAGES/ 104E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/it/LC_MESSAGES/ksystemlog.mo 105E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/ 106E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/ 107E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/ksystemlog.mo 108E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/pa/ 109E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/pa/LC_MESSAGES/ 110E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/pa/LC_MESSAGES/ksystemlog.mo 111E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/ 112E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/ 113E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/ksystemlog.mo 114E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/ 115E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/ 116E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/ksystemlog.mo 117E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/rw/ 118E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/rw/LC_MESSAGES/ 119E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/rw/LC_MESSAGES/ksystemlog.mo 120E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/sv/ 121E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/sv/LC_MESSAGES/ 122E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/sv/LC_MESSAGES/ksystemlog.mo 123E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/tr/ 124E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/tr/LC_MESSAGES/ 125E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/locale/tr/LC_MESSAGES/ksystemlog.mo 126E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/man/ 127E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/man/man1/ 128E: ksystemlog-trinity: dir-or-file-in-opt opt/trinity/share/man/man1/ksystemlog.1 129E: ksystemlog-trinity source: epoch-changed-but-upstream-version-did-not-go-backwards 0.3.2-2ubuntu0 -> 4:14.2.0~pre39-0ubuntu20.04.0+7 130N: 131N: The previous version of this package had a different version epoch to 132N: the current version but the upstream version did not go "backwards". For 133N: example, the previous package version was "1:1.0-1" and the current 134N: version is "2:2.0-1". 135N: 136N: This was likely an accidental bump or addition of an epoch. 137N: 138N: Epochs exist to cope with changes to the upstream version numbering 139N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 140N: has many downsides including causing issues with versioned dependencies, 141N: being misleading to users and being aesthetically unappealing. Whilst 142N: they should be avoided, valid reasons to add or increment the epoch 143N: include: 144N: 145N: - Upstream changed their versioning scheme in a way that makes the 146N: latest version lower than the previous one. 147N: - You need to permanently revert to a lower upstream version. 148N: 149N: Temporary revertions (eg. after an NMU) should use not modify or 150N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 151N: upload the latest version again. 152N: 153N: If you are unsure whether you need to increase the epoch for a package, 154N: please consult the debian-devel mailing list. 155N: 156N: Severity: error 157N: 158N: Check: debian/changelog 159N: 160E: ksystemlog-trinity source: missing-build-dependency cdbs 161N: 162N: The package doesn't specify a build dependency on a package that is used 163N: in debian/rules. 164N: 165N: Lintian intentionally does not take into account transitive 166N: dependencies. Even if the package build-depends on some package that in 167N: turn depends on the needed package, an explicit build dependency should 168N: be added. Otherwise, a latent bug is created that will appear without 169N: warning if the other package is ever updated to change its dependencies. 170N: Even if this seems unlikely, please always add explicit build 171N: dependencies on every non-essential, non-build-essential package that is 172N: used directly during the build. 173N: 174N: Refer to Debian Policy Manual section 4.2 (Package relationships) for 175N: details. 176N: 177N: Severity: error 178N: 179N: Check: debian/rules 180N: 181W: ksystemlog-trinity source: ancient-standards-version 3.8.4 (released 2010-01-27) (current is 4.5.0) 182N: 183N: The source package refers to a Standards-Version that has been obsolete 184N: for more than two years. Please update your package to latest Policy and 185N: set this control field appropriately. 186N: 187N: If the package is already compliant with the current standards, you 188N: don't have to re-upload the package just to adjust the Standards-Version 189N: control field. However, please remember to update this field next time 190N: you upload the package. 191N: 192N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 193N: debian-policy package for a summary of changes in newer versions of 194N: Policy. 195N: 196N: Refer to 197N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 198N: details. 199N: 200N: Severity: warning 201N: 202N: Check: fields/standards-version 203N: 204W: ksystemlog-trinity source: binary-nmu-debian-revision-in-source 4:14.2.0~pre39-0ubuntu20.04.0+7 205N: 206N: The version number of your source package ends in +b and a number or has 207N: a Debian revision containing three parts. These version numbers are used 208N: by binary NMUs and should not be used as the source version. (The +b 209N: form is the current standard; the three-part version number now 210N: obsolete.) 211N: 212N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or 213N: binary-only NMU) for details. 214N: 215N: Severity: warning 216N: 217N: Check: fields/version 218N: 219W: ksystemlog-trinity source: debian-source-options-has-custom-compression-settings compression = "xz" (line 2) 220N: 221N: The debian/source/options file for this package specifies a custom 222N: compression level or algorithm. 223N: 224N: Whilst higher levels may reduce the size of big files, they have the 225N: side effect of consuming a lot of memory during both compression and 226N: extraction. This can not only also waste time unnecessarily, it can 227N: cause packages to FTBFS or even fail to install in resource-constrained 228N: environments or architectures. 229N: 230N: Please remove the call and let dpkg-deb(1) select suitable defaults. 231N: 232N: Refer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page 233N: for details. 234N: 235N: Severity: warning 236N: 237N: Check: debian/source-dir 238N: 239W: ksystemlog-trinity source: debian-source-options-has-custom-compression-settings compression-level = 9 (line 3) 240W: ksystemlog-trinity: description-contains-homepage 241N: 242N: The extended description contains a "Homepage" pseudo-field following 243N: the old Developer's Reference recommendation. As of 1.14.6, dpkg now 244N: supports Homepage as a regular field in debian/control. This 245N: pseudo-field should be moved from the extended description to the fields 246N: for the relevant source or binary packages. 247N: 248N: Severity: warning 249N: 250N: Check: fields/description 251N: 252W: ksystemlog-trinity source: epoch-change-without-comment 0.3.2-2ubuntu0 -> 4:14.2.0~pre39-0ubuntu20.04.0+7 253N: 254N: The previous version of this package had a different version epoch (eg. 255N: 2:1.0-1) to the current version but there's no reference to this in the 256N: changelog entry. 257N: 258N: Epochs exist to cope with changes to the upstream version numbering 259N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 260N: has many downsides including causing issues with versioned dependencies, 261N: being misleading to users and being aesthetically unappealing. Whilst 262N: they should be avoided, valid reasons to add or increment the epoch 263N: include: 264N: 265N: - Upstream changed their versioning scheme in a way that makes the 266N: latest version lower than the previous one. 267N: - You need to permanently revert to a lower upstream version. 268N: 269N: Temporary revertions (eg. after an NMU) should use not modify or 270N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 271N: upload the latest version again. 272N: 273N: If you are unsure whether you need to increase the epoch for a package, 274N: please consult the debian-devel mailing list. 275N: 276N: Lintian looks in this version's changelog entry for the phrase "epoch". 277N: 278N: Severity: warning 279N: 280N: Check: debian/changelog 281N: 282W: ksystemlog-trinity: hardening-no-relro opt/trinity/bin/ksystemlog 283N: 284N: This package provides an ELF binary that lacks the "read-only 285N: relocation" link flag. This package was likely not built with the 286N: default Debian compiler flags defined by dpkg-buildflags. If built using 287N: dpkg-buildflags directly, be sure to import LDFLAGS. 288N: 289N: Refer to https://wiki.debian.org/Hardening for details. 290N: 291N: Severity: warning 292N: 293N: Check: binaries 294N: 295W: ksystemlog-trinity: menu-command-not-in-package usr/share/menu/ksystemlog-trinity:4 ksystemlog 296N: 297N: The menu item specifies a command which is not available in the package. 298N: In most cases this is a typo or after you moved a binary around, but 299N: forgot to update the menu file. 300N: 301N: Severity: warning 302N: 303N: Check: menu-format 304N: 305W: ksystemlog-trinity: menu-item-creates-new-section Apps/Tools usr/share/menu/ksystemlog-trinity:4 306N: 307N: The menu item has a line that specifies an unknown section or uses a 308N: section that is intended only as a menu root, not as a section that 309N: applications should use directly. Check the spelling of the section and 310N: check the section against the list in the menu policy. (The menu 311N: sections changed as of June of 2007.) 312N: 313N: Refer to The Debian Menu sub-policy section 2.1 (Preferred menu 314N: structure) for details. 315N: 316N: Severity: warning 317N: 318N: Check: menu-format 319N: 320W: ksystemlog-trinity: menu-item-uses-apps-section usr/share/menu/ksystemlog-trinity:4 321N: 322N: The menu item has a line that specifies a section under "Apps". This 323N: section has been moved to "Applications". 324N: 325N: Refer to The Debian Menu sub-policy section 2.1 (Preferred menu 326N: structure) for details. 327N: 328N: Severity: warning 329N: 330N: Check: menu-format 331N: 332W: ksystemlog-trinity: package-relation-with-self breaks: ksystemlog-trinity (<< 4:14.0.0~) 333N: 334N: The package declares a relationship with itself. This is not very useful 335N: except in the case of a package Conflicting with itself if its package 336N: name doubles as a virtual package. 337N: 338N: Severity: warning 339N: 340N: Check: fields/package-relations 341N: 342W: ksystemlog-trinity: spelling-error-in-description occuring occurring 343N: 344N: Lintian found a spelling error in the package description. Lintian has a 345N: list of common misspellings that it looks for. It does not have a 346N: dictionary like a spelling checker does. It is particularly picky about 347N: spelling and capitalization in package descriptions since they're very 348N: visible to end users. 349N: 350N: Severity: warning 351N: 352N: Check: fields/description 353N: 354W: ksystemlog-trinity: unknown-section tde 355N: 356N: The "Section:" field in this package's control file is not one of the 357N: sections in use on the ftp archive. Valid sections are currently admin, 358N: comm, cli-mono, database, debug, devel, doc, editors, electronics, 359N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, 360N: haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, 361N: lisp, localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, 362N: otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex, 363N: text, utils, vcs, video, web, x11, xfce, zope. 364N: 365N: The section name should be preceded by "non-free/" if the package is in 366N: the non-free archive area, and by "contrib/" if the package is in the 367N: contrib archive area. 368N: 369N: Refer to Debian Policy Manual section 2.4 (Sections) for details. 370N: 371N: Severity: warning 372N: 373N: Check: fields/section 374N: 375I: ksystemlog-trinity source: debian-watch-file-is-missing 376N: 377N: This source package is not Debian-native but it does not have a 378N: debian/watch file. This file is used for automatic detection of new 379N: upstream versions by the Debian External Health Status project and other 380N: project infrastructure. If this package is maintained upstream, please 381N: consider adding a debian/watch file to detect new releases. 382N: 383N: If the package is not maintained upstream or if upstream uses a 384N: distribution mechanism that cannot be meaningfully monitored by uscan 385N: and the Debian External Health Status project, please consider adding a 386N: debian/watch file containing only comments documenting the situation. 387N: 388N: Refer to Debian Policy Manual section 4.11 (Optional upstream source 389N: location: debian/watch) and the uscan(1) manual page for details. 390N: 391N: Severity: info 392N: 393N: Check: debian/watch 394N: 395I: ksystemlog-trinity source: no-dh-sequencer 396N: 397N: This package does not use the dh sequencer in debian/rules. 398N: 399N: While maintainers may use a variety of build systems, this one is by far 400N: the most popular. 401N: 402N: Maintainers are strongly encouraged to use the dh sequencer in new 403N: packages and convert existing ones when appropriate. 404N: 405N: Severity: info 406N: 407N: Check: debian/rules/dh-sequencer 408N: 409I: ksystemlog-trinity source: testsuite-autopkgtest-missing 410N: 411N: This package does not declare a test suite. 412N: 413N: Having a test suite aids with automated quality assurance of the archive 414N: outside of your package. For example, if your package has a test suite 415N: it is possible to re-run that test suite when any of your package's 416N: dependencies have a new version and check whether that update causes 417N: problems for your package. 418N: 419N: In addition, since May 2018 these tests now influence migration from 420N: unstable to testing: 421N: 422N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html 423N: 424N: Please add a debian/tests/control file to your package to declare a 425N: testsuite, but please make sure to only add autopkgtests if they provide 426N: meaningful coverage of your package. 427N: 428N: Refer to https://ci.debian.net/doc/ for details. 429N: 430N: Severity: info 431N: 432N: Check: testsuite 433N: 434P: ksystemlog-trinity source: co-maintained-package-with-no-vcs-fields 435N: 436N: Based on the content of the maintainer and uploader fields this package 437N: is co-maintained but there are no Vcs-* fields. 438N: 439N: It is recommended that shared maintenance of packages are co-ordinated 440N: via a revision control system. 441N: 442N: Severity: pedantic 443N: 444N: Check: fields/vcs 445N: 446P: ksystemlog-trinity: copyright-refers-to-symlink-license usr/share/common-licenses/GPL 447N: 448N: The copyright file refers to the versionless symlink in 449N: /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL 450N: license. This symlink is updated to point to the latest version of the 451N: license when a new one is released. The package appears to allow 452N: relicensing under later versions of its license, so this is legally 453N: consistent, but it implies that Debian will relicense the package under 454N: later versions of those licenses as they're released. It is normally 455N: better to point to the version of the license the package references in 456N: its license statement. 457N: 458N: For example, if the package says something like "you may redistribute it 459N: and/or modify it under the terms of the GNU General Public License as 460N: published by the Free Software Foundation; either version 2, or (at your 461N: option) any later version", the debian/copyright file should refer to 462N: /usr/share/common-licenses/GPL-2, not /GPL. 463N: 464N: For packages released under the same terms as Perl, Perl references the 465N: GPL version 1, so point to /usr/share/common-licenses/GPL-1. 466N: 467N: Severity: pedantic 468N: 469N: Check: debian/copyright 470N: 471P: ksystemlog-trinity: copyright-with-old-dh-make-debian-copyright 472N: 473N: The copyright file contains the incomplete Debian packaging copyright 474N: boilerplate from older versions of dh_make. (C) alone is not considered 475N: a valid copyright notice in some countries. The word Copyright or the © 476N: symbol should be used instead or in addition to (C). 477N: 478N: Copyright notices like this are, in any country that's a signatory to 479N: the Berne Convention, not required to claim copyright on a work, but 480N: their presence may allow claiming additional damages should a copyright 481N: case go to court. If you provide a notice, you may as well provide one 482N: that's legally recognized in a broader range of countries. 483N: 484N: Severity: pedantic 485N: 486N: Check: debian/copyright 487N: 488P: ksystemlog-trinity source: file-contains-trailing-whitespace debian/changelog (line 58) 489N: 490N: This file appears to contain one or more lines with trailing whitespace 491N: characters. 492N: 493N: Whilst typically harmless and merely unsightly, they can often cause 494N: difficult-to-spot issues where tools interpret the whitespace characters 495N: literally as well as introduce unnecessary diff(1) noise. They are thus 496N: best avoided in their entirity. 497N: 498N: Whitespace at the end of lines may be removed with the following: 499N: 500N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 501N: 502N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 503N: 504N: However, if you wish to only remove trailing spaces and leave trailing 505N: tabs (eg. for Makefiles), you can use the following code snippet: 506N: 507N: $ sed -i -e 's@[ ]*$@@g' debian/rules 508N: 509N: To remove empty lines from the end of a file, you can use: 510N: 511N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 512N: 513N: Severity: pedantic 514N: 515N: Check: cruft 516N: 517P: ksystemlog-trinity source: file-contains-trailing-whitespace debian/changelog (line 85) 518P: ksystemlog-trinity source: no-dep5-copyright 519N: 520N: This package does not use a machine-readable debian/copyright file. 521N: 522N: This format makes it easier to review licenses and can be easily parsed 523N: by Lintian. 524N: 525N: Refer to 526N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 527N: details. 528N: 529N: Severity: pedantic 530N: 531N: Check: debian/copyright 532N: 533P: ksystemlog-trinity source: no-homepage-field 534N: 535N: This non-native package lacks a Homepage field. If the package has an 536N: upstream home page that contains useful information or resources for the 537N: end user, consider adding a Homepage control field to debian/control. 538N: 539N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. 540N: 541N: Severity: pedantic 542N: 543N: Check: fields/homepage 544N: 545P: ksystemlog-trinity source: package-uses-old-debhelper-compat-version 10 546N: 547N: The debhelper compatibility version used by this package is marked as 548N: not recommended by the debhelper developer. You may consider using a 549N: recommended compatibility version. 550N: 551N: The compatibility version can be set by specifying debhelper-compat (= 552N: 12) in your package's Build-Depends, by the legacy debian/compat file or 553N: even by setting and exporting DH_COMPAT in debian/rules. If it is not 554N: set in either place, debhelper defaults to the deprecated compatibility 555N: version 1. 556N: 557N: Refer to the debhelper(7) manual page for details. 558N: 559N: Severity: pedantic 560N: 561N: Check: debhelper 562N: 563P: ksystemlog-trinity source: rules-requires-root-missing 564N: 565N: The debian/control file is missing an explicit Rules-Requires-Root 566N: field. 567N: 568N: Traditionally, Debian packages have required root privileges for some 569N: debian/rules target requiring a split between build and binary targets. 570N: This makes the builds slower due to the increased amount of invocations 571N: as well as the overhead of fakeroot itself. 572N: 573N: Please specify (eg.) Rules-Requires-Root: no in the debian/control 574N: source stanza, but packagers should verify using diffoscope(1) that the 575N: binaries built with this field present are identical. 576N: 577N: Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy 578N: Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian 579N: Policy Manual section 5.6.31 (Rules-Requires-Root) for details. 580N: 581N: Severity: pedantic 582N: 583N: Check: debian/control 584N: 585X: ksystemlog-trinity source: upstream-metadata-file-is-missing 586N: 587N: This source package is not Debian-native but it does not have a 588N: debian/upstream/metadata file. 589N: 590N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort 591N: to collect meta-information about upstream projects from any source 592N: package. This file is in YAML format and it is used in to feed the data 593N: in the UltimateDebianDatabase. For example, it can contains the way the 594N: authors want their software be cited in publications and some 595N: bibliographic references about the software. 596N: 597N: Please add a debian/upstream/metadata file. 598N: 599N: Refer to https://dep-team.pages.debian.net/deps/dep12/ and 600N: https://wiki.debian.org/UpstreamMetadata for details. 601N: 602N: Severity: pedantic 603N: 604N: Check: debian/upstream/metadata 605N: 606N: This tag is experimental. Please file a bug report if the tag seems 607N: wrong. 608N: 609C: ksystemlog-trinity: control-tarball-compression-format xz 610N: 611N: This is the compressor format used for the control.tar tarball. 612N: 613N: Severity: classification 614N: 615N: Check: deb-format 616N: 617N: This tag is a classification. There is no issue in your package. 618N: 619C: ksystemlog-trinity: ctrl-script postinst 620N: 621N: This package has one or more maintainer scripts (or other executable 622N: control files). 623N: 624N: This flags any control file with the executable bit set. 625N: 626N: Severity: classification 627N: 628N: Check: control-files 629N: 630N: This tag is a classification. There is no issue in your package. 631N: 632C: ksystemlog-trinity: ctrl-script postrm 633C: ksystemlog-trinity: data-tarball-compression-format xz 634N: 635N: This is the compressor format used for the data.tar tarball. 636N: 637N: Severity: classification 638N: 639N: Check: deb-format 640N: 641N: This tag is a classification. There is no issue in your package. 642N: 643C: ksystemlog-trinity: debhelper-autoscript-in-maintainer-scripts dh_installmenu/12.10ubuntu1 644N: 645N: The maintainer scripts of the package contain one or more auto-generated 646N: shell snippets inserted by the listed debhelper tool. 647N: 648N: Severity: classification 649N: 650N: Check: maintainer-scripts/generated 651N: 652N: This tag is a classification. There is no issue in your package. 653N: 654C: ksystemlog-trinity source: debhelper-compat-level 10 655N: 656N: This is the debhelper compat level used specified by this package. 657N: 658N: Severity: classification 659N: 660N: Check: debhelper 661N: 662N: This tag is a classification. There is no issue in your package. 663N: 664C: ksystemlog-trinity source: debian-build-system cdbs-with-debhelper.mk 665N: 666N: This is the build system that Lintian believes the package is using. 667N: 668N: Severity: classification 669N: 670N: Check: debhelper 671N: 672N: This tag is a classification. There is no issue in your package. 673N: 674C: ksystemlog-trinity: maintainer-script-interpreter control/postinst /bin/sh 675N: 676N: Interpreter used in maintainer script or ELF 677N: 678N: Severity: classification 679N: 680N: Check: scripts 681N: 682N: This tag is a classification. There is no issue in your package. 683N: 684C: ksystemlog-trinity: maintainer-script-interpreter control/postrm /bin/sh 685C: ksystemlog-trinity source: package-is-co-maintained 2 686N: 687N: The package is co-maintained but not team-maintained according to the 688N: maintainer/uploaders fields in the debian/control file. 689N: 690N: Severity: classification 691N: 692N: Check: fields/vcs 693N: 694N: This tag is a classification. There is no issue in your package. 695N: 696C: ksystemlog-trinity: package-is-maintained-by-individual 697N: 698N: The package is maintained by an individual according to the 699N: maintainer/uploaders fields in the debian/control file. 700N: 701N: Severity: classification 702N: 703N: Check: fields/vcs 704N: 705N: This tag is a classification. There is no issue in your package. 706N: 707C: ksystemlog-trinity source: patch-system quilt 708N: 709N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 710N: 711N: Severity: classification 712N: 713N: Check: patch-systems 714N: 715N: This tag is a classification. There is no issue in your package. 716N: 717C: ksystemlog-trinity source: source-format 3.0 (quilt) 718N: 719N: This is the source format declared in the package. 720N: 721N: Severity: classification 722N: 723N: Check: debian/source-dir 724N: 725N: This tag is a classification. There is no issue in your package. 726N: 727C: ksystemlog-trinity source: standards-version 3.8.4 728N: 729N: The standards version of the package according to Standards-Version 730N: field in the debian/control file. 731N: 732N: Severity: classification 733N: 734N: Check: fields/standards-version 735N: 736N: This tag is a classification. There is no issue in your package. 737N: 738 739--------------------