⇦ | classified-ads [main]
Last updated on: 2024-12-18 02:13 [UTC]

Hints for classified-ads in main

classified_ads.desktop ⚙ amd64

Errors

  • gui-app-without-icon
    The component is a GUI application (application which has a .desktop file for the XDG menu and Type=Application), but we could not find a matching icon for this application.

Warnings

  • asv-cid-desktopapp-is-not-rdns
    classified-ads.appdata.xml:4 - classified_ads.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-spdx-license-unknown
    classified-ads.appdata.xml:6 - LGPLv2
    The license ID was not found in the SPDX database. Please check that the license ID is written in an SPDX-conformant way and is a valid free software license.
  • asv-description-para-markup-invalid
    classified-ads.appdata.xml:18 - ul
    This description paragraph contains invalid markup. Currently, only <em/> and <code/> are permitted.
  • asv-description-para-markup-invalid
    classified-ads.appdata.xml:33 - ul
    This description paragraph contains invalid markup. Currently, only <em/> and <code/> are permitted.
  • missing-launchable-desktop-file
    The MetaInfo file references a .desktop file with ID 'classified_ads.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-url-not-secure
    classified-ads.appdata.xml:54 - http://katiska.org/classified_ads/
    Consider using a secure (HTTPS) URL for this web link.
  • asv-unknown-tag
    classified-ads.appdata.xml:55 - 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.
  • asv-desktop-app-launchable-omitted
    classified-ads.appdata.xml -
    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.
  • asv-content-rating-missing
    classified-ads.appdata.xml -
    This component has no `content_rating` tag to provide age rating information. You can generate the tag data online by answering a few questions at https://hughsie.github.io/oars/
  • asv-developer-info-missing
    classified-ads.appdata.xml -
    This component contains no `developer` element with information about its author.

classified-ads.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata.
    We currently took some data from its desktop-entry file and the long description of 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.
    Additionally, a lot of software with desktop-entry files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be tagged accordingly via MetaInfo files.
    Please consider to either hide this desktop-entry file from AppStream by adding a X-AppStream-Ignore=true field to it, or to write a MetaInfo file for this component and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software may vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers) in a future distribution release.
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug with the upstream author of this software component.