Package: obnam Version: 1.0-1 Severity: normal Hello,
During the initialization of the first backup, the creation of the metadata on the repository side might take a few time; I assume that this happens especially when gpg encryption is used. If the backup is interrupted at this time, it is then no longer possible to remove the lock on the repository. Steps to reproduce the problem: 1. create a new backup $ obnam --lock-timeout=3 -r sftp://damien@server/home/damien/ttt backup /data 2. abort the backup before it has started sending some backup data 3. restart the backup - you get a lock timeout 4. cannot force the lock: $ obnam --lock-timeout=3 -r sftp://damien@server/home/damien/ttt backup /data ERROR: Lock timeout This problem is easy to solve by erasing the contents of the directory that will receive the repository files on the server side. I don't know if a fix is really necessary, maybe a simple warning in obnam documentation would be enough. 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 [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
