⇦ | picom-conf [main]
Last updated on: 2024-07-20 14:30 [UTC]

Hints for picom-conf in main

picom_conf ⚙ amd64

Warnings

  • asv-cid-desktopapp-is-not-rdns
    picom_conf.appdata.xml:3 - picom_conf
    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-app-description-required
    picom_conf.appdata.xml -
    The component is missing a long description. Components of this type must have a long description.
  • screenshot-save-error
    Unable to store screenshot for 'https://github.com/qtilities/picom-conf/blob/master/resources/screenshot.png': Could not load source screenshot for storing: Unrecognized image file format

Hints

  • asv-developer-name-tag-deprecated
    picom_conf.appdata.xml:11 -
    The toplevel `developer_name` element is deprecated. Please use the `name` element in a `developer` block instead.
  • asv-developer-info-missing
    picom_conf.appdata.xml -
    This component contains no `developer` element with information about its author.
  • 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.