⇦ | freeciv-client-extras [main]
Last updated on: 2021-02-27 09:35 [UTC]

Hints for freeciv-client-extras in main

freeciv-mp-gtk3.desktop ⚙ amd64

Errors

  • internal-unknown-tag
    The given tag was unknown. This is a bug.

Warnings

  • asv-cid-desktopapp-is-not-rdns
    freeciv-mp-gtk3.appdata.xml:4 - freeciv-mp-gtk3.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.

Hints

  • asv-url-not-secure
    freeciv-mp-gtk3.appdata.xml:16 - http://www.freeciv.org/
    Consider using a secure (HTTPS) URL for this web link.
  • asv-id-tag-has-type
    freeciv-mp-gtk3.appdata.xml:4 - freeciv-mp-gtk3.desktop
    The <id/> tag still contains a `type` property, probably from an old conversion to the recent metainfo format.
  • asv-cid-contains-hyphen
    freeciv-mp-gtk3.appdata.xml:4 - freeciv-mp-gtk3.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 (`_`).

freeciv-ruledit.desktop ⚙ amd64

Errors

  • missing-desktop-file
    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.