Package: barman
Version: 2.12
Severity: important

See
https://github.com/EnterpriseDB/barman/issues/302
and this is fixed in commit
https://github.com/EnterpriseDB/barman/commit/45ccd9d2f315ec208eee778eba1333c0aa4a4460

This is going to hit Bullseyes users.
Severity might need to be rised - after all it makes barman somewhat broken.

Jérémy


-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages barman depends on:
ii  adduser                3.118
ii  python3                3.9.2-3
pn  python3-barman         <none>
ii  python3-pkg-resources  52.0.0-3
ii  rsync                  3.2.3-4

Versions of packages barman recommends:
ii  openssh-client                            1:8.4p1-5
ii  openssh-server                            1:8.4p1-5
ii  postgresql-client                         13+225
ii  postgresql-client-13 [postgresql-client]  13.3-1

Versions of packages barman suggests:
pn  barman-cli  <none>
pn  repmgr      <none>

Reply via email to