Re: [Duplicity-talk] 0.6.07 gpg error

[edgar . soldin]

How about a unit test for these parameters? ede

On 02.03.2010 16:58, Michael Terry wrote:
> Guh.  Why is gpg-options such a punk?  I'll look into making sure the
> options are propagated correctly tonight.  ede, I wish I had had you
> test this before release.  :-/
> -mt
> 
> On 2 March 2010 10:47,  <address@hidden> wrote:
>> :) .. sorry
>>
>> it tells there is no assurance that the key belongs to the owner and
>> therefore it says invalid key for sign+encrypt
>>
>> with 0.6.06 this works flawless, because --gpg-options '--trust-model
>> always' is given .. 0.6.07 breaks
>>
>> ede
>>
>> On 02.03.2010 15:35, Kenneth Loafman wrote:
>>> Translation, please?
>>>
>>> ...Ken
>>>
>>> address@hidden wrote:
>>>> Here is the next one. Is it possible that --gpg-options does not reach
>>>> the gpg.py gpg call? ... ede
>>>>
>>>> call:
>>>>
>>>> TMPDIR='/tmp' PASSPHRASE='pass' FTP_PASSWORD='pass'
>>>> /home/me/_apps/duplicity-0.6.07/bin/duplicity --name 'duply_test'
>>>> --encrypt-key '00000000' --sign-key '00000000' --verbosity '4'
>>>> --gpg-options '--trust-model always' --full-if-older-than 1M --volsize
>>>> 50 --exclude-globbing-filelist /home/me/.duply/test/exclude /home/me/
>>>> 'ftp://address@hidden/test/'
>>>>
>>>> error:
>>>>
>>>> Removing still remembered temporary file
>>>> /tmp/duplicity-PBgtxB-tempdir/mkstemp-FzDoNy-2
>>>> Removing still remembered temporary file
>>>> /tmp/duplicity-PBgtxB-tempdir/mktemp-EJFn4p-4
>>>> Removing still remembered temporary file
>>>> /tmp/duplicity-PBgtxB-tempdir/mkstemp-zzkpLV-1
>>>> GPG error detail: Traceback (most recent call last):
>>>>   File "/home/me/_apps/duplicity-0.6.07/bin/duplicity", line 1240, in
>>>> <module>
>>>>     with_tempdir(main)
>>>>   File "/home/me/_apps/duplicity-0.6.07/bin/duplicity", line 1233, in
>>>> with_tempdir
>>>>     fn()
>>>>   File "/home/me/_apps/duplicity-0.6.07/bin/duplicity", line 1215, in main
>>>>     incremental_backup(sig_chain)
>>>>   File "/home/me/_apps/duplicity-0.6.07/bin/duplicity", line 488, in
>>>> incremental_backup
>>>>     globals.backend)
>>>>   File "/home/me/_apps/duplicity-0.6.07/bin/duplicity", line 295, in
>>>> write_multivol
>>>>     globals.gpg_profile, globals.volsize)
>>>>   File "/home/me/_apps/duplicity-0.6.07/duplicity/gpg.py", line 286, in
>>>> GPGWriteFile
>>>>     file.write(data)
>>>>   File "/home/me/_apps/duplicity-0.6.07/duplicity/gpg.py", line 156, in
>>>> write
>>>>     self.gpg_failed()
>>>>   File "/home/me/_apps/duplicity-0.6.07/duplicity/gpg.py", line 168, in
>>>> gpg_failed
>>>>     raise GPGError, msg
>>>> GPGError: GPG Failed, see log below:
>>>> ===== Begin GnuPG log =====
>>>> gpg: 42E6861C: Es gibt keine Garantie, daà dieser SchlÞssel wirklich
>>>> dem angegebenen Besitzer gehÃķrt.
>>>> gpg: [stdin]: sign+encrypt failed: Unbrauchbarer Ãķffentlicher SchlÞssel
>>>> ===== End GnuPG log =====
>>>>
>>>>
>>>> _______________________________________________
>>>> Duplicity-talk mailing list
>>>> address@hidden
>>>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Duplicity-talk mailing list
>>> address@hidden
>>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
>>
>>
>> _______________________________________________
>> Duplicity-talk mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>>
> 
> 
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk