Home / Docs / Diagnostics
U7013: No resolution: no release meets a need, or a bound of resolution is exceeded
U7013 reports that there is no resolution, and nothing is written. una ita verify, and every command that loads a package, report U7013 too for a registry package they cannot verify.
Why Una rejects it
una ita lock, una ita update and una ita add resolve a package of edition 0.4 by minimal version selection (ADR 0122 rules 23 to 25, spec/30 §10): for each identity, a source, a name and a major line, the highest of the least versions that the needs reached ask for.
U7013 reports that there is no resolution, and nothing is written:
- No release of an identity is at or above a need.
- A selection must be raised past a yanked, advised or avoided release and no later release qualifies, or the one that would is held back by the cooldown, in which case
una ita auditshows why the release is left. - A pre-release would be selected that no need reached names.
- A release needs its own identity.
- A bound of resolution is exceeded, such as 1,000 needs of one release or 10,000 packages in the build list.
- A source of
sourceswith no place this release can read, since it has no https transport, so a source is read from a mirror directory that Itaoca'smirrors.unalists as afile://URL. - A package whose owner's chain holds an entry of a kind this release does not replay, a recovery, a dispute, a co-signer change, a cancellation, an overruling or a registration with recovery cosigners (spec/30 §14 rule 5, "This release"), which a later release may judge. So no release of that owner is resolved until then, or until the owner registers under a new owner name, with new keys.
- A need of
itaty, whose root metadata is not built into this release, so nothing it serves can be verified, and no registry is ever resolved from a partial or unverified view of it.
una ita verify reports U7013 too for a registry package whose copies match the lock but which it does not verify, since it does not hold the owner's key chain.
Every command that loads a package, una check, una run, una build, una test and the others of spec/30 §9 rule 9, also reports U7013, at the locked package's line of ita.lock, for a registry package it cannot verify offline (ADR 0122, amendment of 2026-11-03):
- Its provenance's checkpoint, signed under an older root version, carries the cosignature of a witness that the last root version retired, and the provenance carries no consistency proof that it is a prefix of a checkpoint signed under that last version, as a provenance of the earlier format
ita-provenance/1never does. - Or the root version this machine has accepted for the registry, which Itaoca keeps as a floor, exists and cannot be read.
The load is never decided on fewer cosignatures, nor without the floor. The command ends with exit code 1.
A program cannot cause U7013 on its own: the provenance is a registry's signed documents, which an example of this text cannot carry, so it has no example of its own, and the conformance cases ita_registry_retired_unproven and ita_registry_retired_no_proof hold them.
How to fix it
When there is no resolution:
- When the release that would qualify is held back by the cooldown, the repair is to wait out the cooldown rather than to skip it, since a recent yank or advisory is when a hurried release is most dangerous.
- Name a release that exists.
- Need a version past one that must be raised.
- Remove the
avoidline that excludes the only one. - Need fewer packages.
- Or list a mirror directory for the source in Itaoca's
mirrors.una.
When a command that loads a package cannot verify a registry package offline:
- The repair is
una ita fetch, which stores the registry's provenance of the newer format beside the earlier one, thenuna ita vendorfor a vendored copy, oruna ita lockat a fresh resolution point. - For a floor, make
registry/<id>/root-versionin Itaoca readable again.