Skip to content

Conversation

fpiesche
Copy link
Contributor

@fpiesche fpiesche commented Mar 23, 2025

This is currently failing due to an unnecessary metadata file in the Flatpak build repo which is missing screenshots. I've craeted a PR over there to remove this if that's okay with the person who contributed it; once that gets merged the Flatpak CI builds will pass here :)

The build does a clever thing where it uses the Flatpak repo as is, thus providing early warning if changes will break the Flatpak builds. To do this, just before building the Flatpak packages it'll patch the manifest to build the latest commit on whatever repository is actually triggering the build; in a PR that should always be the commit on the repo and branch to be merged so those changes are going to get built against whatever the current stable Flatpak build manifest is :)

Comment on lines +73 to +74
sed -i "s!luciusDXL/TheForceEngine!${{ github.repository }}!" io.github.theforceengine.tfe.yml && \
sed -i "s/tag: v.*/commit: ${{ github.sha }}/" io.github.theforceengine.tfe.yml
Copy link
Contributor

@JakeSmarter JakeSmarter Mar 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For better readability and manageability I would like to see this patching externalized into a file. Unfortunately, the workflows infrastructure does not provide a programmatic file editor. Anyhow, you could condense these two sed scripts into one call:

sed -i "s!luciusDXL/TheForceEngine!${{ github.repository }}!;\
        s/tag: v.*/commit: ${{ github.sha }}/" \
    io.github.theforceengine.tfe.yml

😉

Comment on lines +81 to +82
flatpak-builder --install-deps-from=flathub \
build --force-clean --install --user io.github.theforceengine.tfe.yml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like below, you may want to use the latest flatpak-builder from Flathub’s org.flatpak.Builder here as well.

Besides, does not flatpak-builder-lint run on every flatpak-builder build command anyway?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants