⇦ | paraview [main]
Last updated on: 2023-11-14 08:15 [UTC]

Hints for paraview in main

org.paraview.paraview ⚙ amd64

Warnings

  • asv-spdx-license-unknown
    :6 - BSD
    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.
  • screenshot-download-error
    Error while downloading screenshot from 'http://www.paraview.org/wp-content/uploads/2014/04/full_AlegraVV.png': URL was not found on the server.
    This might be a temporary server issue, or the screenshot is no longer available.
  • screenshot-download-error
    Error while downloading screenshot from 'http://www.paraview.org/wp-content/uploads/2014/04/seismic.jpg': URL was not found on the server.
    This might be a temporary server issue, or the screenshot is no longer available.
  • screenshot-download-error
    Error while downloading screenshot from 'http://www.paraview.org/wp-content/uploads/2014/04/full_PolarVortexBreakdown.png': URL was not found on the server.
    This might be a temporary server issue, or the screenshot is no longer available.
  • screenshot-download-error
    Error while downloading screenshot from 'http://www.paraview.org/wp-content/uploads/2014/04/full_hydrodynamic_simulation.png': URL was not found on the server.
    This might be a temporary server issue, or the screenshot is no longer available.
  • screenshot-download-error
    Error while downloading screenshot from 'http://www.paraview.org/wp-content/uploads/2014/04/0_full_Fire.png': URL was not found on the server.
    This might be a temporary server issue, or the screenshot is no longer available.

Hints

  • asv-screenshot-media-url-not-secure
    :29 - http://www.paraview.org/wp-content/uploads/2014/04/full_AlegraVV.png
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-screenshot-media-url-not-secure
    :33 - http://www.paraview.org/wp-content/uploads/2014/04/seismic.jpg
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-screenshot-media-url-not-secure
    :37 - http://www.paraview.org/wp-content/uploads/2014/04/full_PolarVortexBreakdown.png
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-screenshot-media-url-not-secure
    :41 - http://www.paraview.org/wp-content/uploads/2014/04/full_hydrodynamic_simulation.png
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-screenshot-media-url-not-secure
    :45 - http://www.paraview.org/wp-content/uploads/2014/04/0_full_Fire.png
    Consider using a secure (HTTPS) URL to reference this screenshot image or video.
  • asv-url-not-secure
    :49 - http://paraview.org/
    Consider using a secure (HTTPS) URL for this web link.
  • asv-content-rating-missing
    -
    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/

paraview.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.