Last updated on: 2022-09-10 14:25 [UTC]
Hints for abiword in main
abiword.desktop ⚙ amd64
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.
com.abisource.AbiWord ⚙ amd64
Found an AppStream MetaInfo XML file, but the associated .desktop file is missing. This often happens when the .desktop file is renamed, but the
<launchable type="desktop-id"/> tag value of the AppStream MetaInfo file is not adapted as well, or if the MetaInfo file is located in a different package than the .desktop file.
Please fix the packaging or work with upstream to resolve this issue.
For older metadata, the desktop-id is inferred from the
<id/> tag. If the component metadata has no
launchable tag and no
icon tag of type stock, check if a .desktop file named after the component-ID is located in the same package.