barman (3.19.1-3)
[PTS] [DDPO]
COMMITS: VCS has seen 3 commits since the debian/3.19.1-3 tag
- Git: https://salsa.debian.org/postgresql/barman.git
-
- Branch: master
- Path: debian/changelog
- Repo size: 729088
- Browser: https://salsa.debian.org/postgresql/barman
- Last scan: 2026-08-08 07:18:04+00
- Error: https://salsa.debian.org/api/v4/projects/postgresql%2Fbarman API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.
- Next scan: 2026-08-14 23:44:00+00
- Debian changelog in Git:
barman (3.19.1-3) unstable; urgency=medium
* Avoid running barman cron twice on systemd systems
* Supervise WAL receivers via systemd instead of forking them
* Add autopkgtests for the systemd receive-wal integration
* Add a NEWS entry for the systemd receive-wal integration
-- Marco Nenciarini <mnencia@debian.org> Fri, 05 Jun 2026 09:19:32 +0200
- This branch is 3 commits ahead of tag debian/3.19.1-3
- Git log:
commit f60d2ef84cd0a094684d284d2aaf529a75f9cb4d
Merge: 1f0e577 93c8213
Author: Marco Nenciarini <mnencia@debian.org>
Date: Mon Jun 8 16:07:12 2026 +0000
Merge branch 'sysusers' into 'master'
Install and use sysusers.d/tmpfiles.d config files
See merge request postgresql/barman!4
commit 93c82132fbb23dc91da2316c5cc712312e58175d
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sat May 30 11:58:07 2026 +0100
Install and use sysusers.d/tmpfiles.d config files
sysusers.d/tmpfiles.d config files allow a package to use
declarative configuration instead of manually written maintainer
scripts. This also allows image-based systems to be created with
/usr/ only, and also allows for factory resetting a system and
recreating /etc/ on boot.
https://www.freedesktop.org/software/systemd/man/latest/sysusers.d.html
https://www.freedesktop.org/software/systemd/man/latest/tmpfiles.d.html
commit 004ec673ceb44385ed469d362ac5dda987237b3f
Author: Luca Boccassi <luca.boccassi@gmail.com>
Date: Sat May 30 11:57:13 2026 +0100
Stop deleting system user on remove/purge
This is widely considered bad practice, as the kernel recycles
UIDs/GIDs. So any potential leftover file/directory can then
become owned by the next user/group that gets added, with
unpredictable consequences.