Capture failed apt state and verify architecture-independent packages - #12
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Known apt failures omitted their observed post-state, and architecture-independent packages appeared absent when libapt reported a concrete architecture while dpkg reported
all. Capture state for every known result before persisting its outcome, and match architecture-independent dpkg rows in transaction/configure verification and observation.The helper's status and tri-state effect report remain authoritative. Unknown effects leave intents open, read failures mark observations unavailable, and ambiguous installed rows fail closed. Preserve the plan's package identity for stable before/after comparison. Development version: 0.0.1.12, with version changes in separate commits.
Validation: 881 source assertions passed; R package check reported 0 errors, 0 warnings, 0 notes. Negative controls failed against the old behavior. The real Ubuntu 26.04 canary passed all 68 mutation assertions and independently verified the durable installed, removed, upgraded and half-configured states, authorization matrices, receipt lifecycle, and cleanup.