Closed OzarkShepherd closed 8 months ago
This will resolve the following issues for this repository: https://github.com/gramps-project/flatpak/issues/22 https://github.com/gramps-project/flatpak/issues/13
--Sorry, this was meant for flathub and I accidentally asked here.
Am I right in guessing that the metainfo is no longer allowed to be overwritten? This was accepted in the past. Below is the last part of the failed run.
FB: Running: appstreamcli compose --no-partial-urls --prefix=/ --origin=org.gramps_project.Gramps --media-baseurl=https://dl.flathub.org/media --media-dir=/srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH/files/share/app-info/media --result-root=/srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH/files --data-dir=/srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH/files/share/app-info/xmls --icons-dir=/srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH/files/share/app-info/icons/flatpak '--components=org.gramps_project.Gramps,org.gramps_project.Gramps.desktop' /srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH/files Only accepting components: org.gramps_project.Gramps, org.gramps_project.Gramps.desktop Processing directory: /srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH/files Composing metadata... Run failed, some data was ignored. Errors were raised during this compose run: general E: filters-but-no-output org.gramps_project.Gramps E: duplicate-component Refer to the generated issue report data for details on the individual problems. Error: ERROR: appstreamcli compose failed: Child process exited with code 1 FB: Unmounting read-only fs: fusermount -uz /srv/buildbot/worker/build-x86_64-4/build/.flatpak-builder/rofiles/rofiles-qqYNFH program finished with exit code 1 elapsedTime=517.202085
@Nick-Hall Flathub is now blocking the metainfo.xml with translations that I was told to use years ago. I posted about this at the flathub discourse and asked them how to check the metainfo.xml generated by the flatpak compiling, so that I can post that metainfo.xml file for gramps-project review. https://discourse.flathub.org/t/is-using-upstream-metadata-blocked-now/6173
@OzarkShepherd Thanks for asking the question. Let me know if we need to make any changes to our metainfo.xml
file.
barthalion came up with the solution. He gave the directory path to remove the autogenerated metadata before manually installing the other metainfo.xml https://discourse.flathub.org/t/is-using-upstream-metadata-blocked-now/6173 The autogenerated metainfo gave the 5.1.3 version and date, by the way.