fix: retain exact APT configure action without pending package repair
Rust development slice / linux (push) Failing after 6s

This commit is contained in:
2026-11-13 16:09:03 +01:00
parent 12557394fa
commit a430de7bf0
6 changed files with 205 additions and 2 deletions
+18
View File
@@ -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
+7 -1
View File
@@ -890,6 +890,9 @@ def check_preconditions(transaction, baseline):
def apt_config():
"""Constant bytes: no job string, URL, shell interpolation, global hooks."""
# APT's default selection rewrite erases explicit Configure operations and
# substitutes --configure --pending. Keep the exact target Configure instead
# while both pending modes remain disabled (upstream dpkgpm.cc, APT 2.7.14).
return ('''Dir::Etc::parts "/var/lib/rmm-apt-transaction/active/empty";
Dir::Etc::main "/dev/null";
Dir::Etc::sourcelist "/dev/null";
@@ -920,6 +923,7 @@ APT::Get::allow-Remove-Essential "false";
DPkg::Lock::Timeout "10";
DPkg::ConfigurePending "false";
DPkg::TriggersPending "false";
dpkg::selection::remove::approved "false";
DPkg::Inhibit-Shutdown "false";
DPkg::Use-Pty "false";
DPkg::Pre-Install-Pkgs { "/usr/lib/rmm-apt-transaction/hook"; };
@@ -946,7 +950,9 @@ def check_hook_config(config):
('dpkg::tools::options::' + HOOK + '::infofd', '0'),
('dir::bin::dpkg', '/usr/bin/dpkg'),
('dir::state::status', '/var/lib/dpkg/status'),
('dpkg::configurepending', 'false')):
('dpkg::configurepending', 'false'),
('dpkg::triggerspending', 'false'),
('dpkg::selection::remove::approved', 'false')):
require([value for name, value in config if name.lower() == key] == [expected],
'APT_CONFIG_BINDING')