• testing-19.0-5-20261016 f8b864050f

    testing-19.0-5-20261016 (debian-13-keel-lnpp_19.0-5_amd64.tar.zst)
    All checks were successful
    tests / python (push) Successful in 29s
    tests / tests (push) Successful in 55s
    tests / package (push) Has been skipped
    tests / appliance (push) Successful in 14s
    security / security (push) Successful in 1m25s
    tests / stack (push) Successful in 1m50s
    Pre-release

    navigator released this 2026-10-16 21:02:39 -03:00 | 5 commits to main since this release

    Testing pre-release of 2026-10-16 (handbook decision 0059). Not for production. Version 19.0-5: it carries keel 0.23.43, so the 19.0-4 image of the same day is superseded.

    Keel LNPP: nginx, PostgreSQL 17 and Python 3 with gunicorn on Keel Web. The check page is https://

    /keel-check/.

    • Built on the build host from f8b8640 with keel-release, on Core 19.0-10 and Web 19.0-6 (keel-web 0.3.0). Packages: Debian 13 and archive.keellinux.org trixie-testing (keel 0.23.43).
    • keel 0.23.43: keel diff does not count a PostgreSQL sender with no client address as a replica (keel#201), and the join names the failed step (keel#198). The MariaDB fixes of this keel do not touch PostgreSQL.
    • Tested on real nodes across two sites (2 CTs on BR1, 1 CT on BR2): a network cut of the primary and a stop of the holder. The first write came 1.7 to 1.8 s after the VIP moved, 0 acknowledged writes were lost, and keel diff reported no drift on the 3 CTs. Evidence: docs/evidence/2026-10-17-lnmp-19.0-4-cross-site.md in Keel-Linux/handbook.
    • The sha512 file is signed by the main key and by the images key (decision 0055). Each key verifies it alone.
    Downloads