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