Source: borgmatic Version: 1.6.3-1 Severity: wishlist Hi,
While borg has backports, I don't see any for borgmatic. But looking at the release history for it (borgmatic), I can see some new features that I think are worth having in stable (as a backport), e.g.: - 1.5.15 with 425: Run arbitrary Borg commands with new "borgmatic borg" action (greatly simplifies interacting with repositories, IMO). - 1.5.23 with #394: Compact repository segments and free space with new "borgmatic compact" action. Borg 1.2+ only. Also run "compact" by default when no actions are specified, as "prune" in Borg 1.2 no longer frees up space unless "compact" is run. (borg 1.2 is in backports, and without this, space will leak) - 1.6.2 with #523: Reduce the default consistency check frequency and support configuring the frequency independently for each check Now, I see upstream as very active and not sure what the policy for backports should be (one-off? continuous update? etc.), but I think it would be good to have some consistency between borg's backports policy and borgmatic's. It might be that if borg 2.0 gets into sid and then via backports into bullseye, borgmatic in bullseye will completely stop working with it. thanks! iustin -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.61-teal0 (SMP w/24 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
