⇦ | geeqie-common [main]
Last updated on: 2023-02-04 08:23 [UTC]

Hints for geeqie-common in main

geeqie.desktop ⚙ all

Errors

  • metainfo-no-name
    Component has no name specified. Ensure that the AppStream MetaInfo file or the .desktop file (if there is any) specify a component name.

Warnings

  • asv-component-name-missing
    -
    The component is missing a name (<name/> tag).
  • asv-component-summary-missing
    -
    The component is missing a summary (<summary/> tag).
  • asv-cid-desktopapp-is-not-rdns
    :3 - geeqie.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.
  • asv-description-markup-invalid
    :10 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :13 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :14 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :15 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :16 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :17 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :18 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :21 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :22 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :23 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :24 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-description-markup-invalid
    :25 - _p
    AppStream descriptions support only a limited set of tags to format text: Paragraphs (<p/>) and lists (<ul/>, <ol/>). This description markup contains an invalid XML tag that would not be rendered correctly in applications supporting the metainfo specification.
  • asv-app-description-required
    -
    The component is missing a long description. Components of this type must have a long description.
  • missing-launchable-desktop-file
    The MetaInfo file references a .desktop file with ID 'geeqie.desktop' in its launchable 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
    :3 - geeqie.desktop
    The <id/> tag still contains a `type` property, probably from an old conversion to the recent metainfo format.
  • asv-unknown-tag
    :7 - _name
    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-unknown-tag
    :8 - _summary
    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-screenshot-media-url-not-secure
    :29 - http://cclark.uk/geeqie/screenshots/Screenshot_2017-08-13_12-02-32_rescaled.png
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-screenshot-media-url-not-secure
    :32 - http://cclark.uk/geeqie/screenshots/Screenshot_2017-08-13_12-29-44_rescaled.png
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-url-not-secure
    :44 - http://geeqie.org
    Consider using a secure (HTTPS) URL for this web link.
  • asv-desktop-app-launchable-omitted
    -
    This `desktop-application` component has no `desktop-id` launchable tag, however it contains all the necessary information to display the application. The omission of the launchable entry means that this application can not be launched directly from installers or software centers. If this is intended, this information can be ignored, otherwise it is strongly recommended to add a launchable tag as well.
  • description-from-package
    This software component gets its description from 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.
    Please consider to either hide this .desktop file from AppStream by adding a X-AppStream-Ignore=true field to its .desktop file, or to write a MetaInfo file for this component to take the long description upstream. In future, components without MetaInfo file might be dropped from the metadata entirely. You can consult the XML quickstart guides for more information on how to write a MetaInfo file.