Package: backintime-common Version: 1.3.3-4 Severity: important Upstream maintainer here.
I migrated from Debian 11 to 12 with fresh installing the whole system including Back In Time (BIT). I realized that "sshfs" is not installed when installing BIT. I would say that "sshfs" should be a "depending" package instead of just a "suggestion". With "sshfs" remote backups using SSH are not possible. BIT gives error messages about a missing "sshfs" but don't handle the situation in an elegant way. Users will get lost. SSH using backup profiles are not disabled in this case. I would ease up a lot for us maintainers and users if "sshfs" would be a hard dependecy. Not sure how the Debian Policy is about it but I would suggest to also fix the current stable (Debian 12) version. Best, Christian Buhtz -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-21-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: 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 /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages backintime-common depends on: ii cron [cron-daemon] 3.0pl1-162 ii openssh-client 1:9.2p1-2+deb12u2 ii python3 3.11.2-1+b1 ii python3-dbus 1.3.2-4+b1 ii python3-keyring 23.9.3-2 ii python3-packaging 23.0-1 ii rsync 3.2.7-1 Versions of packages backintime-common recommends: ii backintime-qt 1.3.3-4 Versions of packages backintime-common suggests: pn encfs <none> pn powermgmt-base <none> pn sshfs <none> -- no debconf information
