Package: borgmatic Version: 1.9.3-0.1 Severity: normal X-Debbugs-Cc: deb...@rocketjump.eu
Hello! When pressing ctrl+c on a borgmatic command, it no longer terminates the underlying borg process. This leads to borg still running, polluting the terminal, and of course locking the repo until you kill the process by hand. This is a regression from bookworm, where pressing ctrl+c would terminate borgmatic and also borg. Example output: # borgmatic -c /etc/borgmatic.d/complete_system.yaml check --progress [...] using builtin fallback logging configuration 33 self tests completed in 0.05 seconds Starting repository check Verified integrity of /mnt/target/borgbackup_workstation/index.4105 Read committed index of transaction 4105 Segment transaction is 4105 Determined transaction is 4105 Found 2580 segments checking segment file /mnt/target/borgbackup_workstation/data/0/1... checking segment file /mnt/target/borgbackup_workstation/data/0/2... checking segment file /mnt/target/borgbackup_workstation/data/0/3... checking segment file /mnt/target/borgbackup_workstation/data/0/4... checking segment file /mnt/target/borgbackup_workstation/data/0/5... checking segment file /mnt/target/borgbackup_workstation/data/0/6... checking segment file /mnt/target/borgbackup_workstation/data/0/7... [hit ctrl+c] [python traceback from borgmatic omitted] checking segment file /mnt/target/borgbackup_workstation/data/0/8... checking segment file /mnt/target/borgbackup_workstation/data/0/9... checking segment file /mnt/target/borgbackup_workstation/data/0/10... checking segment file /mnt/target/borgbackup_workstation/data/0/11... checking segment file /mnt/target/borgbackup_workstation/data/0/12... checking segment file /mnt/target/borgbackup_workstation/data/0/13... checking segment file /mnt/target/borgbackup_workstation/data/0/14... checking segment file /mnt/target/borgbackup_workstation/data/0/15... checking segment file /mnt/target/borgbackup_workstation/data/0/16... checking segment file /mnt/target/borgbackup_workstation/data/0/17... checking segment file /mnt/target/borgbackup_workstation/data/0/18... checking segment file /mnt/target/borgbackup_workstation/data/0/19... checking segment file /mnt/target/borgbackup_workstation/data/0/20... checking segment file /mnt/target/borgbackup_workstation/data/0/21... checking segment file /mnt/target/borgbackup_workstation/data/0/22... checking segment file /mnt/target/borgbackup_workstation/data/0/23... checking segment file /mnt/target/borgbackup_workstation/data/0/24... checking segment file /mnt/target/borgbackup_workstation/data/0/25... checking segment file /mnt/target/borgbackup_workstation/data/0/26... killall borg [further python traceback omitted] -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.12.12-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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.0-4+b1 ii python3 3.13.1-2 ii python3-colorama 0.4.6-4 ii python3-jsonschema 4.19.2-6 ii python3-packaging 24.2-1 ii python3-requests 2.32.3+dfsg-1 ii python3-ruamel.yaml 0.18.10+ds-1 borgmatic recommends no packages. Versions of packages borgmatic suggests: pn apprise <none> -- no debconf information
