Hints for cavepacker in main

Warnings

• asv-cid-is-not-rdns
  cavepacker.appdata.xml:4 - cavepacker.desktop
  The component ID is required to follow a reverse domain-name scheme for its name. See the AppStream specification for details.
• asv-description-para-markup-invalid
  cavepacker.appdata.xml:14 - br
  This description paragraph contains invalid markup. Currently, only <em/> and <code/> are permitted.
• asv-screenshot-no-media
  cavepacker.appdata.xml:100 -
  A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
• asv-description-para-markup-invalid
  cavepacker.appdata.xml:27 - b
  This description paragraph contains invalid markup. Currently, only <em/> and <code/> are permitted.
• asv-description-para-markup-invalid
  cavepacker.appdata.xml:31 - b
  This description paragraph contains invalid markup. Currently, only <em/> and <code/> are permitted.
• asv-screenshot-no-media
  cavepacker.appdata.xml:99 -
  A screenshot must contain at least one image or video in order to be useful. Please add an <image/> to it.
• 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.