On Sun, 06 Sep 2020 00:02:38 +0200 Jeremie Courreges-Anglas <[email protected]>:
> On Sat, Sep 05 2020, Solène Rapenne <[email protected]> wrote: > > Le 2020-09-05 13:25, Edd Barrett a écrit : > >> Hi all, > >> We've been talking about trying to remove security/gnupg (i.e. gpg > >> version 1) for some time, and the recent plist clash has given me the > >> kick up the butt I needed to look more seriously at this. > >> Below is a list of things that still depend upon gpg1, by maintainer, > >> as > >> determined by: > >> select fullpkgpath from ports where build_depends glob > >> '*security/gnupg[^2]*' or run_depends glob '*security/gnupg[^2]*' > >> order by maintainer; > >> Let's see if we can move these to gpg2. I'll start by working my way > >> through the ports with no maintainer. I'd appreciate it if maintainers > >> could help out with their ports. > >> solene@: > >> mail/mailpile > > > > It seems mailpile isn't going to support gpg2 before some time. > > https://github.com/mailpile/Mailpile/issues/1133 > > Well there is > https://github.com/mailpile/Mailpile/commit/a01e9c5107cc30dce14c357e71b8d9f50badce55 > > Looking at mailpile/crypto/gpgi.py in the current port, support for > gnupg2 seems available. > > > The development has slowed in the last years, maybe we should remove > > mailpile from ports, the project doesn't seem to be going anywhere. > > Valid concern IMO. > mail/mailpile works with gnupg2 given you start it with this: env MAILPILE_GNUPG="/usr/local/bin/gpg2" mp When you start mailpile without "gpg" binary in $PATH, you get this message: > Required binary missing or unusable: GnuPG not found > If you know where it is, or would like to skip this test and run Mailpile > anyway, you can set one of the following environment variables: > MAILPILE_GNUPG="/path/to/binary" > or > MAILPILE_IGNORE_BINARIES="GnuPG" > Note that skipping a binary check may cause the app to become unstable or > fail in unexpected ways. If it breaks you get to keep both pieces! Not sure what to do about this port.
