Log message:
Extend PYTHON_VERSIONS_INCOMPATIBLE to 35

Log message:
Add SHA512 digests for distfiles for security category

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.

Log message:
Mark packages that are not ready for python-3.3 also not ready for 3.4,
until proven otherwise.

Log message:
Mark packages as not ready for python-3.x where applicable;
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE=  33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE=  33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.

Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.

Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.

Whitespace cleanups and other nits corrected, where necessary.

Log message:
Disable integrated assembler with Clang, it doesn't like some of the
Intel assembler parts.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Split version into sane and excessive parts.

Upstream's version is 0.6.0.X, where X appears to be a large integer
in decimal that corresponds to a git sha1 has.  Such large numbers
violate the assumption, true with just about every previous package,
that version number components will fit in an int --- code that
handles version numbers does not use a multiprecision integer library
like gmp.  To address this, split the version into what would have
been the version under normal procedures (0.6.0), and put the bignum
into ${VERSION_EXCESSIVE}, allowing it be used in DISTNAME but not
PKGNAME.

Log message:
fix distinfo; patch-aa is gone

Log message:
Set license (GPLv2, or boutique license not in pkgsrc/licenses).

Log message:
Update to 0.6.0.1206569328141510525648634803928199668821045408958.
(Yes, that ridiculous version number really is what upstream calls it.)

No NEWS entry, but announcement includes:

2012-03-13  Zooko Wilcox-O'Hearn  <zooko@zooko.com>

      * src/pycryptopp/_version.py: release pycryptopp-0.6.0
      * add Ed25519 signatures (#75)
      * add XSalsa20 cipher (#40)
      * switch from darcs to git for revision control
      * pycryptopp version numbers now include a decimal encoding of *
      * reorganize the source tree and the version number generation
      * aesmodule.cpp: validate size of IV and throw exception if it
        is not 16 (#70)
      * fixed compile errors with gcc-4.7.0 (#78)
      * fixed compile errors concerning \ 
"CryptoPP::g_nullNameValuePairs" (#77)
      * suppress warnings from valgrind with new OpenSSL 1.0.1 on Fedora (#82)
      * raise Python exception instead of uncaught C++ exception
        (resulting in abort) when deserializing malformed RSA keys (#83)