Package: rdiff-backup Version: 1.2.8-7 Severity: important Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Probably an aborted backup due to a system shutdown while rdiff-backup was
running.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Trying to repair the backup by manually starting the backup again.
* What was the outcome of this action?
Quite a long Error message, starting with:
Previous backup seems to have failed, regressing destination now.
Exception '[Errno 40] Too many levels of symbolic links: '/....
* What outcome did you expect instead?
Correction of the inconsistencies due to the abortion of the former backup-
attempt and again a working backup.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 8.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages rdiff-backup depends on:
ii libc6 2.19-18+deb8u1
ii librsync1 0.9.7-10
ii python 2.7.9-1
ii python2.7 2.7.9-2
Versions of packages rdiff-backup recommends:
ii python-pylibacl 0.5.2-1
ii python-pyxattr 0.5.3-1
rdiff-backup suggests no packages.
-- no debconf information
FullErrorMessage.7z
Description: application/7z-compressed
