pkglint -r --network --only "migrate"
As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.
pkgsrc changes:
* Switch to distutils.mk in order to avoid installation error in the install
phase (``error: option --single-version-externally-managed not recognized''
ref. to setup.py). No functional changes intended.
* Use MASTER_SITE_PYPI instead of hard-coding the entire pypi.python.org URL.
Changes:
* It was updated in python-3.5 to handle IPAddresses in ServerAltName fields
(something that backports.ssl_match_hostname will do if you also install the
ipaddress library from pypi).
Problems found locating distfiles:
Package f-prot-antivirus6-fs-bin: missing distfile fp-NetBSD.x86.32-fs-6.2.3.tar.gz
Package f-prot-antivirus6-ws-bin: missing distfile fp-NetBSD.x86.32-ws-6.2.3.tar.gz
Package libidea: missing distfile libidea-0.8.2b.tar.gz
Package openssh: missing distfile openssh-7.1p1-hpn-20150822.diff.bz2
Package uvscan: missing distfile vlp4510e.tar.Z
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
security/py-backports.ssl_match_hostname.
The Secure Sockets layer is only actually secure if you check the
hostname in the certificate returned by the server to which you
are connecting, and verify that it matches to hostname that you
are trying to reach.
But the matching logic, defined in RFC2818, can be a bit tricky to
implement on your own. So the ssl package in the Standard Library
of Python 3.2 and greater now includes a match_hostname() function
for performing this check instead of requiring every application
to implement the check separately.
This package contains the backport of this functionality to Python 2.
