notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
Some details on the 2023-01-16 website outage.
We just rebooted with several updates: * new HMTLify code * no port maintainer is now highly visible (e.g. * fixed search logic error when using plain/ text details at
Port details
gnupg22 The GNU Privacy Guard (modern version)
2.2.0_1 security Deleted on this many watch lists=0 search for ports that depend on this port Find issues related to this port Report an issue related to this port View this port on Repology. pkg-fallout Version of this port present on the latest quarterly branch.
Maintainer: search for ports maintained by this maintainer
Port Added: 2017-08-28 13:11:36
Last Update: 2017-09-19 18:31:49
SVN Revision: 450153
License: GPLv3 LGPL3
Homepage    cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ SVNWeb
pkg-plist: as obtained via: make generate-plist
There is no configure plist information for this port.
Dependency lines:
  • gnupg22>0:security/gnupg22
No installation instructions:
This port has been deleted.
PKGNAME: gnupg22
Flavors: there is no flavor information for this port.

No package information for this port in our database
Sometimes this happens. Not all ports have packages. This is doubly so for new ports, like this one.
NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
Build dependencies:
  1. libassuan>=2.4.3 : security/libassuan
  2. libgpg-error>=1.16 : security/libgpg-error
  3. gmake : devel/gmake
  4. pkgconf>=1.3.0_1 : devel/pkgconf
  5. msgfmt : devel/gettext-tools
Runtime dependencies:
  1. pinentry : security/pinentry
  2. indexinfo : print/indexinfo
Library dependencies:
  1. : security/libassuan
  2. : security/libgcrypt
  3. : security/libgpg-error
  4. : security/libksba
  5. : devel/npth
  6. : security/gnutls
  7. : converters/libiconv
  8. : databases/sqlite3
  9. : devel/gettext-runtime
There are no ports dependent upon this port

Configuration Options:
Options name:
FreshPorts was unable to extract/find any pkg message
Master Sites:
Expand this list (13 items)
Collapse this list.
Collapse this list.
Port Moves
  • port moved to security/gnupg on 2017-09-19
    REASON: Removed, security/gnupg is now gnupg22

Number of commits found: 4

Commit History - (may be incomplete: for full details, see links to repositories near top of page)
CommitCreditsLog message
19 Sep 2017 18:31:49
Revision:450153Original commit files touched by this commit
adamw search for other commits by this committer
Update gnupg to 2.2.1, and remove the security/gnupg22 port

I misjudged the timeline for 2.3, and had not processed that the
intent of 2.3 is different from 2.1. Rather than 2.3 being a "modern"
branch and 2.2 being purely "stable," 2.3 will be development and
users are encouraged to remain on 2.2. Furthermore, upstream doesn't
expent a 2.3 release for a year or so.

Accordingly, I'm removing the gnupg22 port and updating security/gnupg
to be 2.2. gnugp20 is still scheduled for deletion at the end of the
10 Sep 2017 20:55:39
Revision:449591Original commit files touched by this commit
gerald search for other commits by this committer
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/ and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/ which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++11-lang,
   c++14-lang, c++0x, c11, or gcc-c++11-lib.

PR:		219275
28 Aug 2017 13:53:12
Revision:448868Original commit files touched by this commit
adamw search for other commits by this committer
Fix PKGBASE collision.

Reported by:	antoine
28 Aug 2017 13:02:24
Revision:448867Original commit files touched by this commit
adamw search for other commits by this committer
Add gnupg22 port. GnuPG 2.2 is the new LTS stable version. gnupg20 is
now marked for deprecation at the end of the year (when upstream support
for it will end). Users of gnupg20 should migrate to gnupg22.

The gnupg port is remaining at 2.1.x for now, as it's essentially the
same thing as 2.2.0. It will become 2.3 soon-ish.

Number of commits found: 4