Instead of copy-pasting %check desktop-file-validate %{buildroot}%{_datadir}/applications/*.desktop appstream-util validate-relax --nonet %{buildroot}%{_datadir}/appdata/*.appdata.xml ... to each and every GUI app's spec file, would be nice if this happened automatically. I'm attaching the patch discussed in the devel ML here to avoid drowning in the mailing list noise. Original discussion in https://lists.fedoraproject.org/pipermail/devel/2014-September/202711.html and https://lists.fedoraproject.org/pipermail/devel/2014-October/202846.html
Created attachment 943695 [details] [PATCH] Run desktop file and appdata validation scripts if they exist
Created attachment 943696 [details] brp script that desktop-file-utils would ship
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Sorry, this got dropped. Is this still planned? Is the brb script already in place? (Couldn't find it on my system)
No worries, thanks for looking at it Florian! I'd be great to move forward with this. The brp scripts are not in place yet - I wanted to hear someone's thoughts from redhat-rpm-config side first. Could easily add them now though if you think they look roughly sane? attachment 943696 [details] has a brp script sample that would go to desktop-file-utils; the one that would run appdata validation would be pretty much the same, with just a different binary name to execute.
Hmm, shipping this brb file else where does not make much sense to me as it barely contains anything. So I'd rather check for the presence of desktop-file-validate. The question is how can we make sure that desktop-file-utils is installed/added as build requires. May be we should also sto the build if it is not there. But that might need some more discussion and probably doing a rough estimate how many package this will break.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.