[BUG] Crypto dependency update leaves Cargo source catalog behind #121

Open
opened 2026-10-14 15:25:58 +02:00 by erikinkinen · 1 comment
Owner

Summary

The component and Cargo source catalogs select different revisions of E2fsd, LibFsCrypto and LibAES. The component rustdoc check stops before the remaining builds and VM checks.

Reproduction

Run CI 2612 at 7d2b8d95b8d99ae47796810b267d818145f488cc. The failing step runs check-rustdoc-policy.py with components.toml and cargo-repos.toml.

Expected and actual behavior

Both catalogs must identify the same source for each shared repository. Instead, the check reports e2fsd: component/Cargo revision identity differs. Comparing the complete catalogs finds three mismatches:

Repository Component revision Cargo catalog revision
E2fsd c0b9ce7f a6c39b7b
LibFsCrypto 283b30be 945a00b3
LibAES aed2eef2 e96f1e47

Environment and identity

Linux 6.14.0-1-pve, x86-64 Docker integration job. The selected E2fsd manifest already pins LibFsCrypto 283b30be, whose manifest pins LibAES aed2eef2; the stale selections are in Integration's Cargo source catalog. The last complete passing workflow for this graph is not established here.

Evidence and prior checks

The linked run gets past the repaired clang prerequisite and native C runtime cases. Its Rust and Markdown jobs pass. The complete integration log retains the first catalog mismatch; inspection of both catalogs identifies the other two.

Tracking

Clang prerequisite, repository audit, implementation PR, phase completion.

  • Align all three Cargo catalog entries with the selected component revisions.
  • Check the complete catalog coverage while preserving strict identity checks and existing manifest pins.
  • Complete the original integration workflow with the corrected graph.
## Summary The component and Cargo source catalogs select different revisions of E2fsd, LibFsCrypto and LibAES. The component rustdoc check stops before the remaining builds and VM checks. ## Reproduction Run [CI 2612](https://git.erikinkinen.fi/erix/integration/actions/runs/2612) at `7d2b8d95b8d99ae47796810b267d818145f488cc`. The failing step runs `check-rustdoc-policy.py` with `components.toml` and `cargo-repos.toml`. ## Expected and actual behavior Both catalogs must identify the same source for each shared repository. Instead, the check reports `e2fsd: component/Cargo revision identity differs`. Comparing the complete catalogs finds three mismatches: | Repository | Component revision | Cargo catalog revision | | --- | --- | --- | | E2fsd | `c0b9ce7f` | `a6c39b7b` | | LibFsCrypto | `283b30be` | `945a00b3` | | LibAES | `aed2eef2` | `e96f1e47` | ## Environment and identity Linux 6.14.0-1-pve, x86-64 Docker integration job. The selected E2fsd manifest already pins LibFsCrypto `283b30be`, whose manifest pins LibAES `aed2eef2`; the stale selections are in Integration's Cargo source catalog. The last complete passing workflow for this graph is not established here. ## Evidence and prior checks The linked run gets past the repaired clang prerequisite and native C runtime cases. Its Rust and Markdown jobs pass. The complete integration log retains the first catalog mismatch; inspection of both catalogs identifies the other two. ## Tracking [Clang prerequisite](https://git.erikinkinen.fi/erix/integration/issues/120), [repository audit](https://git.erikinkinen.fi/erix/integration/issues/11), [implementation PR](https://git.erikinkinen.fi/erix/integration/pulls/12), [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Align all three Cargo catalog entries with the selected component revisions. - [x] Check the complete catalog coverage while preserving strict identity checks and existing manifest pins. - [ ] Complete the original integration workflow with the corrected graph.
Author
Owner

Commit 9d76db96 aligns the three Cargo catalog entries. Both full-catalog checks pass, and each original mismatch still fails independently. The new workflow will check the remaining build and VM stages.

[Commit 9d76db96](https://git.erikinkinen.fi/erix/integration/commit/9d76db96c4ec17452352377f401060287417d0e2) aligns the three Cargo catalog entries. Both full-catalog checks pass, and each original mismatch still fails independently. The new workflow will check the remaining build and VM stages.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:16 +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/integration#121
No description provided.