Skip to content

GB-078: no release signer is known, so the update refuses

Generated from ops/errors/catalog.yaml by ops/ci/check-error-catalog.py --write; do not edit here. GB-078 is printed by goatbuilder. The same text offline: goat explain GB-078 or goatbuilder explain GB-078.

What it means

goatbuilder update checks SHA256SUMS against the repository whose release workflow signed it. It found none: the working directory is in no checkout whose ops/goatbuilder/goatbuilder.yaml names repo.release_source or repo.source, and this binary was built outside a release workflow, so it names no publisher itself. Nothing was installed.

Why it happens

  • goatbuilder update ran outside a deployment checkout with a locally built binary

What to do

One line per step or alternative:

goatbuilder -C <checkout> update (a checkout whose goatbuilder.yaml names repo.release_source)
install a goatbuilder from a release, which carries its own publisher

Read more

Exit code

goatbuilder exits with 1.