#263448: lintian: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7

Result: Failure

Fail on: error

Lintian output

Summary of tags

error: 89
warning: 8
info: 6
pedantic: 22
experimental: 2
overridden: 0
classification: 69

Tags

ksensors-trinity_14.2.0~pre33-0debian12.0.0+7_amd64.deb

E dir-or-file-in-opt

Lintian did not output a note for this tag [opt/trinity/]
Lintian did not output a note for this tag [opt/trinity/bin/]
Lintian did not output a note for this tag [opt/trinity/bin/ksensors]
Lintian did not output a note for this tag [opt/trinity/share/]
Lintian did not output a note for this tag [opt/trinity/share/applications/]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/]
Lintian did not output a note for this tag [opt/trinity/share/applications/tde/ksensors.desktop]
Lintian did not output a note for this tag [opt/trinity/share/apps/]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/ksensorsui.rc]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/battery.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/battery18x18.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/computers.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/cooler.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/cooler18x18.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/earth.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/harddisk.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/ksensorsbackground.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/ksensorsdocked.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/ksensorssplash.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/motherboard.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/thermometer.png]
Lintian did not output a note for this tag [opt/trinity/share/apps/ksensors/pics/thermometer18x18.png]
Lintian did not output a note for this tag [opt/trinity/share/autostart/]
Lintian did not output a note for this tag [opt/trinity/share/autostart/ksensors.desktop]
Lintian did not output a note for this tag [opt/trinity/share/doc/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/ksensors/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/ksensors/common]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/ksensors/index.cache.bz2]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/ksensors/index.docbook]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/]
Lintian did not output a note for this tag [opt/trinity/share/icons/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/16x16/apps/ksensors.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/32x32/apps/ksensors.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/hicolor/]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/16x16/]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/16x16/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/16x16/apps/ksensors.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/32x32/]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/32x32/apps/]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/32x32/apps/ksensors.png]
Lintian did not output a note for this tag [opt/trinity/share/icons/locolor/]
Lintian did not output a note for this tag [opt/trinity/share/locale/]
Lintian did not output a note for this tag [opt/trinity/share/locale/cs/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/cs/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/cs/]
Lintian did not output a note for this tag [opt/trinity/share/locale/de/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/de/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/de/]
Lintian did not output a note for this tag [opt/trinity/share/locale/es/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/es/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/es/]
Lintian did not output a note for this tag [opt/trinity/share/locale/fr/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/fr/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/fr/]
Lintian did not output a note for this tag [opt/trinity/share/locale/ka/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/ka/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/ka/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nb/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nb/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/nb/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/]
Lintian did not output a note for this tag [opt/trinity/share/locale/pl/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/pl/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/pl/]
Lintian did not output a note for this tag [opt/trinity/share/locale/ru/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/ru/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/ru/]
Lintian did not output a note for this tag [opt/trinity/share/locale/sv/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/sv/LC_MESSAGES/ksensors.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/sv/]
Lintian did not output a note for this tag [opt/trinity/share/man/]
Lintian did not output a note for this tag [opt/trinity/share/man/man1/]
Lintian did not output a note for this tag [opt/trinity/share/man/man1/ksensors.1]
Lintian did not output a note for this tag [opt/trinity/share/pixmaps/]
Lintian did not output a note for this tag [opt/trinity/share/pixmaps/ksensors.xpm]
Lintian did not output a note for this tag [opt/trinity/share/sounds/]
Lintian did not output a note for this tag [opt/trinity/share/sounds/ksensors_alert.wav]

W hardening-no-relro

This package provides an ELF binary that lacks the "read-only relocation"
link flag. This package was likely not built with the default Debian
compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags
directly, be sure to import LDFLAGS.

Please refer to https://wiki.debian.org/Hardening for details.

Visibility: warning
Show-Always: no
Check: binaries/hardening

Lintian did not output a note for this tag [opt/trinity/bin/ksensors]

W unknown-section

The "Section:" field in this package's control file is not one of the
sections in use on the ftp archive. Valid sections are currently admin,
comm, cli-mono, database, debug, devel, doc, editors, electronics,
embedded, fonts, games, gnome, gnu-r, gnustep, graphics, hamradio,
haskell, httpd, interpreters, java, javascript, kde, libdevel, libs, lisp,
localization, kernel, mail, math, misc, net, news, ocaml, oldlibs,
otherosfs, perl, php, python, ruby, rust, science, shells, sound, tex,
text, utils, vcs, video, web, x11, xfce, zope.

The section name should be preceded by either "contrib/", "non-free/" or
"non-free-firmware/" if the package is in the according archive area.

Please refer to Sections (Section 2.4) in the Debian Policy Manual for
details.

Visibility: warning
Show-Always: no
Check: fields/section

I hardening-no-bindnow

This package provides an ELF binary that lacks the "bindnow" linker flag.

This is needed (together with "relro") to make the "Global Offset Table"
(GOT) fully read-only. The bindnow feature trades startup time for
improved security. Please consider enabling this feature or consider
overriding the tag (possibly with a comment about why).

If you use dpkg-buildflags, you may have to add hardening=+bindnow or
hardening=+all to DEB_BUILD_MAINT_OPTIONS.

The relevant compiler flags are set in LDFLAGS.

Please refer to https://wiki.debian.org/Hardening for details.

Visibility: info
Show-Always: no
Check: binaries/hardening

Lintian did not output a note for this tag [opt/trinity/bin/ksensors]

I hardening-no-fortify-functions

This package provides an ELF binary that lacks the use of fortified libc
functions. Either there are no potentially unfortified functions called by
any routines, all unfortified calls have already been fully validated at
compile-time, or the package was not built with the default Debian
compiler flags defined by dpkg-buildflags. If built using dpkg-buildflags
directly, be sure to import CPPFLAGS.

NB: Due to false-positives, Lintian ignores some unprotected functions
(e.g. memcpy).

Please refer to https://wiki.debian.org/Hardening and Bug#673112 for
details.

Visibility: info
Show-Always: no
Check: binaries/hardening

Lintian did not output a note for this tag [opt/trinity/bin/ksensors]

C control-tarball-compression-format

C ctrl-script

Lintian did not output a note for this tag [postinst]
Lintian did not output a note for this tag [postrm]

C data-tarball-compression-format

C debhelper-autoscript-in-maintainer-scripts

The maintainer scripts of the package contain one or more auto-generated
shell snippets inserted by the listed debhelper tool.

Visibility: classification
Show-Always: no
Check: maintainer-scripts/generated
This tag is a classification. There is no issue in your package.

dh_installmenu/13.11.4

C mail-contact

This person is a contact in the named group for this package.

Visibility: classification
Show-Always: no
Check: fields/mail-address
Renamed from: maintainer uploader
This tag is a classification. There is no issue in your package.

Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org>

C maintainer-script-interpreter

/bin/sh [postinst]
/bin/sh [postrm]

C package-is-maintained-by-individual

The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.

Visibility: classification
Show-Always: no
Check: fields/vcs
This tag is a classification. There is no issue in your package.

Lintian did not output a note for this tag

C trimmed-field

Architecture amd64
Depends libc6 (>= 2.34), libgcc-s1 (>= 3.0), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5), libtqt3-mt (>= 4:14.2.0~pre279), tdelibs14-trinity (>= 4:14.2.0~pre294), lm-sensors
Description lm-sensors frontend for TDE
This is a lm-sensors frontend for TDE for monitoring a motherboard.
It allows you to access information from temperature and fan speed
sensors.
.
You will need lm-sensors kernel modules to use this package.
Installed-Size 741
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package ksensors-trinity
Priority optional
Recommends hddtemp (>= 0.3beta2-1)
Section tde
Version 4:14.2.0~pre33-0debian12.0.0+7

ksensors-trinity-dbgsym_14.2.0~pre33-0debian12.0.0+7_amd64.deb

C control-tarball-compression-format

C data-tarball-compression-format

C mail-contact

This person is a contact in the named group for this package.

Visibility: classification
Show-Always: no
Check: fields/mail-address
Renamed from: maintainer uploader
This tag is a classification. There is no issue in your package.

Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org>

C no-ctrl-scripts

The package does not rely on any maintainer scripts (or other executable
control files).

Visibility: classification
Show-Always: no
Check: control-files
This tag is a classification. There is no issue in your package.

Lintian did not output a note for this tag

C package-is-maintained-by-individual

The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.

Visibility: classification
Show-Always: no
Check: fields/vcs
This tag is a classification. There is no issue in your package.

Lintian did not output a note for this tag

C trimmed-field

Architecture amd64
Auto-Built-Package debug-symbols
Build-Ids c4294577aca884e07d3fa9cdb0a9b3b775561ff2
Depends ksensors-trinity (= 4:14.2.0~pre33-0debian12.0.0+7)
Description debug symbols for ksensors-trinity
Installed-Size 1772
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package ksensors-trinity-dbgsym
Priority optional
Section debug
Source ksensors-trinity
Version 4:14.2.0~pre33-0debian12.0.0+7

ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.dsc

E epoch-changed-but-upstream-version-did-not-go-backwards

The previous version of this package had a different version epoch to the
current version but the upstream version did not go "backwards". For
example, the previous package version was "1:1.0-1" and the current
version is "2:2.0-1".

This was likely an accidental bump or addition of an epoch.

Epochs exist to cope with changes to the upstream version numbering
scheme. Whilst they are a powerful tool, increasing or adding an epoch has
many downsides including causing issues with versioned dependencies, being
misleading to users and being aesthetically unappealing. Whilst they
should be avoided, valid reasons to add or increment the epoch include:

- Upstream changed their versioning scheme in a way that makes the
latest version lower than the previous one.
- You need to permanently revert to a lower upstream version.

Temporary revertions (eg. after an NMU) should use not modify or introduce
an epoch - please use the CURRENT+reallyFORMER until you can upload the
latest version again.

If you are unsure whether you need to increase the epoch for a package,
please consult the debian-devel mailing list.

Visibility: error
Show-Always: no
Check: debian/changelog

0.7.3-18 -> 4:14.2.0~pre33-0debian12.0.0+7 [debian/changelog:1]

E rules-require-build-prerequisite

(does not satisfy cdbs:any) [debian/rules]

W binary-nmu-debian-revision-in-source

The version number of your source package ends in +b and a number or has a
Debian revision containing three parts. These version numbers are used by
binary NMUs and should not be used as the source version. (The +b form is
the current standard; the three-part version number now obsolete.)

Please refer to Recompilation or binary-only NMU (Section 5.10.2.1) in the
Debian Developer's Reference for details.

Visibility: warning
Show-Always: no
Check: fields/version

4:14.2.0~pre33-0debian12.0.0+7
Comment:

The code in debian/rules requires a prerequisite
that is not presently listed in the package's Build-Depends.

In the special case of Python, affected packages should Build-Depend on
one of python3, python3-all, python3-dev, or python3-all-dev. Which one
depends on whether a package supports multiple Python versions, and also
whether the package builds Python modules or uses Python only as part of
the build process.

Packages that depend on a specific Python version may build-depend on any
appropriate pythonX.Y or pythonX.Y-dev package instead.

The condition you see in the context is not a recommendation on what to
add. If you see a list, more than likely only one member is needed to make
this tag go away. You probably also do not need the :any multiarch
qualifier, if you see one.

Please refer to Package relationships (Section 4.2) in the Debian Policy
Manual for details.

Visibility: error
Show-Always: no
Check: debian/rules
Renamed from: missing-build-dependency missing-python-build-dependency

W custom-compression-in-debian-source-options

compression = "xz" [debian/source/options:2]
compression-level = 9 [debian/source/options:3]

W epoch-change-without-comment

The previous version of this package had a different version epoch (eg.
2:1.0-1) to the current version but there's no reference to this in the
changelog entry.

Epochs exist to cope with changes to the upstream version numbering
scheme. Whilst they are a powerful tool, increasing or adding an epoch has
many downsides including causing issues with versioned dependencies, being
misleading to users and being aesthetically unappealing. Whilst they
should be avoided, valid reasons to add or increment the epoch include:

- Upstream changed their versioning scheme in a way that makes the
latest version lower than the previous one.
- You need to permanently revert to a lower upstream version.

Temporary revertions (eg. after an NMU) should use not modify or introduce
an epoch - please use the CURRENT+reallyFORMER until you can upload the
latest version again.

If you are unsure whether you need to increase the epoch for a package,
please consult the debian-devel mailing list.

Lintian looks in this version's changelog entry for the phrase "epoch".

Visibility: warning
Show-Always: no
Check: debian/changelog

0.7.3-18 -> 4:14.2.0~pre33-0debian12.0.0+7 [debian/changelog:1]

W no-nmu-in-changelog

When you NMU a package, that fact should be mentioned on the first line in
the changelog entry. Use the words "NMU" or "Non-maintainer upload" (case
insensitive).

Maybe you didn't intend this upload to be a NMU, in that case, please
double-check that the most recent entry in the changelog is byte-for-byte
identical to the maintainer or one of the uploaders. If this is a local
package (not intended for Debian), you can suppress this warning by
putting "local" in the version number or "local package" on the first line
of the changelog entry.

Please refer to Using the DELAYED/ queue (Section 5.11.3) in the Debian
Developer's Reference for details.

Visibility: warning
Show-Always: no
Check: nmu
Renamed from: changelog-should-mention-nmu

Lintian did not output a note for this tag [debian/changelog:1]

W source-nmu-has-incorrect-version-number

A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a
native package). This is to prevent stealing version numbers from the
maintainer.

Maybe you didn't intend this upload to be a NMU, in that case, please
double-check that the most recent entry in the changelog is byte-for-byte
identical to the maintainer or one of the uploaders. If this is a local
package (not intended for Debian), you can suppress this warning by
putting "local" in the version number or "local package" on the first line
of the changelog entry.

Please refer to NMUs and debian/changelog (Section 5.11.2) in the Debian
Developer's Reference for details.

Visibility: warning
Show-Always: no
Check: nmu

4:14.2.0~pre33-0debian12.0.0+7 [debian/changelog:1]

I debian-watch-file-is-missing

This source package is not Debian-native but it does not have a
debian/watch file. This file is used for automatic detection of new
upstream versions by the Debian External Health Status project and other
project infrastructure. If this package is maintained upstream, please
consider adding a debian/watch file to detect new releases.

If the package is not maintained upstream or if upstream uses a
distribution mechanism that cannot be meaningfully monitored by uscan and
the Debian External Health Status project, please consider adding a
debian/watch file containing only comments documenting the situation.

Please refer to Upstream source location: debian/watch (Section 4.11) in
the Debian Policy Manual and the uscan(1) manual page for details.

Visibility: info
Show-Always: no
Check: debian/watch

Lintian did not output a note for this tag

I no-dh-sequencer

This package does not use the dh sequencer in debian/rules.

While maintainers may use a variety of build systems, this one is by far
the most popular.

Maintainers are strongly encouraged to use the dh sequencer in new
packages and convert existing ones when appropriate.

Visibility: info
Show-Always: no
Check: debian/rules/dh-sequencer

Lintian did not output a note for this tag [debian/rules]

I ored-build-depends-on-obsolete-package

The package build-depends on an ORed group of packages which includes a
package that has been superseded.

Visibility: info
Show-Always: no
Check: fields/package-relations

Build-Depends: libsensors4-dev => libsensors-dev

I out-of-date-standards-version

The source package refers to a Standards-Version older than the one that
was current at the time the package was created (according to the
timestamp of the latest debian/changelog entry). Please consider updating
the package to current Policy and setting this control field
appropriately.

If the package is already compliant with the current standards, you don't
have to re-upload the package just to adjust the Standards-Version control
field. However, please remember to update this field next time you upload
the package.

See /usr/share/doc/debian-policy/upgrading-checklist.txt.gz in the
debian-policy package for a summary of changes in newer versions of
Policy.

Please refer to
https://www.debian.org/doc/debian-policy/upgrading-checklist.html for
details.

Visibility: info
Show-Always: no
Check: fields/standards-version

3.8.3 (released 2009-08-16) (current is 4.6.2)

P no-dep5-copyright

This package does not use a machine-readable debian/copyright file.

This format makes it easier to review licenses and can be easily parsed by
Lintian.

Please refer to
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for
details.

Visibility: pedantic
Show-Always: no
Check: debian/copyright/dep5

Lintian did not output a note for this tag [debian/copyright]

P no-homepage-field

This non-native package lacks a Homepage field. If the package has an
upstream home page that contains useful information or resources for the
end user, consider adding a Homepage control field to debian/control.

Please refer to Homepage (Section 5.6.23) in the Debian Policy Manual for
details.

Visibility: pedantic
Show-Always: no
Check: fields/homepage

Lintian did not output a note for this tag

P package-uses-old-debhelper-compat-version

This package uses a debhelper compatibility level that is no longer
recommended. Please consider using the recommended level.

For most packages, the best way to set the compatibility level is to
specify debhelper-compat (= X) as a Build-Depends in debian/control. You
can also use the debian/compat file or export DH_COMPAT in debian/rules.

If no level is selected debhelper defaults to level 1, which is
deprecated.

Please refer to the debhelper(7) manual page for details.

Visibility: pedantic
Show-Always: no
Check: debhelper

P silent-on-rules-requiring-root

The field Rules-Requires-Root is missing from the file debian/control.

Over time, Debian has successively narrowed the steps for which elevated
privileges are required. It speeds up the building of installation
packages in the archive. Eventually, Debian will switch the default
archive-wide behaviour to expedite the build process further.

Please declare explicitly that the sources do not require root privileges.
You can use the setting Rules-Requires-Root: no in the source stanza of
debian/control, but please verify with diffoscope(1) that the installation
packages produced are in fact identical.

Please refer to usr/share/doc/dpkg/rootless-builds.txt.gz, debian/rules
and Rules-Requires-Root (Section 4.9.2) in the Debian Policy Manual, and
Rules-Requires-Root (Section 5.6.31) in the Debian Policy Manual for
details.

Visibility: pedantic
Show-Always: no
Check: debian/control/field/rules-requires-root
Renamed from: rules-requires-root-missing

Lintian did not output a note for this tag [debian/control]

P trailing-whitespace

Lintian did not output a note for this tag [debian/changelog:108]
Lintian did not output a note for this tag [debian/changelog:131]
Lintian did not output a note for this tag [debian/changelog:132]
Lintian did not output a note for this tag [debian/changelog:153]
Lintian did not output a note for this tag [debian/changelog:161]
Lintian did not output a note for this tag [debian/changelog:17]
Lintian did not output a note for this tag [debian/changelog:189]
Lintian did not output a note for this tag [debian/changelog:211]
Lintian did not output a note for this tag [debian/changelog:280]
Lintian did not output a note for this tag [debian/changelog:293]
Lintian did not output a note for this tag [debian/changelog:315]
Lintian did not output a note for this tag [debian/changelog:320]
Lintian did not output a note for this tag [debian/changelog:388]
Lintian did not output a note for this tag [debian/changelog:400]
Lintian did not output a note for this tag [debian/changelog:406]
Lintian did not output a note for this tag [debian/changelog:418]
Lintian did not output a note for this tag [debian/changelog:43]
Lintian did not output a note for this tag [debian/changelog:77]

X upstream-metadata-file-is-missing

This source package is not Debian-native but it does not have a
debian/upstream/metadata file.

The Upstream MEtadata GAthered with YAml (UMEGAYA) project is an effort to
collect meta-information about upstream projects from any source package.
This file is in YAML format and it is used in to feed the data in the
UltimateDebianDatabase. For example, it can contains the way the authors
want their software be cited in publications and some bibliographic
references about the software.

Please add a debian/upstream/metadata file.

Please refer to https://dep-team.pages.debian.net/deps/dep12/ and
https://wiki.debian.org/UpstreamMetadata for details.

Visibility: pedantic
Show-Always: no
Check: debian/upstream/metadata
This tag is experimental.

Lintian did not output a note for this tag

X very-long-line-length-in-source-file

The source file includes a line length that is well beyond the normally
human made code line length.

This very long line length does not allow Lintian to do correctly some
source file checks.

This line could also be the result of some text injected by a computer
program, and thus could lead to FTBFS bugs.

Last but not least, long line in source code could be used to obfuscate
the source code and to hide stuff like backdoors or security problems.

It could be due to jslint source comments or other build tool comments.

You may report this issue upstream.

Visibility: pedantic
Show-Always: no
Check: files/contents/line-length
Renamed from: insane-line-length-in-source-file
This tag is experimental.

Screen: autotools/long-lines
Advocates: "Russ Allbery" <rra@debian.org>
Reason:
Upstream sources using autoconf have traditionally been
distributed with generated ./configure scripts as well as
other third-party m4 macro files such as libtool.

When paired with automake, there may also be some intermediate
Makefile.in files.

A lot of sources potentially contain such files, but they are
not actionable by either the Debian distributor or by the
upstream maintainer.

As a side note, modern Debian build protocols will re-create
many of those files via dh_autoreconf. They are present merely
to aid in bootstrapping systems where the GNU suite may not yet
be available.

Read more in Bug#996740.

1830 > 512 [src/aboutcfgdesign.ui:1405]

C debhelper-compat-level

This is the debhelper compat level used specified by this package.

Visibility: classification
Show-Always: no
Check: debhelper
This tag is a classification. There is no issue in your package.

C debian-build-system

This is the build system that Lintian believes the package is using.

Visibility: classification
Show-Always: no
Check: debhelper
This tag is a classification. There is no issue in your package.

cdbs-with-debhelper.mk [debian/rules]

C mail-contact

This person is a contact in the named group for this package.

Visibility: classification
Show-Always: no
Check: fields/mail-address
Renamed from: maintainer uploader
This tag is a classification. There is no issue in your package.

Maintainer "TDE Debian Team" <team-debian@trinitydesktop.org>

C number-of-patches

The number of patches according to the debian/patches/series file.

Visibility: classification
Show-Always: no
Check: debian/patches/count
This tag is a classification. There is no issue in your package.

0 [debian/patches/series]

C package-is-maintained-by-individual

The package is maintained by an individual according to the
maintainer/uploaders fields in the debian/control file.

Visibility: classification
Show-Always: no
Check: fields/vcs
This tag is a classification. There is no issue in your package.

Lintian did not output a note for this tag

C patch-system

This package uses the specified patch system (eg. "quilt" or "dpatch").

Visibility: classification
Show-Always: no
Check: debian/patches
This tag is a classification. There is no issue in your package.

quilt

C source-format

This is the source format declared in the package.

Visibility: classification
Show-Always: no
Check: debian/source-dir
This tag is a classification. There is no issue in your package.

3.0 (quilt)

C standards-version

The standards version of the package according to Standards-Version field
in the debian/control file.

Visibility: classification
Show-Always: no
Check: fields/standards-version
This tag is a classification. There is no issue in your package.

3.8.3

C trimmed-deb822-field

§1 Build-Conflicts autoconf2.13 [debian/control:6]
§1 Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, libsensors-dev | libsensors4-dev, tdelibs14-trinity-dev, imagemagick [debian/control:5]
§1 Maintainer TDE Debian Team <team-debian@trinitydesktop.org> [debian/control:4]
§1 Priority optional [debian/control:3]
§1 Section tde [debian/control:2]
§1 Source ksensors-trinity [debian/control:1]
§1 Standards-Version 3.8.3 [debian/control:7]
§2 Architecture any [debian/control:10]
§2 Depends ${shlibs:Depends}, ${misc:Depends}, lm-sensors [debian/control:11]
§2 Description lm-sensors frontend for TDE
This is a lm-sensors frontend for TDE for monitoring a motherboard.
It allows you to access information from temperature and fan speed
sensors.
.
You will need lm-sensors kernel modules to use this package. [debian/control:13]
§2 Package ksensors-trinity [debian/control:9]
§2 Recommends hddtemp (>= 0.3beta2-1) [debian/control:12]

C trimmed-field

Architecture any
Binary ksensors-trinity
Build-Conflicts autoconf2.13
Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, libsensors-dev | libsensors4-dev, tdelibs14-trinity-dev, imagemagick
Checksums-Sha1 70871e1a157af198f64e0e657a3f76687050977f 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz
257e278791754bf92d553873a59753f9d585ff1d 4884 ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.debian.tar.xz
Checksums-Sha256 e1bfc84f6fca83c13547511e9e50f713f4885fe1915c1de366c636eb3f990160 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz
c7e0a7608f8e766174f25c9bcb5f07a6479dcd7e7a8ae2b18f471484d0f7f7f5 4884 ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.debian.tar.xz
Files 0fddf341cc1ee455f60926144b4ed912 231836 ksensors-trinity_14.2.0~pre33.orig.tar.xz
5bf681ca63903bb461e736e66340ed59 4884 ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.debian.tar.xz
Format 3.0 (quilt)
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package-List ksensors-trinity deb tde optional arch=any
Source ksensors-trinity
Standards-Version 3.8.3
Version 4:14.2.0~pre33-0debian12.0.0+7

Description

Lintian run for ksensors-trinity package.

Additional details:

Source packages: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7
Binary packages: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7
Executed in environment system.tar.xz
Fail on severity: error
Build architecture: amd64
Target distribution: debian:bookworm
Include tags: none
Exclude tags: none

Input artifacts

Type Alphabetical order Reverse alphabetical order	Name
Source package	ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7
System tar	system.tar.xz
Package upload	ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7

Workflow information

⬆️ debian_pipeline ( Aborted )
⬆️ QA ( Aborted )
⬆️ lintian ( Aborted )

Output artifacts

Type Alphabetical order Reverse alphabetical order	Name
Debug log	debusine:work-request-debug-logs
Lintian report	lintian: ksensors-trinity, ksensors-trinity-dbgsym
Lintian report	lintian: ksensors-trinity

Output data

Runtime statistics:
- Duration: 00:00:54
- CPU time: 00:01:37
- Disk space: 916.6 MB
- Memory: 2.5 GB
- Available disk space: 31.4 GB
- Available memory: 62.8 GB
- CPU count: 32
Errors:

Dependencies

Work requests that must be completed before this one can run.

ID Lowest first Highest first	Created Oldest first Newest first	Task type Alphabetical order Reverse alphabetical order	Task Alphabetical order Reverse alphabetical order	Status Alphabetical order Reverse alphabetical order	Result Alphabetical order Reverse alphabetical order
260946	3 days, 2 hours	Worker	sbuild: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7 (amd64)	Completed	Success

Reverse dependencies

This work request is not required by any other one.

Internal collection: workflow-260939

Task data

backend: unshare
build_architecture: amd64
environment: debian/match:codename=bookworm
exclude_tags: []
fail_on_severity: error
include_tags: []
input:
  binary_artifacts:
  - internal@collections/name:build-amd64
  source_artifact: 819004@artifacts
output: {}
target_distribution: debian:bookworm

Task data after applying task configuration

backend: unshare
build_architecture: amd64
environment: debian/match:codename=bookworm
exclude_tags: []
fail_on_severity: error
include_tags: []
input:
  binary_artifacts:
  - internal@collections/name:build-amd64
  source_artifact: 819004@artifacts
output: {}
target_distribution: debian:bookworm
task_configuration: 1021

Scheduler tags

provided:
- task:group:debusine::Admins
- task:group:debusine::TDE-Owners
- task:scope:debusine
- task:source-package:ksensors-trinity
- task:workspace:debusine:trinity-testing
required:
- worker:executor:unshare
- worker:task:worker:lintian:version:1
- worker:type:external

Dynamic data

configuration_context: bookworm
environment_id: 27526
input_binary_artifacts_ids:
- 829027
input_source_artifact_id: 819004
parameter_summary: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7
runtime_context: binary-all+binary-any+source:bookworm
subject: ksensors-trinity

Workflow data

{
  "step": "lintian-amd64",
  "retry_count": 1,
  "display_name": "Lintian for amd64+all+source"
}

Event reactions

{
  "on_success": [
    {
      "action": "update-collection-with-artifacts",
      "variables": null,
      "collection": "internal@collections",
      "name_template": "lintian-amd64",
      "artifact_filters": {
        "category": "debian:lintian"
      }
    }
  ]
}

Output data

{
  "runtime_statistics": {
    "memory": 2635317248,
    "cpu_time": 97,
    "duration": 54,
    "cpu_count": 32,
    "disk_space": 961093632,
    "available_memory": 67418435584,
    "available_disk_space": 33709219840
  }
}

lintian: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7… 260990… 260939… Completed Failure trinity-testing… SlavekB 2 days, 17 hours ago garm… 5 hours, 21 minutes 0 minutes 3 weeks, 6 days

#263448: lintian: ksensors-trinity_4:14.2.0~pre33-0debian12.0.0+7

Summary of tags

Tags

ksensors-trinity_14.2.0~pre33-0debian12.0.0+7_amd64.deb

E dir-or-file-in-opt

W hardening-no-relro

Explanation

W unknown-section

Explanation

I hardening-no-bindnow

Explanation

I hardening-no-fortify-functions

Explanation

C control-tarball-compression-format

C ctrl-script

C data-tarball-compression-format

C debhelper-autoscript-in-maintainer-scripts

Explanation

C mail-contact

Explanation

C maintainer-script-interpreter

C package-is-maintained-by-individual

Explanation

C trimmed-field

ksensors-trinity-dbgsym_14.2.0~pre33-0debian12.0.0+7_amd64.deb

C control-tarball-compression-format

C data-tarball-compression-format

C mail-contact

Explanation

C no-ctrl-scripts

Explanation

C package-is-maintained-by-individual

Explanation

C trimmed-field

ksensors-trinity_14.2.0~pre33-0debian12.0.0+7.dsc

E epoch-changed-but-upstream-version-did-not-go-backwards

Explanation

E rules-require-build-prerequisite

W binary-nmu-debian-revision-in-source

Explanation

W custom-compression-in-debian-source-options

W epoch-change-without-comment

Explanation

W no-nmu-in-changelog

Explanation

W source-nmu-has-incorrect-version-number

Explanation

I debian-watch-file-is-missing

Explanation

I no-dh-sequencer

Explanation

I ored-build-depends-on-obsolete-package

Explanation

I out-of-date-standards-version

Explanation

P no-dep5-copyright

Explanation

P no-homepage-field

Explanation

P package-uses-old-debhelper-compat-version

Explanation

P silent-on-rules-requiring-root

Explanation

P trailing-whitespace

X upstream-metadata-file-is-missing

Explanation

X very-long-line-length-in-source-file

Explanation

C debhelper-compat-level

Explanation

C debian-build-system

Explanation

C mail-contact

Explanation

C number-of-patches

Explanation

C package-is-maintained-by-individual

Explanation

C patch-system

Explanation