fix: harden post-install migrations and bundle multi-ABI Python runtimes

- safely migrate historical Bashrc and Log2RAM installations
- align post-install function versions across both flows
- bundle gevent runtimes for CPython 3.11 and 3.13
- select the correct Python ABI at runtime
- validate both supported Proxmox VE Python versions in AppImage workflows
- fix #327, #328 and #331
This commit is contained in:
MacRimi
2026-09-03 11:55:39 +02:00
parent ac09cc24a8
commit 86305cf261
9 changed files with 730 additions and 59 deletions
@@ -106,10 +106,10 @@ ensure_flow_loaded() {
}
# Suppress the Monitor's `service_fail` notifications while this
# wrapper runs. Tools like log2ram or chrony stop and reinstall their
# systemd units, and systemd flags the transient "failed" state
# before the fresh unit starts — same class of noise as PVE services
# restarting during an apt full-upgrade. Shared markers with
# wrapper runs. Some post-install functions legitimately restart their
# services, and systemd can expose a transient "failed" state before the
# fresh unit starts — same class of noise as PVE services restarting
# during an apt full-upgrade. Shared markers with
# scripts/utilities/proxmox_update.sh; consumed by
# AppImage/scripts/notification_events.py::is_apt_active_on_host.
_PROXMENUX_UPDATE_MARKER="/var/run/proxmenux-update-in-progress"