Repository navigation
Package brig-broker in the bundle #27
Description
Problem
A direct install of the runtime bundle has no brig-broker. The bundle packages brig and brigd only, and brig-broker comes from Brig's own installer, which adds it after it replaces the binaries. On a direct install doctor reports:
-- broker brig-broker is not installed, so a run with a route cannot start
So a direct install and a brig.sh/install install differ, and neither installer says so.
Proposed solution
Package brig-broker from the Brig release next to brig and brigd, in the tree's bin, and let the launchers find it there.
Activity
fix(bundle): Package brig-broker from a brig release that has one
pmoust commentedon Oct 30, 2026
A correction: Brig's installer does not fill this gap today either. The v0.4.0 and v0.4.1 release archives carry no
brig-broker, and the first archive with one is the 0.4.2 main-channel prerelease. So this stays open until the bundle pins a brig release that has it. The pull request gets the bundle ready and records the result inpins.env.fix(bundle): Package brig-broker from a brig release that has one
fix(bundle): Package brig-broker from a brig release that has one
pmoust commentedon Oct 31, 2026
rc20 packages it. Its
pins.envreadsBRIG_VERSION=v0.5.0andBRIG_BROKER_INSTALLED=true. On a fresh rc20 user install on Ubuntu 24.04,brig doctorreadbroker: not started; brig starts .../data/bin/brig-broker on the first run with a route. #34 makes a build fail when a brig release has no broker, so this does not come back quietly.