fix: retain exact APT configure action without pending package repair
Rust development slice / linux (push) Failing after 6s
Rust development slice / linux (push) Failing after 6s
This commit is contained in:
@@ -1,5 +1,23 @@
|
||||
# Root-helper APT transaction provider / explicit first native acceptance
|
||||
|
||||
**Current 2026-11-13:** Cloud fixture retry reached armed hook and APT exit 0,
|
||||
but independent verification found an unpacked/unconfigured package; outcome
|
||||
remains **unknown**, with all original/retry tombstones and ledger preserved.
|
||||
No native acceptance record, package repair or further retry. Root test policy
|
||||
closed. Detailed real evidence: `../../docs/implementation-status.md`.
|
||||
|
||||
Source configuration now disables APT's `dpkg::selection::remove::approved`
|
||||
rewrite, retaining the exact package's Configure operation while both pending
|
||||
modes remain disabled and hook-pinned. Upstream explanation:
|
||||
[APT 2.7.14 dpkgpm.cc](https://github.com/Debian/apt/blob/2.7.14/apt-pkg/deb/dpkgpm.cc#L1626-L1657).
|
||||
Local actual APT 2.6.2 regression in an offline readonly unprivileged container
|
||||
proved unpack + exact `--configure rmm-mvp-test:all`, no `--pending` or foreign
|
||||
target; independent dpkg guard simulated effects, real/copied status unchanged.
|
||||
67 Python tests passed with this opt-in regression. **This source correction
|
||||
is not deployed or natively accepted on the Cloud VM.** No automatic repair,
|
||||
marker reset or implicit unknown-resolution is introduced. Older sections below
|
||||
describe historical increments; current operational status is the linked log.
|
||||
|
||||
Current dedicated runner/probe/profile/agent integration and executed local
|
||||
checks: [`../../deploy/linux/apt-helper-README.md`](../../deploy/linux/apt-helper-README.md).
|
||||
The general helper unit remains unchanged; actual native VM measurements are
|
||||
|
||||
Reference in New Issue
Block a user