Hints for abraflexi-changes-processor in main

Warnings

• missing-launchable-desktop-file
  The MetaInfo file references a .desktop file with ID 'cz.vitexsoftware.abraflexi_changes_processor_desktop' in its launchable tag, but the file was not found in the same package. 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.
• asv-tag-empty
  cz.vitexsoftware.abraflexi_changes_processor.metainfo.xml:18 - screenshots
  The mentioned tag is empty, which is highly likely not intended as it should have content.
• asv-tag-empty
  cz.vitexsoftware.abraflexi_changes_processor.metainfo.xml:11 - description
  The mentioned tag is empty, which is highly likely not intended as it should have content.
• asv-tag-empty
  cz.vitexsoftware.abraflexi_changes_processor.metainfo.xml:12 - p
  The mentioned tag is empty, which is highly likely not intended as it should have content.
• no-metainfo
  This software component is missing a MetaInfo file to provide metadata about it.
  We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
  Please consider to either hide this .desktop file from AppStream by adding a X-AppStream-Ignore=true field to its .desktop file, 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 will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
  You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.