1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-xb7tjj2s/ksensors-trinity_14.2.0~pre33-0ubuntu20.04.0+7.dsc' '/tmp/debusine-fetch-exec-upload-xb7tjj2s/ksensors-trinity_14.2.0~pre33-0ubuntu20.04.0+7_ppc64el.deb' 2output (contains stderr only, stdout was captured): 3 4Files in working directory: 5lintian.txt 6-------------------- 7E: ksensors-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: ksensors-trinity: dir-or-file-in-opt opt/trinity/bin/ 20E: ksensors-trinity: dir-or-file-in-opt opt/trinity/bin/ksensors 21E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/ 22E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/applications/ 23E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/applications/tde/ 24E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/applications/tde/ksensors.desktop 25E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ 26E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/ 27E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/ksensorsui.rc 28E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/ 29E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/battery.png 30E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/battery18x18.png 31E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/computers.png 32E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/cooler.png 33E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/cooler18x18.png 34E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/earth.png 35E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/harddisk.png 36E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/ksensorsbackground.png 37E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/ksensorsdocked.png 38E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/ksensorssplash.png 39E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/motherboard.png 40E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/thermometer.png 41E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/apps/ksensors/pics/thermometer18x18.png 42E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/autostart/ 43E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/autostart/ksensors.desktop 44E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/ 45E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/ 46E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/ 47E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ 48E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksensors/ 49E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksensors/common 50E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksensors/index.cache.bz2 51E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/doc/tde/HTML/en/ksensors/index.docbook 52E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/ 53E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/ 54E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/ 55E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/apps/ 56E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/16x16/apps/ksensors.png 57E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/ 58E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/apps/ 59E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/hicolor/32x32/apps/ksensors.png 60E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/ 61E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/16x16/ 62E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/16x16/apps/ 63E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/16x16/apps/ksensors.png 64E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/32x32/ 65E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/32x32/apps/ 66E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/icons/locolor/32x32/apps/ksensors.png 67E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ 68E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/cs/ 69E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/cs/LC_MESSAGES/ 70E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/cs/LC_MESSAGES/ksensors.mo 71E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/de/ 72E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/de/LC_MESSAGES/ 73E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/de/LC_MESSAGES/ksensors.mo 74E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/es/ 75E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/es/LC_MESSAGES/ 76E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/es/LC_MESSAGES/ksensors.mo 77E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/fr/ 78E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/fr/LC_MESSAGES/ 79E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/fr/LC_MESSAGES/ksensors.mo 80E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/ 81E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/LC_MESSAGES/ 82E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ka/LC_MESSAGES/ksensors.mo 83E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/nb/ 84E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/nb/LC_MESSAGES/ 85E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/nb/LC_MESSAGES/ksensors.mo 86E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/ 87E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/ 88E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/nl/LC_MESSAGES/ksensors.mo 89E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/ 90E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/ 91E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/pl/LC_MESSAGES/ksensors.mo 92E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/ 93E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/ 94E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/ru/LC_MESSAGES/ksensors.mo 95E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/sv/ 96E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/sv/LC_MESSAGES/ 97E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/locale/sv/LC_MESSAGES/ksensors.mo 98E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/man/ 99E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/man/man1/ 100E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/man/man1/ksensors.1 101E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/pixmaps/ 102E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/pixmaps/ksensors.xpm 103E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/sounds/ 104E: ksensors-trinity: dir-or-file-in-opt opt/trinity/share/sounds/ksensors_alert.wav 105E: ksensors-trinity source: epoch-changed-but-upstream-version-did-not-go-backwards 0.7.3-18 -> 4:14.2.0~pre33-0ubuntu20.04.0+7 106N: 107N: The previous version of this package had a different version epoch to 108N: the current version but the upstream version did not go "backwards". For 109N: example, the previous package version was "1:1.0-1" and the current 110N: version is "2:2.0-1". 111N: 112N: This was likely an accidental bump or addition of an epoch. 113N: 114N: Epochs exist to cope with changes to the upstream version numbering 115N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 116N: has many downsides including causing issues with versioned dependencies, 117N: being misleading to users and being aesthetically unappealing. Whilst 118N: they should be avoided, valid reasons to add or increment the epoch 119N: include: 120N: 121N: - Upstream changed their versioning scheme in a way that makes the 122N: latest version lower than the previous one. 123N: - You need to permanently revert to a lower upstream version. 124N: 125N: Temporary revertions (eg. after an NMU) should use not modify or 126N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 127N: upload the latest version again. 128N: 129N: If you are unsure whether you need to increase the epoch for a package, 130N: please consult the debian-devel mailing list. 131N: 132N: Severity: error 133N: 134N: Check: debian/changelog 135N: 136E: ksensors-trinity source: missing-build-dependency cdbs 137N: 138N: The package doesn't specify a build dependency on a package that is used 139N: in debian/rules. 140N: 141N: Lintian intentionally does not take into account transitive 142N: dependencies. Even if the package build-depends on some package that in 143N: turn depends on the needed package, an explicit build dependency should 144N: be added. Otherwise, a latent bug is created that will appear without 145N: warning if the other package is ever updated to change its dependencies. 146N: Even if this seems unlikely, please always add explicit build 147N: dependencies on every non-essential, non-build-essential package that is 148N: used directly during the build. 149N: 150N: Refer to Debian Policy Manual section 4.2 (Package relationships) for 151N: details. 152N: 153N: Severity: error 154N: 155N: Check: debian/rules 156N: 157W: ksensors-trinity source: ancient-standards-version 3.8.3 (released 2009-08-16) (current is 4.5.0) 158N: 159N: The source package refers to a Standards-Version that has been obsolete 160N: for more than two years. Please update your package to latest Policy and 161N: set this control field appropriately. 162N: 163N: If the package is already compliant with the current standards, you 164N: don't have to re-upload the package just to adjust the Standards-Version 165N: control field. However, please remember to update this field next time 166N: you upload the package. 167N: 168N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 169N: debian-policy package for a summary of changes in newer versions of 170N: Policy. 171N: 172N: Refer to 173N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 174N: details. 175N: 176N: Severity: warning 177N: 178N: Check: fields/standards-version 179N: 180W: ksensors-trinity source: binary-nmu-debian-revision-in-source 4:14.2.0~pre33-0ubuntu20.04.0+7 181N: 182N: The version number of your source package ends in +b and a number or has 183N: a Debian revision containing three parts. These version numbers are used 184N: by binary NMUs and should not be used as the source version. (The +b 185N: form is the current standard; the three-part version number now 186N: obsolete.) 187N: 188N: Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or 189N: binary-only NMU) for details. 190N: 191N: Severity: warning 192N: 193N: Check: fields/version 194N: 195W: ksensors-trinity source: debian-source-options-has-custom-compression-settings compression = "xz" (line 2) 196N: 197N: The debian/source/options file for this package specifies a custom 198N: compression level or algorithm. 199N: 200N: Whilst higher levels may reduce the size of big files, they have the 201N: side effect of consuming a lot of memory during both compression and 202N: extraction. This can not only also waste time unnecessarily, it can 203N: cause packages to FTBFS or even fail to install in resource-constrained 204N: environments or architectures. 205N: 206N: Please remove the call and let dpkg-deb(1) select suitable defaults. 207N: 208N: Refer to https://bugs.debian.org/829100 and the dpkg-deb(1) manual page 209N: for details. 210N: 211N: Severity: warning 212N: 213N: Check: debian/source-dir 214N: 215W: ksensors-trinity source: debian-source-options-has-custom-compression-settings compression-level = 9 (line 3) 216W: ksensors-trinity source: epoch-change-without-comment 0.7.3-18 -> 4:14.2.0~pre33-0ubuntu20.04.0+7 217N: 218N: The previous version of this package had a different version epoch (eg. 219N: 2:1.0-1) to the current version but there's no reference to this in the 220N: changelog entry. 221N: 222N: Epochs exist to cope with changes to the upstream version numbering 223N: scheme. Whilst they are a powerful tool, increasing or adding an epoch 224N: has many downsides including causing issues with versioned dependencies, 225N: being misleading to users and being aesthetically unappealing. Whilst 226N: they should be avoided, valid reasons to add or increment the epoch 227N: include: 228N: 229N: - Upstream changed their versioning scheme in a way that makes the 230N: latest version lower than the previous one. 231N: - You need to permanently revert to a lower upstream version. 232N: 233N: Temporary revertions (eg. after an NMU) should use not modify or 234N: introduce an epoch - please use the CURRENT+reallyFORMER until you can 235N: upload the latest version again. 236N: 237N: If you are unsure whether you need to increase the epoch for a package, 238N: please consult the debian-devel mailing list. 239N: 240N: Lintian looks in this version's changelog entry for the phrase "epoch". 241N: 242N: Severity: warning 243N: 244N: Check: debian/changelog 245N: 246W: ksensors-trinity: hardening-no-relro opt/trinity/bin/ksensors 247N: 248N: This package provides an ELF binary that lacks the "read-only 249N: relocation" link flag. This package was likely not built with the 250N: default Debian compiler flags defined by dpkg-buildflags. If built using 251N: dpkg-buildflags directly, be sure to import LDFLAGS. 252N: 253N: Refer to https://wiki.debian.org/Hardening for details. 254N: 255N: Severity: warning 256N: 257N: Check: binaries 258N: 259W: ksensors-trinity: unknown-section tde 260N: 261N: The "Section:" field in this package's control file is not one of the 262N: sections in use on the ftp archive. Valid sections are currently admin, 263N: comm, cli-mono, database, debug, devel, doc, editors, electronics, 264N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, 265N: haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, 266N: lisp, localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, 267N: otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex, 268N: text, utils, vcs, video, web, x11, xfce, zope. 269N: 270N: The section name should be preceded by "non-free/" if the package is in 271N: the non-free archive area, and by "contrib/" if the package is in the 272N: contrib archive area. 273N: 274N: Refer to Debian Policy Manual section 2.4 (Sections) for details. 275N: 276N: Severity: warning 277N: 278N: Check: fields/section 279N: 280I: ksensors-trinity source: debian-watch-file-is-missing 281N: 282N: This source package is not Debian-native but it does not have a 283N: debian/watch file. This file is used for automatic detection of new 284N: upstream versions by the Debian External Health Status project and other 285N: project infrastructure. If this package is maintained upstream, please 286N: consider adding a debian/watch file to detect new releases. 287N: 288N: If the package is not maintained upstream or if upstream uses a 289N: distribution mechanism that cannot be meaningfully monitored by uscan 290N: and the Debian External Health Status project, please consider adding a 291N: debian/watch file containing only comments documenting the situation. 292N: 293N: Refer to Debian Policy Manual section 4.11 (Optional upstream source 294N: location: debian/watch) and the uscan(1) manual page for details. 295N: 296N: Severity: info 297N: 298N: Check: debian/watch 299N: 300I: ksensors-trinity: hardening-no-fortify-functions opt/trinity/bin/ksensors 301N: 302N: This package provides an ELF binary that lacks the use of fortified libc 303N: functions. Either there are no potentially unfortified functions called 304N: by any routines, all unfortified calls have already been fully validated 305N: at compile-time, or the package was not built with the default Debian 306N: compiler flags defined by dpkg-buildflags. If built using 307N: dpkg-buildflags directly, be sure to import CPPFLAGS. 308N: 309N: NB: Due to false-positives, Lintian ignores some unprotected functions 310N: (e.g. memcpy). 311N: 312N: Refer to https://wiki.debian.org/Hardening and 313N: https://bugs.debian.org/673112 for details. 314N: 315N: Severity: info 316N: 317N: Check: binaries 318N: 319I: ksensors-trinity source: no-dh-sequencer 320N: 321N: This package does not use the dh sequencer in debian/rules. 322N: 323N: While maintainers may use a variety of build systems, this one is by far 324N: the most popular. 325N: 326N: Maintainers are strongly encouraged to use the dh sequencer in new 327N: packages and convert existing ones when appropriate. 328N: 329N: Severity: info 330N: 331N: Check: debian/rules/dh-sequencer 332N: 333I: ksensors-trinity source: testsuite-autopkgtest-missing 334N: 335N: This package does not declare a test suite. 336N: 337N: Having a test suite aids with automated quality assurance of the archive 338N: outside of your package. For example, if your package has a test suite 339N: it is possible to re-run that test suite when any of your package's 340N: dependencies have a new version and check whether that update causes 341N: problems for your package. 342N: 343N: In addition, since May 2018 these tests now influence migration from 344N: unstable to testing: 345N: 346N: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html 347N: 348N: Please add a debian/tests/control file to your package to declare a 349N: testsuite, but please make sure to only add autopkgtests if they provide 350N: meaningful coverage of your package. 351N: 352N: Refer to https://ci.debian.net/doc/ for details. 353N: 354N: Severity: info 355N: 356N: Check: testsuite 357N: 358P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 108) 359N: 360N: This file appears to contain one or more lines with trailing whitespace 361N: characters. 362N: 363N: Whilst typically harmless and merely unsightly, they can often cause 364N: difficult-to-spot issues where tools interpret the whitespace characters 365N: literally as well as introduce unnecessary diff(1) noise. They are thus 366N: best avoided in their entirity. 367N: 368N: Whitespace at the end of lines may be removed with the following: 369N: 370N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 371N: 372N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 373N: 374N: However, if you wish to only remove trailing spaces and leave trailing 375N: tabs (eg. for Makefiles), you can use the following code snippet: 376N: 377N: $ sed -i -e 's@[ ]*$@@g' debian/rules 378N: 379N: To remove empty lines from the end of a file, you can use: 380N: 381N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 382N: 383N: Severity: pedantic 384N: 385N: Check: cruft 386N: 387P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 131) 388P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 132) 389P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 153) 390P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 161) 391P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 17) 392P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 189) 393P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 211) 394P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 280) 395P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 293) 396P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 315) 397P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 320) 398P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 388) 399P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 400) 400P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 406) 401P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 418) 402P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 43) 403P: ksensors-trinity source: file-contains-trailing-whitespace debian/changelog (line 77) 404P: ksensors-trinity source: no-dep5-copyright 405N: 406N: This package does not use a machine-readable debian/copyright file. 407N: 408N: This format makes it easier to review licenses and can be easily parsed 409N: by Lintian. 410N: 411N: Refer to 412N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 413N: details. 414N: 415N: Severity: pedantic 416N: 417N: Check: debian/copyright 418N: 419P: ksensors-trinity source: no-homepage-field 420N: 421N: This non-native package lacks a Homepage field. If the package has an 422N: upstream home page that contains useful information or resources for the 423N: end user, consider adding a Homepage control field to debian/control. 424N: 425N: Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. 426N: 427N: Severity: pedantic 428N: 429N: Check: fields/homepage 430N: 431P: ksensors-trinity source: package-uses-old-debhelper-compat-version 10 432N: 433N: The debhelper compatibility version used by this package is marked as 434N: not recommended by the debhelper developer. You may consider using a 435N: recommended compatibility version. 436N: 437N: The compatibility version can be set by specifying debhelper-compat (= 438N: 12) in your package's Build-Depends, by the legacy debian/compat file or 439N: even by setting and exporting DH_COMPAT in debian/rules. If it is not 440N: set in either place, debhelper defaults to the deprecated compatibility 441N: version 1. 442N: 443N: Refer to the debhelper(7) manual page for details. 444N: 445N: Severity: pedantic 446N: 447N: Check: debhelper 448N: 449P: ksensors-trinity source: rules-requires-root-missing 450N: 451N: The debian/control file is missing an explicit Rules-Requires-Root 452N: field. 453N: 454N: Traditionally, Debian packages have required root privileges for some 455N: debian/rules target requiring a split between build and binary targets. 456N: This makes the builds slower due to the increased amount of invocations 457N: as well as the overhead of fakeroot itself. 458N: 459N: Please specify (eg.) Rules-Requires-Root: no in the debian/control 460N: source stanza, but packagers should verify using diffoscope(1) that the 461N: binaries built with this field present are identical. 462N: 463N: Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy 464N: Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian 465N: Policy Manual section 5.6.31 (Rules-Requires-Root) for details. 466N: 467N: Severity: pedantic 468N: 469N: Check: debian/control 470N: 471X: ksensors-trinity source: upstream-metadata-file-is-missing 472N: 473N: This source package is not Debian-native but it does not have a 474N: debian/upstream/metadata file. 475N: 476N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort 477N: to collect meta-information about upstream projects from any source 478N: package. This file is in YAML format and it is used in to feed the data 479N: in the UltimateDebianDatabase. For example, it can contains the way the 480N: authors want their software be cited in publications and some 481N: bibliographic references about the software. 482N: 483N: Please add a debian/upstream/metadata file. 484N: 485N: Refer to https://dep-team.pages.debian.net/deps/dep12/ and 486N: https://wiki.debian.org/UpstreamMetadata for details. 487N: 488N: Severity: pedantic 489N: 490N: Check: debian/upstream/metadata 491N: 492N: This tag is experimental. Please file a bug report if the tag seems 493N: wrong. 494N: 495C: ksensors-trinity: control-tarball-compression-format xz 496N: 497N: This is the compressor format used for the control.tar tarball. 498N: 499N: Severity: classification 500N: 501N: Check: deb-format 502N: 503N: This tag is a classification. There is no issue in your package. 504N: 505C: ksensors-trinity: ctrl-script postinst 506N: 507N: This package has one or more maintainer scripts (or other executable 508N: control files). 509N: 510N: This flags any control file with the executable bit set. 511N: 512N: Severity: classification 513N: 514N: Check: control-files 515N: 516N: This tag is a classification. There is no issue in your package. 517N: 518C: ksensors-trinity: ctrl-script postrm 519C: ksensors-trinity: data-tarball-compression-format xz 520N: 521N: This is the compressor format used for the data.tar tarball. 522N: 523N: Severity: classification 524N: 525N: Check: deb-format 526N: 527N: This tag is a classification. There is no issue in your package. 528N: 529C: ksensors-trinity: debhelper-autoscript-in-maintainer-scripts dh_installmenu/12.10ubuntu1 530N: 531N: The maintainer scripts of the package contain one or more auto-generated 532N: shell snippets inserted by the listed debhelper tool. 533N: 534N: Severity: classification 535N: 536N: Check: maintainer-scripts/generated 537N: 538N: This tag is a classification. There is no issue in your package. 539N: 540C: ksensors-trinity source: debhelper-compat-level 10 541N: 542N: This is the debhelper compat level used specified by this package. 543N: 544N: Severity: classification 545N: 546N: Check: debhelper 547N: 548N: This tag is a classification. There is no issue in your package. 549N: 550C: ksensors-trinity source: debian-build-system cdbs-with-debhelper.mk 551N: 552N: This is the build system that Lintian believes the package is using. 553N: 554N: Severity: classification 555N: 556N: Check: debhelper 557N: 558N: This tag is a classification. There is no issue in your package. 559N: 560C: ksensors-trinity: maintainer-script-interpreter control/postinst /bin/sh 561N: 562N: Interpreter used in maintainer script or ELF 563N: 564N: Severity: classification 565N: 566N: Check: scripts 567N: 568N: This tag is a classification. There is no issue in your package. 569N: 570C: ksensors-trinity: maintainer-script-interpreter control/postrm /bin/sh 571C: ksensors-trinity source: package-is-maintained-by-individual 572N: 573N: The package is maintained by an individual according to the 574N: maintainer/uploaders fields in the debian/control file. 575N: 576N: Severity: classification 577N: 578N: Check: fields/vcs 579N: 580N: This tag is a classification. There is no issue in your package. 581N: 582C: ksensors-trinity: package-is-maintained-by-individual 583C: ksensors-trinity source: patch-system quilt 584N: 585N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 586N: 587N: Severity: classification 588N: 589N: Check: patch-systems 590N: 591N: This tag is a classification. There is no issue in your package. 592N: 593C: ksensors-trinity source: source-format 3.0 (quilt) 594N: 595N: This is the source format declared in the package. 596N: 597N: Severity: classification 598N: 599N: Check: debian/source-dir 600N: 601N: This tag is a classification. There is no issue in your package. 602N: 603C: ksensors-trinity source: standards-version 3.8.3 604N: 605N: The standards version of the package according to Standards-Version 606N: field in the debian/control file. 607N: 608N: Severity: classification 609N: 610N: Check: fields/standards-version 611N: 612N: This tag is a classification. There is no issue in your package. 613N: 614 615--------------------