Repository navigation
ci: let CI update the Flatpak SDK so publishing stops crashing - #25
Merged
Merged
Conversation
…updates work Flatpak can't move a runtime that ships in the CI image aside on the image's layered filesystem, so updating the SDK failed with "Invalid cross-device link" and flatpak-builder crashed.
A background git gc repacked the cached T3 Code mirror while flatpak-builder copied it, so the copy lost a pack file.
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.
Publishing T3 Code v0.1.10 failed, and most validation runs today did too. Before building, CI updates the Flatpak SDK that ships in the container image (25.08.17) to Flathub's current 25.08.20. Flatpak then can't move the old version out of the way on the image's layered filesystem, so the update fails with "Invalid cross-device link" and
flatpak-buildercrashes.Both workflows now mount
/var/lib/flatpakas a volume. Docker fills the volume with the image's installation, and updates there work normally. I reproduced the failure locally in the same image, and the volume fixed it: the SDK updated to 25.08.20 with no errors.With the SDK fixed, the next build hit a second problem: right after fetching,
flatpak-buildercopied its cached T3 Code git mirror while git's automatic cleanup was still repacking it in the background, and a pack file disappeared mid-copy. Both workflows now setgc.autoDetach false, so git finishes that cleanup before the fetch returns.