Skip to content

Brew bundle appears stuck after `Using` lines

Source: Troubleshooting reference

Symptom: bootstrap prints its package inventory, ending in a line such as Using surrealdb/tap/surreal, then produces no visible build output.

Root cause: current Homebrew Bundle lists satisfied and actionable entries before running one batched install. Without --verbose, it captures that child’s output and can discard it on success. The last inventory line does not identify the running package or prove the process is hung.

Confirm: on Linux, inspect the original bootstrap’s descendants:

Terminal window
pgrep -af 'bootstrap.sh'
pstree -ap BOOTSTRAP_PID

A compiler beneath brew establishes an active build. A different installer means Bundle has already returned. If the tree names google-mcp.py, check Python’s cache lock wait.

Fix: the Linux and macOS package installers now pass --verbose to Bundle, including Linux’s single verified retry. After the original process exits, rerun ~/dotfiles/bootstrap.sh upgrade with the updated sources. This exposes build output; it does not shorten a build or bypass dependency checks. Sources: Homebrew Bundle, linux-packages.sh, and homebrew.sh.