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