Package: obnam Version: 1.13-1 Severity: normal Dear Maintainer,
Every time obnam terminated by external signal (Ctrl-C for example) it remain repository locked. Is unlocking on termination is "missing feature" too, or leaving it locked is "intent feature"? I think locking only makes sense while obnam is running, does not it? -- 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
