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. Severity: warning Check: fields/package-relations
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. Refer to Debian Policy Manual section 2.5 (Priorities) for details. Severity: warning Check: fields/priority
This package has a name suggesting that it belongs to a section other than the one it is currently categorized in. Severity: info Check: fields/section
The copyright file refers to the versionless symlink in /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement. For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the debian/copyright file should refer to /usr/share/common-licenses/GPL-2, not /GPL. For packages released under the same terms as Perl, Perl references the GPL version 1, so point to /usr/share/common-licenses/GPL-1. Severity: pedantic Check: debian/copyright
This is the compressor format used for the control.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
This is the compressor format used for the data.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
The package does not rely on any maintainer scripts (or other executable control files). Severity: classification Check: control-files This tag is a classification. There is no issue in your package.
The package is maintained by an individual 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.
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 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. Severity: warning Check: fields/package-relations
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 copyright file refers to the versionless symlink in /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement. For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the debian/copyright file should refer to /usr/share/common-licenses/GPL-2, not /GPL. For packages released under the same terms as Perl, Perl references the GPL version 1, so point to /usr/share/common-licenses/GPL-1. Severity: pedantic Check: debian/copyright
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 is the compressor format used for the control.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
This is the compressor format used for the data.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
The package does not rely on any maintainer scripts (or other executable control files). Severity: classification Check: control-files This tag is a classification. There is no issue in your package.
The package is maintained by an individual 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.
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. Severity: warning Check: fields/package-relations
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
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). Refer to https://wiki.debian.org/Hardening and https://bugs.debian.org/673112 for details. Severity: info Check: binaries
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. Severity: info Check: binaries
The copyright file refers to the versionless symlink in /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement. For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the debian/copyright file should refer to /usr/share/common-licenses/GPL-2, not /GPL. For packages released under the same terms as Perl, Perl references the GPL version 1, so point to /usr/share/common-licenses/GPL-1. Severity: pedantic Check: debian/copyright
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 is the compressor format used for the control.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
This is the compressor format used for the data.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
The package does not rely on any maintainer scripts (or other executable control files). Severity: classification Check: control-files This tag is a classification. There is no issue in your package.
The package is maintained by an individual 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.
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. Severity: warning Check: fields/package-relations
The copyright file refers to the versionless symlink in /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement. For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the debian/copyright file should refer to /usr/share/common-licenses/GPL-2, not /GPL. For packages released under the same terms as Perl, Perl references the GPL version 1, so point to /usr/share/common-licenses/GPL-1. Severity: pedantic Check: debian/copyright
This is the compressor format used for the control.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
This is the compressor format used for the data.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
The package does not rely on any maintainer scripts (or other executable control files). Severity: classification Check: control-files This tag is a classification. There is no issue in your package.
The package is maintained by an individual 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.
The arch all pkg-config file contains a reference to a multi-arch path. This can be usually be fixed by moving this file to a multi-arch path. Another likely cause is using debhelper 9 or newer (thus enabling multi-arch paths by default) on a package without multi-arch support. The usual cure in this case is to update it for multi-arch. Last but not least, this file could contain a reference to a cross architecture (like for instance an x86_64-linux-gnu pkg-config file referencing an i386-linux-gnu file). In this case the usual cure is to fix this path. Severity: error Check: files/pkgconfig
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. Severity: warning Check: fields/package-relations
The copyright file refers to the versionless symlink in /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement. For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the debian/copyright file should refer to /usr/share/common-licenses/GPL-2, not /GPL. For packages released under the same terms as Perl, Perl references the GPL version 1, so point to /usr/share/common-licenses/GPL-1. Severity: pedantic Check: debian/copyright
This is the compressor format used for the control.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
This is the compressor format used for the data.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
The package does not rely on any maintainer scripts (or other executable control files). Severity: classification Check: control-files This tag is a classification. There is no issue in your package.
The package is maintained by an individual 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.
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. Severity: warning Check: fields/package-relations
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 copyright file refers to the versionless symlink in /usr/share/common-licenses for the full text of the GPL, LGPL, or GFDL license. This symlink is updated to point to the latest version of the license when a new one is released. The package appears to allow relicensing under later versions of its license, so this is legally consistent, but it implies that Debian will relicense the package under later versions of those licenses as they're released. It is normally better to point to the version of the license the package references in its license statement. For example, if the package says something like "you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version", the debian/copyright file should refer to /usr/share/common-licenses/GPL-2, not /GPL. For packages released under the same terms as Perl, Perl references the GPL version 1, so point to /usr/share/common-licenses/GPL-1. Severity: pedantic Check: debian/copyright
This is the compressor format used for the control.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
This is the compressor format used for the data.tar tarball. Severity: classification Check: deb-format This tag is a classification. There is no issue in your package.
The package does not rely on any maintainer scripts (or other executable control files). Severity: classification Check: control-files This tag is a classification. There is no issue in your package.
The package is maintained by an individual 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.
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. Severity: error Check: debian/changelog
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 first package has a relation on the second package using a dpkg-control substitution variable to generate the versioned part of the relation. However the second package is not built from this source package. Usually this means there is a mistake or typo in the package name in this dependency. Severity: error Check: debian/version-substvars
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
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". Severity: warning Check: debian/changelog
The debian/control file includes declaration of -dbg package. Debug package are now autogenerated avoiding waste of miror space. Please note that -dbg should be dropped from control file and must not be transitioned to a dummy package depending on -dbgsym. Refer to https://wiki.debian.org/AutomaticDebugPackages for details. Severity: info Check: debian/control
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
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
quilt patch files should start with a description of patch. All lines before the start of the patch itself are considered part of the description. You can edit the description with quilt header -e when the patch is at the top of the stack. As well as a description of the purpose and function of the patch, the description should ideally contain author information, a URL for the bug report (if any), Debian or upstream bugs fixed by it, upstream status, the Debian version and date the patch was first included, and any other information that would be useful if someone were investigating the patch and underlying problem. Please consider using the DEP 3 format for this information. Refer to https://dep-team.pages.debian.net/deps/dep3/ for details. Severity: info Check: patch-systems
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 original source tarball contains the specified examples directory. However, no examples are installed in any binary packages. Please use dh_installexamples to install these to the most relevant package, for example by adding the directory name followed by a wildcard to a debian/pkgname.examples file. Lintian looks for any directory called examples under /usr/share/doc in all binary packages. Refer to the dh_installexamples(1) manual page for details. Severity: pedantic Check: cruft
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 arts-trinity package.
|
Name
|
|
|
|---|---|---|
| Package upload | arts-trinity_4:14.2.0~pre56-0ubuntu20.04.0+9 |
|
| Package upload | arts-trinity_4:14.2.0~pre56-0ubuntu20.04.0+9 |
|
| System tar | system.tar.xz |
|
| Source package | arts-trinity_4:14.2.0~pre56-0ubuntu20.04.0+9 |
|
|
Name
|
|
|
|---|---|---|
| Debug log | debusine:work-request-debug-logs | |
| Lintian report | lintian: arts-trinity-dbg, libarts1-trinity-dev, libarts1c2a-trinity, libartsc0-trinity, libartsc0-trinity-dev | |
| Lintian report | lintian: arts-trinity | |
| Lintian report | lintian: arts-trinity |
Work requests that must be completed before this one can run.
| 269033 | 2 days, 23 hours | Worker | sbuild: arts-trinity_4:14.2.0~pre56-0ubuntu20.04.0+9 (amd64) | Completed | Success |
| 269030 | 2 days, 23 hours | Worker | sbuild: arts-trinity_4:14.2.0~pre56-0ubuntu20.04.0+9 (all) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-268786
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: 845931@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: 845931@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:arts-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: - 846945 - 846972 input_source_artifact_id: 845931 parameter_summary: arts-trinity_4:14.2.0~pre56-0ubuntu20.04.0+9 runtime_context: binary-all+binary-any+source:focal subject: arts-trinity
{ "step": "lintian-amd64", "retry_count": 1, "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": 1373253632, "cpu_time": 47, "duration": 58, "cpu_count": 12, "disk_space": 715853824, "available_memory": 16606613504, "available_disk_space": 11976994816 } }