The file appears to be in ELF format but readelf produced the indicated error when parsing it. In case of a false positive, you may need to install binutils-multiarch so that ELF files from other architectures are handled correctly. It is also possible that the file is not actually in ELF format but was misidentified as such. Please refer to https://refspecs.linuxfoundation.org/elf/elf.pdf and the readelf(1) manual page for details. Visibility: warning Show-Always: no Check: binaries/corrupted Renamed from: apparently-corrupted-elf-binary
[usr/lib/debug/.build-id/05/1719f17cdaa4cd8ed3f0f75b2b98460b19c9f0.debug]
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
This package has a name suggesting that it belongs to a section other than the one it is currently categorized in. Visibility: info Show-Always: no Check: fields/section
[usr/bin/akode-config]
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
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. Please 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. Visibility: pedantic Show-Always: no Check: files/config-scripts
[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]
[usr/lib/x86_64-linux-gnu/libakode.so.2.0.0]
[usr/lib/x86_64-linux-gnu/libakode_alsa_sink.so]
[usr/lib/x86_64-linux-gnu/libakode_mpc_decoder.so]
[usr/lib/x86_64-linux-gnu/libakode_oss_sink.so]
[usr/lib/x86_64-linux-gnu/libakode_src_resampler.so]
[usr/lib/x86_64-linux-gnu/libakode_xiph_decoder.so]
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
[usr/lib/x86_64-linux-gnu/libakode.so.2.0.0]
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. Please refer to the dpkg-gensymbols(1) manual page and https://wiki.debian.org/UsingSymbolsFiles for details. Visibility: info Show-Always: no Check: debian/shlibs
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
[usr/bin/akodeplay]
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. Please refer to Debian Policy Manual section 7.4 for details. Visibility: info Show-Always: no Check: fields/package-relations
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
[usr/lib/*/libakode_ffmpeg_decoder.so]
[usr/lib/x86_64-linux-gnu/libakode_ffmpeg_decoder.so]
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
[usr/lib/*/libakode_jack_sink.so]
[usr/lib/x86_64-linux-gnu/libakode_jack_sink.so]
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
[usr/lib/*/libakode_mpeg_decoder.so]
[usr/lib/x86_64-linux-gnu/libakode_mpeg_decoder.so]
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
[usr/lib/*/libakode_pulse_sink.so]
[usr/lib/x86_64-linux-gnu/libakode_pulse_sink.so]
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
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]
The debian/control file declares a -dbg package. Debug packages are now generated automatically. It reduces the space requirements for archive mirrors for regular operations. Please drop the -dbg package the debian/control file. Do not change it to a dummy package that depends on the -dbgsym package. Please refer to https://wiki.debian.org/AutomaticDebugPackages for details. Visibility: info Show-Always: no Check: debug/obsolete
[debian/control:116]
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
The listed binary packages all share the same short description, i.e. the first line of the Description field in debian/control. Please add a word or two, in parentheses if needed, to describe to users what they are installing. It is not okay to rely solely on package naming conventions to indicate what is inside. Visibility: info Show-Always: no Check: debian/control/field/description/duplicate
The named field for an installation package in debian/control has the same value as the one inherited from the source paragraph. In the interest of shorter and clearer files, you may wish to take advantage of the inheritance rules. This field is redundant. Visibility: info Show-Always: no Check: debian/control/field/redundant Renamed from: binary-control-field-duplicates-source
[debian/control:119]
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
Your package specifies the named override but there were no tags that could have been silenced by it. Maybe you fixed an underlying condition but forgot to remove the override. It is also possible that the Lintian maintainers fixed a false positive. If the override is now unused, please remove it. This tag is similar to mismatched-override except there a tag could have been silenced if the context had matched. Sometimes, overrides end up not being used because a tag appears only on some architectures. In that case, overrides can be equipped with an architecture qualifier. Please refer to Lintian User's Manual section 2.4.3 for details. Visibility: info Show-Always: yes Check: lintian
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 named field in the debian/control file lists multiple package relationships when one would be sufficient. The less restrictive declaration can be removed. The tools dpkg-source and dpkg-gencontrol do that automatically, so it does not affect the package generated from this source. Visibility: pedantic Show-Always: no Check: debian/control/field/relation Renamed from: duplicate-in-relation-field
[debian/control:106]
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]
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.
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
We want XZ regardless of the default compression.
We want XZ regardless of the default compression.
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.
[!hurd-i386]
[!hurd-i386]
Lintian run for akode package.
|
Name
|
|
|
|---|---|---|
| Source package | akode_4:14.1.6~pre2-0ubuntu22.04.0+3 |
|
| System tar | system.tar.xz |
|
| Package upload | akode_4:14.1.6~pre2-0ubuntu22.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.
| 266137 | 1 day, 7 hours | Worker | sbuild: akode_4:14.1.6~pre2-0ubuntu22.04.0+3 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-266115
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: 837882@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: 837882@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:akode - 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: - 838621 input_source_artifact_id: 837882 parameter_summary: akode_4:14.1.6~pre2-0ubuntu22.04.0+3 runtime_context: binary-all+binary-any+source:jammy 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": 3218845696, "cpu_time": 53, "duration": 39, "cpu_count": 20, "disk_space": 792686592, "available_memory": 33649803264, "available_disk_space": 16824901632 } }