Package: backintime-common Version: 1.1.24-0.1 Severity: normal Dear Maintainer,
If I restore a file within a symbolic-linked directory, the symbolic link is removed by the restoration. For example, if we make a test file like this: mkdir abc ln -s abc def touch abc/file1 and then restore it within backintime at def/file1, backintime removes the symbolic link from def -> abc and creates a new directory def/ into which it restores file1. In order to avoid this, it is necessary to restore from abc/file1 (which preserves the def -> abc link). It seems to me that expected behaviour would be for the symbolic link to be preserved. I say “expected” based on my experience: I organise some of my files into directory by date, with a symbolic link to most recent directory as “current” and was rather surprised that when I restored a file within current/ everything else disappeared! I think I am running backintime with default settings. Do forgive me if not: I am very much a “user” and don’t often submit bug reports. Equally, please accept my apologies if I have missed something obvious in this report for the same reason. Thanks! Best wishes, Jacob -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages backintime-common depends on: ii cron [cron-daemon] 3.0pl1-130 ii openssh-client 1:7.9p1-5 ii python3 3.7.1-3 ii python3-dbus 1.2.8-2+b3 ii python3-keyring 17.1.1-1 ii rsync 3.1.3-1 Versions of packages backintime-common recommends: ii backintime-qt4 1.1.24-0.1 Versions of packages backintime-common suggests: pn encfs <none> ii powermgmt-base 1.33 pn sshfs <none> -- no debconf information
