Mattia Verga píše v Ne 17. 01. 2016 v 20:51 +0100:
> Il 17/01/2016 18:58, Richard Hughes ha scritto:
> > Are you using non-breaking UTF-8 spaces perhaps? Have a look in
> > vim
> > and see if it has lots of control chars showing. At the moment
> > even
> > xmllint won't validate it. Richard.
> T
On 17 January 2016 at 19:51, Mattia Verga wrote:
> Do also addons metainfo.xml files need to be validated in .spec file? I
> can't find anything about that on Packaging Guidelines.
Up to you; Kalev did try and get this validation automatic when
building rpms in koji. Kalev, did we stall on someth
Il 17/01/2016 18:58, Richard Hughes ha scritto:
Are you using non-breaking UTF-8 spaces perhaps? Have a look in vim
and see if it has lots of control chars showing. At the moment even
xmllint won't validate it. Richard.
Thanks, yes. That was the problem.
Using validate-relax now is ok.
Do als
On 17 January 2016 at 09:44, Mattia Verga wrote:
> Just curious: how can a metainfo.xml file be validated?
> I tried to use also appstream-util validate-relax, but it always fail:
> $ appstream-util validate-relax blenderplayer.metainfo.xml
> blenderplayer.metainfo.xml: failed to parse blenderplay
Just curious: how can a metainfo.xml file be validated?
I tried to use also appstream-util validate-relax, but it always fail:
$ appstream-util validate-relax blenderplayer.metainfo.xml
blenderplayer.metainfo.xml: failed to parse blenderplayer.metainfo.xml:
Errore alla riga 2 carattere 2: Il docu
Based on the Workstation wiki related to appdata addons[1], I created
each metainfo.xml for the missing addons including for some applications
like Blender.[2]
Nearly all on them are associated with the related applications and it
is a matter of filling the missing informations. Each metainfo.xml