docs(install-personal): agent-only, arch-pinned package globs (#143)#144
Merged
Conversation
`sudo dnf install ./sigil-*.rpm` matched the fleet packages too (sigil-sender / sigil-server / sigil-signer) and both architectures, so a personal install silently pulled in the server/sender/signer binaries. Use `sigil-[0-9]*.$(uname -m).rpm` — the version starts with a digit, so it excludes the `sigil-<name>` fleet packages, and the arch is pinned. Add the apt equivalent (`sigil_*_$(dpkg --print-architecture).deb`; the agent .deb is `sigil_<ver>` with an underscore, which already excludes the `sigil-…` fleet) that the ".rpm / .deb" heading promised but omitted. Fixes #143 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
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.
Fixes #143.
Problem
docs/install-personal.mdtold personal users to runsudo dnf install ./sigil-*.rpm, but that glob matches all four rpms in a release dir —sigil-0.5.1-1.x86_64.rpm(the agent) plussigil-sender/sigil-server/sigil-signer(the fleet), and both architectures. A personal install silently pulled in the server/sender/signer binaries. Same glob footgun class as #138, in user-facing docs.Fix
Agent-only, arch-pinned, version-agnostic globs:
sigil-[0-9]…— the agent version starts with a digit, so thesigil-<name>fleet packages (letter aftersigil-) are excluded.sigil_<ver>…(underscore) — the agent.debnaming already excludes thesigil-…fleet debs.Verification
Against the real v0.5.1 asset names, the new globs match only the agent package (rpm and deb), while the old
sigil-*.rpmmatched all five (both arches + 3 fleet packages). Docs-only change.🤖 Generated with Claude Code