diff options
| author | Hermes Agent <hermes@localhost> | 2026-08-12 08:42:11 +0000 |
|---|---|---|
| committer | Hermes Agent <hermes@localhost> | 2026-08-12 08:42:11 +0000 |
| commit | accfdafe37212a4656033c728cd03f4ed6936eb5 (patch) | |
| tree | ccbc35ef28ab180947992060e412017a99c493c2 /docs/legacy-comparison.md | |
| parent | 2e334d04573fd7a4b7e9eadc4f7d86d56a630a63 (diff) | |
Record native build cleanup verification
Diffstat (limited to 'docs/legacy-comparison.md')
| -rw-r--r-- | docs/legacy-comparison.md | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/docs/legacy-comparison.md b/docs/legacy-comparison.md index bcd98c3..97246a8 100644 --- a/docs/legacy-comparison.md +++ b/docs/legacy-comparison.md @@ -82,14 +82,17 @@ without invoking GNU Make, `mkimage`, or `mkimage-profiles`, but this host does not permit Hasher's installed privilege helper to run. Exact command evidence: ```text -$ ./target/release/alt-controller-image build --spec profiles/alt-controller.toml --workspace /mnt/hermes-workspace/alt-controller-native-work-20260812 --output /mnt/hermes-workspace/alt-controller-native-20260812.tar +$ ./target/release/alt-controller-image build --spec profiles/alt-controller.toml --workspace /mnt/hermes-workspace/alt-controller-native-work-20260812-tick --output /mnt/hermes-workspace/alt-controller-native-20260812-tick.tar hsh: /usr/libexec/hasher-priv/getconf.sh: cannot access getconf helper. error: hsh exited with exit status: 1 +build_exit=1 cleanup_exit=0 ``` -No workspace, tarball, or companion manifest was produced, so no native versus -legacy semantic comparison can honestly be recorded yet. The next corrective -action is to run the same native CLI build in an environment where the host's -Hasher privilege helper is usable (or have the host Hasher installation repaired), -then inspect its generated companion manifest and compare it with the observed -legacy Controller tarball. +`cleanup_exit=0` verifies that the executor removed the newly created workspace +and that no tarball or companion manifest remained after the failed installer. +No native artifact was produced, so no native-versus-legacy semantic comparison +can honestly be recorded yet. The next corrective action is to run the same +native CLI build in an environment where the host's Hasher privilege helper is +usable (or have the host Hasher installation repaired), then inspect its +generated companion manifest and compare it with the observed legacy Controller +tarball. |