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 following file is an old style config file, used to retrieve information about installed libraries in the system. It is typically used to compile and link against one or more libraries. Using this kind of system to pass compile file is obsolete and will likely introduce bugs in a multi-arch system. Particularly, this kind of script could only belong to a package that is not Multi-Arch. You should consider to move to pkg-config file and warn your user to not use this script, and open a bug upstream. You should also consider to implement this file as a compatibility wrapper over pkg-config. After fixing every reverse depends of your package and use pkg-config reverse depends makefile, you should consider to put this script, as a temporary convenience of your users, under /usr/lib/$DEB_HOST_MULTIARCH/$PACKAGE/bin where $DEB_HOST_MULTIARCH is the multi-arch triplet and $PACKAGE is the package name. You should also consider to add a NEWS.Debian entry. Refer to the pkg-config(1) manual page and http://sources.debian.net/src/imagemagick/8:6.8.9.9-6/debian/NEWS/ for details. Severity: pedantic Check: files/config-scripts
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
Although the package includes a shared library, the package does not have a symbols control file. dpkg can use symbols files in order to generate more accurate library dependencies for applications, based on the symbols from the library that are actually used by the application. Refer to the dpkg-gensymbols(1) manual page and https://wiki.debian.org/UsingSymbolsFiles for details. Severity: info Check: shared-libs
[usr/lib/*/libakode_alsa_sink.so]
[usr/lib/*/libakode_mpc_decoder.so]
[usr/lib/*/libakode_oss_sink.so]
[usr/lib/*/libakode_src_resampler.so]
[usr/lib/*/libakode_xiph_decoder.so]
An earlier-than version clause is normally an indication that Breaks should be used instead of Conflicts. Breaks is a weaker requirement that provides the package manager more leeway to find a valid upgrade path. Conflicts should only be used if two packages can never be unpacked at the same time, or for some situations involving virtual packages (where a version clause is not appropriate). In particular, when moving files between packages, use Breaks plus Replaces, not Conflicts plus Replaces. Refer to Debian Policy Manual section 7.4 (Conflicting binary packages - Conflicts) for details. Severity: info Check: fields/package-relations
[usr/lib/*/libakode_ffmpeg_decoder.so]
[usr/lib/*/libakode_jack_sink.so]
[usr/lib/*/libakode_mpeg_decoder.so]
[usr/lib/*/libakode_pulse_sink.so]
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
In debian/control, this field for a binary package duplicates the value inherited from the source package paragraph. This doesn't hurt anything, but you may want to take advantage of the inheritance and set the value in only one place. It prevents missing duplicate places that need to be fixed if the value ever changes. Severity: info Check: debian/control
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
The listed binary packages all share the same short description (the first line of the Description control field). The package names may provide enough additional information to distinguish between the packages, but it's common to also add a word or two to the short description to clarify the difference. Severity: info Check: debian/control
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
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
The given field in the debian/control file contains relations that are either identical or imply each other. The less restrictive one can be removed. This is done automatically by dpkg-source and dpkg-gencontrol, so this does not affect the generated package. Severity: pedantic Check: debian/control
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 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.
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
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 akode package.
|
Name
|
|
|
|---|---|---|
| Source package | akode_4:14.1.6~pre2-0ubuntu20.04.0+3 |
|
| System tar | system.tar.xz |
|
| Package upload | akode_4:14.1.6~pre2-0ubuntu20.04.0+3 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: akode-dbg, libakode-dev, libakode2, libakode2-bin, libakode2-ffmpeg, libakode2-jack, libakode2-mpeg, libakode2-pulse | |
| Lintian report | lintian: akode | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 267726 | 1 day, 1 hour | Worker | sbuild: akode_4:14.1.6~pre2-0ubuntu20.04.0+3 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-267660
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: 839850@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: 839850@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:akode - task:workspace:debusine:trinity-sb required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: focal environment_id: 27634 input_binary_artifacts_ids: - 843485 input_source_artifact_id: 839850 parameter_summary: akode_4:14.1.6~pre2-0ubuntu20.04.0+3 runtime_context: binary-all+binary-any+source:focal subject: akode
{ "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": 163060736, "cpu_time": 246, "duration": 71, "cpu_count": 24, "disk_space": 1655365632, "available_memory": 67425996800, "available_disk_space": 33713000448 } }