brew: gpg broken after update

After a brew upgrade today, the gpg binary is no longer linked into /usr/local/bin/gpg.

% brew list gnupg
/usr/local/Cellar/gnupg/1.4.20_1/bin/gpg-zip1
/usr/local/Cellar/gnupg/1.4.20_1/bin/gpg1
/usr/local/Cellar/gnupg/1.4.20_1/bin/gpgsplit1
/usr/local/Cellar/gnupg/1.4.20_1/bin/gpgv1
/usr/local/Cellar/gnupg/1.4.20_1/libexec/gnupg/ (4 files)
/usr/local/Cellar/gnupg/1.4.20_1/libexec/gpgbin/ (4 files)
/usr/local/Cellar/gnupg/1.4.20_1/share/gnupg/ (2 files)
/usr/local/Cellar/gnupg/1.4.20_1/share/info/gnupg1.info
/usr/local/Cellar/gnupg/1.4.20_1/share/locale/ (32 files)
/usr/local/Cellar/gnupg/1.4.20_1/share/man/ (3 files)

It appears to have installed a binary gpg1 instead. However, this does not execute:

% /usr/local/bin/gpg1
dyld: Library not loaded: /usr/local/opt/libusb-compat/lib/libusb-0.1.4.dylib
  Referenced from: /usr/local/bin/gpg1
  Reason: image not found
[1]    41295 trace trap  /usr/local/bin/gpg1

Cheers, Chris

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 2
Comments: 31 (15 by maintainers)

Links to this issue

github - gpg failed to sign the data fatal: failed to write commit object [Git 2.10.0] - Stack Overflow

Commits related to this issue

gnupg: prevent accidental libusb-compat linkage Closes https://github.com/Homebrew/brew/issues/708. Closes #3856. Signed-off-by: Dominyk Tiller <dominyktiller@gmail.com> — committed to Homebrew/homebrew-core by DomT4 8 years ago
Add `gpg.program` Ref Homebrew/brew#708 — committed to SimenB/vcsh_git by SimenB 8 years ago

Most upvoted comments

@SimenB Unless you specifically need GnuPG 1.x for the older crypto, we (and upstream) pretty strongly recommend using gnupg2, which contains the plain executables.

Thanks for letting everyone know in the mailing list about this breaking change…

@diclophis Thanks for understanding that Homebrew is extremely time consuming & a tiny, tiny, tiny amount of active users bother to check the mailing list or Twitter from our prior experiences & therefore may not be the highest priority.

Appreciate your constructive & carefully considered feedback.

DomT4 on Aug 15, 2016

Git commit signing broke for me after this, but a quick git config --global gpg.program gpg1 fixed it. ATM I only use Mac, but might mess up if I go back to Linux in the future.

SimenB on Aug 15, 2016

Hi @apjanke.

When I select Americas/USA as my region, locale’s output is:

LANG="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_CTYPE="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_ALL=

When I select Asia/Japan, the output is:

LANG=
LC_COLLATE="C"
LC_CTYPE="UTF-8"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL=

I managed resolve the issue by exporting LANG to en_US.UTF-8 at the start of my shell.

Thanks!

jorgebucaran on Dec 6, 2016

You might also want to state more clearly that “this is a breaking upgrade to gnupg, which renames the gpg command line tool as gpg1”. Also suggest users consider installing gnupg2 to resolve the issue.

There’s still the problem of new users installing gnupg, which is the obvious package to install if you want to use gpg, and then being confused by the lack of a gpg command line tool.

cleishm on Aug 14, 2016