Skip to content

ci: let CI update the Flatpak SDK so publishing stops crashing - #25

Merged
TB516 merged 2 commits into
mainfrom
ci/flatpak-volume
Nov 18, 2026
Merged

TB516 merged 2 commits into
mainfrom
ci/flatpak-volume

Conversation

@TB516

@TB516 TB516 commented Nov 18, 2026 •

Copy link
Copy Markdown
Owner

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-builder crashes.

Both workflows now mount /var/lib/flatpak as 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-builder copied 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 set gc.autoDetach false, so git finishes that cleanup before the fetch returns.

…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.
@TB516
TB516 merged commit 5f69704 into main Nov 18, 2026
2 checks passed
@TB516
TB516 deleted the ci/flatpak-volume branch November 18, 2026 23:39
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.

1 participant