Sorry. A fatal ERROR occured:
Encryption failed.
usage: gpg [options] --sign [filename]
Hint:
This error means that gpg is probably misconfigured or not working
correctly. The error message above should help to solve the problem.
However, if for some reason duply should misinterpret the situation you
can define GPG_TEST='disabled' in the conf file to bypass the test.
Please do not forget to report the bug in order to resolve the problem
in future versions of duply.
duply config:
$ grep -v ^# /etc/duply/varwww/conf
GPG_PW='foobar'
TARGET='ssh://backup:****@backup.example.com/varwww'
SOURCE='/var/www'
MAX_FULL_BACKUPS=3
TEMP_DIR="/var/tmp/backup"
DUPL_PARAMS="${DUPL_PARAMS} --full-if-older-than 1M"
VOLSIZE=25
DUPL_PARAMS="${DUPL_PARAMS} --volsize ${VOLSIZE}"
DUPL_PARAMS="${DUPL_PARAMS} --archive-dir=/var/cache/backup"
Confirmed here too:
Start duply v1.5.5, time is 2011-06-06 09:35:56.
Using profile '/etc/duply/etc'.
Using installed duplicity version 0.6.12, python 3.2, gpg 1.4.11 (Home: ~/.gnupg), awk 'GNU Awk 3.1.8', bash '4.2.10(2)-release (x86_64-unknown-linux-gnu)'.
Test - Encryption with passphrase (FAILED)
My config:
GPG_PW='whatever'
TARGET='webdavs://user:passw@webdav.mydrive.ch/DailyBackup/etc/'
SOURCE='/etc'
found and fixed, please try the latest snapshot from here
http://duply.net/?title=Duply-code
thanks ede
Thanks, confirmed fixed. When can we expect a new version with this fix?
considering the impact of this bug i'd say i'll put 1.5.5.1 out this week .. ede
Amazing, thanks! A big thanks for duply again.
glad you like it.. ede
Thanks for 1.5.5.1, that was really quick!