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