⇦ | chocolate-doom [main]
Last updated on: 2022-09-10 14:25 [UTC]

Hints for chocolate-doom in main

chocolate-doom.desktop ⚙ amd64

Warnings

  • asv-component-summary-missing
    chocolate-doom.appdata.xml -
    The component is missing a summary (<summary/> tag).
  • asv-component-name-missing
    chocolate-doom.appdata.xml -
    The component is missing a name (<name/> tag).
  • asv-cid-desktopapp-is-not-rdns
    chocolate-doom.appdata.xml:4 - chocolate-doom.desktop
    The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.

Hints

  • asv-cid-contains-hyphen
    chocolate-doom.appdata.xml:4 - chocolate-doom.desktop
    The component ID contains a hyphen/minus. Using a hyphen is strongly discouraged, to improve interoperability with other tools such as D-Bus. A good option is to replace any hyphens with underscores (`_`).
  • asv-content-rating-missing
    chocolate-doom.appdata.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/

chocolate-strife.desktop ⚙ amd64

Warnings

  • asv-cid-desktopapp-is-not-rdns
    chocolate-strife.appdata.xml:4 - chocolate-strife.desktop
    The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.
  • asv-component-name-missing
    chocolate-strife.appdata.xml -
    The component is missing a name (<name/> tag).
  • asv-component-summary-missing
    chocolate-strife.appdata.xml -
    The component is missing a summary (<summary/> tag).

Hints

  • asv-content-rating-missing
    chocolate-strife.appdata.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-cid-contains-hyphen
    chocolate-strife.appdata.xml:4 - chocolate-strife.desktop
    The component ID contains a hyphen/minus. Using a hyphen is strongly discouraged, to improve interoperability with other tools such as D-Bus. A good option is to replace any hyphens with underscores (`_`).

chocolate-hexen.desktop ⚙ amd64

Warnings

  • asv-cid-desktopapp-is-not-rdns
    chocolate-hexen.appdata.xml:4 - chocolate-hexen.desktop
    The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.
  • asv-component-name-missing
    chocolate-hexen.appdata.xml -
    The component is missing a name (<name/> tag).
  • asv-component-summary-missing
    chocolate-hexen.appdata.xml -
    The component is missing a summary (<summary/> tag).

Hints

  • asv-cid-contains-hyphen
    chocolate-hexen.appdata.xml:4 - chocolate-hexen.desktop
    The component ID contains a hyphen/minus. Using a hyphen is strongly discouraged, to improve interoperability with other tools such as D-Bus. A good option is to replace any hyphens with underscores (`_`).
  • asv-content-rating-missing
    chocolate-hexen.appdata.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/

chocolate-heretic.desktop ⚙ amd64

Warnings

  • asv-component-name-missing
    chocolate-heretic.appdata.xml -
    The component is missing a name (<name/> tag).
  • asv-component-summary-missing
    chocolate-heretic.appdata.xml -
    The component is missing a summary (<summary/> tag).
  • asv-cid-desktopapp-is-not-rdns
    chocolate-heretic.appdata.xml:4 - chocolate-heretic.desktop
    The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data.

Hints

  • asv-content-rating-missing
    chocolate-heretic.appdata.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-cid-contains-hyphen
    chocolate-heretic.appdata.xml:4 - chocolate-heretic.desktop
    The component ID contains a hyphen/minus. Using a hyphen is strongly discouraged, to improve interoperability with other tools such as D-Bus. A good option is to replace any hyphens with underscores (`_`).

chocolate-setup.desktop ⚙ amd64

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.