#180855: lintian: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0

Result: Failure

Fail on: error

Lintian output

Summary of tags

error: 57
warning: 13
info: 7
pedantic: 6
experimental: 1
overridden: 0
classification: 45

Tags

tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0_amd64.deb

E dir-or-file-in-opt

opt/trinity/
opt/trinity/lib/
opt/trinity/lib/trinity/
opt/trinity/lib/trinity/tastymenu_panelapplet.la
opt/trinity/lib/trinity/tastymenu_panelapplet.so
opt/trinity/share/
opt/trinity/share/apps/
opt/trinity/share/apps/kicker/
opt/trinity/share/apps/kicker/applets/
opt/trinity/share/apps/kicker/applets/tastymenu.desktop
opt/trinity/share/config.kcfg/
opt/trinity/share/config.kcfg/tastymenu.kcfg
opt/trinity/share/doc/
opt/trinity/share/doc/tde/
opt/trinity/share/doc/tde/HTML/
opt/trinity/share/doc/tde/HTML/en/
opt/trinity/share/doc/tde/HTML/en/tastymenu/
opt/trinity/share/doc/tde/HTML/en/tastymenu/common
opt/trinity/share/doc/tde/HTML/en/tastymenu/index.cache.bz2
opt/trinity/share/doc/tde/HTML/en/tastymenu/index.docbook
opt/trinity/share/doc/tde/HTML/en/tastymenu/screenshot.png
opt/trinity/share/locale/
opt/trinity/share/locale/de/
opt/trinity/share/locale/de/LC_MESSAGES/
opt/trinity/share/locale/de/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/es/
opt/trinity/share/locale/es/LC_MESSAGES/
opt/trinity/share/locale/es/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/fi/
opt/trinity/share/locale/fi/LC_MESSAGES/
opt/trinity/share/locale/fi/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/fr/
opt/trinity/share/locale/fr/LC_MESSAGES/
opt/trinity/share/locale/fr/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/it/
opt/trinity/share/locale/it/LC_MESSAGES/
opt/trinity/share/locale/it/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/nl/
opt/trinity/share/locale/nl/LC_MESSAGES/
opt/trinity/share/locale/nl/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/pl/
opt/trinity/share/locale/pl/LC_MESSAGES/
opt/trinity/share/locale/pl/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/pt_BR/
opt/trinity/share/locale/pt_BR/LC_MESSAGES/
opt/trinity/share/locale/pt_BR/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/ru/
opt/trinity/share/locale/ru/LC_MESSAGES/
opt/trinity/share/locale/ru/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/sl/
opt/trinity/share/locale/sl/LC_MESSAGES/
opt/trinity/share/locale/sl/LC_MESSAGES/tastymenu.mo
opt/trinity/share/locale/uk/
opt/trinity/share/locale/uk/LC_MESSAGES/
opt/trinity/share/locale/uk/LC_MESSAGES/tastymenu.mo

W copyright-refers-to-versionless-license-file

The copyright file refers to the versionless symlink in
/usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL
license, but the package does not appear to allow distribution under later
versions of the license. This symlink will change with each release of a
new version of the license and may therefore point to a different version
than the package is released under. debian/copyright should instead refers
to the specific version of the license that the package references.

For example, if the package says something like "you can redistribute it
and/or modify it under the terms of the GNU General Public License as
published by the Free Software Foundation; version 2 dated June, 1991,"
the debian/copyright file should refer to
/usr/share/common-licenses/GPL-2, not /GPL.

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

usr/share/common-licenses/LGPL

W copyright-without-copyright-notice

The copyright file for this package does not appear to contain a copyright
notice. You should copy the copyright notice from the upstream source (or
add one of your own for a native package). A copyright notice must consist
of Copyright, Copr., or the Unicode symbol of C in a circle followed by
the years and the copyright holder. A copyright notice is not required for
a work to be copyrighted, but Debian requires the copyright file include
the authors and years of copyright, and including a valid copyright notice
is the best way to do that. Examples:

Copyright YYYY Firstname Lastname <address@example.com>
Copr. YYYY-YYYY Firstname Lastname <address@example.com>
© YYYY,YYYY Firstname Lastname <address@example.com>

If the package is in the public domain rather than copyrighted, be sure to
mention "public domain" in the copyright file. Please be aware that this
is very rare and not the same as a DFSG-free license. True public domain
software is generally limited to such special cases as a work product of a
United States government agency.

Please refer to https://ftp-master.debian.org/REJECT-FAQ.html for details.

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

Lintian did not output a note for this tag

W extended-description-line-too-long

One or more lines in the extended part of the "Description:" field have
been found to contain more than 80 characters. For the benefit of users of
80x25 terminals, it is recommended that the lines do not exceed 80
characters.

Please refer to Debian Policy Manual section 3.4.1 for details.

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

line 1

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/lib/trinity/tastymenu_panelapplet.so]

W old-fsf-address-in-copyright-file

The /usr/share/doc/*pkg*/copyright file refers to the old postal address
of the Free Software Foundation (FSF). The new address is:

Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston,
MA 02110-1301, USA.

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

Lintian did not output a note for this tag

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 Debian Policy Manual section 8.1.1 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 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 "non-free/" if the package is in
the non-free archive area, and by "contrib/" if the package is in the
contrib archive area.

Please refer to Debian Policy Manual section 2.4 for details.

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

I extended-description-is-probably-too-short

The extended description (the lines after the first line of the
"Description:" field) is only one or two lines long. The extended
description should provide a user with enough information to decide
whether they want to install this package, what it contains, and how it
compares to similar packages. One or two lines is normally not enough to
do this.

Please refer to Debian Developer's Reference section 6.2.1 and Debian
Developer's Reference section 6.2.3 for details.

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

Lintian did not output a note for this tag

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/lib/trinity/tastymenu_panelapplet.so]

I spelling-error-in-binary

Lintian found a spelling error in the given binary. Lintian has a list of
common misspellings that it looks for. It does not have a dictionary like
a spelling checker does.

If the string containing the spelling error is translated with the help of
gettext or a similar tool, please fix the error in the translations as
well as the English text to avoid making the translations fuzzy. With
gettext, for example, this means you should also fix the spelling mistake
in the corresponding msgids in the *.po files.

You can often find the word in the source code by running:

grep -rw <word> <source-tree>

This tag may produce false positives for words that contain non-ASCII
characters due to limitations in strings.

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

opt/trinity/lib/trinity/tastymenu_panelapplet.so informations information

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

This is the compressor format used for the control.tar tarball.

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

C data-tarball-compression-format

This is the compressor format used for the data.tar tarball.

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

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
Depends libc6 (>= 2.4), libgcc-s1 (>= 3.3.1), libstdc++6 (>= 5), libtqt3-mt (>= 4:14.1.6~pre28), libxau6 (>= 1:1.0.9), tdelibs14-trinity (>= 4:14.1.6~pre16)
Description Replacement for TMenu
Tasty Menu is a TMenu replacement aiming to provide the maximum usability and flexibility.
Installed-Size 585
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package tastymenu-trinity
Priority optional
Section tde
Version 4:14.1.6~pre5-0ubuntu22.04.0+0

tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0.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-0debian7.0.0+0 -> 4:14.1.6~pre5-0ubuntu22.04.0+0

E rules-require-build-prerequisite

(does not satisfy cdbs)

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 Debian Developer's Reference section 5.10.2.1 for details.

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

4:14.1.6~pre5-0ubuntu22.04.0+0
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
acceptor, if you see one.

Please refer to Debian Policy Manual section 4.2 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" (line 2)
compression-level = 9 (line 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

tastymenu-trinity

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-0debian7.0.0+0 -> 4:14.1.6~pre5-0ubuntu22.04.0+0

W no-newline-at-end

The named text file does not end with a newline.

Git considers it a whitespace error. Emacs will offer to add it. It is
usually a good idea to do so.

Visibility: warning
Show-Always: no
Check: debian/trailing-whitespace

debian/changelog

I adopted-extended-field

A field in debian/control has an extension prefix but is also known
without it.

Extension prefixes like XS-* or XC-* allow experimental fields to
propagate to the right place when packages are built with dpkg. In this
case, however, the field is also known without the prefix. In all
likelihood the field was permanently adopted, and dpkg learned how to deal
with it.

Please consider removing the extension prefix for the field name.

Visibility: info
Show-Always: no
Check: debian/control/field/adopted
Renamed from: xc-package-type-in-debian-control
xs-testsuite-field-in-debian-control xs-vcs-field-in-debian-control

(in section for source) X-Original-Maintainer [debian/control:5]

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 Debian Policy Manual section 4.11 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

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.0 (released 2008-06-04) (current is 4.6.0.1)

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 Debian Policy Manual section 5.6.23 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 sucessively 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 Policy
Manual section 4.9.2, and Debian Policy Manual section 5.6.31 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 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: cruft
Renamed from: insane-line-length-in-source-file

doc/en/index.docbook line 138 is 571 characters long (>512)

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.

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

C trimmed-deb822-field

debian/control §1 Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, tdelibs-trinity-dev, libxau-dev
debian/control §1 Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
debian/control §1 Priority optional
debian/control §1 Section tde
debian/control §1 Source tastymenu-trinity
debian/control §1 Standards-Version 3.8.0
debian/control §1 X-Original-Maintainer Marco Martin <notmart@gmail.com>
debian/control §2 Architecture any
debian/control §2 Depends ${shlibs:Depends}
debian/control §2 Description Replacement for TMenu
Tasty Menu is a TMenu replacement aiming to provide the maximum usability and flexibility.
debian/control §2 Package tastymenu-trinity

C trimmed-field

Architecture any
Binary tastymenu-trinity
Build-Depends tde-cdbs, debhelper (>= 10~), quilt, tde-cmake, ninja-build, tdelibs-trinity-dev, libxau-dev
Checksums-Sha1 32a9f92962d93047e37b0005d53a2974640a837e 152704 tastymenu-trinity_14.1.6~pre5.orig.tar.xz
d4562c8feb0abcf2841debfade6421e9cdf6ba25 2800 tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0.debian.tar.xz
Checksums-Sha256 403751716793b5343dd5da59b4ec804c61fd6c8f49674f644934d3923e10f0ed 152704 tastymenu-trinity_14.1.6~pre5.orig.tar.xz
b2dc0eaf731da796fa32038468eb80a32bae9c0d169965fb8a4cbd34cf1d2c52 2800 tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0.debian.tar.xz
Files 7d8f086cc9cc7f2a60b4e7d78180b43f 152704 tastymenu-trinity_14.1.6~pre5.orig.tar.xz
0af62dde021f5688c44e91f2011c78fb 2800 tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0.debian.tar.xz
Format 3.0 (quilt)
Maintainer TDE Debian Team <team-debian@trinitydesktop.org>
Package-List tastymenu-trinity deb tde optional arch=any
Source tastymenu-trinity
Standards-Version 3.8.0
Version 4:14.1.6~pre5-0ubuntu22.04.0+0

Description

Lintian run for tastymenu-trinity package.

Additional details:

Source packages: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0
Binary packages: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0
Executed in environment system.tar.xz
Fail on severity: error
Build architecture: amd64
Target distribution: debian:jammy
Include tags: none
Exclude tags: none

Input artifacts

Type Alphabetical order Reverse alphabetical order	Name
Source package	tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0
System tar	system.tar.xz
Package upload	tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0

Workflow information

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

Output artifacts

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

Output data

Runtime statistics:
- Duration: 00:00:39
- CPU time: 00:01:45
- Disk space: 1.8 GB
- Memory: 200.3 MB
- Available disk space: 31.4 GB
- Available memory: 62.8 GB
- CPU count: 24
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
180835	2 weeks, 1 day	Worker	sbuild: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0 (amd64)	Completed	Success

Reverse dependencies

This work request is not required by any other one.

Internal collection: workflow-180831

Task data

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

Task data after applying task configuration

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

Scheduler tags

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

Dynamic data

configuration_context: jammy
environment_id: 27656
input_binary_artifacts_ids:
- 637595
input_source_artifact_id: 604872
parameter_summary: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0
runtime_context: binary-all+binary-any+source:jammy
subject: tastymenu-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": 210004992,
    "cpu_time": 105,
    "duration": 39,
    "cpu_count": 24,
    "disk_space": 1943269376,
    "available_memory": 67425996800,
    "available_disk_space": 33713000448
  }
}

lintian: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0… 180831… Completed Failure trinity-sb… SlavekB 2 weeks, 1 day ago fenrir-03… 1 day, 3 hours 0 minutes 2 weeks

#180855: lintian: tastymenu-trinity_4:14.1.6~pre5-0ubuntu22.04.0+0

Summary of tags

Tags

tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0_amd64.deb

E dir-or-file-in-opt

W copyright-refers-to-versionless-license-file

Explanation

W copyright-without-copyright-notice

Explanation

W extended-description-line-too-long

Explanation

W hardening-no-relro

Explanation

W old-fsf-address-in-copyright-file

Explanation

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

Explanation

W unknown-section

Explanation

I extended-description-is-probably-too-short

Explanation

I hardening-no-bindnow

Explanation

I spelling-error-in-binary

Explanation

P repeated-path-segment

Explanation

C control-tarball-compression-format

Explanation

C data-tarball-compression-format

Explanation

C mail-contact

Explanation

C no-ctrl-scripts

Explanation

C package-is-maintained-by-individual

Explanation

C trimmed-field

tastymenu-trinity_14.1.6~pre5-0ubuntu22.04.0+0.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-newline-at-end

Explanation

I adopted-extended-field

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 very-long-line-length-in-source-file

Explanation

X upstream-metadata-file-is-missing

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