⇦ | 0install-core [universe]
Last updated on: 2022-05-03 16:55 [UTC]

Hints for 0install-core in universe

0install.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-tag-empty
    0install.appdata.xml:27 - translation
    The mentioned tag is empty, which is highly likely not intended as it should have content.
  • asv-type-property-required
    0install.appdata.xml:27 - translation ()
    This tag requires a type property.
  • asv-screenshot-no-media
    0install.appdata.xml:23 -
    A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
  • asv-cid-desktopapp-is-not-rdns
    0install.appdata.xml:4 - 0install.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.
  • missing-launchable-desktop-file
    The MetaInfo file references a .desktop file with ID '0install.desktop' in its launchable tag, but the file was not found in the same source tree. In order to be able to launch the software once it was installed, please place the MetaInfo file and its .desktop files in the same package.

Hints

  • asv-unknown-tag
    0install.appdata.xml:26 - updatecontact
    Found invalid tag. Non-standard tags should be prefixed with `x-`. AppStream also provides the <custom/> tag to add arbitrary custom data to metainfo files. This tag is read by AppStream libraries and may be useful instead of defining new custom toplevel or `x-`-prefixed tags if you just want to add custom data to a metainfo file.
  • asv-id-tag-has-type
    0install.appdata.xml:4 - 0install.desktop
    The <id/> tag still contains a `type` property, probably from an old conversion to the recent metainfo format.
  • asv-content-rating-missing
    0install.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-url-not-secure
    0install.appdata.xml:25 - http://0install.net
    Consider using a secure (HTTPS) URL for this web link.
  • asv-cid-has-number-prefix
    0install.appdata.xml:4 - 0install.desktop: 0install → _0install
    The component ID contains a segment starting with a number. Starting a segment of the reverse-DNS ID with a number is strongly discouraged, to keep interoperability with other tools such as D-Bus. Ideally, prefix these segments with an underscore.