Hints for wsjtx-improved in main

wsjtx.desktop ⚙ amd64

metainfo-duplicate-id
The component-id 'wsjtx.desktop' already appeared in package 'wsjtx'. AppStream-IDs must be unique, please resolve which package will be providing this component by default.
This issue may happen temporarily when metadata is moved from one package to another. In that case, ignore this issue, it will vanish soon.

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.

metainfo-duplicate-id
The component-id 'message_aggregator.desktop' already appeared in package 'wsjtx'. AppStream-IDs must be unique, please resolve which package will be providing this component by default.
This issue may happen temporarily when metadata is moved from one package to another. In that case, ignore this issue, it will vanish soon.

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.