[[!comment format=mdwn username="https://www.google.com/accounts/o8/id?id=AItOawkck-Tokgfh_1Fwh6pkl69xPA_dYUgA4Tg" nickname="Benjamin" subject="autobuild test" date="2014-10-21T22:09:47Z" content=""" Okay I managed to package the autobuild for my Arch system and installed. Here is what I get, retrieving finished glacier retrieval jobs which was started yesterday: Without AWS credentials as environment variables, the call fails: [[!format sh \"\"\" [ben@voyagerS9 annextest]$ git annex get --from=glacier mydir/myfile1 get mydir/myfile (from glacier...) (gpg) ['/usr/local/bin/glacier', '--region=us-east-1', 'archive', 'retrieve', '-o-', 'glacier-myvault', 'GPGHMACSHA1--4286b1a121892c9e64de436725478b0bc5038e67'] glacier: archive 'GPGHMACSHA1--4286b1a121892c9e64de436725478b0bc5038e67' not found failed git-annex: get: 1 failed \"\"\"]] I patched the glacier-cli Python source so that it prints out the command arguments argv. The archive _does_ exist. Executing the glacier-cli command manually is successful. So is calling git-annex with AWS credentials exported into env: [[!format sh \"\"\" [ben@voyagerS9 annextest]$ git annex get --from=glacier mydir/myfile2 get mydir/myfile2 (from glacier...) (gpg) ['/usr/local/bin/glacier', '--region=us-east-1', 'archive', 'retrieve', '-o-', 'glacier-myvault', 'GPGHMACSHA1--c3827c03d48b4829c7cc584778652c66e2784b0f'] ok (Recording state in git...) \"\"\"]] So I guess one bug is fixed, although I think there is a wrong error message. Regarding AWS credentials, I have no success in updating credentials or finding out which if any are embedded: [[!format sh \"\"\" [ben@voyagerS9 annextest]$ git annex info glacier remote: glacier description: [glacier] uuid: b4dcf525-40c7-4f04-86cc-3850d1260680 cost: 1050.0 type: glacier glacier vault: glacier-myvault encryption: encrypted (to gpg keys: MYKEY) chunking: none \"\"\"]] When I checkout the git-annex branch and look into the remote.log I see fields for cipher, cipherkeys, datacenter, embedcreds=yes, name, s3creds, type, vault, timestamp. The s3creds field does not look like my current AWS credentials, at least not in plaintext. """]]