Skip to content

roster 0.7.11 - #57

Merged
2styx2 merged 10 commits into
mainfrom
dev
Nov 10, 2026
Merged

2styx2 merged 10 commits into
mainfrom
dev

Conversation

@2styx2

@2styx2 2styx2 commented Nov 10, 2026

Copy link
Copy Markdown
Owner

roster 0.7.11

Install on a fresh machine, with every dependency (source only):

curl -fsSL https://raw.githubusercontent.com/2styx2/roster/main/scripts/bootstrap.sh -o bootstrap.sh
less bootstrap.sh && sh bootstrap.sh

Since 0.7.9:

  • Every error is a plain one-line message, often with a hint: line saying what to do. Raw bw, keyctl, sudo, ssh, curl and fzf output no longer reaches the terminal.
    • vault: wrong master password, no vault item named "X", several vault items match "X", keyring and keyutils problems.
    • sudo: sudo rejected the password from bw:ITEM, sudo needs a password, each with the roster.yml fix.
    • ssh: can't reach, can't resolve, nothing listening, key or password not accepted, host key changed (the ssh-keygen -R line is shown, never run).
    • web: nothing listening, untrusted certificate, login refused (HTTP 401); secrets stay masked.
    • Inventory: where roster looked, and FILE:LINE: not valid YAML.
    • pick: fzf missing or failing, tmux unable to open a window.
    • File errors drop (os error N); usage errors end with a hint.
  • roster vault unlock works on WSL and after su (0.7.10). The session key is stored from a fresh session keyring, so keyctl setperm no longer fails.
  • make deps and bootstrap: a full upgrade on Arch before installing, and downloads retry.

Note: run now holds a Host's stderr until its stdout starts or it ends; --json still carries ssh's raw stderr.

Found on WSL: `roster vault unlock` said keyctl setperm failed. Its
default session keyring is the user-session keyring, whose keys the
process doesn't possess, so a key added there can't have its permissions
set (0.7.6 moved the add there to fix su, where @U had the same problem).
unlock now runs the whole store in a new session keyring (keyctl session
-), whose keys are always possessed: added, permissions and timeout set,
linked into @U, unlinked; any failure invalidates the key. Checked with
the real keyctl on WSL and after su. Version 0.7.10.
CI found both on a fresh container: Arch supports no partial upgrades, so
pacman -Sy then -S broke on an openssl transition; both scripts now use
pacman -Syu. A GitHub 500 on the bw download failed the whole install;
the fzf and bw downloads now retry (3 times, on any error).
vault unlock: store the key from a new session keyring (WSL); 0.7.10
src/errors.rs turns another program's stderr into one line of roster's
own, with a hint line when there is a next step. bw's output no longer
reaches the terminal: a wrong master password, a missing item, several
matches or a locked vault each get a message. A keyring that won't take
the session key says why. In run, a Host's stderr is held until its
stdout starts or it ends, so ssh's and sudo's failures are told plainly;
the command's own stderr still shows, labelled. check gives the same
reasons, one line per Host.
A Host setup can't reach, whose password or Box key isn't accepted, or
whose host key changed, gets the same message and hint as run. The Mesh
and undo scripts' failures show their last line, with the Windows hint
on a line of its own. ssh-keygen's output is captured; file errors drop
their (os error N). "N Hosts not done" names the command and hints at
the rerun.
curl's errors are collected instead of printed, and told by its exit
code: a name that won't resolve, nothing listening, a timeout, an
untrusted certificate (with the verify: false / -k hint), an empty
reply. HTTP 401 and 403, from the request or the token login, read
"login refused", with a hint. The password stays masked.
No Inventory names where roster looked and how to name one; a missing
-c or ROSTER_CONFIG file says so without an OS error code, with the
lookup order as a hint. Bad YAML puts the line up front like every other
Inventory error. A usage error's "(see roster -h)" becomes a hint line;
an unknown command points at `roster help plugins` too.
fzf or tmux missing or failing in the picker, ssh missing, an unknown
Host, an auth: cmd: that fails, no terminal to ask on, and a locked vault
during sync's import each get one line and a hint where there's a next
step. tmux's stderr is captured; fzf keeps the terminal, as ssh does.
File errors in add drop their (os error N).
roster.1 gets a DIAGNOSTICS section listing each message and its hint,
and run and web say where their failures are told. The tutorial's
troubleshooting table matches the new messages.
Nice errors: one plain line, and a hint
@2styx2
2styx2 merged commit ed09c29 into main Nov 10, 2026
16 checks passed
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