fix: make the CI ISO build work (pacman keyring init + protobuf/cmake/clang) - #3
Merged
Merged
Conversation
After the findmnt fix let the ISO build proceed, it failed at the
CachyOS keyring step: `pacman-key --lsign-key` needs a local signing
key, which a fresh CI container lacks ("no secret key available to sign
with"). Run `pacman-key --init` first; it's a no-op where the keyring is
already initialized. (Pre-existing — masked until the findmnt fix.)
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The ISO build compiles the workspace, whose lancedb stack (lance-encoding) requires `protoc` at build time. build-iso.yml only installed base-devel, so the cargo build failed ~25 min in with "Could not find protoc". Add protobuf + cmake + clang — the same build-tool set the CI rust job already uses. (Pre-existing: lancedb is pulled via the orchestrator's path dep on indos-context-engine.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
debpalash
changed the title
After the protoc fix, the workspace compiled (47 min) but the parallel indos-shell build failed: build-iso.yml lacked the Wayland/GL libs that the iced shell needs (build-iso.sh builds shell alongside the workspace binaries). Add the same Wayland dep set the `gui` job uses. Also cache ~/.cargo + the workspace/shell target dirs: the uncached release build of the lancedb/lance/datafusion tree takes ~47 min on a 2-core runner, which made every ISO build impractically slow. Co-Authored-By: Claude Opus 4.8 <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.
Third in the chain of ISO-build fixes uncovered after the workspace migration (#1) made the
Build IndOS ISOworkflow actually run onmain.Problem
With the
findmntfix (#2) letting the build proceed past dependency install, it then failed at the CachyOS keyring step:build-iso.shrunspacman-key --lsign-key F3B607488DB35A47, which needs a local pacman signing key. A fresh CI container never ranpacman-key --init, so there's none. (Pre-existing — every prior CI ISO build died earlier at thefindmntstep, so this was never reached.)Fix
Run
pacman-key --initbefore--lsign-key. It generates the master key on fresh hosts and is a no-op where the keyring is already initialized (real CachyOS dev machines).Verification
Dispatched the
Build IndOS ISOworkflow on this branch: it now gets past dependency install and the keyring step into the mainBuild ISOphase (pacstrap + cargo + squashfs) — which also exercises the #2 workspace-binary-path fix.🤖 Generated with Claude Code