diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-19 13:20:05 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-19 13:20:05 -0500 |
| commit | 4e2d8006215da6f5b08c1de360d7cb842ca8de95 (patch) | |
| tree | 479d200070d7c3bc4e5d4e3390f7d772290c4a37 /README.md | |
| parent | a33eb10faddba2595deba81f52f89352255f1cf2 (diff) | |
| download | archsetup-4e2d8006215da6f5b08c1de360d7cb842ca8de95.tar.gz archsetup-4e2d8006215da6f5b08c1de360d7cb842ca8de95.zip | |
chore: log AUR exit-0 fix verification and close the sub-task
Two updates in todo.org. I marked the two dconf entries in the `[#B] Fix install errors` parent body as RESOLVED in `296bd5f`, since the system-wide dconf db migration verified clean in last night's VM run.
I converted the `*** TODO [#B] AUR exit-0 logged as error` sub-task into a dated event-log entry. The root cause was a bash if-compound semantics trap in `retry_install` (the if-compound exits 0 when no condition tested true, overwriting the eval's actual exit code that `last_exit_code=$?` was trying to capture). Today's VM run verified the fix: `mkinitcpio-firmware` and `tidaler` now report `error code: 1` instead of the misleading `error code: 0`.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions
