Merged
Conversation
openjdk25 is only available for flatpak runtime 25.08.
Solve chicken-and-egg problem: `git rev-parse HEAD` will insert the current HEAD sha into the flatpak manifest, which causes a change in the submodule, and will thus show flatpak/flathub submodule as modified. This can be fixed by git -C flatpak/flathub commit -a -m 'superproject updated' git commit -m 'flatpak/flathub updated' flatpak/flathub But now the commit ID will have changed again. Solve this by excluding flatpak/flathub when generating the commit ID.
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello Hervé,
here's what I did to create this PR:
./gradlew --info :flatpak:buildFlatpak- this causes changes inflatpak/flathubflatpak/flathub:org.audiveris.audiveris.metainfo.xml, content fromdocs/_pages/reference/updates.mdbeta-5.7.1on https://github.com/flathub/org.audiveris.audiverisbetabranch (could habe usedmastertoo, here)betabranchgit add flatpak/flathubgit commit -m "flatpak/flathub: Java 25 and 5.7 changes"I'm still waiting for the new build to show up on beta.flathub.org.
Most of these steps could be easily automated in a workflow. The exception is the metainfo generation, which could also be automated I suppose, but that's more difficult and would require some sort of smart markdown processing.
There are flatpak github actionis which can be used to build flatpaks, but AFAICS there is no official workflow for publishing on flathub. I think that's deliberate; they want to require human intervention in the publishing process. That said, some applications like OBS Studio do have automatic workflows for publishing. I'm not sure if that's worth the effort to create, stabilize, and maintain such a workflow.