Failure to login using keybase in terminal on Mac OS X

I setup my keybase account and installed it for the first time today on my Mac OS X (10.11.3) machine and got a gpg error. Ultimately a friend helped me resolve the issue by running `gpg -K` then attempting to re-login which was pretty unintuitive.

The error:

``` bash
computer: kris$ keybase login
warn: No config file found; tried '/Users/kris/.config/keybase/config.json'
Your keybase username or email: REDACTED
Your keybase login passphrase: REDACTED
- run scrypt [==================================] 100%
info: Made directory '/Users/kris/.cache/keybase'
info: Updated file: /Users/kris/.cache/keybase/session.json
info: Made directory '/Users/kris/.config/keybase'
info: Updated file: /Users/kris/.config/keybase/config.json
error: `gpg` exited with code 2
warn: gpg: keyblock resource `/Users/kris/.gnupg/secring.gpg': file open error
warn: gpg: keyblock resource `/Users/kris/.gnupg/pubring.gpg': file open error
warn: gpg: fatal: /Users/kris/.gnupg: directory does not exist!
warn: secmem usage: 0/0 bytes in 0/0 blocks of pool 0/32768
```

Ideally I think keybase should prep gpg to make it as easy as possible but at the very least I would have liked to see a message in the error stating how I could fix such an issue.

Start by reproducing `keybase login` on Mac OS X 10.11.3 with no `~/.gnupg` directory, then inspect the login path that invokes `gpg`. Compare the behavior with running `gpg -K`; done means login either prepares the required GPG state or reports an actionable fix instead of the raw error.

Written by the indexing model from the issue text.