Your message dated Mon, 3 Aug 2015 11:58:40 +0300
with message-id <[email protected]>
and subject line Re: Bug#794455: obnam: locked repository
has caused the Debian Bug report #794455,
regarding obnam: locked repository
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
794455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794455
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Mon, Aug 03, 2015 at 11:51:46AM +0300, Vladmimir Stavrinov wrote:
> 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?
Use "obnam force-lock", please.
--
sic transit disci mundi, ergo obnam
--- End Message ---
