The copyright file refers to /usr/share/common-licenses/BSD. Due to the brevity of this license, the specificity of this copy to code whose copyright is held by the Regents of the University of California, and the frequency of minor wording changes in the license, its text should be included in the copyright file directly rather than referencing this file. This file may be removed from a future version of base-files if references to it drop sufficiently. Please refer to Debian Policy Manual section 12.5 for details. Visibility: warning Show-Always: no Check: debian/copyright
The extended description contains a "Homepage" pseudo-field following the old Developer's Reference recommendation. As of 1.14.6, dpkg now supports Homepage as a regular field in debian/control. This pseudo-field should be moved from the extended description to the fields for the relevant source or binary packages. Visibility: warning Show-Always: no Check: fields/description
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. Please refer to Debian Policy Manual section 3.4.1 for details. Visibility: warning Show-Always: no Check: fields/description
[opt/trinity/bin/kbarcode]
[opt/trinity/lib/trinity/tdefile_kbarcode.so]
A file is not valid UTF-8. Debian has used UTF-8 for many years. Support for national encodings is being phased out. This file probably appears to users in mangled characters (also called mojibake). Packaging control files must be encoded in valid UTF-8. Please convert the file to UTF-8 using iconv or a similar tool. Visibility: warning Show-Always: no Check: files/encoding Renamed from: national-encoding-in-text-file debian-changelog-file-uses-obsolete-national-encoding debian-control-file-uses-obsolete-national-encoding debian-copyright-file-uses-obsolete-national-encoding debian-news-file-uses-obsolete-national-encoding debian-tests-control-uses-national-encoding doc-base-file-uses-obsolete-national-encoding national-encoding-in-debconf-template national-encoding-in-manpage
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. Please refer to Debian Policy Manual section 8.1.1 and Bug#204975 for details. Visibility: warning Show-Always: no Check: libraries/shared/trigger/ldconfig
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 provides an ELF binary that lacks the "bindnow" linker flag. This is needed (together with "relro") to make the "Global Offset Table" (GOT) fully read-only. The bindnow feature trades startup time for improved security. Please consider enabling this feature or consider overriding the tag (possibly with a comment about why). If you use dpkg-buildflags, you may have to add hardening=+bindnow or hardening=+all to DEB_BUILD_MAINT_OPTIONS. The relevant compiler flags are set in LDFLAGS. Please refer to https://wiki.debian.org/Hardening for details. Visibility: info Show-Always: no Check: binaries/hardening
[opt/trinity/lib/trinity/tdefile_kbarcode.so]
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. Visibility: info Show-Always: no Check: documentation
The copyright file contains the incomplete Debian packaging copyright boilerplate from older versions of dh_make. (C) alone is not considered a valid copyright notice in some countries. The word Copyright or the © symbol should be used instead or in addition to (C). Copyright notices like this are, in any country that's a signatory to the Berne Convention, not required to claim copyright on a work, but their presence may allow claiming additional damages should a copyright case go to court. If you provide a notice, you may as well provide one that's legally recognized in a broader range of countries. Visibility: pedantic Show-Always: no Check: debian/copyright
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. Please refer to Bug#950052 and Bug#950027 for details. Visibility: pedantic Show-Always: no Check: files/hierarchy/path-segments
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.
[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.
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 code in debian/rules requires a prerequisite that is not presently listed in the package's Build-Depends. In the special case of Python, affected packages should Build-Depend on one of python3, python3-all, python3-dev, or python3-all-dev. Which one depends on whether a package supports multiple Python versions, and also whether the package builds Python modules or uses Python only as part of the build process. Packages that depend on a specific Python version may build-depend on any appropriate pythonX.Y or pythonX.Y-dev package instead. The condition you see in the context is not a recommendation on what to add. If you see a list, more than likely only one member is needed to make this tag go away. You probably also do not need the :any multiarch acceptor, if you see one. Please refer to Debian Policy Manual section 4.2 for details. Visibility: error Show-Always: no Check: debian/rules Renamed from: missing-build-dependency missing-python-build-dependency
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 file is not valid UTF-8. Debian has used UTF-8 for many years. Support for national encodings is being phased out. This file probably appears to users in mangled characters (also called mojibake). Packaging control files must be encoded in valid UTF-8. Please convert the file to UTF-8 using iconv or a similar tool. Visibility: warning Show-Always: no Check: files/encoding Renamed from: national-encoding-in-text-file debian-changelog-file-uses-obsolete-national-encoding debian-control-file-uses-obsolete-national-encoding debian-copyright-file-uses-obsolete-national-encoding debian-news-file-uses-obsolete-national-encoding debian-tests-control-uses-national-encoding doc-base-file-uses-obsolete-national-encoding national-encoding-in-debconf-template national-encoding-in-manpage
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
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. Visibility: pedantic Show-Always: no Check: fields/vcs Renamed from: co-maintained-package-with-no-vcs-headers
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]
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 co-maintained but not team-maintained 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.
Lintian run for kbarcode-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | kbarcode-trinity_4:14.2.0~pre47-0ubuntu22.04.0+7 |
|
| System tar | system.tar.xz |
|
| Package upload | kbarcode-trinity_4:14.2.0~pre47-0ubuntu22.04.0+7 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: kbarcode-trinity | |
| Lintian report | lintian: kbarcode-trinity | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 257713 | 2 days, 7 hours | Worker | sbuild: kbarcode-trinity_4:14.2.0~pre47-0ubuntu22.04.0+7 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-257666
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: 818508@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: 818508@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:kbarcode-trinity - task:workspace:debusine:trinity-testing required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: jammy environment_id: 27656 input_binary_artifacts_ids: - 821336 input_source_artifact_id: 818508 parameter_summary: kbarcode-trinity_4:14.2.0~pre47-0ubuntu22.04.0+7 runtime_context: binary-all+binary-any+source:jammy subject: kbarcode-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": 4253253632, "cpu_time": 81, "duration": 50, "cpu_count": 12, "disk_space": 2377859072, "available_memory": 67425996800, "available_disk_space": 33713000448 } }