Package: obnam Version: 1.7-1 Severity: important Dear Maintainer,
I upgraded to obnam 1.7.1 (digression here: the Debian changelog for 1.7.1 should have carried the same mention of possible repository corruption that website News did carry. As a debian user, the Debian changelog/alert mechanism is the only thing I'm likely to see during a 100+ packages upgrade). obnam 1.7.1 sees my 1.6.1 repository properly and restores & backup from it properly. However, 'obnam mount' fails to properly access any file > 64KB. md5 shows differing checksums, diff fails, and a 'cp backedfile /tmp/restoredfile' command either fails silently having copied only part of the file, or else dies with this error: cp: error reading ‘backedfile’: Invalid argument cp: failed to extend ‘/tmp/restoredfile’: Invalid argument This happens on every file > 64KB that I've tried (and all those files restore properly with obnam restore). Files < 64KB appear OK. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages obnam depends on: ii libc6 2.18-4 ii python 2.7.5-5 ii python-cliapp 1.20130808-1 ii python-fuse 2:0.2.1-9 ii python-larch 1.20131130-1 ii python-paramiko 1.10.1-1 ii python-tracing 0.8-1 ii python-ttystatus 0.23-1 ii python-yaml 3.10-4+b2 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
