Log message:
Add python-3.6 to incompatible versions.

Log message:
Remove python33: adapt all packages that refer to it.

Log message:
Extend PYTHON_VERSIONS_INCOMPATIBLE to 35

Log message:
Add SHA512 digests for distfiles for time category

Problems found with mismatching existing digests for:
	distfiles/asclock-classic-1.0.tar.gz
	distfiles/asclock-gtk-2.1.10beta.tar.gz
	distfiles/asclock-xlib-2.0.11.tar.gz
	distfiles/emiclock-2.0.2.tar.gz

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:
Improve EGG_NAME default to work for packages with '-' in their name.
Remove now unnecessary overrides in various packages.

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

Log message:
Update to 3.2.7. Changes not found.
Set LICENSE. Fix interpreter path in installed files.

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

Log message:
Update to 3.2.4:

Changes from 3.2.3 to 3.2.4

    Fixed a possible double deallocation in the mxDateTime C API
    import helper. Thanks to Daniele Varrazzo for reporting this.

Changes from 3.2.2 to 3.2.3

    Fixed a possible segfault when using the .pydate(), .pydatetime()
    and .pytime() methods. Thanks to Daniel Szoska for reporting
    this.

Changes from 3.2.1 to 3.2.2

    mxDateTime seconds rounding is now more careful to not show
    60.00 or 61.00 as second value.
    mxDateTime will now correctly work with numeric arrays (numpy)
    again. Thanks to Christian Marquardt for reporting the problem.
    mxDateTime's DateTimeFromAbsDateTime() now accepts leap second
    values (86400.0 - <86401.0) as well. Thanks to Christian
    Marquardt for reporting the problem.
    mxDateTime range errors did not always format the wrong value.
    Made mxDateTime compile again on Python 2.1 and 2.2.

Changes from 3.2.0 to 3.2.1

    Fixed a segfault when comparing DateTime/DateTimeDelta with
    None objects. Thanks to Mark Matthews for reporting this.

Changes from 3.1.2 to 3.2.0

    Added new .rebuild() methods to both DateTime and DateTimeDelta
    objects, making it easier creating new objects from existing
    ones by just replacing some of the parameters (akin to the
    mxURL .rebuild() method).
    Greatly enhanced the interoperability with the Python datetime
    module objects:
	Added support for handling mixed type operations with
	datetime.time objects.
	Added new constructor methods to DateTime and DateTimeDelta
	objects which aid in combining them with Python datetime
	module objects: .pytime(), .pytimedelta(), .pydatetime()
	and .pydate() as appropriate.
	Added support for Python datetime module objects to the
	generic mxDateTime constructors DateTimeFrom(), DateFrom(),
	DateTimeDeltaFrom() (and their aliases).
	The Python datetime module's C API is now loaded on demand
	whenever mxDateTime needs to work with PyDateTime objects.
	mxDateTime was updated to use mixed type number slots, a
	feature which was added to Python in version 2.1 (by the
	author of mxDateTime, Marc-André Lemburg). This has made
	working with DateTime and DateTimeDelta objects and other
	date/time types a lot more orbust.
    mxDateTime's gmtime() now also works for ticks values beyond
    2038 on 32-bit platforms that implement a POSIX confirm gmtime(),
    but cannot handle post 2038 dates due to data type restrictions,
    e.g. older 32-bit Linux platforms. As side-effect, this also
    speeds up the gmtime() implementation on all platforms with
    POSIX conform date/time handling.
    mxDateTime will try to use the most accurate clock available
    on the system for now(). For most POSIX systems, this is a
    nanosecond resolution clock. A new global now_resolution allows
    checking the resolution reported by the system. The performance
    of now() was enhanced by directly interfacing to the various
    platform C APIs.
    Changed: mxDateTime will now format the seconds value in the
    repr() and the str() output rounded to two decimal places. In
    previous versions, it used to truncate the fraction after two
    decimal places.
    Known problem: mxDateTime doesn't build on FreeBSD with Python
    2.7 and 2.7.1. This is a known problem with Python 2.7 and will
    be fixed in Python 2.7.2. See  http://bugs.python.org/issue10547
    for details.
    DateTimeFrom() now accepts a defaultdate parameter when parsing
    strings or keyword-only arguments. defaultdate provides the
    defaults to assume when pars of the date/time are not given.
    It defaults to today().
    DateFrom() will now only parse the date parts of a string and
    only accept date-related keyword arguments.
    Fixed a bug in the mxDateTime parser that triggered with some
    ISO formats using second fractions. Thanks to Francesco
    Pierfederici for bringing this to our attention.
    Added support for more US AM/PM date formats such as "5:08pm"
    (without space), "5:08 p.m." (with additional dots) to the
    mxDateTime parser. Thanks to Tom at TicketStumbler for bringing
    this to our attention.
    Changed C API: mxDateTime now uses C longs for years internally
    and in the C API. Note that the published C API has changed
    because of this: mxDateTime.DateTime_FromDateAndTime() now
    expects a long as year instead of an int. This change will
    require a recompile of the applications using the mxDateTime
    C API, but should only be noticeable on 64-bit platforms.
    Added new C API DateTime_FromAbsDateTime to the mxDateTime C
    API.
    Added version number to C API object: Due to the changes in
    the C API, the name of the C API object "mxDateTimeAPI" was
    changed to "mxDateTimeAPI2", so that applications relying on
    the old API don't import the changed API by accident.
    Added optional calendar parameter to DateTimeFromAbsDateTime().
    This allows creating DateTime instances with a given calendar.
    Default is to use the Gregorian calendar.
    Added BST to mx.DateTime.Timezone.
    Fixed problem with now() resolution on Windows. It now provides
    millisecond resolution again.
    Fixed a bug in mx.DateTime.DateTimeFromAbsDateTime() which
    caused an endless loop on 64-bit platforms for very large year
    values.
    Fixed Debian bug#494792: Incorrect subtraction with regular
    Python datetime. This was actually a side-effect of the coercion
    logic previously used in mxDateTime and not really a bug. The
    new mixed type number slot implementations made it possible
    to Darko Zurman for pointing this out.
    Removed left-over debug code which caused the builtin strptime()
    never to get used. Thanks to Alok Singhal for this one.
    Fixed a bug in the mxDateTime .ticks() method which causes it
    to raise an error for vahe Epoch.

Log message:
Set BUILDLINK_ABI_DEPENDS correctly (with +=, not ?=)
It turns out there were a lot of these.