On Sat, Sep 05 2020, Solène Rapenne <sol...@perso.pw> 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. -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
