[guardian-dev] gnugpg-for-android --gen-key
hans at guardianproject.info
Fri Dec 28 14:00:08 EST 2012
It seems that you haven't pushed the pinentry commits that the git submodule
is looking for:
hans at palatschinken gnupg-for-android $ git submodule update
Submodule path 'external/gnupg': checked out
Cloning into 'external/pinentry'...
remote: Counting objects: 1689, done.
remote: Compressing objects: 100% (1676/1676), done.
remote: Total 1689 (delta 1179), reused 0 (delta 0)
Receiving objects: 100% (1689/1689), 901.35 KiB | 478 KiB/s, done.
Resolving deltas: 100% (1179/1179), done.
fatal: reference is not a tree: 67c0f9b6d553d86472d87265f1baa52ae15a6b06
Unable to checkout '67c0f9b6d553d86472d87265f1baa52ae15a6b06' in submodule
On 12/28/2012 08:14 AM, Abel Luck wrote:
> Hans of Guardian:
>> Sure, I'll look today.
>> Also, I think that the 'pinentry' build target should be a dependency of 'gnupg', instead of having it need to be called on its own, i.e. 'make pinentry-install'. Any reason why it shouldn't be a dependency?
> I totally agree.
> That makefile is a bit daunting, and the dependency order is a bit wonky
> too. Adding it separately was just a quick way to get it up and running.
>> On Dec 25, 2012, at 6:23 AM, Abel Luck wrote:
>>> Hey Hans,
>>> I needed a feature to test the pinentry stuff on, and the "Gen Key" menu
>>> option was right there, so I figured I'd use that.
>>> However, it doesn't seem to be working. I debugged it a bit but didn't
>>> quite come up with anything (this was a few days ago).
>>> Rather than go down that rabbit hole, I'm gonna test pinentry-android
>>> with --decrypt instead.
>>> Wanna take a look at the gen-key feature?
More information about the Guardian-dev