Package: borgmatic
Version: 2.0.11-1
Severity: important
# Upstream provides a config file migration tool, so let's save the
# user time by running it. Notably, it highlights deprecated config
# keys and introduces their replacements in a commented-out state.
if [ "$1" = "configure" ]; then
if [ -d /etc/borgmatic ]; then
for i in /etc/borgmatic/*.yaml; do
borgmatic config generate --source "$i" --destination "${i}.dpkg-
dist"
done
fi
fi
There are two things here:
1. To my knowledge, and how I do it on my machines (but which may be a
misunderstanding), user configs go into /etc/borgmatic.d, not /etc/borgmatic.
2. If there are no files matching /etc/borgmatic/*.yaml (like on my machine)
the script fails with
Generating a configuration file at: /etc/borgmatic/*.yaml.dpkg-dist
[Errno 2] No such file or directory: '/etc/borgmatic/*.yaml'
because the loop doesn't have zero steps, but one, with
$i=/etc/borgmatic/*.yaml.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.17.7+deb14+1-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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.4.2-2
ii python3 3.13.7-1
ii python3-jsonschema 4.25.1-2
ii python3-packaging 25.0-1
ii python3-requests 2.32.5+dfsg-1
ii python3-ruamel.yaml 0.18.10+ds-1
borgmatic recommends no packages.
Versions of packages borgmatic suggests:
pn apprise <none>
-- debconf-show failed
