This is a similar situation to ARM build (only) fails due to missing screenshots - #5 by bbhtt but there are a couple of minor differences:
- Tag or Website problem? Even though I could not obtain the xml.gz file in this build because it failed due to the tag check for screenshots, I was able to obtain the xml.gz file from navigating the environment of the same flatpak compiled by Github Actions on my own github. https://github.com/user-attachments/files/20760686/org.gramps_project.Gramps.xml.txt (I added the .txt at the end to force Github to upload it while discussing this problem at the gramps-project Github, so just remove the .txt at the end to open it as an xml). There is a tag to obtain media from gramp-project.org but not specifically the
<screenshots>tag. Is the build failure for Flathub due to screenshot tag method being done differently, or because the website hosting the media is blocked by Github Actions? - Is there a temporary workaround until the apps metainfo generation gets changed in a future update? I suspect that if a change is made to metainfo generation by Gramps, it will be placed in a future update. I have already asked the project head about whether they are willing to change the metainfo generation and when. Is there a workaround available to update Gramps at Flathub until the Gramps metainfo generation is altered at some future point?
Here is the error:
“info”: [
"appstream-missing-screenshots: Catalogue file has no screenshots. Please check if screenshot URLs are reachable"],
“message”: “Please consult the documentation at Flatpak builder lint | Flathub Documentation”
