Hints for transmission-base in community
transmission-gtk.desktop ⚙ aarch64
Errors
-
gui-app-without-icon
The component is a GUI application (application which has a .desktop file for the XDG menu andType=Application
), but we could not find a matching icon for this application.
Warnings
-
asv-cid-desktopapp-is-not-rdns
:7
- transmission-gtk.desktop
The component ID is not a reverse domain-name. Please update the ID to avoid future issues and be compatible with all AppStream implementations. You may also consider to update the name of the accompanying .desktop file to follow the latest version of the Desktop-Entry specification and use a rDNS name for it as well. In any case, do not forget to mention the new desktop-entry in a <launchable/> tag for this component to keep the application launchable from software centers and the .desktop file data associated with the metainfo data. -
missing-launchable-desktop-file
The MetaInfo file references a .desktop file with ID 'transmission-gtk.desktop' in itslaunchable
tag, but the file was not found in the same source tree. 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.
Hints
-
asv-id-tag-has-type
:7
- transmission-gtk.desktop
The <id/> tag still contains a `type` property, probably from an old conversion to the recent metainfo format. -
asv-cid-contains-hyphen
:7
- transmission-gtk.desktop
The component ID contains a hyphen/minus. Using a hyphen is strongly discouraged, to improve interoperability with other tools such as D-Bus. A good option is to replace any hyphens with underscores (`_`). -
asv-unknown-tag
:83
- 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.