Skip to content

the .deb ships no dign binary — documented dign capsule fetch is command-not-found on a package install #316

Description

@MichaelTaylor3d

Task

The .deb ships no dign binary. dpkg -L on a package install lists only /usr/bin/dig-node.

The verb exists — dig-node capsule fetch works — but every doc, runbook and issue that names dign capsule fetch is wrong for anyone who installed from the package rather than from source. A person following the documented command gets command not found and has no way to know the binary is simply named differently.

Evidence

Observed on a package install of dig-node 0.141.0 during the three-machine capsule-warm run (https://github.com/DIG-Network/dig_ecosystem/issues/3128). This is the shape of #857, still true at 0.141.0.

Context

Parent epic: https://github.com/DIG-Network/dig_ecosystem/issues/3128
Prior: https://github.com/DIG-Network/dig-node/issues/857

Scope

Either ship dign in the package (a symlink or a second bin target), or correct every doc that names it. Prefer shipping it: dign is the name used across docs.dig.net and the ecosystem's own issues, so renaming the documentation is the larger and more error-prone change.

Evidence bar

dpkg -L on a built package lists the dign path, asserted by the packaging test rather than by hand.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions