[BUG] Dynamic-link inventories omit realm clients and current dependencies #109

Closed
opened 2026-10-12 18:23:04 +02:00 by erikinkinen · 1 comment
Owner

Summary

Two maintained Posixd client executables have no dynamic-link migration entries, so Integration CI stops at executable discovery. The published dependency metadata also omits those clients and retains older dependency lists for several changed manifests.

Reproduction

At Integration 0579c15ae294b01dd26dd06e0892dde25d6f4a9a, fetch its exact catalogs and run:

python3 scripts/check-dynlink-executable-inventory.py
python3 scripts/check-dynlink-dependency-closure.py

Expected and actual behavior

Every discovered executable needs an explicit migration classification and its actual declared dependency closure. Instead, discovery exits 1 for realm-binding-client and realm-pipe-client. Independent closure checking also finds missing client records and stale dependency/digest pairs for 12 targets.

Environment and identity

Linux host with the signed component catalogs, including Posixd 4462a514289d74cfaaeb764d530e07346ca03a5a. These are metadata gates before guest execution; no guest authority is involved. The missing target entries also occur at the preceding Integration revision.

Evidence and prior checks

Integration CI 2477 fails at the two discovered client entries after passing the ext corpus check. Reading the same signed manifests separately identifies the stale dependency rows. No working revision of the complete current inventory is known.

Tracking

Register both clients in the gated realm wave, derive records from their actual manifests and retain missing-entry, digest and static-bundling refusals. Phase 6 tracking.

## Summary Two maintained Posixd client executables have no dynamic-link migration entries, so Integration CI stops at executable discovery. The published dependency metadata also omits those clients and retains older dependency lists for several changed manifests. ## Reproduction At Integration `0579c15ae294b01dd26dd06e0892dde25d6f4a9a`, fetch its exact catalogs and run: ```sh python3 scripts/check-dynlink-executable-inventory.py python3 scripts/check-dynlink-dependency-closure.py ``` ## Expected and actual behavior Every discovered executable needs an explicit migration classification and its actual declared dependency closure. Instead, discovery exits 1 for `realm-binding-client` and `realm-pipe-client`. Independent closure checking also finds missing client records and stale dependency/digest pairs for 12 targets. ## Environment and identity Linux host with the signed component catalogs, including Posixd `4462a514289d74cfaaeb764d530e07346ca03a5a`. These are metadata gates before guest execution; no guest authority is involved. The missing target entries also occur at the preceding Integration revision. ## Evidence and prior checks [Integration CI 2477](https://git.erikinkinen.fi/erix/integration/actions/runs/2477) fails at the two discovered client entries after passing the ext corpus check. Reading the same signed manifests separately identifies the stale dependency rows. No working revision of the complete current inventory is known. ## Tracking Register both clients in the gated realm wave, derive records from their actual manifests and retain missing-entry, digest and static-bundling refusals. [Phase 6 tracking](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

The fix registers the two original clients and derives all 55 dependency records from the selected signed manifests, including the 12 stale rows. Both actual inventory checkers pass and independently refuse either missing client row. The realm wave remains gated; its native acceptance requirements and sole Bootloader static exception are unchanged.

The [fix](https://git.erikinkinen.fi/erix/integration/commit/5cdd151b807b2e3bfc914d58c40fb7da413eb49c) registers the two original clients and derives all 55 dependency records from the selected signed manifests, including the 12 stale rows. Both actual inventory checkers pass and independently refuse either missing client row. The realm wave remains gated; its native acceptance requirements and sole Bootloader static exception are unchanged.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39: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#109
No description provided.