[email protected] (new formula)

[anthumchris]

Adds a new keg-only versioned formula for GNU Privacy Guard gnupg v2.5.14 (release notes).

Should this package be considered cryptography and exempt from the error below? GNU Privacy Guard generates cryptographic encryption/signing/auth keys (via libcrypt). I commented out system "make", "check" to satisfy brew audit --strict --new [email protected].

Formulae in homebrew/core (except e.g. cryptography, libraries) should not run build-time checks

Feature parity is maintained with the Homebrew's curent release. Explicit pinentry path is not needed to build

[email protected] (this)                          gnupg
——————————————————————————————————————    ——————————————————————————————————————
                                          
GnuPG v2.5.14 has been                    GnuPG v2.4.8 has been
  configured as follows:                    configured as follows:
                                          
Revision:  4d993c37d  (19865)             Revision:  6f39568ae  (28473)
Platform:  Darwin                         Platform:  Darwin
                                          
OpenPGP:   yes                            OpenPGP:   yes
S/MIME:    yes                            S/MIME:    yes
Agent:     yes                            Agent:     yes
Smartcard: yes                            Smartcard: yes 
TPM:       no                             TPM:       no 
G13:       no                             G13:       no
Dirmngr:   yes                            Dirmngr:   yes
Keyboxd:   yes                            Keyboxd:   yes
Gpgtar:    yes                            Gpgtar:    yes
WKS tools: yes                            WKS tools: yes
                                          
Protect tool:       (default)             Protect tool:       (default)
LDAP wrapper:       (default)             LDAP wrapper:       (default)
Default agent:      (default)             Default agent:      (default)
Default pinentry:                         Default pinentry:
  /usr/local/opt/pinentry/bin/pinentry      /usr/local/opt/pinentry/bin/pinentry
Default scdaemon:   (default)             Default scdaemon:   (default)
Default keyboxd:    (default)             Default keyboxd:    (default)
Default tpm2daemon: (default)             Default tpm2daemon: (default)
Default dirmngr:    (default)             Default dirmngr:    (default)
                                          
Dirmngr auto start:  yes                  Dirmngr auto start:  yes
Readline support:    yes                  Readline support:    yes
LDAP support:        yes                  LDAP support:        yes
TLS support:         gnutls               TLS support:         gnutls
TOFU support:        yes                  TOFU support:        yes
Tor support:         yes                  Tor support:         yes

---

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

[carlocab]

Given this announcement we should probably update the gnupg formula to 2.5 (and consider adding a [email protected]) instead.

[fxcoudert]

A few days ago, we decided not to. #257408

The status has not changed, the announcement as already that way for previous releases. But the homepage still lists it as “devel”:

[fxcoudert]

We ship versioned formulas in some cases, but usually for older versions, not for "pre-releases". This is a bit of a weird case.

[anthumchris]

should we rename to [email protected]? This provides the latest security/features to users while explicitly removing ambiguity.

[anthumchris]

new commit 3cfbe06 provides disambiguation, here's how it displays to users:

[anthumchris]

closing until I resolve this failed test. possibly caused by excluding --with-pinentry-pgm --with-readline from build config

$ gpg --quick-generate-key --batch --passphrase '' test1@test

$ gpg --quick-generate-key --batch test2@test
gpg: agent_genkey failed: No pinentry
gpg: key generation failed: No pinentry