⇦ | chocolate-doom-heretic [main]
Last updated on: 2025-07-04 21:38 [UTC]

Hints for chocolate-doom-heretic in main

org.chocolate_doom.Heretic_Setup ⚙ x86_64

Errors

  • pkg-empty-file
    Could not extract file 'chocolate-heretic-setup.png' from package 'chocolate-doom-heretic-3.1.0-10-1-x86_64.eopkg'. Icon data was empty. The icon might be a symbolic link pointing at a file outside of this package. Please do not do that and instead place the icons in their appropriate directories in /usr/share/icons/hicolor/.
  • icon-not-found
    The icon 'chocolate-heretic-setup' was not found in the archive. This issue can have multiple reasons:
    • The icon is not present in the archive.
    • The icon is in a wrong directory.
    • The icon is not available in a suitable size (at least 64x64px)
    • On Debian and Ubuntu, the icon is a symlink. The generator cannot read symlinks on these distributions - make the icon a real file.
    To make the icon easier to find, place it in /usr/share/icons/hicolor/<size>/apps and ensure the Icon= value of the .desktop file is set correctly.

Warnings

  • asv-desktop-entry-category-invalid
    org.chocolate_doom.Heretic_Setup.desktop - Settings:
    A category defined in the desktop-entry file is not valid. Refer to the XDG Menu Specification for a list of valid categories.
  • 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.

org.chocolate_doom.Heretic ⚙ x86_64

Warnings

  • asv-desktop-app-launchable-missing
    org.chocolate_doom.Heretic.metainfo.xml -
    This `desktop-application` component is missing a `desktop-id` launchable tag. This means that this application can not be launched and has no association with its desktop-entry file. It also means no icon data or category information from the desktop-entry file will be available, which will result in this application being ignored entirely.

Hints

  • asv-developer-name-tag-deprecated
    org.chocolate_doom.Heretic.metainfo.xml:9 -
    The toplevel `developer_name` element is deprecated. Please use the `name` element in a `developer` block instead.
  • asv-content-rating-missing
    org.chocolate_doom.Heretic.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
    org.chocolate_doom.Heretic.metainfo.xml -
    This component contains no `developer` element with information about its author.