Package: backupninja Version: 1.2.1-1 Severity: normal
Dear Maintainer,
* What led up to the situation?
upgraded system to bullseye
* What exactly did you do (or not do) that was effective (or
ineffective)?
remote backups that were working fine with buster (& older releases),
started failing after upgrade to bullseye.
after a small check it seems that backupninja doesn't read
/root/.ssh/config anymore (remote ssh details are included there), and
uses by default port 22 for ssh connections..
so existing (remote borg) backups failed.after adding non-default ssh 'port' parameter in backupninja's configuration files, everything works again. maybe this is kind of serious since it -potentially- breaks existing backups... (?)
thanks in advance, d. -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages backupninja depends on: ii bash 5.1-2+b3 ii dialog 1.3-20201126-1 ii gawk 1:5.1.0-1 ii mawk 1.3.4.20200120-2 Versions of packages backupninja recommends: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-2 Versions of packages backupninja suggests: ii borgbackup 1.1.16-3 ii bzip2 1.0.8-4 ii debconf-utils 1.5.77 pn duplicity <none> ii fdisk 2.36.1-8 pn genisoimage <none> ii hwinfo 21.72-1 pn mdadm <none> ii rdiff-backup 2.0.5-2 pn restic <none> ii rsync 3.2.3-4 pn subversion <none> pn trickle <none> ii util-linux 2.36.1-8 pn wodim <none> -- Configuration Files: /etc/backupninja.conf changed [not included] /etc/logrotate.d/backupninja changed [not included] -- no debconf information
OpenPGP_signature
Description: OpenPGP digital signature
