Package: borgmatic Version: 1.5.12-2 Severity: grave Tags: upstream fixed-upstream Forwarded: https://projects.torsion.org/borgmatic-collective/borgmatic/issues/574 Control: found -1 1.6.3-1
Hi, Recently I reported the bug mentioned above upstream, which causes most data to be silently excluded from backups if /root/.borgmatic exists. Since details of the bug are already available in the upstream bug report, I will omit them here for brevity. Since the issue has already been fixed upstream, this bug is only meant to track the issue in Debian. I've set the severity to grave, because the bug causes borgmatic to produce effectively empty backups, while the user may believe to have secure backups, which qualifies as data loss to me. Feel free to lower the severity to normal if you disagree. Regards Sven -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (990, 'testing-debug'), (990, 'testing'), (102, 'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101, 'experimental') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages borgmatic depends on: ii borgbackup 1.2.1-2 ii python3 3.10.6-1 ii python3-colorama 0.4.5-2 ii python3-jsonschema 4.6.0-3 ii python3-pkg-resources 59.6.0-1.2 ii python3-requests 2.27.1+dfsg-1 ii python3-ruamel.yaml 0.17.16-1 borgmatic recommends no packages. borgmatic suggests no packages. -- no debconf information
