⇦ | aravis-tools [main]
Last updated on: 2023-11-14 08:15 [UTC]

Hints for aravis-tools in main

org.arv-viewer.desktop ⚙ amd64

Warnings

  • screenshot-download-error
    Error while downloading screenshot from 'https://raw.githubusercontent.com/AravisProject/aravis/main/viewer/icons/gnome/256x256/apps/aravis.png': URL was not found on the server.
    This might be a temporary server issue, or the screenshot is no longer available.

Hints

  • asv-cid-contains-hyphen
    :5 - org.arv-viewer.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-cid-missing-affiliation-gnome
    :5 - org.arv-viewer.desktop
    The component is part of the GNOME project, but its ID does not start with GNOMEs reverse-DNS name ("org.gnome").

arv-viewer-0.8.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.