Package: obnam Version: 1.13-1 Severity: normal Dear Maintainer,
The problem with nonexistent chunks still exists. I have tried to run Your software few times with options: --fsck-fix --fsck-rm-unused --no-fsck-ignore-chunks --no-fsck-skip-dirs --no-fsck-skip-files --no-fsck-skip-generations --no-fsck-skip-per-client-b-trees --no-fsck-skip-shared-b-trees fsck but every time there was a lot of messages like this: chunk ... does not exist checksum whole-file checksum mismatch This means that fsck command does nothing and repository remains broken. Why this command does not remove references pointing to nonexistent chunk when it finds such ones? And what to do with "checksum mismatch"? Does this mean the file is broken? If so, why do You not remove them? If there are no way to keep repository in consistent state, then we compelled to start new repository every time when it gets broken. This is bad methodology and if there are no other solutions, I am not sure that such backup software is usable at all. This is sad news. -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages obnam depends on: ii libc6 2.19-19 ii python 2.7.9-1 ii python-cliapp 1.20150701-1 ii python-fuse 2:0.2.1-11 ii python-larch 1.20131130-1 ii python-paramiko 1.15.2-1 ii python-tracing 0.8-1 ii python-ttystatus 0.23-1 ii python-yaml 3.11-2 obnam recommends no packages. obnam suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
