⇦ | caja [universe]
Last updated on: 2020-04-23 11:40 [UTC]

Hints for caja in universe

caja.desktop ⚙ amd64

Errors

  • no-valid-category
    This software component is no member of any valid category.

Warnings

  • asv-cid-desktopapp-is-not-rdns
    caja.appdata.xml:4 - caja.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-unknown-tag
    caja.appdata.xml:238 - updatecontact
    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.

caja-browser.desktop ⚙ amd64

Hints

  • description-from-package
    This 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 writing 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.

caja-file-management-properties.desktop ⚙ amd64

Hints

  • description-from-package
    This 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 writing 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.