Re: [Duplicity-talk] Duplicity 0.6.20 sets terminal parameters

[Scott Hannahs]

On Nov 14, 2012, at 04:46, address@hidden wrote:
> On 14.11.2012 04:59, Scott Hannahs wrote:
>> I recently upgraded to duplicity 0.6.20 and tested it from my terminal and 
>> it ran fine.  However when run as a cron job it now fails.  My sh script 
>> that is run periodically (actually as a launch daemon) has the following in 
>> it:
>> ….
> 
> 
> hi scott.. still around :)
> 
> ups, actually it should have been
> "The passphrase to be used for --sign-key , if SIGN_PASSPHRASE is not set but 
> PASSPHRASE is set and the sign key is also one of the encryption keys, the 
> latter will be used."
> 
> relationale is: 
> it's plausible that you probably don't have two keys with the same 
> passphrase. so to make sure we do not simply reuse PASSPHRASE we check if the 
> same key is used to encrypt against also beforehand.
> 
> simply set SIGN_PASSPHRASE and your problem should disappear.


Yep, "still around", duplicity has just been working fine.  I see the logic and 
the update to the man page wording will clarify my confusion.

I had tried that solution but need to wait for the next launchdaemon job to run 
to check it.

Thanks!

-Scott