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