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
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 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. Refer to Debian Policy Manual section 8.1.1 (ldconfig) and Bug#204975 for details. Severity: warning Check: shared-libs
See the Policy Manual for a list of the possible fields in a package control files. Refer to Debian Policy Manual section 5.3 (Binary package control files – DEBIAN/control) and Debian Policy Manual section 5.4 (Debian source control files – .dsc) for details. Severity: warning Check: fields/unknown Renamed from: unknown-field-in-dsc unknown-field-in-control
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
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. Refer to Debian Developer's Reference section 6.2.1 (General guidelines for package descriptions) and Debian Developer's Reference section 6.2.3 (The long description) for details. Severity: info Check: fields/description
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. Refer to Bug#950052 and Bug#950027 for details. Severity: pedantic Check: files/hierarchy/path-segments
This person is a contact in the named group for this package. Severity: classification Check: fields/mail-address Renamed from: maintainer uploader 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.
See the Policy Manual for a list of the possible fields in a package control files. Refer to Debian Policy Manual section 5.3 (Binary package control files – DEBIAN/control) and Debian Policy Manual section 5.4 (Debian source control files – .dsc) for details. Severity: warning Check: fields/unknown Renamed from: unknown-field-in-dsc unknown-field-in-control
This person is a contact in the named group for this package. Severity: classification Check: fields/mail-address Renamed from: maintainer uploader 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 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
When you NMU a package, that fact should be mentioned on the first line in the changelog entry. Use the words "NMU" or "Non-maintainer upload" (case insensitive). Maybe you didn't intend this upload to be a NMU, in that case, please double-check that the most recent entry in the changelog is byte-for-byte identical to the maintainer or one of the uploaders. If this is a local package (not intended for Debian), you can suppress this warning by putting "local" in the version number or "local package" on the first line of the changelog entry. Refer to Debian Developer's Reference section 5.11.3 (Using the DELAYED/ queue) for details. Severity: warning Check: nmu Renamed from: changelog-should-mention-nmu
A source NMU should have a Debian revision of "-x.x" (or "+nmuX" for a native package). This is to prevent stealing version numbers from the maintainer. Maybe you didn't intend this upload to be a NMU, in that case, please double-check that the most recent entry in the changelog is byte-for-byte identical to the maintainer or one of the uploaders. If this is a local package (not intended for Debian), you can suppress this warning by putting "local" in the version number or "local package" on the first line of the changelog entry. Refer to Debian Developer's Reference section 5.11.2 (NMUs and debian/changelog) for details. Severity: warning Check: nmu
See the Policy Manual for a list of the possible fields in a package control files. Refer to Debian Policy Manual section 5.3 (Binary package control files – DEBIAN/control) and Debian Policy Manual section 5.4 (Debian source control files – .dsc) for details. Severity: warning Check: fields/unknown Renamed from: unknown-field-in-dsc unknown-field-in-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
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/dep5
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
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. 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 Renamed from: rules-requires-root-missing
This file contains lines with trailing whitespace characters.
Whilst often harmless and unsightly, such extra whitespaces can also
cause tools to interpret the whitespace characters literally. The tool
diff(1) does not like them, either. They are best avoided.
Some of these problems can be hard to track down.
Whitespace at the end of lines may be removed with the following:
$ sed -i -e 's@[[:space:]]*$@@g' debian/control debian/changelog
If you use Emacs, you can also use "M-x wh-cl" (whitespace-cleanup).
However, if you wish to only remove trailing spaces and leave trailing
tabs (eg. for Makefiles), you can use the following code snippet:
$ sed -i -e 's@[ ]*$@@g' debian/rules
To remove empty lines from the end of a file, you can use:
$ sed -i -e :a -e '/^\n*$/{$d;N;};/\n$/ba' debian/rules
Severity: pedantic
Check: debian/trailing-whitespace
Renamed from: file-contains-trailing-whitespace
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.
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.
This person is a contact in the named group for this package. Severity: classification Check: fields/mail-address Renamed from: maintainer uploader This tag is a classification. There is no issue in your package.
The number of patches according to the debian/patches/series file. Severity: classification Check: debian/patches/count 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: debian/patches 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 twin-style-mallory-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | twin-style-mallory-trinity_4:14.2.0~pre47-0debian11.0.0+5 |
|
| System tar | system.tar.xz |
|
| Package upload | twin-style-mallory-trinity_4:14.2.0~pre47-0debian11.0.0+5 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: twin-style-mallory-trinity, twin-style-mallory-trinity-dbgsym | |
| Lintian report | lintian: twin-style-mallory-trinity | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 254187 | 2 days | Worker | sbuild: twin-style-mallory-trinity_4:14.2.0~pre47-0debian11.0.0+5 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-254118
backend: unshare build_architecture: amd64 environment: debian/match:codename=bullseye exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-amd64 source_artifact: 810204@artifacts output: {} target_distribution: debian:bullseye
backend: unshare build_architecture: amd64 environment: debian/match:codename=bullseye exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-amd64 source_artifact: 810204@artifacts output: {} target_distribution: debian:bullseye task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:twin-style-mallory-trinity - task:workspace:debusine:trinity-testing required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: bullseye environment_id: 27514 input_binary_artifacts_ids: - 812853 input_source_artifact_id: 810204 parameter_summary: twin-style-mallory-trinity_4:14.2.0~pre47-0debian11.0.0+5 runtime_context: binary-all+binary-any+source:bullseye subject: twin-style-mallory-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": 4246478848, "cpu_time": 297, "duration": 109, "cpu_count": 24, "disk_space": 1135177728, "available_memory": 67425996800, "available_disk_space": 33713000448 } }