Package: obnam Version: 1.0-1 Severity: normal Hello,
obnam does not release the repository lock when an error is raised. >From the error message I assume the error is correctly treated in obnam (i.e. the error is correctly catched, and obnam does not crash abruptly). $ obnam --lock-timeout=3 -r /home/damien/tmp/disk fsck --fsck-fix ERROR: Larch B-tree is in read-only mode, no changes allowed damien@marchand:~/tmp/disk$ obnam --lock-timeout=3 -r /home/damien/tmp/disk fsck ERROR: Lock timeout ==> here there is no reason why the repo is still locked; I am the only user accessing to this repo. After fsck has met the first error, I assume it should release the repository lock. best regards, Damien -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (450, 'stable-updates'), (450, 'stable'), (300, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages obnam depends on: ii libc6 2.13-32 ii python 2.7.2-10 ii python-cliapp 0.29-1 ii python-larch 0.31-1 ii python-paramiko 1.7.7.1-2 ii python-tracing 0.6-2 ii python-ttystatus 0.18-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 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
