Upgrading on OS X: GPG not available, then forced reprovision
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I installed the new Keybase without first installing GPG. It worked fine, including Keybase FS.
After upgrading to 1.0.16-20160803190018+268b023: Keybase forced login, which failed with an error about GPG not being available.
After brew install gnupg2, logging in worked, but Keybase took me through the new device process.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the report. Start by reproducing the upgrade from the described pre-GPG state on OS X, then trace the login and device-provisioning flow; done means the upgrade handles missing GPG without forcing an unnecessary reprovision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- authentication, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100