⇦ | kdocker [main]
Last updated on: 2025-07-04 20:13 [UTC]

Hints for kdocker in main

com.kdocker.KDocker.desktop ⚙ x86_64

Warnings

  • asv-metainfo-invalid-icon-type
    com.kdocker.KDocker.metainfo.xml:13 - local
    Metainfo files may only contain icons of type `stock` or `remote`, the set type is not allowed.
  • asv-release-timestamp-invalid
    com.kdocker.KDocker.metainfo.xml:31 - 2024-12-07T07:08:12
    The release timestamp is invalid.
  • asv-description-spurious-text
    com.kdocker.KDocker.metainfo.xml:32 -
    The description element contains raw text that is not in any paragraph or other permitted tag. This is not allowed and the additional text may be ignored by parsers or raise errors.
  • asv-description-no-valid-content
    com.kdocker.KDocker.metainfo.xml:32 -
    The description element does not contain any valid content (paragraphs, enumerations, etc.).

Hints

  • asv-desktop-app-launchable-omitted
    com.kdocker.KDocker.metainfo.xml -
    This `desktop-application` component has no `desktop-id` launchable tag, however it contains all the necessary information to display the application. The omission of the launchable entry means that this application can not be launched directly from installers or software centers. If this is intended, this information can be ignored, otherwise it is strongly recommended to add a launchable tag as well.
  • asv-content-rating-missing
    com.kdocker.KDocker.metainfo.xml -
    This component has no `content_rating` tag to provide age rating information. You can generate the tag data online by answering a few questions at https://hughsie.github.io/oars/
  • asv-developer-info-missing
    com.kdocker.KDocker.metainfo.xml -
    This component contains no `developer` element with information about its author.

com.kdocker.KDocker ⚙ x86_64

Errors

  • description-missing
    Software components of type 'desktop-application' require a long description, and we were unable to find one. Please add one via a MetaInfo file.

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata.
    We currently took some data from its desktop-entry file and the long description of the package it is located in.
    This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.
    Additionally, a lot of software with desktop-entry files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be tagged accordingly via MetaInfo files.
    Please consider to either hide this desktop-entry file from AppStream by adding a X-AppStream-Ignore=true field to it, or to write a MetaInfo file for this component and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software may vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers) in a future distribution release.
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.