[Duplicity-talk] duplicity claiming: PASSPHRASE variable not set

[Mogliii]

Hi,

Running duplicity 0.6.15 on ubuntu 10.04 in conjuncture with duply
(latest development version from 21stAugust).
I am trying to do a backup encrypted against two public keys and sign
with a private key. When I run the command I get this:


[snip]
-----------------
Connecting with backend: FTPBackend
Archive dir: /root/.cache/duplicity/duply_vserver

Found 0 secondary backup chains.

Found primary backup chain with matching signature chain:
-------------------------
Chain start time: Sun Aug 21 23:08:42 2011
Chain end time: Sun Aug 21 23:10:03 2011
Number of contained backup sets: 2
Total number of contained volumes: 2
 Type of backup set:                            Time:      Num volumes:
                Full         Sun Aug 21 23:08:42 2011                 1
         Incremental         Sun Aug 21 23:10:03 2011                 1
-------------------------
No orphaned or incomplete backup sets found.
PASSPHRASE variable not set, asking user.
GnuPG passphrase for signing key:

(I entered the passphrase twice by hand, thats why there are two
backups. Another odd thing is that gpg ask to repeat the passphrase. But
this does not make sense, I don't have to enter a passphrase twice to
log-in to eg. ssh...)

Duply with the --preview option offers the following command:

--- Start running command BKP at 23:23:13.186 ---
 TMPDIR='/tmp' PASSPHRASE='********' FTP_PASSWORD='********' duplicity
--name 'duply_vserver' --encrypt-key 9F039678 --encrypt-key 234D7ED2
--sign-key 9F039678 --verbosity '9' --full-if-older-than 1M --volsize
200 --include-globbing-filelist
/etc/duply/vserver/duplicity.exclude_test --timeout 100 --num-retries 20
--exclude-globbing-filelist '/etc/duply/vserver/exclude' '/etc'
'ftp://address@hidden:59999/16G/****/'
--- Finished state OK at 23:23:13.207 - Runtime 00:00:00.021 ---

So PASSPHRASE variable is being set. Even if I copy/paste the --preview
generated command to a new input I get the same error.
I executed "export PASSPHRASE='********'" before running duplicity, but
to no avail.

I believe this is a duplicity problem as the generated command follows
the man-page. Also: before signing duplicity had already access to the
ftp (so it could check that everything is up to date), for which it
requires the FTP_PASSWORD variable.