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. Refer to https://ftp-master.debian.org/REJECT-FAQ.html for details. Severity: warning Check: debian/copyright
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. Refer to https://wiki.debian.org/Hardening for details. Severity: warning 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
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 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 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.
Refer to the debhelper(7) manual page for details.
Severity: warning
Check: debhelper
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
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
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
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
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 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.
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 kdirstat-trinity package.
|
Name
|
|
|
|---|---|---|
| Package upload | kdirstat-trinity_4:14.2.0~pre39-0ubuntu20.04.0+8 |
|
| System tar | system.tar.xz |
|
| Source package | kdirstat-trinity_4:14.2.0~pre39-0ubuntu20.04.0+8 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: kdirstat-trinity | |
| Lintian report | lintian: kdirstat-trinity | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 258848 | 2 days | Worker | sbuild: kdirstat-trinity_4:14.2.0~pre39-0ubuntu20.04.0+8 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-258730
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-amd64 source_artifact: 818650@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-amd64 source_artifact: 818650@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:kdirstat-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: - 824089 input_source_artifact_id: 818650 parameter_summary: kdirstat-trinity_4:14.2.0~pre39-0ubuntu20.04.0+8 runtime_context: binary-all+binary-any+source:focal subject: kdirstat-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": 175217664, "cpu_time": 186, "duration": 56, "cpu_count": 24, "disk_space": 690171904, "available_memory": 67425996800, "available_disk_space": 33713000448 } }