The first line of the "Description:" should omit any initial indefinite
or definite article: "a", "an", or "the". A good heuristic is that it
should be possible to substitute the package name and synopsis into this
formula:
The package name provides {a,an,the,some} synopsis.
Refer to Debian Developer's Reference section 6.2.2 (The package
synopsis, or short description) for details.
Severity: warning
Check: fields/description
The maintainer scripts of the package contain one or more auto-generated shell snippets inserted by the listed debhelper tool. Severity: classification Check: maintainer-scripts/generated This tag is a classification. There is no issue in your package.
The listed file appears to be linked against the C library, but the
package doesn't depend on the C library package. Normally this indicates
that ${shlibs:Depends} was omitted from the Depends line for this
package in debian/control.
All shared libraries and compiled binaries must be run through
dpkg-shlibdeps to find out any libraries they are linked against (often
via the dh_shlibdeps debhelper command). The package containing these
files must then depend on ${shlibs:Depends} in debian/control to get the
proper package dependencies for those libraries.
Refer to Debian Policy Manual section 8.6.1 (Generating dependencies on
shared libraries) for details.
Severity: error
Check: binaries
The listed file appears to be linked against the C++ library, but the
package doesn't depend on the C++ library package. Normally this
indicates that ${shlibs:Depends} was omitted from the Depends line for
this package in debian/control.
All shared libraries and compiled binaries must be run through
dpkg-shlibdeps to find out any libraries they are linked against (often
via the dh_shlibdeps debhelper command). The package containing these
files must then depend on ${shlibs:Depends} in debian/control to get the
proper package dependencies for those libraries.
Refer to Debian Policy Manual section 8.6.1 (Generating dependencies on
shared libraries) for details.
Severity: error
Check: binaries
This tag is experimental. Please file a bug report if the tag seems
wrong.
This package ships a documentation file outside /usr/share/doc Documentation files are normally installed inside /usr/share/doc. If this file doesn't describe the contents or purpose of the directory it is in, please consider moving this file to /usr/share/doc/ or maybe even removing it. If this file does describe the contents or purpose of the directory it is in, please add a lintian override. Severity: info Check: documentation
The package ships a .html or .pdf file under /usr/share/doc/, which are usually documentation, but it does not register anything in doc-base. (Files under an examples directory are excluded.) Refer to Debian Policy Manual section 9.10 (Registering Documents using doc-base) for details. Severity: info Check: menus
The listed shared library calls the C library exit() or _exit() functions. In the case of an error, the library should instead return an appropriate error code to the calling program which can then determine how to handle the error, including performing any required clean-up. In most cases, removing the call should be discussed with upstream, particularly as it may produce an ABI change. Severity: info Check: shared-libs This tag is experimental. Please file a bug report if the tag seems wrong.
This executable file is not an ELF format binary, and does not start with the #! sequence that marks interpreted scripts. It might be a sh script that fails to name /bin/sh as its shell, or it may be incorrectly marked as executable. Sometimes upstream files developed on Windows are marked unnecessarily as executable on other systems. If you are using debhelper to build your package, running dh_fixperms will often correct this problem for you. Refer to Debian Policy Manual section 10.4 (Scripts) for details. Severity: warning Check: scripts
This binary package appears to be empty, and its description does not say that it's a metapackage or a transitional package. This is often due to problems with updating debhelper *.install files during package renames or similar problems where installation rules don't put files in the correct place. If the package is deliberately empty, please mention in the package long description one of the phrases "metapackage", "dummy", "dependency package", or "empty package". Previously, Lintian also accepted the use of "virtual package". This was removed to avoid overloading the term. If you have been relying on the phrase "virtual package" to avoid this warning, please replace it with one of the others. Severity: warning Check: files/empty-package
The first line of the "Description:" should omit any initial indefinite
or definite article: "a", "an", or "the". A good heuristic is that it
should be possible to substitute the package name and synopsis into this
formula:
The package name provides {a,an,the,some} synopsis.
Refer to Debian Developer's Reference section 6.2.2 (The package
synopsis, or short description) for details.
Severity: warning
Check: fields/description
Lintian found a spelling error in the README.Debian file. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does. Severity: warning Check: debian/readme
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. Refer to Debian Policy Manual section 2.4 (Sections) for details. Severity: warning Check: fields/section
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. Refer to Debian Policy Manual section 3.4.1 (The single line synopsis) for details. Severity: warning Check: fields/description
The architecture string in the source relation includes an unknown architecture. This may be a typo, or it may be an architecture that dpkg doesn't know about yet. A common problem is incorrectly separating architectures with a comma, such as [i386, m68k]. Architectures are separated by spaces; this should instead be [i386 m68k]. Refer to Debian Policy Manual section 5.6.8 (Architecture) for details. Severity: error Check: fields/package-relations
[amd64 i386 armel armhf arm64 mipsel ia64 powerpc ppc64el riscv64 loong64 s390 sparc]]
The package doesn't specify a build dependency on a package that is used in debian/rules. Lintian intentionally does not take into account transitive dependencies. Even if the package build-depends on some package that in turn depends on the needed package, an explicit build dependency should be added. Otherwise, a latent bug is created that will appear without warning if the other package is ever updated to change its dependencies. Even if this seems unlikely, please always add explicit build dependencies on every non-essential, non-build-essential package that is used directly during the build. Refer to Debian Policy Manual section 4.2 (Package relationships) for details. Severity: error Check: debian/rules
The given package appears to be a shared library -dev package, but the
dependency on what seems to be a corresponding shared library package
does not force the same package version. To ensure that compiling and
linking works properly, and that the symlinks in the -dev package point
to the correct files in the shared library package, a -dev package
should normally use (= ${binary:Version}) for the dependency on the
shared library package.
Sometimes, such as for -dev packages that are architecture-independent
to not break binNMUs or when one doesn't want to force a tight
dependency, a weaker dependency is warranted. Something like (>=
${source:Upstream-Version}), (<< ${source:Upstream-Version}+1~),
possibly using ${source:Version} instead, is the right approach. The
goal is to ensure that a new upstream version of the library package
doesn't satisfy the -dev package dependency, since the minor version of
the shared library may have changed, breaking the *.so links.
Refer to Debian Policy Manual section 8.5 (Dependencies between the
packages of the same library) for details.
Severity: error
Check: debian/control
The source package refers to a Standards-Version that has been obsolete for more than two years. Please update your package to latest Policy and set 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. Refer to https://www.debian.org/doc/debian-policy/upgrading-checklist.html for details. Severity: warning Check: fields/standards-version
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.) Refer to Debian Developer's Reference section 5.10.2.1 (Recompilation or binary-only NMU) for details. Severity: warning Check: fields/version
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. Refer to Debian Policy Manual section 4.11 (Optional upstream source location: debian/watch) and the uscan(1) manual page for details. Severity: info Check: debian/watch
The listed binary packages all share the same short description (the first line of the Description control field). The package names may provide enough additional information to distinguish between the packages, but it's common to also add a word or two to the short description to clarify the difference. Severity: info Check: debian/control
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. Severity: info Check: debian/rules/dh-sequencer
This package does not declare a test suite. Having a test suite aids with automated quality assurance of the archive outside of your package. For example, if your package has a test suite it is possible to re-run that test suite when any of your package's dependencies have a new version and check whether that update causes problems for your package. In addition, since May 2018 these tests now influence migration from unstable to testing: https://lists.debian.org/debian-devel-announce/2018/05/msg00001.html Please add a debian/tests/control file to your package to declare a testsuite, but please make sure to only add autopkgtests if they provide meaningful coverage of your package. Refer to https://ci.debian.net/doc/ for details. Severity: info Check: testsuite
Based on the content of the maintainer and uploader fields this package is co-maintained but there are no Vcs-* fields. It is recommended that shared maintenance of packages are co-ordinated via a revision control system. Severity: pedantic Check: fields/vcs
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. Refer to https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ for details. Severity: pedantic Check: debian/copyright
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. Refer to Debian Policy Manual section 5.6.23 (Homepage) for details. Severity: pedantic Check: fields/homepage
The debhelper compatibility version used by this package is marked as not recommended by the debhelper developer. You may consider using a recommended compatibility version. The compatibility version can be set by specifying debhelper-compat (= 12) in your package's Build-Depends, by the legacy debian/compat file or even by setting and exporting DH_COMPAT in debian/rules. If it is not set in either place, debhelper defaults to the deprecated compatibility version 1. Refer to the debhelper(7) manual page for details. Severity: pedantic Check: debhelper
The debian/control file is missing an explicit Rules-Requires-Root field. Traditionally, Debian packages have required root privileges for some debian/rules target requiring a split between build and binary targets. This makes the builds slower due to the increased amount of invocations as well as the overhead of fakeroot itself. Please specify (eg.) Rules-Requires-Root: no in the debian/control source stanza, but packagers should verify using diffoscope(1) that the binaries built with this field present are identical. Refer to /usr/share/doc/dpkg-dev/rootless-builds.txt.gz, Debian Policy Manual section 4.9.2 (debian/rules and Rules-Requires-Root), and Debian Policy Manual section 5.6.31 (Rules-Requires-Root) for details. Severity: pedantic Check: debian/control
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. Refer to https://dep-team.pages.debian.net/deps/dep12/ and https://wiki.debian.org/UpstreamMetadata for details. Severity: pedantic Check: debian/upstream/metadata This tag is experimental. Please file a bug report if the tag seems wrong.
This is the debhelper compat level used specified by this package. Severity: classification Check: debhelper This tag is a classification. There is no issue in your package.
This is the build system that Lintian believes the package is using. Severity: classification Check: debhelper This tag is a classification. There is no issue in your package.
The package is co-maintained but not team-maintained according to the maintainer/uploaders fields in the debian/control file. Severity: classification Check: fields/vcs This tag is a classification. There is no issue in your package.
This package uses the specified patch system (eg. "quilt" or "dpatch"). Severity: classification Check: patch-systems This tag is a classification. There is no issue in your package.
This is the source format declared in the package. Severity: classification Check: debian/source-dir This tag is a classification. There is no issue in your package.
The standards version of the package according to Standards-Version field in the debian/control file. Severity: classification Check: fields/standards-version This tag is a classification. There is no issue in your package.
Lintian run for tdebindings-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | tdebindings-trinity_4:14.2.0~pre84-0ubuntu20.04.0+9 |
|
| System tar | system.tar.xz |
|
| Package upload | tdebindings-trinity_4:14.2.0~pre84-0ubuntu20.04.0+9 |
|
| Package upload | tdebindings-trinity_4:14.2.0~pre84-0ubuntu20.04.0+9 |
|
Work requests that must be completed before this one can run.
| 143925 | 3 weeks, 3 days | Worker | sbuild: tdebindings-trinity_4:14.2.0~pre84-0ubuntu20.04.0+9 (all) | Completed | Success |
| 143926 | 3 weeks, 3 days | Worker | sbuild: tdebindings-trinity_4:14.2.0~pre84-0ubuntu20.04.0+9 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-143915
backend: unshare build_architecture: amd64 environment: debian/match:codename=focal exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-all - internal@collections/name:build-amd64 source_artifact: 498408@artifacts output: {} target_distribution: debian:focal
backend: unshare build_architecture: amd64 environment: debian/match:codename=focal exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-all - internal@collections/name:build-amd64 source_artifact: 498408@artifacts output: {} target_distribution: debian:focal task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:tdebindings-trinity - task:workspace:debusine:trinity-testing required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: focal environment_id: 27634 input_binary_artifacts_ids: - 507082 - 507130 input_source_artifact_id: 498408 parameter_summary: tdebindings-trinity_4:14.2.0~pre84-0ubuntu20.04.0+9 runtime_context: binary-all+binary-any+source:focal subject: tdebindings-trinity
{ "step": "lintian-amd64", "display_name": "Lintian for amd64+all+source" }
{ "on_success": [ { "action": "update-collection-with-artifacts", "variables": null, "collection": "internal@collections", "name_template": "lintian-amd64", "artifact_filters": { "category": "debian:lintian" } } ] }
{ "runtime_statistics": { "memory": 369593344, "cpu_time": 413, "duration": 64, "cpu_count": 12, "disk_space": 2479124480, "available_memory": 67425996800, "available_disk_space": 33713000448 } }