Hints for cavepacker in main

Warnings

• asv-cid-is-not-rdns
  <code>cavepacker.appdata.xml:4</code> - <em>cavepacker.desktop</em><br/>The component ID is required to follow a reverse domain-name scheme for its name. See the AppStream specification for details.
• asv-summary-too-long
  <code>cavepacker.appdata.xml:8</code> - <em>CavePacker is a Sokoban game.\n\nIt is a puzzle game where you have to move the packages onto their targets without getting stuck. The lesser steps you made for solving a level, the better.\n\nYou may only push but not pull packages.\n</em><br/>The summary text is very long, and will likely not be displayed properly everywhere. It should be &lt;= 90 characters.
• asv-description-para-markup-invalid
  <code>cavepacker.appdata.xml:14</code> - <em>br</em><br/>This description paragraph contains invalid markup. Currently, only &lt;em/&gt; and &lt;code/&gt; are permitted.
• asv-description-para-markup-invalid
  <code>cavepacker.appdata.xml:27</code> - <em>b</em><br/>This description paragraph contains invalid markup. Currently, only &lt;em/&gt; and &lt;code/&gt; are permitted.
• asv-description-para-markup-invalid
  <code>cavepacker.appdata.xml:31</code> - <em>b</em><br/>This description paragraph contains invalid markup. Currently, only &lt;em/&gt; and &lt;code/&gt; are permitted.
• asv-screenshot-no-media
  <code>cavepacker.appdata.xml:99</code> - <em></em><br/>A screenshot must contain at least one image or video in order to be useful. Please add an &lt;image/&gt; to it.
• asv-screenshot-no-media
  <code>cavepacker.appdata.xml:100</code> - <em></em><br/>A screenshot must contain at least one image or video in order to be useful. Please add an &lt;image/&gt; to it.
• asv-desktop-entry-value-invalid-chars
  <code>cavepacker.desktop</code> - <em>Comment</em><br/>The value of this desktop-entry field contains invalid or non-printable UTF-8 characters, which can not be displayed properly.
• no-metainfo
  This software component is missing a <a href="https://freedesktop.org/software/appstream/docs/chap-Metadata.html#sect-Metadata-GenericComponent">MetaInfo file</a> to provide metadata.<br/> We currently took some data from its desktop-entry file and the long description of the package it is located in.<br/> This has several disadvantages, like poor markup, too technical descriptions for users of software centers, different components having the same description, etc.<br/> 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.<br/> Please consider to either hide this desktop-entry file from AppStream by adding a <code>X-AppStream-Ignore=true</code> field to it, or to write a MetaInfo file for this component and send it upstream.<br/> Generating components from non-MetaInfo files is <b>deprecated</b>, 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.<br> You can consult the <a href="http://freedesktop.org/software/appstream/docs/chap-Quickstart.html">MetaInfo quickstart guides</a> for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.