barman (3.19.1-3) unstable; urgency=medium

  On systemd systems the periodic "barman cron" run is now driven by
  barman.timer (the /etc/cron.d/barman entry no longer runs there),
  and it supervises each streaming server's WAL receiver through a
  dedicated barman-receive-wal@<server>.service unit instead of
  forking and detaching it. Inspect or stop a receiver with systemctl
  and read its log with journalctl; a shipped polkit rule lets the
  unprivileged barman user manage these units. Interactive commands
  such as "barman receive-wal --stop" continue to work unchanged.

  Where polkit is absent (a Recommends, e.g. a --no-install-recommends
  install), barman falls back to forking the receivers as before, so they
  will not appear as systemd units; WAL streaming still works.

 -- Marco Nenciarini <mnencia@debian.org>  Thu, 04 Jun 2026 14:25:06 +0200