Fix the Flatpak build (appstreamcli compose fails)
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, python, xml
- Domain
- build-system, ci-cd, release
Research direction
Start by checking build-aux/flatpak/io.gknowledge.Gknowledge.yaml, data/io.gknowledge.Gknowledge.metainfo.xml, and the Flatpak job in .github/workflows/release.yml to trace how the MetaInfo file reaches appstreamcli compose. Run the release build or the relevant Flatpak compose step to reproduce the file-read-error. Done means the release workflow attaches a working .flatpak bundle.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- Python
- Stars
- 13
- Forks
- 0
- Avg merge
- 17m
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openapi/gknowledge
-
area: ui good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
openapi/gknowledge#19 ·
-
area: ui good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
openapi/gknowledge#13 ·
-
area: ui good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openapi/gknowledge#11 ·
-
area: ui good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
openapi/gknowledge#10 ·
-
area: ui good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
openapi/gknowledge#8 ·
All issues in openapi/gknowledge
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Deltares/imod-python#1940 ·
Maintainers usually reply within 1 day
-
effort: low prio: low ready
Difficulty 1/5 Under an hour Newbie friendliness 82/100
digitalfabrik/integreat-cms#4621 ·
Maintainers usually reply within 5 days
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
netbox status: backlog topic: testing type: housekeeping
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
netbox-community/netbox#23395 ·
Maintainers usually reply within 1 day