1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-8cqo4mdl/ksensors-trinity_14.2.0~pre33-0raspbian12.0.0+7.dsc' '/tmp/debusine-fetch-exec-upload-8cqo4mdl/ksensors-trinity-dbgsym_14.2.0~pre33-0raspbian12.0.0+7_armhf.deb' '/tmp/debusine-fetch-exec-upload-8cqo4mdl/ksensors-trinity_14.2.0~pre33-0raspbian12.0.0+7_armhf.deb' 2output (contains stderr only, stdout was captured): 3 4Files in working directory: 5lintian.txt 6-------------------- 7N: 8E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/] 9N: 10N: Debian packages should not install into /opt, because it is reserved for 11N: add-on software. 12N: 13N: Please refer to /opt : Add-on application software packages (Section 3.13) 14N: in the Filesystem Hierarchy Standard for details. 15N: 16N: Visibility: error 17N: Show-Always: no 18N: Check: files/hierarchy/standard 19N: 20N: 21E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/bin/] 22N: 23E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/bin/ksensors] 24N: 25E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/] 26N: 27E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/applications/] 28N: 29E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/applications/tde/] 30N: 31E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/applications/tde/ksensors.desktop] 32N: 33E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/] 34N: 35E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/] 36N: 37E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/ksensorsui.rc] 38N: 39E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/] 40N: 41E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/battery.png] 42N: 43E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/battery18x18.png] 44N: 45E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/computers.png] 46N: 47E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/cooler.png] 48N: 49E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/cooler18x18.png] 50N: 51E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/earth.png] 52N: 53E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/harddisk.png] 54N: 55E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/ksensorsbackground.png] 56N: 57E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/ksensorsdocked.png] 58N: 59E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/ksensorssplash.png] 60N: 61E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/motherboard.png] 62N: 63E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/thermometer.png] 64N: 65E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/apps/ksensors/pics/thermometer18x18.png] 66N: 67E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/autostart/] 68N: 69E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/autostart/ksensors.desktop] 70N: 71E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/] 72N: 73E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/HTML/] 74N: 75E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/HTML/en/] 76N: 77E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/HTML/en/ksensors/] 78N: 79E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/HTML/en/ksensors/common] 80N: 81E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/HTML/en/ksensors/index.cache.bz2] 82N: 83E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/HTML/en/ksensors/index.docbook] 84N: 85E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/doc/tde/] 86N: 87E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/] 88N: 89E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/16x16/] 90N: 91E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/16x16/apps/] 92N: 93E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/16x16/apps/ksensors.png] 94N: 95E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/32x32/] 96N: 97E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/32x32/apps/] 98N: 99E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/32x32/apps/ksensors.png] 100N: 101E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/hicolor/] 102N: 103E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/16x16/] 104N: 105E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/16x16/apps/] 106N: 107E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/16x16/apps/ksensors.png] 108N: 109E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/32x32/] 110N: 111E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/32x32/apps/] 112N: 113E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/32x32/apps/ksensors.png] 114N: 115E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/icons/locolor/] 116N: 117E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/] 118N: 119E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/cs/LC_MESSAGES/] 120N: 121E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/cs/LC_MESSAGES/ksensors.mo] 122N: 123E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/cs/] 124N: 125E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/de/LC_MESSAGES/] 126N: 127E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/de/LC_MESSAGES/ksensors.mo] 128N: 129E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/de/] 130N: 131E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/es/LC_MESSAGES/] 132N: 133E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/es/LC_MESSAGES/ksensors.mo] 134N: 135E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/es/] 136N: 137E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/fr/LC_MESSAGES/] 138N: 139E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/fr/LC_MESSAGES/ksensors.mo] 140N: 141E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/fr/] 142N: 143E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/ka/LC_MESSAGES/] 144N: 145E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/ka/LC_MESSAGES/ksensors.mo] 146N: 147E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/ka/] 148N: 149E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/nb/LC_MESSAGES/] 150N: 151E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/nb/LC_MESSAGES/ksensors.mo] 152N: 153E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/nb/] 154N: 155E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/nl/LC_MESSAGES/] 156N: 157E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/nl/LC_MESSAGES/ksensors.mo] 158N: 159E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/nl/] 160N: 161E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/pl/LC_MESSAGES/] 162N: 163E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/pl/LC_MESSAGES/ksensors.mo] 164N: 165E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/pl/] 166N: 167E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/ru/LC_MESSAGES/] 168N: 169E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/ru/LC_MESSAGES/ksensors.mo] 170N: 171E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/ru/] 172N: 173E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/sv/LC_MESSAGES/] 174N: 175E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/sv/LC_MESSAGES/ksensors.mo] 176N: 177E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/locale/sv/] 178N: 179E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/man/] 180N: 181E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/man/man1/] 182N: 183E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/man/man1/ksensors.1] 184N: 185E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/pixmaps/] 186N: 187E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/pixmaps/ksensors.xpm] 188N: 189E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/sounds/] 190N: 191E: ksensors-trinity: dir-or-file-in-opt [opt/trinity/share/sounds/ksensors_alert.wav] 192N: 193E: ksensors-trinity source: epoch-changed-but-upstream-version-did-not-go-backwards 0.7.3-18 -> 4:14.2.0~pre33-0raspbian12.0.0+7 [debian/changelog:1] 194N: 195N: The previous version of this package had a different version epoch to the 196N: current version but the upstream version did not go "backwards". For 197N: example, the previous package version was "1:1.0-1" and the current 198N: version is "2:2.0-1". 199N: 200N: This was likely an accidental bump or addition of an epoch. 201N: 202N: Epochs exist to cope with changes to the upstream version numbering 203N: scheme. Whilst they are a powerful tool, increasing or adding an epoch has 204N: many downsides including causing issues with versioned dependencies, being 205N: misleading to users and being aesthetically unappealing. Whilst they 206N: should be avoided, valid reasons to add or increment the epoch include: 207N: 208N: - Upstream changed their versioning scheme in a way that makes the 209N: latest version lower than the previous one. 210N: - You need to permanently revert to a lower upstream version. 211N: 212N: Temporary revertions (eg. after an NMU) should use not modify or introduce 213N: an epoch - please use the CURRENT+reallyFORMER until you can upload the 214N: latest version again. 215N: 216N: If you are unsure whether you need to increase the epoch for a package, 217N: please consult the debian-devel mailing list. 218N: 219N: Visibility: error 220N: Show-Always: no 221N: Check: debian/changelog 222N: 223N: 224E: ksensors-trinity source: rules-require-build-prerequisite (does not satisfy cdbs:any) [debian/rules] 225N: 226N: 227N: The code in debian/rules requires a prerequisite 228N: that is not presently listed in the package's Build-Depends. 229N: 230N: In the special case of Python, affected packages should Build-Depend on 231N: one of python3, python3-all, python3-dev, or python3-all-dev. Which one 232N: depends on whether a package supports multiple Python versions, and also 233N: whether the package builds Python modules or uses Python only as part of 234N: the build process. 235N: 236N: Packages that depend on a specific Python version may build-depend on any 237N: appropriate pythonX.Y or pythonX.Y-dev package instead. 238N: 239N: The condition you see in the context is not a recommendation on what to 240N: add. If you see a list, more than likely only one member is needed to make 241N: this tag go away. You probably also do not need the :any multiarch 242N: qualifier, if you see one. 243N: 244N: Please refer to Package relationships (Section 4.2) in the Debian Policy 245N: Manual for details. 246N: 247N: Visibility: error 248N: Show-Always: no 249N: Check: debian/rules 250N: Renamed from: missing-build-dependency missing-python-build-dependency 251N: 252N: 253W: ksensors-trinity source: binary-nmu-debian-revision-in-source 4:14.2.0~pre33-0raspbian12.0.0+7 254N: 255N: The version number of your source package ends in +b and a number or has a 256N: Debian revision containing three parts. These version numbers are used by 257N: binary NMUs and should not be used as the source version. (The +b form is 258N: the current standard; the three-part version number now obsolete.) 259N: 260N: Please refer to Recompilation or binary-only NMU (Section 5.10.2.1) in the 261N: Debian Developer's Reference for details. 262N: 263N: Visibility: warning 264N: Show-Always: no 265N: Check: fields/version 266N: 267N: 268W: ksensors-trinity source: custom-compression-in-debian-source-options compression = "xz" [debian/source/options:2] 269N: 270N: This package selects a custom compression level or algorithm in 271N: debian/source/options. Please remove the call and let dpkg-deb(1) select 272N: suitable defaults. 273N: 274N: Custom compression settings are usually chosen for one of two reasons: 275N: 276N: Higher compression levels or more advanced algorithms shrink the sizes of 277N: large files, but they can cause problems in the resource constrained 278N: environments used in Debian's buildd infrastructure. For example, higher 279N: than expected memory consumption may trigger an FTBFS or a failure to 280N: install. 281N: 282N: Lower compression levels or less advanced algorithms are sometimes needed 283N: to support older Debian version. Unfortunately, they also make it harder 284N: to change the defaults on an archive-wide basis. 285N: 286N: Some legitimate use cases trigger this tag. Please override it. 287N: 288N: Please refer to Bug#829100, Bug#906614, Bug#909696, and the dpkg-deb(1) 289N: manual page for details. 290N: 291N: Visibility: warning 292N: Show-Always: no 293N: Check: debian/source-dir 294N: Renamed from: debian-source-options-has-custom-compression-settings 295N: 296N: 297W: ksensors-trinity source: custom-compression-in-debian-source-options compression-level = 9 [debian/source/options:3] 298N: 299W: ksensors-trinity source: epoch-change-without-comment 0.7.3-18 -> 4:14.2.0~pre33-0raspbian12.0.0+7 [debian/changelog:1] 300N: 301N: The previous version of this package had a different version epoch (eg. 302N: 2:1.0-1) to the current version but there's no reference to this in the 303N: changelog entry. 304N: 305N: Epochs exist to cope with changes to the upstream version numbering 306N: scheme. Whilst they are a powerful tool, increasing or adding an epoch has 307N: many downsides including causing issues with versioned dependencies, being 308N: misleading to users and being aesthetically unappealing. Whilst they 309N: should be avoided, valid reasons to add or increment the epoch include: 310N: 311N: - Upstream changed their versioning scheme in a way that makes the 312N: latest version lower than the previous one. 313N: - You need to permanently revert to a lower upstream version. 314N: 315N: Temporary revertions (eg. after an NMU) should use not modify or introduce 316N: an epoch - please use the CURRENT+reallyFORMER until you can upload the 317N: latest version again. 318N: 319N: If you are unsure whether you need to increase the epoch for a package, 320N: please consult the debian-devel mailing list. 321N: 322N: Lintian looks in this version's changelog entry for the phrase "epoch". 323N: 324N: Visibility: warning 325N: Show-Always: no 326N: Check: debian/changelog 327N: 328N: 329W: ksensors-trinity: hardening-no-pie [opt/trinity/bin/ksensors] 330N: 331N: This package provides an ELF executable that was not compiled as a 332N: position independent executable (PIE). 333N: 334N: In Debian, since version 6.2.0-7 of the gcc-6 package GCC will compile ELF 335N: binaries with PIE by default. In most cases a simple rebuild will be 336N: sufficient to remove this tag. 337N: 338N: PIE is required for fully enabling Address Space Layout Randomization 339N: (ASLR), which makes "Return-oriented" attacks more difficult. 340N: 341N: Historically, PIE has been associated with noticeable performance overhead 342N: on i386. However, GCC >= 5 has implemented an optimization that can reduce 343N: the overhead significantly. 344N: 345N: If you use dpkg-buildflags with hardening=+all,-pie in 346N: DEB_BUILD_MAINT_OPTIONS, remove the -pie. 347N: 348N: Please refer to https://wiki.debian.org/Hardening, 349N: https://gcc.gnu.org/gcc-5/changes.html, and 350N: https://software.intel.com/en-us/blogs/2014/12/26/new-optimizations-for-x86-in-upcoming-gcc-50-32bit-pic-mode 351N: for details. 352N: 353N: Visibility: warning 354N: Show-Always: no 355N: Check: binaries/hardening 356N: 357N: 358W: ksensors-trinity: hardening-no-relro [opt/trinity/bin/ksensors] 359N: 360N: This package provides an ELF binary that lacks the "read-only relocation" 361N: link flag. This package was likely not built with the default Debian 362N: compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags 363N: directly, be sure to import LDFLAGS. 364N: 365N: Please refer to https://wiki.debian.org/Hardening for details. 366N: 367N: Visibility: warning 368N: Show-Always: no 369N: Check: binaries/hardening 370N: 371N: 372W: ksensors-trinity source: no-nmu-in-changelog [debian/changelog:1] 373N: 374N: When you NMU a package, that fact should be mentioned on the first line in 375N: the changelog entry. Use the words "NMU" or "Non-maintainer upload" (case 376N: insensitive). 377N: 378N: Maybe you didn't intend this upload to be a NMU, in that case, please 379N: double-check that the most recent entry in the changelog is byte-for-byte 380N: identical to the maintainer or one of the uploaders. If this is a local 381N: package (not intended for Debian), you can suppress this warning by 382N: putting "local" in the version number or "local package" on the first line 383N: of the changelog entry. 384N: 385N: Please refer to Using the DELAYED/ queue (Section 5.11.3) in the Debian 386N: Developer's Reference for details. 387N: 388N: Visibility: warning 389N: Show-Always: no 390N: Check: nmu 391N: Renamed from: changelog-should-mention-nmu 392N: 393N: 394W: ksensors-trinity source: source-nmu-has-incorrect-version-number 4:14.2.0~pre33-0raspbian12.0.0+7 [debian/changelog:1] 395N: 396N: A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a 397N: native package). This is to prevent stealing version numbers from the 398N: maintainer. 399N: 400N: Maybe you didn't intend this upload to be a NMU, in that case, please 401N: double-check that the most recent entry in the changelog is byte-for-byte 402N: identical to the maintainer or one of the uploaders. If this is a local 403N: package (not intended for Debian), you can suppress this warning by 404N: putting "local" in the version number or "local package" on the first line 405N: of the changelog entry. 406N: 407N: Please refer to NMUs and debian/changelog (Section 5.11.2) in the Debian 408N: Developer's Reference for details. 409N: 410N: Visibility: warning 411N: Show-Always: no 412N: Check: nmu 413N: 414N: 415W: ksensors-trinity: unknown-section tde 416N: 417N: The "Section:" field in this package's control file is not one of the 418N: sections in use on the ftp archive. Valid sections are currently admin, 419N: comm, cli-mono, database, debug, devel, doc, editors, electronics, 420N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, 421N: haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, lisp, 422N: localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, 423N: otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex, 424N: text, utils, vcs, video, web, x11, xfce, zope. 425N: 426N: The section name should be preceded by either "contrib/", "non-free/" or 427N: "non-free-firmware/" if the package is in the according archive area. 428N: 429N: Please refer to Sections (Section 2.4) in the Debian Policy Manual for 430N: details. 431N: 432N: Visibility: warning 433N: Show-Always: no 434N: Check: fields/section 435N: 436N: 437I: ksensors-trinity source: debian-watch-file-is-missing 438N: 439N: This source package is not Debian-native but it does not have a 440N: debian/watch file. This file is used for automatic detection of new 441N: upstream versions by the Debian External Health Status project and other 442N: project infrastructure. If this package is maintained upstream, please 443N: consider adding a debian/watch file to detect new releases. 444N: 445N: If the package is not maintained upstream or if upstream uses a 446N: distribution mechanism that cannot be meaningfully monitored by uscan and 447N: the Debian External Health Status project, please consider adding a 448N: debian/watch file containing only comments documenting the situation. 449N: 450N: Please refer to Upstream source location: debian/watch (Section 4.11) in 451N: the Debian Policy Manual and the uscan(1) manual page for details. 452N: 453N: Visibility: info 454N: Show-Always: no 455N: Check: debian/watch 456N: 457N: 458I: ksensors-trinity: hardening-no-bindnow [opt/trinity/bin/ksensors] 459N: 460N: This package provides an ELF binary that lacks the "bindnow" linker flag. 461N: 462N: This is needed (together with "relro") to make the "Global Offset Table" 463N: (GOT) fully read-only. The bindnow feature trades startup time for 464N: improved security. Please consider enabling this feature or consider 465N: overriding the tag (possibly with a comment about why). 466N: 467N: If you use dpkg-buildflags, you may have to add hardening=+bindnow or 468N: hardening=+all to DEB_BUILD_MAINT_OPTIONS. 469N: 470N: The relevant compiler flags are set in LDFLAGS. 471N: 472N: Please refer to https://wiki.debian.org/Hardening for details. 473N: 474N: Visibility: info 475N: Show-Always: no 476N: Check: binaries/hardening 477N: 478N: 479I: ksensors-trinity: hardening-no-fortify-functions [opt/trinity/bin/ksensors] 480N: 481N: This package provides an ELF binary that lacks the use of fortified libc 482N: functions. Either there are no potentially unfortified functions called by 483N: any routines, all unfortified calls have already been fully validated at 484N: compile-time, or the package was not built with the default Debian 485N: compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags 486N: directly, be sure to import CPPFLAGS. 487N: 488N: NB: Due to false-positives, Lintian ignores some unprotected functions 489N: (e.g. memcpy). 490N: 491N: Please refer to https://wiki.debian.org/Hardening and Bug#673112 for 492N: details. 493N: 494N: Visibility: info 495N: Show-Always: no 496N: Check: binaries/hardening 497N: 498N: 499I: ksensors-trinity source: no-dh-sequencer [debian/rules] 500N: 501N: This package does not use the dh sequencer in debian/rules. 502N: 503N: While maintainers may use a variety of build systems, this one is by far 504N: the most popular. 505N: 506N: Maintainers are strongly encouraged to use the dh sequencer in new 507N: packages and convert existing ones when appropriate. 508N: 509N: Visibility: info 510N: Show-Always: no 511N: Check: debian/rules/dh-sequencer 512N: 513N: 514I: ksensors-trinity source: ored-build-depends-on-obsolete-package Build-Depends: libsensors4-dev => libsensors-dev 515N: 516N: The package build-depends on an ORed group of packages which includes a 517N: package that has been superseded. 518N: 519N: Visibility: info 520N: Show-Always: no 521N: Check: fields/package-relations 522N: 523N: 524I: ksensors-trinity source: out-of-date-standards-version 3.8.3 (released 2009-08-16) (current is 4.6.2) 525N: 526N: The source package refers to a Standards-Version older than the one that 527N: was current at the time the package was created (according to the 528N: timestamp of the latest debian/changelog entry). Please consider updating 529N: the package to current Policy and setting this control field 530N: appropriately. 531N: 532N: If the package is already compliant with the current standards, you don't 533N: have to re-upload the package just to adjust the Standards-Version control 534N: field. However, please remember to update this field next time you upload 535N: the package. 536N: 537N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 538N: debian-policy package for a summary of changes in newer versions of 539N: Policy. 540N: 541N: Please refer to 542N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 543N: details. 544N: 545N: Visibility: info 546N: Show-Always: no 547N: Check: fields/standards-version 548N: 549N: 550P: ksensors-trinity source: no-dep5-copyright [debian/copyright] 551N: 552N: This package does not use a machine-readable debian/copyright file. 553N: 554N: This format makes it easier to review licenses and can be easily parsed by 555N: Lintian. 556N: 557N: Please refer to 558N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 559N: details. 560N: 561N: Visibility: pedantic 562N: Show-Always: no 563N: Check: debian/copyright/dep5 564N: 565N: 566P: ksensors-trinity source: no-homepage-field 567N: 568N: This non-native package lacks a Homepage field. If the package has an 569N: upstream home page that contains useful information or resources for the 570N: end user, consider adding a Homepage control field to debian/control. 571N: 572N: Please refer to Homepage (Section 5.6.23) in the Debian Policy Manual for 573N: details. 574N: 575N: Visibility: pedantic 576N: Show-Always: no 577N: Check: fields/homepage 578N: 579N: 580P: ksensors-trinity source: package-uses-old-debhelper-compat-version 10 581N: 582N: This package uses a debhelper compatibility level that is no longer 583N: recommended. Please consider using the recommended level. 584N: 585N: For most packages, the best way to set the compatibility level is to 586N: specify debhelper-compat (= X) as a Build-Depends in debian/control. You 587N: can also use the debian/compat file or export DH_COMPAT in debian/rules. 588N: 589N: If no level is selected debhelper defaults to level 1, which is 590N: deprecated. 591N: 592N: Please refer to the debhelper(7) manual page for details. 593N: 594N: Visibility: pedantic 595N: Show-Always: no 596N: Check: debhelper 597N: 598N: 599P: ksensors-trinity source: silent-on-rules-requiring-root [debian/control] 600N: 601N: The field Rules-Requires-Root is missing from the file debian/control. 602N: 603N: Over time, Debian has successively narrowed the steps for which elevated 604N: privileges are required. It speeds up the building of installation 605N: packages in the archive. Eventually, Debian will switch the default 606N: archive-wide behaviour to expedite the build process further. 607N: 608N: Please declare explicitly that the sources do not require root privileges. 609N: You can use the setting Rules-Requires-Root: no in the source stanza of 610N: debian/control, but please verify with diffoscope(1) that the installation 611N: packages produced are in fact identical. 612N: 613N: Please refer to usr/share/doc/dpkg/rootless-builds.txt.gz, debian/rules 614N: and Rules-Requires-Root (Section 4.9.2) in the Debian Policy Manual, and 615N: Rules-Requires-Root (Section 5.6.31) in the Debian Policy Manual for 616N: details. 617N: 618N: Visibility: pedantic 619N: Show-Always: no 620N: Check: debian/control/field/rules-requires-root 621N: Renamed from: rules-requires-root-missing 622N: 623N: 624P: ksensors-trinity source: trailing-whitespace [debian/changelog:108] 625N: 626N: This file contains lines with trailing whitespace characters. 627N: 628N: Whilst often harmless and unsightly, such extra whitespaces can also cause 629N: tools to interpret the whitespace characters literally. The tool diff(1) 630N: does not like them, either. They are best avoided. 631N: 632N: Some of these problems can be hard to track down. 633N: 634N: Whitespace at the end of lines may be removed with the following: 635N: 636N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 637N: 638N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 639N: 640N: However, if you wish to only remove trailing spaces and leave trailing 641N: tabs (eg. for Makefiles), you can use the following code snippet: 642N: 643N: $ sed -i -e 's@[ ]*$@@g' debian/rules 644N: 645N: To remove empty lines from the end of a file, you can use: 646N: 647N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 648N: 649N: Visibility: pedantic 650N: Show-Always: no 651N: Check: debian/trailing-whitespace 652N: Renamed from: file-contains-trailing-whitespace 653N: 654N: 655P: ksensors-trinity source: trailing-whitespace [debian/changelog:131] 656N: 657P: ksensors-trinity source: trailing-whitespace [debian/changelog:132] 658N: 659P: ksensors-trinity source: trailing-whitespace [debian/changelog:153] 660N: 661P: ksensors-trinity source: trailing-whitespace [debian/changelog:161] 662N: 663P: ksensors-trinity source: trailing-whitespace [debian/changelog:17] 664N: 665P: ksensors-trinity source: trailing-whitespace [debian/changelog:189] 666N: 667P: ksensors-trinity source: trailing-whitespace [debian/changelog:211] 668N: 669P: ksensors-trinity source: trailing-whitespace [debian/changelog:280] 670N: 671P: ksensors-trinity source: trailing-whitespace [debian/changelog:293] 672N: 673P: ksensors-trinity source: trailing-whitespace [debian/changelog:315] 674N: 675P: ksensors-trinity source: trailing-whitespace [debian/changelog:320] 676N: 677P: ksensors-trinity source: trailing-whitespace [debian/changelog:388] 678N: 679P: ksensors-trinity source: trailing-whitespace [debian/changelog:400] 680N: 681P: ksensors-trinity source: trailing-whitespace [debian/changelog:406] 682N: 683P: ksensors-trinity source: trailing-whitespace [debian/changelog:418] 684N: 685P: ksensors-trinity source: trailing-whitespace [debian/changelog:43] 686N: 687P: ksensors-trinity source: trailing-whitespace [debian/changelog:77] 688N: 689X: ksensors-trinity source: upstream-metadata-file-is-missing 690N: 691N: This source package is not Debian-native but it does not have a 692N: debian/upstream/metadata file. 693N: 694N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to 695N: collect meta-information about upstream projects from any source package. 696N: This file is in YAML format and it is used in to feed the data in the 697N: UltimateDebianDatabase. For example, it can contains the way the authors 698N: want their software be cited in publications and some bibliographic 699N: references about the software. 700N: 701N: Please add a debian/upstream/metadata file. 702N: 703N: Please refer to https://dep-team.pages.debian.net/deps/dep12/ and 704N: https://wiki.debian.org/UpstreamMetadata for details. 705N: 706N: Visibility: pedantic 707N: Show-Always: no 708N: Check: debian/upstream/metadata 709N: This tag is experimental. 710N: 711N: 712X: ksensors-trinity source: very-long-line-length-in-source-file 1830 > 512 [src/aboutcfgdesign.ui:1405] 713N: 714N: The source file includes a line length that is well beyond the normally 715N: human made code line length. 716N: 717N: This very long line length does not allow Lintian to do correctly some 718N: source file checks. 719N: 720N: This line could also be the result of some text injected by a computer 721N: program, and thus could lead to FTBFS bugs. 722N: 723N: Last but not least, long line in source code could be used to obfuscate 724N: the source code and to hide stuff like backdoors or security problems. 725N: 726N: It could be due to jslint source comments or other build tool comments. 727N: 728N: You may report this issue upstream. 729N: 730N: Visibility: pedantic 731N: Show-Always: no 732N: Check: files/contents/line-length 733N: Renamed from: insane-line-length-in-source-file 734N: This tag is experimental. 735N: 736N: Screen: autotools/long-lines 737N: Advocates: "Russ Allbery" <rra@debian.org> 738N: Reason: 739N: Upstream sources using autoconf have traditionally been 740N: distributed with generated ./configure scripts as well as 741N: other third-party m4 macro files such as libtool. 742N: 743N: When paired with automake, there may also be some intermediate 744N: Makefile.in files. 745N: 746N: A lot of sources potentially contain such files, but they are 747N: not actionable by either the Debian distributor or by the 748N: upstream maintainer. 749N: 750N: As a side note, modern Debian build protocols will re-create 751N: many of those files via dh_autoreconf. They are present merely 752N: to aid in bootstrapping systems where the GNU suite may not yet 753N: be available. 754N: 755N: Read more in Bug#996740. 756N: 757N: 758C: ksensors-trinity: control-tarball-compression-format xz 759N: 760N: This is the compressor format used for the control.tar tarball. 761N: 762N: Visibility: classification 763N: Show-Always: no 764N: Check: deb-format 765N: This tag is a classification. There is no issue in your package. 766N: 767N: 768C: ksensors-trinity-dbgsym: control-tarball-compression-format xz 769N: 770C: ksensors-trinity: ctrl-script [postinst] 771N: 772N: This package has one or more maintainer scripts (or other executable 773N: control files). 774N: 775N: This flags any control file with the executable bit set. 776N: 777N: Visibility: classification 778N: Show-Always: no 779N: Check: control-files 780N: This tag is a classification. There is no issue in your package. 781N: 782N: 783C: ksensors-trinity: ctrl-script [postrm] 784N: 785C: ksensors-trinity: data-tarball-compression-format xz 786N: 787N: This is the compressor format used for the data.tar tarball. 788N: 789N: Visibility: classification 790N: Show-Always: no 791N: Check: deb-format 792N: This tag is a classification. There is no issue in your package. 793N: 794N: 795C: ksensors-trinity-dbgsym: data-tarball-compression-format xz 796N: 797C: ksensors-trinity: debhelper-autoscript-in-maintainer-scripts dh_installmenu/13.11.4 798N: 799N: The maintainer scripts of the package contain one or more auto-generated 800N: shell snippets inserted by the listed debhelper tool. 801N: 802N: Visibility: classification 803N: Show-Always: no 804N: Check: maintainer-scripts/generated 805N: This tag is a classification. There is no issue in your package. 806N: 807N: 808C: ksensors-trinity source: debhelper-compat-level 10 809N: 810N: This is the debhelper compat level used specified by this package. 811N: 812N: Visibility: classification 813N: Show-Always: no 814N: Check: debhelper 815N: This tag is a classification. There is no issue in your package. 816N: 817N: 818C: ksensors-trinity source: debian-build-system cdbs-with-debhelper.mk [debian/rules] 819N: 820N: This is the build system that Lintian believes the package is using. 821N: 822N: Visibility: classification 823N: Show-Always: no 824N: Check: debhelper 825N: This tag is a classification. There is no issue in your package. 826N: 827N: 828C: ksensors-trinity source: mail-contact Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org> 829N: 830N: This person is a contact in the named group for this package. 831N: 832N: Visibility: classification 833N: Show-Always: no 834N: Check: fields/mail-address 835N: Renamed from: maintainer uploader 836N: This tag is a classification. There is no issue in your package. 837N: 838N: 839C: ksensors-trinity: mail-contact Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org> 840N: 841C: ksensors-trinity-dbgsym: mail-contact Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org> 842N: 843C: ksensors-trinity: maintainer-script-interpreter /bin/sh [postinst] 844N: 845N: Interpreter used in maintainer script or ELF 846N: 847N: Visibility: classification 848N: Show-Always: no 849N: Check: scripts 850N: This tag is a classification. There is no issue in your package. 851N: 852N: 853C: ksensors-trinity: maintainer-script-interpreter /bin/sh [postrm] 854N: 855C: ksensors-trinity-dbgsym: no-ctrl-scripts 856N: 857N: The package does not rely on any maintainer scripts (or other executable 858N: control files). 859N: 860N: Visibility: classification 861N: Show-Always: no 862N: Check: control-files 863N: This tag is a classification. There is no issue in your package. 864N: 865N: 866C: ksensors-trinity source: number-of-patches 0 [debian/patches/series] 867N: 868N: The number of patches according to the debian/patches/series file. 869N: 870N: Visibility: classification 871N: Show-Always: no 872N: Check: debian/patches/count 873N: This tag is a classification. There is no issue in your package. 874N: 875N: 876C: ksensors-trinity source: package-is-maintained-by-individual 877N: 878N: The package is maintained by an individual according to the 879N: maintainer/uploaders fields in the debian/control file. 880N: 881N: Visibility: classification 882N: Show-Always: no 883N: Check: fields/vcs 884N: This tag is a classification. There is no issue in your package. 885N: 886N: 887C: ksensors-trinity: package-is-maintained-by-individual 888N: 889C: ksensors-trinity-dbgsym: package-is-maintained-by-individual 890N: 891C: ksensors-trinity source: patch-system quilt 892N: 893N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 894N: 895N: Visibility: classification 896N: Show-Always: no 897N: Check: debian/patches 898N: This tag is a classification. There is no issue in your package. 899N: 900N: 901C: ksensors-trinity source: source-format 3.0 (quilt) 902N: 903N: This is the source format declared in the package. 904N: 905N: Visibility: classification 906N: Show-Always: no 907N: Check: debian/source-dir 908N: This tag is a classification. There is no issue in your package. 909N: 910N: 911C: ksensors-trinity source: standards-version 3.8.3 912N: 913N: The standards version of the package according to Standards-Version field 914N: in the debian/control file. 915N: 916N: Visibility: classification 917N: Show-Always: no 918N: Check: fields/standards-version 919N: This tag is a classification. There is no issue in your package. 920N: 921N: 922C: ksensors-trinity source: trimmed-deb822-field §1 Build-Conflicts autoconf2.13 [debian/control:6] 923N: 924N: The raw but trimmed contents of the named field in the given Deb822 file. 925N: The number indicates the section from the top, starting at 1. 926N: 927N: Visibility: classification 928N: Show-Always: no 929N: Check: fields/deb822 930N: This tag is a classification. There is no issue in your package. 931N: 932N: 933C: ksensors-trinity source: trimmed-deb822-field §1 Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, libsensors-dev | libsensors4-dev, tdelibs14-trinity-dev, imagemagick [debian/control:5] 934N: 935C: ksensors-trinity source: trimmed-deb822-field §1 Maintainer TDE Debian Team <team-debian@trinitydesktop.org> [debian/control:4] 936N: 937C: ksensors-trinity source: trimmed-deb822-field §1 Priority optional [debian/control:3] 938N: 939C: ksensors-trinity source: trimmed-deb822-field §1 Section tde [debian/control:2] 940N: 941C: ksensors-trinity source: trimmed-deb822-field §1 Source ksensors-trinity [debian/control:1] 942N: 943C: ksensors-trinity source: trimmed-deb822-field §1 Standards-Version 3.8.3 [debian/control:7] 944N: 945C: ksensors-trinity source: trimmed-deb822-field §2 Architecture any [debian/control:10] 946N: 947C: ksensors-trinity source: trimmed-deb822-field §2 Depends ${shlibs:Depends}, ${misc:Depends}, lm-sensors [debian/control:11] 948N: 949C: ksensors-trinity source: trimmed-deb822-field §2 Description lm-sensors frontend for TDE\n This is a lm-sensors frontend for TDE for monitoring a motherboard.\n It allows you to access information from temperature and fan speed\n sensors.\n .\n You will need lm-sensors kernel modules to use this package. [debian/control:13] 950N: 951C: ksensors-trinity source: trimmed-deb822-field §2 Package ksensors-trinity [debian/control:9] 952N: 953C: ksensors-trinity source: trimmed-deb822-field §2 Recommends hddtemp (>= 0.3beta2-1) [debian/control:12] 954N: 955C: ksensors-trinity source: trimmed-field Architecture any 956N: 957N: These are the raw but trimmed contents of the named field in the package's 958N: primary control file. 959N: 960N: Visibility: classification 961N: Show-Always: no 962N: Check: fields/trimmed 963N: This tag is a classification. There is no issue in your package. 964N: 965N: 966C: ksensors-trinity source: trimmed-field Binary ksensors-trinity 967N: 968C: ksensors-trinity source: trimmed-field Build-Conflicts autoconf2.13 969N: 970C: ksensors-trinity source: trimmed-field Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, libsensors-dev | libsensors4-dev, tdelibs14-trinity-dev, imagemagick 971N: 972C: ksensors-trinity source: trimmed-field Checksums-Sha1 70871e1a157af198f64e0e657a3f76687050977f 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz\n 4d3f2fa4f5e8392f748f8a804b5cf0bd2edc90bb 4892 ksensors-trinity_14.2.0~pre33-0raspbian12.0.0+7.debian.tar.xz 973N: 974C: ksensors-trinity source: trimmed-field Checksums-Sha256 e1bfc84f6fca83c13547511e9e50f713f4885fe1915c1de366c636eb3f990160 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz\n d3c02078f811aea3ce3cf06782b76655db6f70c2076fa3096fd3397a442337f3 4892 ksensors-trinity_14.2.0~pre33-0raspbian12.0.0+7.debian.tar.xz 975N: 976C: ksensors-trinity source: trimmed-field Files 0fddf341cc1ee455f60926144b4ed912 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz\n b2c68d285b4e53bc23221fe32d8738ef 4892 ksensors-trinity_14.2.0~pre33-0raspbian12.0.0+7.debian.tar.xz 977N: 978C: ksensors-trinity source: trimmed-field Format 3.0 (quilt) 979N: 980C: ksensors-trinity source: trimmed-field Maintainer TDE Debian Team <team-debian@trinitydesktop.org> 981N: 982C: ksensors-trinity source: trimmed-field Package-List ksensors-trinity deb tde optional arch=any 983N: 984C: ksensors-trinity source: trimmed-field Source ksensors-trinity 985N: 986C: ksensors-trinity source: trimmed-field Standards-Version 3.8.3 987N: 988C: ksensors-trinity source: trimmed-field Version 4:14.2.0~pre33-0raspbian12.0.0+7 989N: 990C: ksensors-trinity: trimmed-field Architecture armhf 991N: 992C: ksensors-trinity: trimmed-field Depends libc6 (>= 2.34), libgcc-s1 (>= 3.5), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5), libtqt3-mt (>= 4:14.2.0~pre279), tdelibs14-trinity (>= 4:14.2.0~pre294), lm-sensors 993N: 994C: ksensors-trinity: trimmed-field Description lm-sensors frontend for TDE\n This is a lm-sensors frontend for TDE for monitoring a motherboard.\n It allows you to access information from temperature and fan speed\n sensors.\n .\n You will need lm-sensors kernel modules to use this package. 995N: 996C: ksensors-trinity: trimmed-field Installed-Size 576 997N: 998C: ksensors-trinity: trimmed-field Maintainer TDE Debian Team <team-debian@trinitydesktop.org> 999N: 1000C: ksensors-trinity: trimmed-field Package ksensors-trinity 1001N: 1002C: ksensors-trinity: trimmed-field Priority optional 1003N: 1004C: ksensors-trinity: trimmed-field Recommends hddtemp (>= 0.3beta2-1) 1005N: 1006C: ksensors-trinity: trimmed-field Section tde 1007N: 1008C: ksensors-trinity: trimmed-field Version 4:14.2.0~pre33-0raspbian12.0.0+7 1009N: 1010C: ksensors-trinity-dbgsym: trimmed-field Architecture armhf 1011N: 1012C: ksensors-trinity-dbgsym: trimmed-field Auto-Built-Package debug-symbols 1013N: 1014C: ksensors-trinity-dbgsym: trimmed-field Build-Ids c5ea33f547b954ce99a339a2767c6430218e308e 1015N: 1016C: ksensors-trinity-dbgsym: trimmed-field Depends ksensors-trinity (= 4:14.2.0~pre33-0raspbian12.0.0+7) 1017N: 1018C: ksensors-trinity-dbgsym: trimmed-field Description debug symbols for ksensors-trinity 1019N: 1020C: ksensors-trinity-dbgsym: trimmed-field Installed-Size 1732 1021N: 1022C: ksensors-trinity-dbgsym: trimmed-field Maintainer TDE Debian Team <team-debian@trinitydesktop.org> 1023N: 1024C: ksensors-trinity-dbgsym: trimmed-field Package ksensors-trinity-dbgsym 1025N: 1026C: ksensors-trinity-dbgsym: trimmed-field Priority optional 1027N: 1028C: ksensors-trinity-dbgsym: trimmed-field Section debug 1029N: 1030C: ksensors-trinity-dbgsym: trimmed-field Source ksensors-trinity 1031N: 1032C: ksensors-trinity-dbgsym: trimmed-field Version 4:14.2.0~pre33-0raspbian12.0.0+7 1033 1034--------------------