[pkgsrc/trunk]: pkgsrc/mail/gmime3 gmime3: update to 3.2.2.

[wiz <wiz%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/821a0c7e4f60
branches:  trunk
changeset: 388155:821a0c7e4f60
user:      wiz <wiz%pkgsrc.org@localhost>
date:      Sat Dec 01 10:45:29 2018 +0000

description:
gmime3: update to 3.2.2.

### GMime 3.2.2

* Fixed packaging to include Vala files.

### GMime 3.2.1

* Fixed GMimeParser to recognize the message/global mime-type
  (a UTF-8 version of message/rfc822). (issue #50)

* Updated GMime to use libidn2 instead of the older libidn
  library. (issue #48)

* Fixed address quoting logic and IDN2 encoding.

    The rules for quoting address names should use 'specials'
    instead of 'tspecials' and when encoding domain names via
    IDN2, check if the encoded domain matches the original
    domain name (other than case). If they match, prefer the
    non-encoded domain name since the user may have used
    uppercase characters to enhance readability of the domain
    name.

* Added GMIME_DECRYPT_ENABLE_ONLINE_CERTIFICATE_CHECKS and
  GMIME_DECRYPT_ENABLE_KEYSERVER_LOOKUPS as possible flags to
  pass to g_mime_crypto_context_decrypt(). Also added
  GMIME_VERIFY_ENABLE_ONLINE_CERTIFICATE_CHECKS and
  GMIME_VERIFY_ENABLE_KEYSERVER_LOOKUPS as possible flags to
  pass to g_mime_crypto_context_verify().

    Clients that wish to enable online certificate and/or
    keyserver lookups now need to explicitly enable this
    functionality.

    These changes are designed to make it more difficult
    for clients to be susceptible to Efail privacy exploits.
    Specifically, it is meant to address the privacy concerns
    regarding CRL and OCSP status check backchannels.

    For more information about Efail, see https://www.efail.de/

* Fixed g_mime_message_write_to_stream() to prioritize message
  headers over body headers (even when they have an offset of -1).
  (issue #46)

* The GMimeParser can now warn about a number of RFC-compliance
  issues that it finds when parsing messages.

* Fixed GMimeTextPart to make sure that the GMimeFilterCharset is
  non-null before trying to use it. This can happen if the charset
  specified in the Content-Type header is unsupported by the
  iconv library.

diffstat:

 mail/gmime3/Makefile |   4 ++--
 mail/gmime3/distinfo |  10 +++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diffs (27 lines):

diff -r ef97b2d4f330 -r 821a0c7e4f60 mail/gmime3/Makefile
--- a/mail/gmime3/Makefile      Sat Dec 01 10:18:38 2018 +0000
+++ b/mail/gmime3/Makefile      Sat Dec 01 10:45:29 2018 +0000
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.3 2018/01/28 15:30:07 wiz Exp $
+# $NetBSD: Makefile,v 1.4 2018/12/01 10:45:29 wiz Exp $
 
-DISTNAME=      gmime-3.2.0
+DISTNAME=      gmime-3.2.2
 PKGNAME=       ${DISTNAME:S/gmime/gmime3/}
 CATEGORIES=    mail
 MASTER_SITES=  ${MASTER_SITE_GNOME:=sources/gmime/3.2/}
diff -r ef97b2d4f330 -r 821a0c7e4f60 mail/gmime3/distinfo
--- a/mail/gmime3/distinfo      Sat Dec 01 10:18:38 2018 +0000
+++ b/mail/gmime3/distinfo      Sat Dec 01 10:45:29 2018 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.3 2018/01/28 15:30:07 wiz Exp $
+$NetBSD: distinfo,v 1.4 2018/12/01 10:45:29 wiz Exp $
 
-SHA1 (gmime-3.2.0.tar.xz) = 78cf0e5fa836720e79c37b8d6b9e531344bce476
-RMD160 (gmime-3.2.0.tar.xz) = e7fd87739a4abaf06cf8212b9ef363e553a118dd
-SHA512 (gmime-3.2.0.tar.xz) = bb45f34b80ff237478602ff05ce0f736373185b7aa260c17aaf00a519d0b75ce9e24b0f6b256ce0f17b613e9f67174c54e302411110bf5f143947591f5f5aa43
-Size (gmime-3.2.0.tar.xz) = 1962544 bytes
+SHA1 (gmime-3.2.2.tar.xz) = e27b747eafa14523a94f6ea003712f1cbfe8606a
+RMD160 (gmime-3.2.2.tar.xz) = 78ede60bac469f8a43b0b71b1ec11136aa681e45
+SHA512 (gmime-3.2.2.tar.xz) = b406492ca9b5aa7b50ccbaf3c76bfbcb0c0ed0280453be35df1c0e13cc5ee60ed61117fa22dacc2fb064c57c50f503c128ff90ec535a04be92ca264e32527e98
+Size (gmime-3.2.2.tar.xz) = 1955796 bytes