Package: borgmatic Version: 1.7.7-1 Severity: normal X-Debbugs-Cc: t...@debian.org
Hi, Today I realised that a borgmatic setup was not performing daily backups, despite not receiving any errors. Upon inspection, I noticed the borgmatic.service file has the following option: ConditionFileNotEmpty=/etc/borgmatic/config.yaml Since I have multiple backup configurations, I created separate files in /etc/borgmatic.d/, as recommended in the official documentation[1]. This means the backup is never launched automatically. This is not documented anywhere, and I am not even sure what would be the workaround, except removing the service option. [1]: https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/ -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable'), (50, 'unstable'), (49, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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.4-1 ii python3 3.11.2-1+b1 ii python3-colorama 0.4.6-2 ii python3-jsonschema 4.10.3-1 ii python3-pkg-resources 66.1.1-1 ii python3-requests 2.28.1+dfsg-1 ii python3-ruamel.yaml 0.17.21-1 borgmatic recommends no packages. borgmatic suggests no packages. -- no debconf information
