Package: duply Version: 1.11.3-1 Severity: normal Hi,
I'm not sure that it's bug actually in duply. Just after upgrading gnupg package duply doesn't work with gpg-encrypted backups. It looks like gpg sanity check in duply fails that's why it don't try to start duplicity. Probably gpg can't read passwords from stdin anymore. Not sure. I've GPG_KEY and GPG_PW in my ~/.duply/backup/conf as requested in conf template. As a workaround it's possible to put GPG_TEST=disabled to config and duply will start duplicity (that will fail itself, but it's probably another bug) I'm attaching easy-to-setup example ~/.duply/gpg_test directory with sample GPG private key that needs to be imported and config file that will backup /home/test to /tmp/backup-test. -- Start duply v1.11.3, time is 2016-08-15 11:08:51. Using profile '/home/test/.duply/gpg_test'. Using installed duplicity version 0.7.07.1, python 2.7.12+, gpg 2.1.14 (Home: /home/test/.gnupg), awk 'GNU Awk 4.1.3, API: 1.1 (GNU MPFR 3.1.4-p2, GNU MP 6.1.1)', grep 'grep (GNU grep) 2.25', bash '4.3.46(1)-release (x86_64-pc-linux-gnu)'. Autoset found secret key of first GPG_KEY entry '5C6E0944F013F4A9BF567D4CA21E49300CE41277' for signing. Checking TEMP_DIR '/tmp' is a folder and writable (OK) Test - Encrypt to '5C6E0944F013F4A9BF567D4CA21E49300CE41277' & Sign with '5C6E0944F013F4A9BF567D4CA21E49300CE41277' (FAILED) Sorry. A fatal ERROR occured: Encryption failed (Code 2). gpg: using "5C6E0944F013F4A9BF567D4CA21E49300CE41277" as default secret key for signing [GNUPG:] KEY_CONSIDERED 5C6E0944F013F4A9BF567D4CA21E49300CE41277 2 [GNUPG:] KEY_CONSIDERED 5C6E0944F013F4A9BF567D4CA21E49300CE41277 0 [GNUPG:] KEY_CONSIDERED 5C6E0944F013F4A9BF567D4CA21E49300CE41277 0 [GNUPG:] PROGRESS need_entropy X 4 16 [GNUPG:] PROGRESS need_entropy X 16 16 [GNUPG:] BEGIN_SIGNING H8 [GNUPG:] PINENTRY_LAUNCHED 27822 gpg: signing failed: Permission denied [GNUPG:] BEGIN_ENCRYPTION 2 9 [GNUPG:] FAILURE sign-encrypt 83918849 gpg: /usr/bin/duply: sign+encrypt failed: Permission denied 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. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.7.0+ (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages duply depends on: pn duplicity <none> ii gnupg 2.1.14-5 duply recommends no packages. Versions of packages duply suggests: ii openssh-client 1:7.3p1-1 -- no debconf information -- WBR, Dmitry
gpg_test.tar.gz
Description: application/gzip
