Hints for merkuro in community
org.kde.merkuro ⚙ aarch64
Hints
-
asv-summary-has-dot-suffix
:46
- Xestione as súas tarefas, eventos e contactos de forma rápida e fácil.
The component summary should not end with a dot (`.`). -
asv-unknown-tag
:63
- developer
Found invalid tag. Non-standard tags should be prefixed with `x-`. AppStream also provides the <custom/> tag to add arbitrary custom data to metainfo files. This tag is read by AppStream libraries and may be useful instead of defining new custom toplevel or `x-`-prefixed tags if you just want to add custom data to a metainfo file.
org.kde.merkuro.calendar ⚙ aarch64
Hints
-
asv-summary-has-dot-suffix
:57
- Xestione as súas tarefas e eventos de forma rápida e fácil.
The component summary should not end with a dot (`.`). -
asv-unknown-tag
:80
- developer
Found invalid tag. Non-standard tags should be prefixed with `x-`. AppStream also provides the <custom/> tag to add arbitrary custom data to metainfo files. This tag is read by AppStream libraries and may be useful instead of defining new custom toplevel or `x-`-prefixed tags if you just want to add custom data to a metainfo file.
org.kde.merkuro.mail ⚙ aarch64
Hints
-
asv-summary-has-dot-suffix
:55
- Le o correo de forma rápida e fácil.
The component summary should not end with a dot (`.`). -
asv-unknown-tag
:76
- developer
Found invalid tag. Non-standard tags should be prefixed with `x-`. AppStream also provides the <custom/> tag to add arbitrary custom data to metainfo files. This tag is read by AppStream libraries and may be useful instead of defining new custom toplevel or `x-`-prefixed tags if you just want to add custom data to a metainfo file.
org.kde.merkuro.contact ⚙ aarch64
Warnings
-
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 aX-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.
Hints
-
asv-summary-has-dot-suffix
:53
- Xestione os seus contactos de forma rápida e fácil.
The component summary should not end with a dot (`.`). -
asv-unknown-tag
:74
- developer
Found invalid tag. Non-standard tags should be prefixed with `x-`. AppStream also provides the <custom/> tag to add arbitrary custom data to metainfo files. This tag is read by AppStream libraries and may be useful instead of defining new custom toplevel or `x-`-prefixed tags if you just want to add custom data to a metainfo file. -
asv-description-first-para-too-short
:78
- Merkuro contact book application.
The first `description/p` paragraph of this component might be too short (< 80 characters). Please consider starting with a longer paragraph to improve how the description looks like in software centers and to provide more detailed information on this component immediately in the first paragraph.