[BUG] Tracked lockfile does not follow the selected immutable manifest graph #3

Open
opened 2026-10-12 13:43:20 +02:00 by erikinkinen · 0 comments
Owner

Summary

Tracked lockfile does not follow the selected immutable manifest graph. Maintained validation cannot reach its intended successful boundary.

Reproduction

At the linked source revision, use the maintained exact Git dependency helper and run cargo build --locked with the workflow toolchain. The original failing source and current repairs are distinct; failures and true exit statuses are retained.

Expected and actual behavior

The maintained source should compile, discover its original controls and complete the specified checks without warnings. The manifest selects newer real Git dependency commits while Cargo.lock still records the previous graph. A locked build refuses to update its input and exits before compilation.

Environment and identity

  • Component repository/revision and Integration source graph: original boot-tool source, original Integration graph.
  • Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report.
  • Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred.
  • Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced.
  • Last known working revision, if known: not established.

Evidence and prior checks

Generate the tracked lockfile from the actual selected manifest graph with explicit canonical Git inputs and registry denial. Preserve --locked and the CI guard. The signed manifest and lockfile fix is 30a83cd5; exact-head CI and warning review are tracked independently.

Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.

Tracking

Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.

## Summary Tracked lockfile does not follow the selected immutable manifest graph. Maintained validation cannot reach its intended successful boundary. ## Reproduction At the linked source revision, use the maintained exact Git dependency helper and run cargo build --locked with the workflow toolchain. The original failing source and current repairs are distinct; failures and true exit statuses are retained. ## Expected and actual behavior The maintained source should compile, discover its original controls and complete the specified checks without warnings. The manifest selects newer real Git dependency commits while Cargo.lock still records the previous graph. A locked build refuses to update its input and exits before compilation. ## Environment and identity - Component repository/revision and Integration source graph: [original boot-tool source](https://git.erikinkinen.fi/erix/boot-tool/commit/52e1f176cc9a883fcfd5ec00692dfeb164d02133), [original Integration graph](https://git.erikinkinen.fi/erix/integration/commit/a615de2f69c25d4575d0c349757a0017082f988b). - Image profile, digest and build/runtime configuration: maintained host validation and selected component workflow; no guest image is claimed by this report. - Hardware or VM, architecture, firmware and toolchain versions: x86_64 host with the workflow-selected toolchain; no hardware or firmware-specific cause is inferred. - Input/session route and granted authority relevant to reproduction: explicit source graph and local validation inputs; no additional runtime authority is introduced. - Last known working revision, if known: not established. ## Evidence and prior checks Generate the tracked lockfile from the actual selected manifest graph with explicit canonical Git inputs and registry denial. Preserve --locked and the CI guard. The signed manifest and lockfile fix is [30a83cd5](https://git.erikinkinen.fi/erix/boot-tool/commit/30a83cd5645a060cca5248edfb0c2bfc43e962bb); exact-head CI and warning review are tracked independently. Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:33:33 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/boot-tool#3
No description provided.