ci: install rpm + libarchive-tools on Linux CI runners (unbreaks #98 regression)#101
Merged
Conversation
PR #98 added rpm + pacman targets to electron-builder.yml without updating the CI workflows that run `npm run build` on ubuntu-latest. electron-builder shells out to fpm → bsdtar for the pacman target and to rpm for the rpm target — both binaries are not on the stock ubuntu-latest image. Result: every Desktop CI and Android CI run since 2026-05-20 (commit 4679cc8) has been red with `fpm process failed 1` / `bash exit 127` deep inside the pacman packaging step. desktop-release.yml already installs both packages (line 68); this commit mirrors that step into the four workflows that were missing it: - desktop-ci.yml (per-push verification) - android-ci.yml (bundleWebUi → build-web-ui.sh → npm run build) - android-test-build.yml (workflow_dispatch parity build) - desktop-test-build.yml (workflow_dispatch matrix; only Linux slot) No code or build-output change — purely a runner-environment fix. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
First push of #101 hit a fresh failure: ubuntu-latest's cached package index pointed to libarchive-tools_3.7.2-2ubuntu0.6 but the mirror had already rolled to a newer version, so the bare apt-get install died with HTTP 404 / exit 100 in <20s. Prepend `apt-get update` so we always resolve against the current index. Applied to all four workflows touched in this PR. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Master CI has been red since PR #98 (`4679cc89`, 2026-05-20) — both Desktop CI and Android CI failing the same way:
```
{message: "Process failed: /bin/bash failed (exit code 127). Full command was:
["/bin/bash", "-c", "LANG=C bsdtar -czf .MTREE ..."]"}
⨯ fpm process failed 1
```
PR #98 added `rpm` and `pacman` targets to `desktop/electron-builder.yml` `linux.target`, and updated `desktop-release.yml` to install `rpm` + `libarchive-tools` (which provides bsdtar) before the build — but missed the four other workflows that also run `npm run build` on `ubuntu-latest`. So every CI run since hit pacman packaging with no bsdtar on the runner → exit 127.
This PR mirrors release.yml's setup step into:
No application code or build-output change. Pure CI runner-env fix.
Failure baseline
Last green master CI: `1f9af7da` (PR #97). Every push after PR #98 has been red on both CI workflows with the same trace. Verified via:
```
gh run list --workflow=desktop-ci.yml --branch=master --limit=5
```
Test plan
🤖 Generated with Claude Code