You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fix the Flatpak build (appstreamcli compose fails) #24
The release workflow builds .deb fine, but the Flatpak job fails in appstreamcli compose with file-read-error on the MetaInfo.
Where to look: build-aux/flatpak/io.gknowledge.Gknowledge.yaml, data/io.gknowledge.Gknowledge.metainfo.xml, .github/workflows/release.yml.
Done when: the release attaches a working .flatpak bundle.
New here? Run make start to open a demo project that restarts on every save, and make test for the core tests. See CONTRIBUTING.md. Comment below to claim the issue.
I'd like to investigate this build failure. I'll reproduce the appstreamcli compose error, inspect the Flatpak manifest and AppStream metadata, and make the smallest change that resolves the validation issue. I'll run the documented packaging checks and include the reproduction details in the change.
The Flatpak job in .github/workflows/release.yml runs with continue-on-error, so the release still goes green and the failure is easy to miss. Reproducing it locally with flatpak-builder --force-clean build-dir build-aux/flatpak/io.gknowledge.Gknowledge.yaml is probably the quickest way in.
The manifest was recently switched from --filesystem=home to portals and has not been verified in a real build yet. If something else turns up while you're in there, feel free to fix it in the same PR.
Running flatpak-builder-lint on the manifest and the build dir would be a nice extra, though it's not required for this issue.
Including the reproduction details in the PR is perfect. Thank you!
Activity
Aaqibhafeezkhan commentedon Oct 13, 2026
I'd like to investigate this build failure. I'll reproduce the appstreamcli compose error, inspect the Flatpak manifest and AppStream metadata, and make the smallest change that resolves the validation issue. I'll run the documented packaging checks and include the reproduction details in the change.
francescobianco commentedon Oct 13, 2026
Thanks again @Aaqibhafeezkhan, this one is yours too 👍
A few pointers that may save you some time:
.github/workflows/release.ymlruns withcontinue-on-error, so the release still goes green and the failure is easy to miss. Reproducing it locally withflatpak-builder --force-clean build-dir build-aux/flatpak/io.gknowledge.Gknowledge.yamlis probably the quickest way in.--filesystem=hometo portals and has not been verified in a real build yet. If something else turns up while you're in there, feel free to fix it in the same PR.flatpak-builder-linton the manifest and the build dir would be a nice extra, though it's not required for this issue.Including the reproduction details in the PR is perfect. Thank you!