Re: [Duplicity-talk] PGP key trouble when restoring a single file

[edgar . soldin]

On 31.03.2017 21:11, Scott Classen via Duplicity-talk wrote:
> Hello,
> 
> I'm attempting to fetch a single file from a backup set.
> 
> 
> 
> Found manifest volume 45
> Found 45 volumes in manifest
> Registering (mktemp) temporary file 
> /tmp/duplicity/duplicity-xkafg6-tempdir/mktemp-8K1tB9-2
> Deleting /tmp/duplicity/duplicity-xkafg6-tempdir/mktemp-8K1tB9-2
> Forgetting temporary file 
> /tmp/duplicity/duplicity-xkafg6-tempdir/mktemp-8K1tB9-2
> Volume was signed by key 5078BD3672BE571D, not 72BE571D
> Releasing lockfile /tmp/duplicity/.duply-cache/duply_home_b/lockfile.lock
> Removing still remembered temporary file 
> /tmp/duplicity/duplicity-xkafg6-tempdir/mkstemp-z9KowK-1
> 12:02:42.179 Task 'FETCH' failed with exit code '22'.
> --- Finished state FAILED 'code 22' at 12:02:42.179 - Runtime 00:00:55.706 ---
> 
> 
> 
> 
> This doesn't make sense. I've only ever used one GPG key.
> 
> It seems suspicious that duply is complaining that the Volume was signed with 
> 5078BD3672BE571D, not 72BE571D <--- notice that the last 8 digits of the 
> longer key matches what is expected? Somehow things are getting truncated ?
> 
> 
> I'm a bit concerned if I am unable to restore anything.
> 

that's a bug in duplicity. try giving the long gpg id or omit the --sign-key 
completely, that should work. ede/duply.net