• 19.0-6 2385b312f2

    Keel LNPP 19.0-6
    All checks were successful
    tests / appliance (push) Successful in 11s
    tests / python (push) Successful in 29s
    tests / package (push) Has been skipped
    tests / tests (push) Successful in 48s
    security / security (push) Successful in 1m35s
    tests / stack (push) Successful in 3m0s
    Stable

    navigator released this 2026-10-26 18:24:01 -03:00 | 0 commits to main since this release

    Keel LNPP 19.0-6 (stable-1 release, 2026-10-26)

    Download:

    Channel pointer: stable → 2026-10-26/1
    Archive: https://archive.keellinux.org (suite trixie, keel 0.23.56)

    Downloads
  • 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
  • testing-19.0-4-20261016 74fd1df249

    testing-19.0-4-20261016 (debian-13-keel-lnpp_19.0-4_amd64.tar.zst)
    All checks were successful
    tests / package (push) Has been skipped
    tests / appliance (push) Successful in 9s
    tests / python (push) Successful in 20s
    tests / tests (push) Successful in 39s
    security / security (push) Successful in 1m1s
    tests / stack (push) Successful in 1m36s
    Pre-release

    navigator released this 2026-10-16 16:12:21 -03:00 | 7 commits to main since this release

    Testing pre-release of 2026-10-16 (handbook decision 0059). Not for production. Version 19.0-4: the release test of 19.0-3 found keel#201 in the image, so no 19.0-3 of LNPP is published.

    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 74fd1df 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.41).
    • keel 0.23.41 carries the fixes of the cross-site release test: the replica gets the primary's Anubis key by itself (common#56); the reseed works when an application revokes CONNECT from PUBLIC (keel#183), and the check database now does; a preset disables postgresql-common's WAL archival, which the first boot enabled (keel#201); etcd forms with every member (keel#188, #199); every mesh peer sends a keepalive (keel#140); the VIP overlay waits for etcd with no drift (keel#106).
    • Signed: debian-13-keel-lnpp_19.0-4_amd64.tar.zst.sha512.asc holds a signature by the main key and one by the images key (decision 0055). Each key verifies it alone, with sqv or gpgv.
    • The .tar.zst alone: the ISO builder does not exist yet (decision 0052, section 8).
    • Tested across 2 sites: 2 CTs on hw12-br1 and 1 CT on nfs1-br2, the PostgreSQL pair across the sites, etcd with 3 members, the VIP, failovers by a network cut and by a stop of the primary, at 5 ms and at 250 ms RTT. The evidence is in the handbook, docs/evidence/2026-10-16-lnmp-lnpp-19.0-3-cross-site.md.
    Downloads
  • testing-19.0-2-20261016 0067f47abf

    testing-19.0-2-20261016 (debian-13-keel-lnpp_19.0-2_amd64.tar.zst)
    All checks were successful
    tests / package (push) Has been skipped
    tests / appliance (push) Successful in 9s
    tests / tests (push) Successful in 36s
    tests / python (push) Successful in 47s
    security / security (push) Successful in 1m1s
    tests / stack (push) Successful in 1m44s
    Pre-release

    navigator released this 2026-10-16 05:26:03 -03:00 | 11 commits to main since this release

    Testing pre-release of 2026-10-16 (handbook decision 0059). Not for production.

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

    /keel-check/.

    • Built on the build host from 0067f47 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.29).
    • Signed: debian-13-keel-lnpp_19.0-2_amd64.tar.zst.sha512.asc holds a signature by the main key and one by the images key (decision 0055). Each key verifies it alone, with sqv or gpgv.
    • The .tar.zst alone: the ISO builder does not exist yet (decision 0052, section 8).
    • Booted on hw12-br1: standalone and as a pair. The evidence is in the handbook, docs/evidence/2026-10-16-lnmp-lnpp-images.md.
    Downloads