Package: borgmatic Version: 1.8.3-1 Severity: normal Dear Maintainer,
With the configuration changes introduced in borgmatic 1.8.0 (dropping the topmost config sections) it is no longer possible to check borg repositories for orphaned object using borgmatic. This has been reported to the borgmatic developers ~5 months ago (see https://projects.torsion.org/borgmatic-collective/borgmatic/issues/779 ) and has been fixed in borgmatic 1.8.5 by allowing the --match-archives option for the "check" action. borgmatic 1.8.5 fixes the handling of simple strings for --override as well. Preferably it should be updated to the latest release, which is 1.8.9 at the time of this writing. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (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 borgmatic depends on: ii borgbackup 1.2.7-2+b1 ii python3 3.11.8-1 ii python3-colorama 0.4.6-4 ii python3-jsonschema 4.19.2-2 ii python3-packaging 23.2-1 ii python3-pkg-resources 68.1.2-2 ii python3-requests 2.31.0+dfsg-1 ii python3-ruamel.yaml 0.17.21-1 borgmatic recommends no packages. borgmatic suggests no packages. -- no debconf information
