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
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
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
[opt/trinity/bin/abakus]
The menu item has a line that specifies an unknown section or uses a section that is intended only as a menu root, not as a section that applications should use directly. Check the spelling of the section and check the section against the list in the menu policy. (The menu sections changed as of June of 2007.) Please refer to The Debian Menu sub-policy section 2.1 for details. Visibility: warning Show-Always: no Check: menu-format
The menu item has a line that specifies a section under "Apps". This section has been moved to "Applications". Please refer to The Debian Menu sub-policy section 2.1 for details. Visibility: warning Show-Always: no Check: menu-format
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. Visibility: warning Show-Always: no Check: fields/package-relations
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
This package has no Homepage field but has a URL in the description and wording that might indicate this is the package Homepage. If it is, add a Homepage control field containing it rather than mentioning it in the package description. Visibility: info Show-Always: no Check: fields/description
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). Please refer to https://wiki.debian.org/Hardening and Bug#673112 for details. Visibility: info Show-Always: no Check: binaries/hardening
[opt/trinity/bin/abakus]
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.
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.
The maintainer scripts of the package contain one or more auto-generated shell snippets inserted by the listed debhelper tool. Visibility: classification Show-Always: no Check: maintainer-scripts/generated This tag is a classification. There is no issue in your package.
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.
[postinst]
[postrm]
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.
[Trinity]
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
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
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
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
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
[debian/control:5]
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
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
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
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
[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. Please refer to Debian Policy Manual section 5.6.23 for details. Visibility: pedantic Show-Always: no 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. Please refer to the debhelper(7) manual page for details. Visibility: pedantic Show-Always: no Check: debhelper
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
[debian/control]
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
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.
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.
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.
[debian/rules]
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.
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.
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.
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.
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.
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.
[Trinity]
Lintian run for abakus-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | abakus-trinity_4:14.1.6~pre8-0ubuntu22.04.0+1 |
|
| System tar | system.tar.xz |
|
| Package upload | abakus-trinity_4:14.1.6~pre8-0ubuntu22.04.0+1 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: abakus-trinity | |
| Lintian report | lintian: abakus-trinity | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 229998 | 5 days, 8 hours | Worker | sbuild: abakus-trinity_4:14.1.6~pre8-0ubuntu22.04.0+1 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-229993
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: 749670@artifacts output: {} target_distribution: debian:jammy
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: 749670@artifacts output: {} target_distribution: debian:jammy task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:abakus-trinity - task:workspace:debusine:trinity-sb required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: jammy environment_id: 27656 input_binary_artifacts_ids: - 766688 input_source_artifact_id: 749670 parameter_summary: abakus-trinity_4:14.1.6~pre8-0ubuntu22.04.0+1 runtime_context: binary-all+binary-any+source:jammy subject: abakus-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": 4359098368, "cpu_time": 73, "duration": 26, "cpu_count": 24, "disk_space": 793460736, "available_memory": 67425996800, "available_disk_space": 33713000448 } }