⇦ | displaycal [main]
Last updated on: 2021-10-24 08:16 [UTC]

Hints for displaycal in main

displaycal-3dlut-maker.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

displaycal-apply-profiles.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

displaycal-testchart-editor.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

net.displaycal.DisplayCAL ⚙ amd64

Warnings

  • translations-not-found
    Unable to add languages information, even though a translation tag was present in the MetaInfo file. Please check that its value is set correctly, and all locale files are placed in the right directories (e.g. /usr/share/locale/*/LC_MESSAGES/ for Gettext .mo files).

Hints

  • asv-content-rating-missing
    net.displaycal.DisplayCAL.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-nonstandard-gnome-extension
    net.displaycal.DisplayCAL.appdata.xml:83 - kudos
    This tag is a GNOME-specific extension to AppStream and not part of the official specification. Do not expect it to work in all implementations and in all software centers.

displaycal-profile-info.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

displaycal-curve-viewer.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

displaycal-synthprofile.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

displaycal-scripting-client.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.

displaycal-vrml-to-x3d-converter.desktop ⚙ amd64

Warnings

  • no-metainfo
    This software component is missing a MetaInfo file to provide metadata about it.
    We currently took some data from its .desktop 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 from .desktop files should either not be installable and searchable via the software catalog (like desktop-specific settings applications) or be properly tagged via MetaInfo files.
    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 and send it upstream.
    Generating components from non-MetaInfo files is deprecated, if you do not add a MetaInfo file, this software will vanish from the metadata catalog (and if it is a GUI application, no longer be visible in software centers).
    You can consult the MetaInfo quickstart guides for more information on how to write a MetaInfo file, or file a bug upstream.