[opt/trinity/]
[opt/trinity/bin/]
[opt/trinity/bin/kcpuload]
[opt/trinity/share/]
[opt/trinity/share/applications/]
[opt/trinity/share/applications/tde/]
[opt/trinity/share/applications/tde/kcpuload.desktop]
[opt/trinity/share/apps/]
[opt/trinity/share/apps/kcpuload/]
[opt/trinity/share/apps/kcpuload/icons/]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/bars.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/barson.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/color.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/color0.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/color1.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/grid.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/gridon.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/labels.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/labelson.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/lines.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/lineson.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/shaded.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/shadedon.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/smp.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/smpon.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/soft.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/softon.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/speedarrow.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/split.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/16x16/actions/spliton.png]
[opt/trinity/share/apps/kcpuload/icons/hicolor/]
[opt/trinity/share/doc/]
[opt/trinity/share/doc/tde/HTML/]
[opt/trinity/share/doc/tde/HTML/en/]
[opt/trinity/share/doc/tde/HTML/en/kcpuload/]
[opt/trinity/share/doc/tde/HTML/en/kcpuload/common]
[opt/trinity/share/doc/tde/HTML/en/kcpuload/index.cache.bz2]
[opt/trinity/share/doc/tde/HTML/en/kcpuload/index.docbook]
[opt/trinity/share/doc/tde/]
[opt/trinity/share/icons/]
[opt/trinity/share/icons/crystalsvg/16x16/]
[opt/trinity/share/icons/crystalsvg/16x16/apps/]
[opt/trinity/share/icons/crystalsvg/16x16/apps/kcpuload.png]
[opt/trinity/share/icons/crystalsvg/32x32/]
[opt/trinity/share/icons/crystalsvg/32x32/apps/]
[opt/trinity/share/icons/crystalsvg/32x32/apps/kcpuload.png]
[opt/trinity/share/icons/crystalsvg/48x48/]
[opt/trinity/share/icons/crystalsvg/48x48/apps/]
[opt/trinity/share/icons/crystalsvg/48x48/apps/kcpuload.png]
[opt/trinity/share/icons/crystalsvg/]
[opt/trinity/share/icons/locolor/16x16/]
[opt/trinity/share/icons/locolor/16x16/apps/]
[opt/trinity/share/icons/locolor/16x16/apps/kcpuload.png]
[opt/trinity/share/icons/locolor/32x32/]
[opt/trinity/share/icons/locolor/32x32/apps/]
[opt/trinity/share/icons/locolor/32x32/apps/kcpuload.png]
[opt/trinity/share/icons/locolor/]
[opt/trinity/share/locale/]
[opt/trinity/share/locale/de/LC_MESSAGES/]
[opt/trinity/share/locale/de/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/de/]
[opt/trinity/share/locale/it/LC_MESSAGES/]
[opt/trinity/share/locale/it/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/it/]
[opt/trinity/share/locale/ka/LC_MESSAGES/]
[opt/trinity/share/locale/ka/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/ka/]
[opt/trinity/share/locale/nl/LC_MESSAGES/]
[opt/trinity/share/locale/nl/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/nl/]
[opt/trinity/share/locale/pl/LC_MESSAGES/]
[opt/trinity/share/locale/pl/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/pl/]
[opt/trinity/share/locale/ru/LC_MESSAGES/]
[opt/trinity/share/locale/ru/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/ru/]
[opt/trinity/share/locale/zh_Hans/LC_MESSAGES/]
[opt/trinity/share/locale/zh_Hans/LC_MESSAGES/kcpuload.mo]
[opt/trinity/share/locale/zh_Hans/]
[opt/trinity/share/man/]
[opt/trinity/share/man/man1/]
[opt/trinity/share/man/man1/kcpuload.1]
[opt/trinity/share/pixmaps/]
[opt/trinity/share/pixmaps/kcpuload.xpm]
[usr/share/doc-base/kcpuload-trinity.kcpuload-trinity:11]
[usr/share/doc-base/kcpuload-trinity.kcpuload-trinity:10]
[usr/share/doc-base/kcpuload-trinity.kcpuload-trinity:11]
[usr/share/doc-base/kcpuload-trinity.kcpuload-trinity:10]
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 first line of the "Description:" should omit any initial indefinite or
definite article: "a", "an", or "the". A good heuristic is that it should
be possible to substitute the package name and synopsis into this formula:
The package name provides {a,an,the,some} synopsis.
Please refer to The package synopsis, or short description (Section 6.2.2)
in the Debian Developer's Reference for details.
Visibility: warning
Show-Always: no
Check: fields/description
The section indicated in the given doc-base control file uses a top-level section named Apps or Applications. Those names are only used in menu, but not in doc-base. You may just be able to drop the Applications/ part in the section. Please refer to The section field (Section 2.3.3) in the Debian doc-base Manual for details. Visibility: warning Show-Always: no Check: menus
[usr/share/doc-base/kcpuload-trinity.kcpuload-trinity:7]
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/kcpuload]
The menu item has a line with a tag that is not a standard tags, such as needs=, section=, title=, longtitle=, or command= etc. While other tags can be used, it is rare. More commonly, the tag name was misspelled. Visibility: warning Show-Always: no Check: menu-format
[usr/share/menu/kcpuload-trinity:7]
The named tag would have been silenced except the context specified with the override did not match. Lintian may now provide a different context for the tag, or something could have changed in a new version of your package. Either way, overrides work best when you require as little context as needed. You can use wildcards, such as * or ? in the context to make a match more likely. Please remove or adjust the override. Visibility: warning Show-Always: yes Check: lintian
[usr/share/lintian/overrides/kcpuload-trinity:2]
The /usr/share/doc/*pkg*/copyright file refers to the old postal address of the Free Software Foundation (FSF). You should refer to https://www.gnu.org/licenses/ instead of a physical address, for example: You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/. Visibility: warning Show-Always: no Check: debian/copyright
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
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/bin/kcpuload]
[postinst]
[postrm]
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]
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 does not rely on any maintainer scripts (or other executable control files). Visibility: classification Show-Always: no Check: control-files 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
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:11]
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
[debian/changelog:41]
[debian/changelog:48]
[debian/changelog:50]
[debian/changelog:51]
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.
[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.
The field Rules-Requires-Root is not declared in the file debian/control. Please refer to usr/share/doc/dpkg/spec/rootless-builds.txt, 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: classification Show-Always: no Check: debian/control/field/rules-requires-root Renamed from: rules-requires-root-missing This tag is a classification. There is no issue in your package.
[debian/control]
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:14]
[debian/control:16]
[debian/control:9]
[debian/control:12]
[debian/control:11]
[debian/control:15]
Lintian run for kcpuload-trinity package.
|
Name
|
|
|
|---|---|---|
| Source package | kcpuload-trinity_4:14.2.0~pre35-0raspbian13.0.0+7 |
|
| System tar | system.tar.xz |
|
| Package upload | kcpuload-trinity_4:14.2.0~pre35-0raspbian13.0.0+7 |
|
|
Name
|
|
|
|---|---|---|
| Debug log | debusine:work-request-debug-logs | |
| Lintian report | lintian: kcpuload-trinity, kcpuload-trinity-dbgsym | |
| Lintian report | lintian: kcpuload-trinity |
Work requests that must be completed before this one can run.
| 258467 | 1 day, 3 hours | Worker | sbuild: kcpuload-trinity_4:14.2.0~pre35-0raspbian13.0.0+7 (amd64) | Completed | Success |
This work request is not required by any other one.
Internal collection: workflow-258188
backend: unshare build_architecture: amd64 environment: debian/match:codename=raspbian-trixie exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-amd64 source_artifact: 818605@artifacts output: {} target_distribution: debian:raspbian-trixie
backend: unshare build_architecture: amd64 environment: debian/match:codename=raspbian-trixie exclude_tags: [] fail_on_severity: error include_tags: [] input: binary_artifacts: - internal@collections/name:build-amd64 source_artifact: 818605@artifacts output: {} target_distribution: debian:raspbian-trixie task_configuration: 1021
provided: - task:group:debusine::Admins - task:group:debusine::TDE-Owners - task:scope:debusine - task:source-package:kcpuload-trinity - task:workspace:debusine:trinity-testing required: - worker:executor:unshare - worker:task:worker:lintian:version:1 - worker:type:external
configuration_context: trixie environment_id: 27472 input_binary_artifacts_ids: - 823129 input_source_artifact_id: 818605 parameter_summary: kcpuload-trinity_4:14.2.0~pre35-0raspbian13.0.0+7 runtime_context: binary-all+binary-any+source:trixie subject: kcpuload-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": 3315847168, "cpu_time": 53, "duration": 29, "cpu_count": 20, "disk_space": 1957007360, "available_memory": 33649803264, "available_disk_space": 16824901632 } }