[opt/trinity/]
[opt/trinity/lib/]
[opt/trinity/lib/trinity/]
[opt/trinity/lib/trinity/tdeio_locate.la]
[opt/trinity/lib/trinity/tdeio_locate.so]
[opt/trinity/share/]
[opt/trinity/share/doc/]
[opt/trinity/share/doc/tde/HTML/]
[opt/trinity/share/doc/tde/HTML/en/]
[opt/trinity/share/doc/tde/HTML/en/tdeioslave/]
[opt/trinity/share/doc/tde/HTML/en/tdeioslave/locate/]
[opt/trinity/share/doc/tde/HTML/en/tdeioslave/locate/common]
[opt/trinity/share/doc/tde/HTML/en/tdeioslave/locate/index.cache.bz2]
[opt/trinity/share/doc/tde/HTML/en/tdeioslave/locate/index.docbook]
[opt/trinity/share/doc/tde/HTML/en/tdeioslave/locate/screenshot.png]
[opt/trinity/share/doc/tde/]
[opt/trinity/share/locale/]
[opt/trinity/share/locale/de/LC_MESSAGES/]
[opt/trinity/share/locale/de/LC_MESSAGES/tdeio_locate.mo]
[opt/trinity/share/locale/de/]
[opt/trinity/share/locale/fr/LC_MESSAGES/]
[opt/trinity/share/locale/fr/LC_MESSAGES/tdeio_locate.mo]
[opt/trinity/share/locale/fr/]
[opt/trinity/share/locale/ka/LC_MESSAGES/]
[opt/trinity/share/locale/ka/LC_MESSAGES/tdeio_locate.mo]
[opt/trinity/share/locale/ka/]
[opt/trinity/share/locale/pt/LC_MESSAGES/]
[opt/trinity/share/locale/pt/LC_MESSAGES/tdeio_locate.mo]
[opt/trinity/share/locale/pt/]
[opt/trinity/share/locale/ru/LC_MESSAGES/]
[opt/trinity/share/locale/ru/LC_MESSAGES/tdeio_locate.mo]
[opt/trinity/share/locale/ru/]
[opt/trinity/share/services/]
[opt/trinity/share/services/locate.protocol]
[opt/trinity/share/services/locater.protocol]
[opt/trinity/share/services/rlocate.protocol]
[opt/trinity/share/services/searchproviders/]
[opt/trinity/share/services/searchproviders/locate.desktop]
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/lib/trinity/tdeio_locate.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
[usr/share/doc/tdeio-locate-trinity/TODO]
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 ldconfig (Section 8.1.1) in the Debian Policy Manual and Bug#204975 for details. Visibility: warning Show-Always: no Check: libraries/shared/trigger/ldconfig
See the Policy Manual for a list of the possible fields in a package control files. Please refer to Binary package control files – DEBIAN/control (Section 5.3) in the Debian Policy Manual and Debian source control files – .dsc (Section 5.4) in the Debian Policy Manual for details. Visibility: warning Show-Always: no 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 either "contrib/", "non-free/" or "non-free-firmware/" if the package is in the according archive area. Please refer to Sections (Section 2.4) in the Debian Policy Manual 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/tdeio_locate.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
[opt/trinity/lib/trinity/tdeio_locate.so]
Lintian found a spelling error in the given binary. Lintian has a list of common misspellings that it looks for. It does not have a dictionary like a spelling checker does. If the string containing the spelling error is translated with the help of gettext or a similar tool, please fix the error in the translations as well as the English text to avoid making the translations fuzzy. With gettext, for example, this means you should also fix the spelling mistake in the corresponding msgids in the *.po files. You can often find the word in the source code by running: grep -rw <word> <source-tree> This tag may produce false positives for words that contain non-ASCII characters due to limitations in strings. Visibility: info Show-Always: no Check: binaries/spelling
[opt/trinity/lib/trinity/tdeio_locate.so]
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
[opt/trinity/lib/trinity/]
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 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]
See the Policy Manual for a list of the possible fields in a package control files. Please refer to Binary package control files – DEBIAN/control (Section 5.3) in the Debian Policy Manual and Debian source control files – .dsc (Section 5.4) in the Debian Policy Manual for details. Visibility: warning Show-Always: no 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. 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 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
[debian/changelog:1]
[debian/rules]
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 Recompilation or binary-only NMU (Section 5.10.2.1) in the Debian Developer's Reference 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 qualifier, if you see one. Please refer to Package relationships (Section 4.2) in the Debian Policy Manual for details. Visibility: error Show-Always: no Check: debian/rules Renamed from: missing-build-dependency missing-python-build-dependency
[debian/source/options:2]
[debian/source/options:3]
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
[debian/changelog:1]
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. Please refer to Using the DELAYED/ queue (Section 5.11.3) in the Debian Developer's Reference for details. Visibility: warning Show-Always: no Check: nmu Renamed from: changelog-should-mention-nmu
[debian/changelog:1]
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. Please refer to NMUs and debian/changelog (Section 5.11.2) in the Debian Developer's Reference for details. Visibility: warning Show-Always: no Check: nmu
[debian/changelog:1]
See the Policy Manual for a list of the possible fields in a package control files. Please refer to Binary package control files – DEBIAN/control (Section 5.3) in the Debian Policy Manual and Debian source control files – .dsc (Section 5.4) in the Debian Policy Manual for details. Visibility: warning Show-Always: no 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. Please refer to Upstream source location: debian/watch (Section 4.11) in the Debian Policy Manual 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
[debian/rules]
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 Homepage (Section 5.6.23) in the Debian Policy Manual 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 successively 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/rules and Rules-Requires-Root (Section 4.9.2) in the Debian Policy Manual, and Rules-Requires-Root (Section 5.6.31) in the Debian Policy Manual for details. Visibility: pedantic Show-Always: no Check: debian/control/field/rules-requires-root Renamed from: rules-requires-root-missing
[debian/control]
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
Visibility: pedantic
Show-Always: no
Check: debian/trailing-whitespace
Renamed from: file-contains-trailing-whitespace
[debian/changelog:196]
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.
[src/klocateconfigwidget.ui:368]
[src/tdeio_locate.cpp:351]
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.
[debian/patches/series]
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.
[debian/control:6]
[debian/control:4]
[debian/control:3]
[debian/control:2]
[debian/control:1]
[debian/control:7]
[debian/control:5]
[debian/control:10]
[debian/control:13]
[debian/control:11]
[debian/control:14]
[debian/control:9]
[debian/control:12]
Lintian run for tdeio-locate-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | tdeio-locate-trinity_4:14.2.0~pre28-0raspbian12.0.0+8 |
|
| System tar | system.tar.xz |
|
| Package upload | tdeio-locate-trinity_4:14.2.0~pre28-0raspbian12.0.0+8 |
|
|
Name
|
|
|
|---|---|---|
| Lintian report | lintian: tdeio-locate-trinity, tdeio-locate-trinity-dbgsym | |
| Lintian report | lintian: tdeio-locate-trinity | |
| Debug log | debusine:work-request-debug-logs |
Work requests that must be completed before this one can run.
| 245307 | 3 days, 2 hours | Worker | sbuild: tdeio-locate-trinity_4:14.2.0~pre28-0raspbian12.0.0+8 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-245208
backend: unshare build_architecture: amd64 environment: debian/match:codename=raspbian-bookworm exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-amd64 source_artifact: 792407@artifacts output: {} target_distribution: debian:raspbian-bookworm
backend: unshare build_architecture: amd64 environment: debian/match:codename=raspbian-bookworm exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-amd64 source_artifact: 792407@artifacts output: {} target_distribution: debian:raspbian-bookworm task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:tdeio-locate-trinity - task:workspace:debusine:trinity-testing required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: bookworm environment_id: 27480 input_binary_artifacts_ids: - 794959 input_source_artifact_id: 792407 parameter_summary: tdeio-locate-trinity_4:14.2.0~pre28-0raspbian12.0.0+8 runtime_context: binary-all+binary-any+source:bookworm subject: tdeio-locate-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": 200013824, "cpu_time": 194, "duration": 56, "cpu_count": 32, "disk_space": 1294929920, "available_memory": 67418435584, "available_disk_space": 33709219840 } }