keybase / keybase/keybase-issues
Installer fails with exit code 2, running it again works.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Trying to set up the keybase CLI on a mostly bare OS X 10.9.2 install, full terminal log from the session is attached at the end.
As you can see from it, I used npm to install `keybase-installer`, then realized I didn't have `gpg` installed so I used npm to install that, figured out it didn't actually work without having `gpg` installed as a binary, so I used brew to install that, then running the installer failed. Running it again worked.
I think it failed because of this warning: `warn: No code-signing key (code@keybase.io) in GPG keychain`
```
Last login: Tue Mar 4 11:26:03 on ttys001
krahjerdi-mbp:Desktop krahjerdi$ npm install -g keybase-installer
npm http GET https://registry.npmjs.org/keybase-installer
npm http 200 https://registry.npmjs.org/keybase-installer
npm http GET https://registry.npmjs.org/keybase-installer/-/keybase-installer-0.1.8.tgz
npm http 200 https://registry.npmjs.org/keybase-installer/-/keybase-installer-0.1.8.tgz
/usr/local/bin/keybase-installer -> /usr/local/lib/node_modules/keybase-installer/bin/main.js
keybase-installer@0.1.8 /usr/local/lib/node_modules/keybase-installer
krahjerdi-mbp:Desktop krahjerdi$ keybase-installer
error: The command `gpg` wasn't found; you need to install it. See this page for more info:
error: https://keybase.io/__/command_line/keybase#prerequisites
krahjerdi-mbp:Desktop krahjerdi$ npm install -g gpg
npm http GET https://registry.npmjs.org/gpg
npm http 200 https://registry.npmjs.org/gpg
npm http GET https://registry.npmjs.org/gpg/-/gpg-0.3.2.tgz
npm http 200 https://registry.npmjs.org/gpg/-/gpg-0.3.2.tgz
gpg@0.3.2 /usr/local/lib/node_modules/gpg
krahjerdi-mbp:Desktop krahjerdi$ keybase-installer
error: The command `gpg` wasn't found; you need to install it. See this page for more info:
error: https://keybase.io/__/command_line/keybase#prerequisites
krahjerdi-mbp:Desktop krahjerdi$ brew install gpg
==> Downloading ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.15.tar.bz2
######################################################################## 100.0%
==> ./configure --prefix=/usr/local/Cellar/gnupg/1.4.15 --disable-asm
==> make CFLAGS= -std=gnu89 -fheinous-gnu-extensions
==> make check
==> make install
/usr/local/Cellar/gnupg/1.4.15: 54 files, 5.0M, built in 51 seconds
krahjerdi-mbp:Desktop krahjerdi$ keybase-installer
info: Made temporary directory: /var/folders/5m/9c0qcmyx3lz58702sv8g4534pj5h2x/T/keybase_install_3fsrGgbm7KXBs7-rurTteA
info: Creating permanent keyring dir: /Users/krahjerdi/.keybase-installer/keyring
warn: No code-signing key (code@keybase.io) in GPG keychain
info: Fetching URL https://dist.keybase.io/sig/files/1/keyset.json
info: Installing keyset version 1
info: Using keyset version v1
info: Fetching URL https://dist.keybase.io/sig/files/1/index.asc
info: cleaning up tmpdir /var/folders/5m/9c0qcmyx3lz58702sv8g4534pj5h2x/T/keybase_install_3fsrGgbm7KXBs7-rurTteA
error: exit code 2
krahjerdi-mbp:Desktop krahjerdi$ keybase-installer
info: Made temporary directory: /var/folders/5m/9c0qcmyx3lz58702sv8g4534pj5h2x/T/keybase_install_CecFxsQY1JrSwq8UL7MQlw
info: Using keyset version v1
info: Fetching URL https://dist.keybase.io/sig/files/1/index.asc
info: Fetching URL https://dist.keybase.io/pkg/stable
Download /pkg/files/keybase-0.0.31.tgz [=================================================] 100% 0.0s (3389392 bytes total)
info: Fetching URL https://dist.keybase.io/sig/files/1/keybase-0.0.31.tgz.asc
info: verified signature of keybase-0.0.31.tgz against keybase-0.0.31.tgz.asc
info: Running npm install keybase-0.0.31.tgz: this may take a minute, please be patient
=====================================================================
Welcome to keybase.io!
...
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the first-run failure with the keybase-installer command after installing GPG, then compare it with the successful second run. Investigate the reported code-signing-key warning and exit code 2; done means a fresh installation succeeds on the first attempt. The payload names no source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100