1cmd: lintian --no-cfg --display-level '>=classification' --display-experimental --info --show-overrides '/tmp/debusine-fetch-exec-upload-vb28gqz8/ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.dsc' '/tmp/debusine-fetch-exec-upload-vb28gqz8/ksensors-trinity-dbgsym_14.2.0~pre33-0debian12.0.0+7_ppc64el.deb' '/tmp/debusine-fetch-exec-upload-vb28gqz8/ksensors-trinity_14.2.0~pre33-0debian12.0.0+7_ppc64el.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-0debian12.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-0debian12.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-0debian12.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-relro [opt/trinity/bin/ksensors] 330N: 331N: This package provides an ELF binary that lacks the "read-only relocation" 332N: link flag. This package was likely not built with the default Debian 333N: compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags 334N: directly, be sure to import LDFLAGS. 335N: 336N: Please refer to https://wiki.debian.org/Hardening for details. 337N: 338N: Visibility: warning 339N: Show-Always: no 340N: Check: binaries/hardening 341N: 342N: 343W: ksensors-trinity source: no-nmu-in-changelog [debian/changelog:1] 344N: 345N: When you NMU a package, that fact should be mentioned on the first line in 346N: the changelog entry. Use the words "NMU" or "Non-maintainer upload" (case 347N: insensitive). 348N: 349N: Maybe you didn't intend this upload to be a NMU, in that case, please 350N: double-check that the most recent entry in the changelog is byte-for-byte 351N: identical to the maintainer or one of the uploaders. If this is a local 352N: package (not intended for Debian), you can suppress this warning by 353N: putting "local" in the version number or "local package" on the first line 354N: of the changelog entry. 355N: 356N: Please refer to Using the DELAYED/ queue (Section 5.11.3) in the Debian 357N: Developer's Reference for details. 358N: 359N: Visibility: warning 360N: Show-Always: no 361N: Check: nmu 362N: Renamed from: changelog-should-mention-nmu 363N: 364N: 365W: ksensors-trinity source: source-nmu-has-incorrect-version-number 4:14.2.0~pre33-0debian12.0.0+7 [debian/changelog:1] 366N: 367N: A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a 368N: native package). This is to prevent stealing version numbers from the 369N: maintainer. 370N: 371N: Maybe you didn't intend this upload to be a NMU, in that case, please 372N: double-check that the most recent entry in the changelog is byte-for-byte 373N: identical to the maintainer or one of the uploaders. If this is a local 374N: package (not intended for Debian), you can suppress this warning by 375N: putting "local" in the version number or "local package" on the first line 376N: of the changelog entry. 377N: 378N: Please refer to NMUs and debian/changelog (Section 5.11.2) in the Debian 379N: Developer's Reference for details. 380N: 381N: Visibility: warning 382N: Show-Always: no 383N: Check: nmu 384N: 385N: 386W: ksensors-trinity: unknown-section tde 387N: 388N: The "Section:" field in this package's control file is not one of the 389N: sections in use on the ftp archive. Valid sections are currently admin, 390N: comm, cli-mono, database, debug, devel, doc, editors, electronics, 391N: embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio, 392N: haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, lisp, 393N: localization, kernel, mail, math, misc, net, news, ocaml, oldlibs, 394N: otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex, 395N: text, utils, vcs, video, web, x11, xfce, zope. 396N: 397N: The section name should be preceded by either "contrib/", "non-free/" or 398N: "non-free-firmware/" if the package is in the according archive area. 399N: 400N: Please refer to Sections (Section 2.4) in the Debian Policy Manual for 401N: details. 402N: 403N: Visibility: warning 404N: Show-Always: no 405N: Check: fields/section 406N: 407N: 408I: ksensors-trinity source: debian-watch-file-is-missing 409N: 410N: This source package is not Debian-native but it does not have a 411N: debian/watch file. This file is used for automatic detection of new 412N: upstream versions by the Debian External Health Status project and other 413N: project infrastructure. If this package is maintained upstream, please 414N: consider adding a debian/watch file to detect new releases. 415N: 416N: If the package is not maintained upstream or if upstream uses a 417N: distribution mechanism that cannot be meaningfully monitored by uscan and 418N: the Debian External Health Status project, please consider adding a 419N: debian/watch file containing only comments documenting the situation. 420N: 421N: Please refer to Upstream source location: debian/watch (Section 4.11) in 422N: the Debian Policy Manual and the uscan(1) manual page for details. 423N: 424N: Visibility: info 425N: Show-Always: no 426N: Check: debian/watch 427N: 428N: 429I: ksensors-trinity: hardening-no-bindnow [opt/trinity/bin/ksensors] 430N: 431N: This package provides an ELF binary that lacks the "bindnow" linker flag. 432N: 433N: This is needed (together with "relro") to make the "Global Offset Table" 434N: (GOT) fully read-only. The bindnow feature trades startup time for 435N: improved security. Please consider enabling this feature or consider 436N: overriding the tag (possibly with a comment about why). 437N: 438N: If you use dpkg-buildflags, you may have to add hardening=+bindnow or 439N: hardening=+all to DEB_BUILD_MAINT_OPTIONS. 440N: 441N: The relevant compiler flags are set in LDFLAGS. 442N: 443N: Please refer to https://wiki.debian.org/Hardening for details. 444N: 445N: Visibility: info 446N: Show-Always: no 447N: Check: binaries/hardening 448N: 449N: 450I: ksensors-trinity: hardening-no-fortify-functions [opt/trinity/bin/ksensors] 451N: 452N: This package provides an ELF binary that lacks the use of fortified libc 453N: functions. Either there are no potentially unfortified functions called by 454N: any routines, all unfortified calls have already been fully validated at 455N: compile-time, or the package was not built with the default Debian 456N: compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags 457N: directly, be sure to import CPPFLAGS. 458N: 459N: NB: Due to false-positives, Lintian ignores some unprotected functions 460N: (e.g. memcpy). 461N: 462N: Please refer to https://wiki.debian.org/Hardening and Bug#673112 for 463N: details. 464N: 465N: Visibility: info 466N: Show-Always: no 467N: Check: binaries/hardening 468N: 469N: 470I: ksensors-trinity source: no-dh-sequencer [debian/rules] 471N: 472N: This package does not use the dh sequencer in debian/rules. 473N: 474N: While maintainers may use a variety of build systems, this one is by far 475N: the most popular. 476N: 477N: Maintainers are strongly encouraged to use the dh sequencer in new 478N: packages and convert existing ones when appropriate. 479N: 480N: Visibility: info 481N: Show-Always: no 482N: Check: debian/rules/dh-sequencer 483N: 484N: 485I: ksensors-trinity source: ored-build-depends-on-obsolete-package Build-Depends: libsensors4-dev => libsensors-dev 486N: 487N: The package build-depends on an ORed group of packages which includes a 488N: package that has been superseded. 489N: 490N: Visibility: info 491N: Show-Always: no 492N: Check: fields/package-relations 493N: 494N: 495I: ksensors-trinity source: out-of-date-standards-version 3.8.3 (released 2009-08-16) (current is 4.6.2) 496N: 497N: The source package refers to a Standards-Version older than the one that 498N: was current at the time the package was created (according to the 499N: timestamp of the latest debian/changelog entry). Please consider updating 500N: the package to current Policy and setting this control field 501N: appropriately. 502N: 503N: If the package is already compliant with the current standards, you don't 504N: have to re-upload the package just to adjust the Standards-Version control 505N: field. However, please remember to update this field next time you upload 506N: the package. 507N: 508N: See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the 509N: debian-policy package for a summary of changes in newer versions of 510N: Policy. 511N: 512N: Please refer to 513N: https://www.debian.org/doc/debian-policy/upgrading-checklist.html for 514N: details. 515N: 516N: Visibility: info 517N: Show-Always: no 518N: Check: fields/standards-version 519N: 520N: 521P: ksensors-trinity source: no-dep5-copyright [debian/copyright] 522N: 523N: This package does not use a machine-readable debian/copyright file. 524N: 525N: This format makes it easier to review licenses and can be easily parsed by 526N: Lintian. 527N: 528N: Please refer to 529N: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for 530N: details. 531N: 532N: Visibility: pedantic 533N: Show-Always: no 534N: Check: debian/copyright/dep5 535N: 536N: 537P: ksensors-trinity source: no-homepage-field 538N: 539N: This non-native package lacks a Homepage field. If the package has an 540N: upstream home page that contains useful information or resources for the 541N: end user, consider adding a Homepage control field to debian/control. 542N: 543N: Please refer to Homepage (Section 5.6.23) in the Debian Policy Manual for 544N: details. 545N: 546N: Visibility: pedantic 547N: Show-Always: no 548N: Check: fields/homepage 549N: 550N: 551P: ksensors-trinity source: package-uses-old-debhelper-compat-version 10 552N: 553N: This package uses a debhelper compatibility level that is no longer 554N: recommended. Please consider using the recommended level. 555N: 556N: For most packages, the best way to set the compatibility level is to 557N: specify debhelper-compat (= X) as a Build-Depends in debian/control. You 558N: can also use the debian/compat file or export DH_COMPAT in debian/rules. 559N: 560N: If no level is selected debhelper defaults to level 1, which is 561N: deprecated. 562N: 563N: Please refer to the debhelper(7) manual page for details. 564N: 565N: Visibility: pedantic 566N: Show-Always: no 567N: Check: debhelper 568N: 569N: 570P: ksensors-trinity source: silent-on-rules-requiring-root [debian/control] 571N: 572N: The field Rules-Requires-Root is missing from the file debian/control. 573N: 574N: Over time, Debian has successively narrowed the steps for which elevated 575N: privileges are required. It speeds up the building of installation 576N: packages in the archive. Eventually, Debian will switch the default 577N: archive-wide behaviour to expedite the build process further. 578N: 579N: Please declare explicitly that the sources do not require root privileges. 580N: You can use the setting Rules-Requires-Root: no in the source stanza of 581N: debian/control, but please verify with diffoscope(1) that the installation 582N: packages produced are in fact identical. 583N: 584N: Please refer to usr/share/doc/dpkg/rootless-builds.txt.gz, debian/rules 585N: and Rules-Requires-Root (Section 4.9.2) in the Debian Policy Manual, and 586N: Rules-Requires-Root (Section 5.6.31) in the Debian Policy Manual for 587N: details. 588N: 589N: Visibility: pedantic 590N: Show-Always: no 591N: Check: debian/control/field/rules-requires-root 592N: Renamed from: rules-requires-root-missing 593N: 594N: 595P: ksensors-trinity source: trailing-whitespace [debian/changelog:108] 596N: 597N: This file contains lines with trailing whitespace characters. 598N: 599N: Whilst often harmless and unsightly, such extra whitespaces can also cause 600N: tools to interpret the whitespace characters literally. The tool diff(1) 601N: does not like them, either. They are best avoided. 602N: 603N: Some of these problems can be hard to track down. 604N: 605N: Whitespace at the end of lines may be removed with the following: 606N: 607N: $ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog 608N: 609N: If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup). 610N: 611N: However, if you wish to only remove trailing spaces and leave trailing 612N: tabs (eg. for Makefiles), you can use the following code snippet: 613N: 614N: $ sed -i -e 's@[ ]*$@@g' debian/rules 615N: 616N: To remove empty lines from the end of a file, you can use: 617N: 618N: $ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules 619N: 620N: Visibility: pedantic 621N: Show-Always: no 622N: Check: debian/trailing-whitespace 623N: Renamed from: file-contains-trailing-whitespace 624N: 625N: 626P: ksensors-trinity source: trailing-whitespace [debian/changelog:131] 627N: 628P: ksensors-trinity source: trailing-whitespace [debian/changelog:132] 629N: 630P: ksensors-trinity source: trailing-whitespace [debian/changelog:153] 631N: 632P: ksensors-trinity source: trailing-whitespace [debian/changelog:161] 633N: 634P: ksensors-trinity source: trailing-whitespace [debian/changelog:17] 635N: 636P: ksensors-trinity source: trailing-whitespace [debian/changelog:189] 637N: 638P: ksensors-trinity source: trailing-whitespace [debian/changelog:211] 639N: 640P: ksensors-trinity source: trailing-whitespace [debian/changelog:280] 641N: 642P: ksensors-trinity source: trailing-whitespace [debian/changelog:293] 643N: 644P: ksensors-trinity source: trailing-whitespace [debian/changelog:315] 645N: 646P: ksensors-trinity source: trailing-whitespace [debian/changelog:320] 647N: 648P: ksensors-trinity source: trailing-whitespace [debian/changelog:388] 649N: 650P: ksensors-trinity source: trailing-whitespace [debian/changelog:400] 651N: 652P: ksensors-trinity source: trailing-whitespace [debian/changelog:406] 653N: 654P: ksensors-trinity source: trailing-whitespace [debian/changelog:418] 655N: 656P: ksensors-trinity source: trailing-whitespace [debian/changelog:43] 657N: 658P: ksensors-trinity source: trailing-whitespace [debian/changelog:77] 659N: 660X: ksensors-trinity source: upstream-metadata-file-is-missing 661N: 662N: This source package is not Debian-native but it does not have a 663N: debian/upstream/metadata file. 664N: 665N: The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to 666N: collect meta-information about upstream projects from any source package. 667N: This file is in YAML format and it is used in to feed the data in the 668N: UltimateDebianDatabase. For example, it can contains the way the authors 669N: want their software be cited in publications and some bibliographic 670N: references about the software. 671N: 672N: Please add a debian/upstream/metadata file. 673N: 674N: Please refer to https://dep-team.pages.debian.net/deps/dep12/ and 675N: https://wiki.debian.org/UpstreamMetadata for details. 676N: 677N: Visibility: pedantic 678N: Show-Always: no 679N: Check: debian/upstream/metadata 680N: This tag is experimental. 681N: 682N: 683X: ksensors-trinity source: very-long-line-length-in-source-file 1830 > 512 [src/aboutcfgdesign.ui:1405] 684N: 685N: The source file includes a line length that is well beyond the normally 686N: human made code line length. 687N: 688N: This very long line length does not allow Lintian to do correctly some 689N: source file checks. 690N: 691N: This line could also be the result of some text injected by a computer 692N: program, and thus could lead to FTBFS bugs. 693N: 694N: Last but not least, long line in source code could be used to obfuscate 695N: the source code and to hide stuff like backdoors or security problems. 696N: 697N: It could be due to jslint source comments or other build tool comments. 698N: 699N: You may report this issue upstream. 700N: 701N: Visibility: pedantic 702N: Show-Always: no 703N: Check: files/contents/line-length 704N: Renamed from: insane-line-length-in-source-file 705N: This tag is experimental. 706N: 707N: Screen: autotools/long-lines 708N: Advocates: "Russ Allbery" <rra@debian.org> 709N: Reason: 710N: Upstream sources using autoconf have traditionally been 711N: distributed with generated ./configure scripts as well as 712N: other third-party m4 macro files such as libtool. 713N: 714N: When paired with automake, there may also be some intermediate 715N: Makefile.in files. 716N: 717N: A lot of sources potentially contain such files, but they are 718N: not actionable by either the Debian distributor or by the 719N: upstream maintainer. 720N: 721N: As a side note, modern Debian build protocols will re-create 722N: many of those files via dh_autoreconf. They are present merely 723N: to aid in bootstrapping systems where the GNU suite may not yet 724N: be available. 725N: 726N: Read more in Bug#996740. 727N: 728N: 729C: ksensors-trinity: control-tarball-compression-format xz 730N: 731N: This is the compressor format used for the control.tar tarball. 732N: 733N: Visibility: classification 734N: Show-Always: no 735N: Check: deb-format 736N: This tag is a classification. There is no issue in your package. 737N: 738N: 739C: ksensors-trinity-dbgsym: control-tarball-compression-format xz 740N: 741C: ksensors-trinity: ctrl-script [postinst] 742N: 743N: This package has one or more maintainer scripts (or other executable 744N: control files). 745N: 746N: This flags any control file with the executable bit set. 747N: 748N: Visibility: classification 749N: Show-Always: no 750N: Check: control-files 751N: This tag is a classification. There is no issue in your package. 752N: 753N: 754C: ksensors-trinity: ctrl-script [postrm] 755N: 756C: ksensors-trinity: data-tarball-compression-format xz 757N: 758N: This is the compressor format used for the data.tar tarball. 759N: 760N: Visibility: classification 761N: Show-Always: no 762N: Check: deb-format 763N: This tag is a classification. There is no issue in your package. 764N: 765N: 766C: ksensors-trinity-dbgsym: data-tarball-compression-format xz 767N: 768C: ksensors-trinity: debhelper-autoscript-in-maintainer-scripts dh_installmenu/13.11.4 769N: 770N: The maintainer scripts of the package contain one or more auto-generated 771N: shell snippets inserted by the listed debhelper tool. 772N: 773N: Visibility: classification 774N: Show-Always: no 775N: Check: maintainer-scripts/generated 776N: This tag is a classification. There is no issue in your package. 777N: 778N: 779C: ksensors-trinity source: debhelper-compat-level 10 780N: 781N: This is the debhelper compat level used specified by this package. 782N: 783N: Visibility: classification 784N: Show-Always: no 785N: Check: debhelper 786N: This tag is a classification. There is no issue in your package. 787N: 788N: 789C: ksensors-trinity source: debian-build-system cdbs-with-debhelper.mk [debian/rules] 790N: 791N: This is the build system that Lintian believes the package is using. 792N: 793N: Visibility: classification 794N: Show-Always: no 795N: Check: debhelper 796N: This tag is a classification. There is no issue in your package. 797N: 798N: 799C: ksensors-trinity source: mail-contact Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org> 800N: 801N: This person is a contact in the named group for this package. 802N: 803N: Visibility: classification 804N: Show-Always: no 805N: Check: fields/mail-address 806N: Renamed from: maintainer uploader 807N: This tag is a classification. There is no issue in your package. 808N: 809N: 810C: ksensors-trinity: mail-contact Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org> 811N: 812C: ksensors-trinity-dbgsym: mail-contact Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org> 813N: 814C: ksensors-trinity: maintainer-script-interpreter /bin/sh [postinst] 815N: 816N: Interpreter used in maintainer script or ELF 817N: 818N: Visibility: classification 819N: Show-Always: no 820N: Check: scripts 821N: This tag is a classification. There is no issue in your package. 822N: 823N: 824C: ksensors-trinity: maintainer-script-interpreter /bin/sh [postrm] 825N: 826C: ksensors-trinity-dbgsym: no-ctrl-scripts 827N: 828N: The package does not rely on any maintainer scripts (or other executable 829N: control files). 830N: 831N: Visibility: classification 832N: Show-Always: no 833N: Check: control-files 834N: This tag is a classification. There is no issue in your package. 835N: 836N: 837C: ksensors-trinity source: number-of-patches 0 [debian/patches/series] 838N: 839N: The number of patches according to the debian/patches/series file. 840N: 841N: Visibility: classification 842N: Show-Always: no 843N: Check: debian/patches/count 844N: This tag is a classification. There is no issue in your package. 845N: 846N: 847C: ksensors-trinity source: package-is-maintained-by-individual 848N: 849N: The package is maintained by an individual according to the 850N: maintainer/uploaders fields in the debian/control file. 851N: 852N: Visibility: classification 853N: Show-Always: no 854N: Check: fields/vcs 855N: This tag is a classification. There is no issue in your package. 856N: 857N: 858C: ksensors-trinity: package-is-maintained-by-individual 859N: 860C: ksensors-trinity-dbgsym: package-is-maintained-by-individual 861N: 862C: ksensors-trinity source: patch-system quilt 863N: 864N: This package uses the specified patch system (eg. "quilt" or "dpatch"). 865N: 866N: Visibility: classification 867N: Show-Always: no 868N: Check: debian/patches 869N: This tag is a classification. There is no issue in your package. 870N: 871N: 872C: ksensors-trinity source: source-format 3.0 (quilt) 873N: 874N: This is the source format declared in the package. 875N: 876N: Visibility: classification 877N: Show-Always: no 878N: Check: debian/source-dir 879N: This tag is a classification. There is no issue in your package. 880N: 881N: 882C: ksensors-trinity source: standards-version 3.8.3 883N: 884N: The standards version of the package according to Standards-Version field 885N: in the debian/control file. 886N: 887N: Visibility: classification 888N: Show-Always: no 889N: Check: fields/standards-version 890N: This tag is a classification. There is no issue in your package. 891N: 892N: 893C: ksensors-trinity source: trimmed-deb822-field §1 Build-Conflicts autoconf2.13 [debian/control:6] 894N: 895N: The raw but trimmed contents of the named field in the given Deb822 file. 896N: The number indicates the section from the top, starting at 1. 897N: 898N: Visibility: classification 899N: Show-Always: no 900N: Check: fields/deb822 901N: This tag is a classification. There is no issue in your package. 902N: 903N: 904C: 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] 905N: 906C: ksensors-trinity source: trimmed-deb822-field §1 Maintainer TDE Debian Team <team-debian@trinitydesktop.org> [debian/control:4] 907N: 908C: ksensors-trinity source: trimmed-deb822-field §1 Priority optional [debian/control:3] 909N: 910C: ksensors-trinity source: trimmed-deb822-field §1 Section tde [debian/control:2] 911N: 912C: ksensors-trinity source: trimmed-deb822-field §1 Source ksensors-trinity [debian/control:1] 913N: 914C: ksensors-trinity source: trimmed-deb822-field §1 Standards-Version 3.8.3 [debian/control:7] 915N: 916C: ksensors-trinity source: trimmed-deb822-field §2 Architecture any [debian/control:10] 917N: 918C: ksensors-trinity source: trimmed-deb822-field §2 Depends ${shlibs:Depends}, ${misc:Depends}, lm-sensors [debian/control:11] 919N: 920C: 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] 921N: 922C: ksensors-trinity source: trimmed-deb822-field §2 Package ksensors-trinity [debian/control:9] 923N: 924C: ksensors-trinity source: trimmed-deb822-field §2 Recommends hddtemp (>= 0.3beta2-1) [debian/control:12] 925N: 926C: ksensors-trinity source: trimmed-field Architecture any 927N: 928N: These are the raw but trimmed contents of the named field in the package's 929N: primary control file. 930N: 931N: Visibility: classification 932N: Show-Always: no 933N: Check: fields/trimmed 934N: This tag is a classification. There is no issue in your package. 935N: 936N: 937C: ksensors-trinity source: trimmed-field Binary ksensors-trinity 938N: 939C: ksensors-trinity source: trimmed-field Build-Conflicts autoconf2.13 940N: 941C: ksensors-trinity source: trimmed-field Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, libsensors-dev | libsensors4-dev, tdelibs14-trinity-dev, imagemagick 942N: 943C: ksensors-trinity source: trimmed-field Checksums-Sha1 70871e1a157af198f64e0e657a3f76687050977f 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz\n 257e278791754bf92d553873a59753f9d585ff1d 4884 ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.debian.tar.xz 944N: 945C: ksensors-trinity source: trimmed-field Checksums-Sha256 e1bfc84f6fca83c13547511e9e50f713f4885fe1915c1de366c636eb3f990160 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz\n c7e0a7608f8e766174f25c9bcb5f07a6479dcd7e7a8ae2b18f471484d0f7f7f5 4884 ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.debian.tar.xz 946N: 947C: ksensors-trinity source: trimmed-field Files 0fddf341cc1ee455f60926144b4ed912 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz\n 5bf681ca63903bb461e736e66340ed59 4884 ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.debian.tar.xz 948N: 949C: ksensors-trinity source: trimmed-field Format 3.0 (quilt) 950N: 951C: ksensors-trinity source: trimmed-field Maintainer TDE Debian Team <team-debian@trinitydesktop.org> 952N: 953C: ksensors-trinity source: trimmed-field Package-List ksensors-trinity deb tde optional arch=any 954N: 955C: ksensors-trinity source: trimmed-field Source ksensors-trinity 956N: 957C: ksensors-trinity source: trimmed-field Standards-Version 3.8.3 958N: 959C: ksensors-trinity source: trimmed-field Version 4:14.2.0~pre33-0debian12.0.0+7 960N: 961C: ksensors-trinity: trimmed-field Architecture ppc64el 962N: 963C: ksensors-trinity: trimmed-field Depends libc6 (>= 2.34), libgcc-s1 (>= 3.0), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5), libtqt3-mt (>= 4:14.2.0~pre279), tdelibs14-trinity (>= 4:14.2.0~pre294), lm-sensors 964N: 965C: 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. 966N: 967C: ksensors-trinity: trimmed-field Installed-Size 829 968N: 969C: ksensors-trinity: trimmed-field Maintainer TDE Debian Team <team-debian@trinitydesktop.org> 970N: 971C: ksensors-trinity: trimmed-field Package ksensors-trinity 972N: 973C: ksensors-trinity: trimmed-field Priority optional 974N: 975C: ksensors-trinity: trimmed-field Recommends hddtemp (>= 0.3beta2-1) 976N: 977C: ksensors-trinity: trimmed-field Section tde 978N: 979C: ksensors-trinity: trimmed-field Version 4:14.2.0~pre33-0debian12.0.0+7 980N: 981C: ksensors-trinity-dbgsym: trimmed-field Architecture ppc64el 982N: 983C: ksensors-trinity-dbgsym: trimmed-field Auto-Built-Package debug-symbols 984N: 985C: ksensors-trinity-dbgsym: trimmed-field Build-Ids 6b6f02b7b2925ff380451ffaa2cd3954606ad6f4 986N: 987C: ksensors-trinity-dbgsym: trimmed-field Depends ksensors-trinity (= 4:14.2.0~pre33-0debian12.0.0+7) 988N: 989C: ksensors-trinity-dbgsym: trimmed-field Description debug symbols for ksensors-trinity 990N: 991C: ksensors-trinity-dbgsym: trimmed-field Installed-Size 1775 992N: 993C: ksensors-trinity-dbgsym: trimmed-field Maintainer TDE Debian Team <team-debian@trinitydesktop.org> 994N: 995C: ksensors-trinity-dbgsym: trimmed-field Package ksensors-trinity-dbgsym 996N: 997C: ksensors-trinity-dbgsym: trimmed-field Priority optional 998N: 999C: ksensors-trinity-dbgsym: trimmed-field Section debug 1000N: 1001C: ksensors-trinity-dbgsym: trimmed-field Source ksensors-trinity 1002N: 1003C: ksensors-trinity-dbgsym: trimmed-field Version 4:14.2.0~pre33-0debian12.0.0+7 1004 1005--------------------