#247930: lintian: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7

Result: Failure

Fail on: error

Lintian output

Summary of tags

error: 60
warning: 21
info: 7
pedantic: 28
experimental: 1
overridden: 0
classification: 78

Tags

gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.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/lib/]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/kcm_kcmgtk.la]
Lintian did not output a note for this tag [opt/trinity/lib/trinity/kcm_kcmgtk.so]
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/kcmgtk.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/kcontrol/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kcontrol/gtk/]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kcontrol/gtk/common]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kcontrol/gtk/index.cache.bz2]
Lintian did not output a note for this tag [opt/trinity/share/doc/tde/HTML/en/kcontrol/gtk/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/locale/]
Lintian did not output a note for this tag [opt/trinity/share/locale/bg/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/bg/LC_MESSAGES/gtk-qt-engine.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/bg/]
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/gtk-qt-engine.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/gtk-qt-engine.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/gtk-qt-engine.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/it/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/it/LC_MESSAGES/gtk-qt-engine.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/it/]
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/gtk-qt-engine.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/nl/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nl/LC_MESSAGES/gtk-qt-engine.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/nn/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/nn/LC_MESSAGES/gtk-qt-engine.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/nn/]
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/gtk-qt-engine.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/gtk-qt-engine.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/gtk-qt-engine.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/locale/tr/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/tr/LC_MESSAGES/gtk-qt-engine.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/tr/]
Lintian did not output a note for this tag [opt/trinity/share/locale/zh_Hans/LC_MESSAGES/]
Lintian did not output a note for this tag [opt/trinity/share/locale/zh_Hans/LC_MESSAGES/gtk-qt-engine.mo]
Lintian did not output a note for this tag [opt/trinity/share/locale/zh_Hans/]

W copyright-without-copyright-notice

Lintian did not output a note for this tag

W extended-description-line-too-long

line 6

W hardening-no-relro

Lintian did not output a note for this tag [opt/trinity/lib/trinity/kcm_kcmgtk.so]
Lintian did not output a note for this tag [usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libqtengine.so]

W package-has-unnecessary-activation-of-ldconfig-trigger

The package activates the ldconfig trigger even though no shared libraries
are installed in a directory controlled by the dynamic library loader.

Note this may be triggered by a bug in debhelper, that causes it to
auto-generate an ldconfig trigger for packages that do not need it.

Please refer to ldconfig (Section 8.1.1) in the Debian Policy Manual and
Bug#204975 for details.

Visibility: warning
Show-Always: no
Check: libraries/shared/trigger/ldconfig

Lintian did not output a note for this tag

W package-relation-with-self

The package declares a relationship with itself. This is not very useful
except in the case of a package Conflicting with itself if its package
name doubles as a virtual package.

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

Breaks: gtk-qt-engine-trinity (<< 4:14.0.0~)

W unknown-field

See the Policy Manual for a list of the possible fields in a package
control files.

Please refer to Binary package control files – DEBIAN/control (Section
5.3) in the Debian Policy Manual and Debian source control files – .dsc
(Section 5.4) in the Debian Policy Manual for details.

Visibility: warning
Show-Always: no
Check: fields/unknown
Renamed from: unknown-field-in-dsc unknown-field-in-control

Original-Maintainer

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

Lintian did not output a note for this tag [opt/trinity/lib/trinity/kcm_kcmgtk.so]
Lintian did not output a note for this tag [usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/engines/libqtengine.so]

P repeated-path-segment

The file is installed into a location that repeats the given path segment.
An example would be /usr/lib/lib or /usr/share/myprogram/share.

More often than not this is unintended.

Please refer to Bug#950052 and Bug#950027 for details.

Visibility: pedantic
Show-Always: no
Check: files/hierarchy/path-segments

trinity [opt/trinity/lib/trinity/]

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

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
Breaks gtk-qt-engine-trinity (<< 4:14.0.0~)
Depends libc6 (>= 2.4), libgcc-s1 (>= 3.0), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.12.0), libgtk2.0-0 (>= 2.18.0), libpango-1.0-0 (>= 1.14.0), libstdc++6 (>= 5), libtqt3-mt (>= 4:14.2.0~pre279), libx11-6, tdelibs14-trinity (>= 4:14.2.0~pre294)
Description theme engine using Qt for GTK+ 2.x and Trinity
The GTK-Qt Theme Engine (also known as gtk-qt-engine) is a GTK 2 theme engine
that calls Qt to do the actual drawing. This makes your GTK 2 applications
look almost like real Qt applications and gives you a more unified desktop
experience.
.
Please note that this package is targeted at Trinity users and therefore provides
a way to configure it from within KControl.
Installed-Size 433
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Bastian Venthur <venthur@debian.org>
Package gtk-qt-engine-trinity
Priority optional
Provides gtk2-engines-gtk-qt-trinity
Recommends gtk3-tqt-engine-trinity
Replaces gtk-qt-engine-trinity (<< 4:14.0.0~)
Section tde
Version 4:14.2.0~pre43-0raspbian12.0.0+7

gtk-qt-engine-trinity-dbg_14.2.0~pre43-0raspbian12.0.0+7_amd64.deb

W copyright-without-copyright-notice

Lintian did not output a note for this tag

W extended-description-line-too-long

line 1
line 2

W priority-extra-is-replaced-by-priority-optional

Since Debian Policy version 4.0.1, the priority extra has been deprecated.

Please update debian/control and replace all instances of Priority: extra
with Priority: optional.

Please refer to Priorities (Section 2.5) in the Debian Policy Manual for
details.

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

Lintian did not output a note for this tag

W unknown-field

See the Policy Manual for a list of the possible fields in a package
control files.

Please refer to Binary package control files – DEBIAN/control (Section
5.3) in the Debian Policy Manual and Debian source control files – .dsc
(Section 5.4) in the Debian Policy Manual for details.

Visibility: warning
Show-Always: no
Check: fields/unknown
Renamed from: unknown-field-in-dsc unknown-field-in-control

Original-Maintainer

I wrong-section-according-to-package-name

This package has a name suggesting that it belongs to a section other than
the one it is currently categorized in.

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

devel => debug

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

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
Build-Ids 015513efdb531d80e63d39866d2c3efec9d86b1b fec86f0aa6074d015ba0ed4027fd936a8dcf44d3
Depends gtk-qt-engine-trinity (= 4:14.2.0~pre43-0raspbian12.0.0+7), tdelibs-trinity-dbg
Description debugging symbols for the GTK-Qt Theme Engine [Trinity]
Installed-Size 685
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Bastian Venthur <venthur@debian.org>
Package gtk-qt-engine-trinity-dbg
Priority extra
Section devel
Source gtk-qt-engine-trinity
Version 4:14.2.0~pre43-0raspbian12.0.0+7

gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.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

1:0.8-1ubuntu3 -> 4:14.2.0~pre43-0raspbian12.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~pre43-0raspbian12.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 debhelper-but-no-misc-depends

The source package uses debhelper, but it does not include ${misc:Depends}
in the given binary package's debian/control entry. Any debhelper command
may add dependencies to ${misc:Depends} that are required for the work
that it does, so recommended best practice is to always add
${misc:Depends} to the dependencies of each binary package if debhelper is
in use.

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

Visibility: warning
Show-Always: no
Check: debhelper

gtk-qt-engine-trinity-dbg

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

1:0.8-1ubuntu3 -> 4:14.2.0~pre43-0raspbian12.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~pre43-0raspbian12.0.0+7 [debian/changelog:1]

W unknown-field

See the Policy Manual for a list of the possible fields in a package
control files.

Please refer to Binary package control files – DEBIAN/control (Section
5.3) in the Debian Policy Manual and Debian source control files – .dsc
(Section 5.4) in the Debian Policy Manual for details.

Visibility: warning
Show-Always: no
Check: fields/unknown
Renamed from: unknown-field-in-dsc unknown-field-in-control

Original-Maintainer

I debian-control-has-obsolete-dbg-package

The debian/control file declares a -dbg package.

Debug packages are now generated automatically. It reduces the space
requirements for archive mirrors for regular operations.

Please drop the -dbg package the debian/control file. Do not change it to
a dummy package that depends on the -dbgsym package.

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

Visibility: info
Show-Always: no
Check: debug/obsolete

(in section for gtk-qt-engine-trinity-dbg) Package [debian/control:25]

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 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.4 (released 2010-01-27) (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:124]
Lintian did not output a note for this tag [debian/changelog:133]
Lintian did not output a note for this tag [debian/changelog:134]
Lintian did not output a note for this tag [debian/changelog:149]
Lintian did not output a note for this tag [debian/changelog:156]
Lintian did not output a note for this tag [debian/changelog:159]
Lintian did not output a note for this tag [debian/changelog:160]
Lintian did not output a note for this tag [debian/changelog:162]
Lintian did not output a note for this tag [debian/changelog:174]
Lintian did not output a note for this tag [debian/changelog:189]
Lintian did not output a note for this tag [debian/changelog:218]
Lintian did not output a note for this tag [debian/changelog:228]
Lintian did not output a note for this tag [debian/changelog:232]
Lintian did not output a note for this tag [debian/changelog:233]
Lintian did not output a note for this tag [debian/changelog:238]
Lintian did not output a note for this tag [debian/changelog:295]
Lintian did not output a note for this tag [debian/changelog:324]
Lintian did not output a note for this tag [debian/changelog:334]
Lintian did not output a note for this tag [debian/changelog:338]
Lintian did not output a note for this tag [debian/changelog:339]
Lintian did not output a note for this tag [debian/changelog:344]
Lintian did not output a note for this tag [debian/changelog:403]
Lintian did not output a note for this tag [debian/changelog:586]

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

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.4

C trimmed-deb822-field

§1 Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, tdelibs14-trinity-dev, libgtk2.0-dev (>= 2.10.1) [debian/control:6]
§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 gtk-qt-engine-trinity [debian/control:1]
§1 Standards-Version 3.8.4 [debian/control:7]
§1 XSBC-Original-Maintainer Bastian Venthur <venthur@debian.org> [debian/control:5]
§2 Architecture any [debian/control:10]
§2 Breaks gtk-qt-engine-trinity (<< 4:14.0.0~) [debian/control:13]
§2 Depends ${shlibs:Depends}, ${misc:Depends} [debian/control:14]
§2 Description theme engine using Qt for GTK+ 2.x and Trinity
The GTK-Qt Theme Engine (also known as gtk-qt-engine) is a GTK 2 theme engine
that calls Qt to do the actual drawing. This makes your GTK 2 applications
look almost like real Qt applications and gives you a more unified desktop
experience.
.
Please note that this package is targeted at Trinity users and therefore provides
a way to configure it from within KControl. [debian/control:16]
§2 Package gtk-qt-engine-trinity [debian/control:9]
§2 Provides gtk2-engines-gtk-qt-trinity [debian/control:11]
§2 Recommends gtk3-tqt-engine-trinity [debian/control:15]
§2 Replaces gtk-qt-engine-trinity (<< 4:14.0.0~) [debian/control:12]
§3 Architecture any [debian/control:27]
§3 Depends gtk-qt-engine-trinity (= ${binary:Version}), tdelibs-trinity-dbg [debian/control:29]
§3 Description debugging symbols for the GTK-Qt Theme Engine [debian/control:30]
§3 Package gtk-qt-engine-trinity-dbg [debian/control:25]
§3 Priority extra [debian/control:28]
§3 Section devel [debian/control:26]

C trimmed-field

Architecture any
Binary gtk-qt-engine-trinity, gtk-qt-engine-trinity-dbg
Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, tdelibs14-trinity-dev, libgtk2.0-dev (>= 2.10.1)
Checksums-Sha1 1e69e883eed102d95de25c2b0bcc8c1b063191c7 61916 gtk-qt-engine-trinity_14.2.0~pre43.orig.tar.xz
39e746bcfae7ee280b3cdf1e1636e5ac1bfce3dd 7120 gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.0.0+7.debian.tar.xz
Checksums-Sha256 f177a8de5f1d9a748013b6079ee69bdef15cfd0cc0d6f5245c5ba6ae545e9bce 61916 gtk-qt-engine-trinity_14.2.0~pre43.orig.tar.xz
0ed3a3c462b56388bf3433e0939efc539c1cd162b89fa88952876705ee5c1653 7120 gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.0.0+7.debian.tar.xz
Files fafd96c3af15e4f9f45dbd16de154b26 61916 gtk-qt-engine-trinity_14.2.0~pre43.orig.tar.xz
d9d5e64b9602e7f3f685c4d0f1f8ade0 7120 gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.0.0+7.debian.tar.xz
Format 3.0 (quilt)
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Original-Maintainer Bastian Venthur <venthur@debian.org>
Package-List gtk-qt-engine-trinity deb tde optional arch=any
gtk-qt-engine-trinity-dbg deb devel extra arch=any
Source gtk-qt-engine-trinity
Standards-Version 3.8.4
Version 4:14.2.0~pre43-0raspbian12.0.0+7

Description

Lintian run for gtk-qt-engine-trinity package.

Additional details:

Source packages: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7
Binary packages: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7
Executed in environment system.tar.xz
Fail on severity: error
Build architecture: amd64
Target distribution: debian:raspbian-bookworm
Include tags: none
Exclude tags: none

Input artifacts

Type Alphabetical order Reverse alphabetical order	Name
Package upload	gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7
System tar	system.tar.xz
Source package	gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7

Workflow information

⬆️ debian_pipeline ( Completed Failure )
⬆️ QA ( Completed Failure )
⬆️ lintian ( Completed Failure )

Output artifacts

Type Alphabetical order Reverse alphabetical order	Name
Lintian report	lintian: gtk-qt-engine-trinity, gtk-qt-engine-trinity-dbg
Lintian report	lintian: gtk-qt-engine-trinity
Debug log	debusine:work-request-debug-logs

Output data

Runtime statistics:
- Duration: 00:00:42
- CPU time: 00:01:13
- Disk space: 915.4 MB
- Memory: 3.0 GB
- Available disk space: 15.7 GB
- Available memory: 31.3 GB
- CPU count: 20
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
247910	3 days, 13 hours	Worker	sbuild: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7 (amd64)	Completed	Success

Reverse dependencies

This work request is not required by any other one.

Internal collection: workflow-247797

Task data

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

Task data after applying task configuration

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

Scheduler tags

provided:
- task:group:debusine::Admins
- task:group:debusine::TDE-Owners
- task:scope:debusine
- task:source-package:gtk-qt-engine-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: 27480
input_binary_artifacts_ids:
- 800363
input_source_artifact_id: 799719
parameter_summary: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7
runtime_context: binary-all+binary-any+source:bookworm
subject: gtk-qt-engine-trinity

Workflow data

{
  "step": "lintian-amd64",
  "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": 3198210048,
    "cpu_time": 73,
    "duration": 42,
    "cpu_count": 20,
    "disk_space": 959864832,
    "available_memory": 33649803264,
    "available_disk_space": 16824901632
  }
}

lintian: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7… 247797… Completed Failure trinity-testing… SlavekB 3 days, 13 hours ago skoll… 33 minutes 0 minutes 3 weeks, 5 days

#247930: lintian: gtk-qt-engine-trinity_4:14.2.0~pre43-0raspbian12.0.0+7

Summary of tags

Tags

gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.0.0+7_amd64.deb

E dir-or-file-in-opt

W copyright-without-copyright-notice

W extended-description-line-too-long

W hardening-no-relro

W package-has-unnecessary-activation-of-ldconfig-trigger

Explanation

W package-relation-with-self

Explanation

W unknown-field

Explanation

W unknown-section

Explanation

I hardening-no-bindnow

P repeated-path-segment

Explanation

C control-tarball-compression-format

C data-tarball-compression-format

C mail-contact

Explanation

C no-ctrl-scripts

C package-is-maintained-by-individual

Explanation

C trimmed-field

gtk-qt-engine-trinity-dbg_14.2.0~pre43-0raspbian12.0.0+7_amd64.deb

W copyright-without-copyright-notice

W extended-description-line-too-long

W priority-extra-is-replaced-by-priority-optional

Explanation

W unknown-field

Explanation

I wrong-section-according-to-package-name

Explanation

C control-tarball-compression-format

C data-tarball-compression-format

C mail-contact

Explanation

C no-ctrl-scripts

C package-is-maintained-by-individual

Explanation

C trimmed-field

gtk-qt-engine-trinity_14.2.0~pre43-0raspbian12.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 debhelper-but-no-misc-depends

Explanation

W epoch-change-without-comment

Explanation

W no-nmu-in-changelog

Explanation

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

Explanation

W unknown-field

Explanation

I debian-control-has-obsolete-dbg-package

Explanation

I debian-watch-file-is-missing

Explanation

I no-dh-sequencer

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