On 04/11/2024 19:21, Louis-Philippe Véronneau wrote:
On 2024-10-28 9 h 12 a.m., Peter B wrote:
Package: lintian
Version: 2.119.0
Severity: normal
X-Debbugs-Cc: pe...@pblackman.plus.com
Dear Maintainer,
Since the release of version 2.119.0, the package trackers for many
(possibly all)
packages that have Appstream metadata are showing the warning
"appstream-metadata-validation-failed".
However, the metadata is valid according to
"appstreamcli validate" & "appstream-util validate".
The link in the tag notes
https://wiki.debian.org/AppStream/Guidelines
does not contain any clues as to what might be the problem here.
If these are not false positives,
please provide information on what maintainers are expected to do
about them.
Appstream is an optional upstream feature.
Please consider introducing Appstream related tags at a lower
severity than Warning.
Regards,
Peter
Hi,
Thanks for reporting this issue. The lintian tag message says the
command you should run is ` --no-net` and not `appstreamcli validate`.
Can you try that instead?
As for more information, the wiki page refers to
https://appstream.debian.org/, which seems to give detailed
information about issues flagged.
Cheers,
Hi,
Running `appstreamcli validate-tree --no-net`
gives the response
I: ~:~: dir-no-metadata-found
✔ Validation was successful: infos: 1
The result is always the same irrespective of whether a path to the
source tree,
or the actual metadata file is given as the parameter.
I can't see any reference to 'appstreamcli validate-tree' from your link,
and haven't found any useful information anywhere else.
I mentioned `appstreamcli validate` because it shows that the metadata
is correct.
It is probably a more reliable test than 'appstreamcli validate-tree'
(There is also appstream-util validate, which also shows the metadata is
valid)
Regards,
Peter
