mirror of
https://github.com/jmcorgan/fips.git
synced 2026-10-30 07:37:36 +00:00
Gustavo Lima Chaves
e34618cb72
deb-install's container plumbing (cleanup_container, build_image, start_systemd_container_with_tun, wait_for_systemd, start_unit, start_unit_queued, wait_for_service_active, container_systemd_version and cexec) moves unchanged into testing/lib/systemd-scenario.sh, so the RPM install suite can source the same functions instead of carrying a copy. deb-install sources it after systemd-container.sh. The bounds the helpers read (BOOT_TIMEOUT, SERVICE_TIMEOUT, UNIT_START_TIMEOUT, EXEC_TIMEOUT) and REPO_ROOT stay defined in the suite, and the file's header lists them. They get their own file rather than going into systemd-container.sh because dns-resolver and tarball-install source that file and then define their own cleanup_container, build_image, wait_for_systemd and start_unit, and wait_for_systemd and tarball-install's start_unit differ from these. Placed there, the shared versions would be silently shadowed in two suites that do not use them. deb-install debian12, which runs both the install and the upgrade scenarios, gives the same verdicts before and after the move against the same package, and passes 48/48 against a package built from this tree.