chore(packaging): abandon the Flathub channel - #174
Merged
Conversation
The manifest was never the problem: it built against org.gnome.Platform//50, appstreamcli compose and desktop-file-validate passed, and the Flatpak installed and ran. The submission was. flathub/flathub#9821 was closed automatically for a missing checklist — the description replaced the mandatory template instead of filling it in — and the maintainers labelled it AI Slop. Getting back in means commenting on the closed PR with a video of the app running from the Flatpak, against a submission already marked as low quality. packaging/flatpak/ and scripts/gen-flatpak-manifest.sh are removed rather than left to rot: no CI job exercised them, so nothing would have caught them going stale. packaging/README.md keeps the app-id reasoning, the three deliberate linter exceptions and the submission mechanics, so reviving this means reading one section and one git revert, not starting over.
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
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.
Follows #173, same reasoning applied to the other channel that never went live.
The manifest was never the problem. It built with
flatpak-builderagainstorg.gnome.Platform//50,appstreamcli composeanddesktop-file-validatepassed, and the resulting Flatpak installed and ran.The submission was. flathub/flathub#9821 was closed automatically — "Checklist(s) not completed or missing", because the description replaced the mandatory template instead of filling it in — and the maintainers labelled it AI Slop. The bot forbids opening a replacement PR; the only way back is a comment on the closed one, carrying a video of the app running from the Flatpak on Linux, against a submission already marked as low quality.
What changes
packaging/flatpak/andscripts/gen-flatpak-manifest.share removed. No CI job exercised them, so nothing would have caught them going stale — unlike the MSIX files, whichverify-packagingstill builds.packaging/README.mdrecords why, and keeps what a revival would need: theapp.voltius.Voltiusid reasoning, the three deliberate linter exceptions with their justifications, and thenew-prbase branch requirement.Reviving this is one section of the README and one
git revert, not a restart.