GUIDES
Failed installs
A synced package can fail to install on one machine. For example, it does not build on this OS, or Homebrew refuses its name.
What Tether does
- Tether records the failure with the error line of the package manager, and warns once
- It tries the package again after 24 hours, or sooner when the version to install changes
- When
brew bundlefails, Tether installs each remaining formula on its own. Only the formulae that really fail count as failed - Tether drops the failure when the package is installed, by any means
- Tether drops the failure when the package leaves this machine's profile
The list of failures stays on this machine, in ~/.tether/state.json.
See the failures
Terminal
tether packages listtether packages list and the dashboard Packages tab show failed installs with their errors.
Stop a failed install
To stop Tether from installing the package on this machine:
Terminal
tether packages remove <manager:name>Or press x on the package on the dashboard Packages tab. Tether records the package as removed on this machine, clears the failure, and stops installing it here. Other machines keep it. The profile rules are the same as for an installed package. See Packages per profile.
Common causes
- A release newer than the release-age limit: Tether holds an older release in the Inbox as "pinned too new". See Release age
- A version that only another OS can install: Tether holds a release for this OS in the Inbox as "other OS version"
- A cask that needs a password: without a terminal, Tether defers it. The next
tether syncin a terminal installs it