[Peter Blackman]
> checking a few installed on my system
I had a look at two of them, first tried atril but lacked the required
disk space to build it, so ended up building two smaller packages and
running 'appstreamcli validate-tree debian/<packagename>' to see what
the issue is.
> mp3guessenc
mp3guessenc.metainfo.xml
W: io.sourceforge.mp3guessenc.mp3guessenc:~: metainfo-filename-cid-mismatch
> tkinfo
tkinfo.appdata.xml
I: de.uni_paderborn.math_.tkinfo:17: url-not-secure
http://math-www.uni-paderborn.de/~axel/tkinfo/
I: de.uni_paderborn.math_.tkinfo:18: url-not-secure
http://math-www.uni-paderborn.de/~axel/tkinfo/README-tkinfo-2.11.txt
I: de.uni_paderborn.math_.tkinfo:30: screenshot-media-url-not-secure
http://math-www.uni-paderborn.de/~axel/tkinfo/tkinfo.gif
W: de.uni_paderborn.math_.tkinfo:~: metainfo-filename-cid-mismatch
If your appstreamcli validate-tree do not report this, I suspect there
is something wrong with it. I'm using the one from appstream version
0.16.1-2.
In any case, the cid mismatch issue is a fatal one, as far as I know,
and will cause the entry to not make it into the Appstream database.
The 'I' (information/hint) issues are not fatal, and will not trigger a
lintian issue either.
<URL:
https://www.freedesktop.org/software/appstream/docs/chap-Validation.html#asv-metainfo-filename-cid-mismatch
>
got some hints on how to fix it. File name and 'id' tag must have
common base.
> On doing my own random checks, I'm finding several on the above
> (affected=yes) list do indeed have some Appstream issues, but would
> seriously question whether they merit a lintain tag at Warning
> severity. IMHO Info, or even Pedantic would be more appropriate.
Please be more specific. I do not know which Appstream issues you see,
and can thus not provide any insight about their severity levels.
--
Happy hacking
Petter Reinholdtsen
