Repository navigation
feat(linux): tarball release, GUI launch opens the surface, glibc 2.28 floor (#168) - #185
Conversation
deckd has no window, so a GUI launch of the AppImage (app menu, file-manager double-click) looked like nothing happened. The launcher now opens the surface in the default browser once /health answers, and when a daemon is already running it just opens the browser and exits instead of failing on the busy port. GUI launch is inferred (no tty + a graphical session); --open / --no-open override it and every autostart path passes --no-open. xdg-open gets the caller's LD_LIBRARY_PATH back, not the frozen bundle's. The relocatable tree now also ships as deckd-<version>-<arch>.tar.gz: no FUSE, a stable install path, and a systemd user service. Its top-level install helper copies the tree to ~/.local/opt/deckd (re-run = upgrade), installs the service, and removes the other channel's autostart on switch. Both install paths add an app-menu entry. The helper gains a DECKD_HELPER_TEST_ROOT sandbox so it is unit-tested without root (sudo/pkexec scrub it). `just build-linux` builds both artifacts from one freeze; the release workflow smoke-tests and uploads both. ADR-0012 amended.
…floor) A PyInstaller bundle needs a glibc at least as new as its build host. The release was frozen on the ubuntu-24.04 runner (glibc 2.39), so both Linux artifacts failed on Ubuntu 22.04 and Debian 12: GLIBC_2.38 not found (required by libpython3.12.so.1.0) `just build-linux-portable` now freezes inside quay.io/pypa/manylinux_2_28 (AlmaLinux 8, glibc 2.28) with Python from python-build-standalone via uv — manylinux's /opt/python builds are static and PyInstaller needs a shared libpython. CI runs the same recipe; the runner only needs Docker. `just test-linux-floor` boots the tarball on debian:10, ubuntu:22.04, debian:12 and fedora:latest. Release CI runs it per arch, and publishing is now a separate job that waits for both arches. The container script zeroes appimagetool's AppImage magic so a host AppImage binfmt handler (NixOS programs.appimage) can't hijack the exec inside the container.
…e race An rc tag (v0.0.0-rc1) must not become the repo's "latest" release. The Linux and macOS workflows both create the release for a tag, so the loser of that race now confirms the release exists instead of failing.
|
Release rehearsal:
The macOS run for the same tag never started ( The only warning: |
GitHub runners force Node 20 actions onto Node 24 with a deprecation warning. Bump each action to its current Node 24 major: checkout v4→v7, setup-node v4→v7, setup-python v5→v7, upload-artifact v4→v7, download-artifact v4→v8, deploy-pages v4→v5, upload-pages-artifact v3→v5 None of the breaking changes apply here: npm caching is already explicit, client/dist has no dotfiles, and no workflow uses setup-python's removed pip-install input. The client now builds on Node 24 LTS everywhere (was 20, EOL April 2026, and 22 for Pages), matching the flox environment. Docs move the stated floor from Node 18+ (EOL) to 22+.
|
Rehearsal 2: |
Part of #168. Three changes to the Linux channel found while preparing the first release.
Summary
1. A GUI launch opens the surface. deckd has no window, so opening the AppImage from the app menu or a file manager looked like nothing happened.
xdg-open gets the caller's
LD_LIBRARY_PATHback, not the frozen bundle's. Every autostart path passes--no-open.2. A tarball beside the AppImage. Same frozen payload, no FUSE, stable path, systemd user service.
3. Release builds run on older distros. A PyInstaller bundle needs a glibc at least as new as its build host, and we were freezing on the runner's Ubuntu 24.04 (glibc 2.39).
Supported: glibc ≥ 2.28, so Debian 10+, Ubuntu 20.04+, RHEL 8+, current Fedora and Arch. Not Alpine or other musl distros.
just build-linuxbuilds both from one freeze (_linux-payload+_stage-linux-integrationare shared). ADR-0012 amended; GUIDE has a new "Linux tarball" section.Evidence
After:
pytestreports 833 passed, 1 skipped (+26test_open_surface.py, +12test_install_helper.py); pyright is clean. Two deliberate mutations of the helper (dropping--no-openfrom the unit, skipping the XDG-autostart removal) each failed a test.just build-linuxlocally on NixOS throughsteam-run:scripts/test_linux_floor.shrun locally against both builds (podman):GLIBC_2.18. The manylinux AppImage also boots on ubuntu:22.04.Merge Danger
Door: two-way
Nothing has been released yet (no
v*tag has ever runrelease-linux.yml), so there are no installs to migrate.Blast Radius: packaging
--no-open, so they would open a browser at login until the helper is re-run. Only dev machines are affected.deckd-linux-appimage-<arch>todeckd-linux-<arch>.quay.io/pypa/manylinux_2_28_*,uv's python-build-standalone download, and Docker Hub images for the floor test. If any of them is unavailable, the release fails before publishing anything.just build-linuxstill freezes against the host's glibc. Usejust build-linux-portablefor anything you hand to someone else.