Update to 0.2.1, latest release on pypi. From ChangeLog:

	* caldav/davclient.py - minor api difference; it feels more
	object-oriented to write principal = client.principal() than
	principal = Principal(client)

	* caldav/tests/test_caldav.py - work to reflect the above

	* docs/source/index.rst - work to reflect the above

	* docs/source/index.rst - added documentation that the tests may
	fail if several test runs are performed simultaneously

	* caldav/davclient.py - support for unicode and utf8

	* caldav/lib/url.py - support for unicode and utf8

	* caldav/objects.py - minor doc enhancement

	* tests/test_caldav.py - load an event or a calendar by the URL

	* tests/test_caldav.py - test calendar.events()

	* tests/test_caldav.py - test utf8 and unicode

	* docs/source/index.rst - documentation on how to run the test
	suite towards private calendar servers

	* caldav/lib/url.py (make): function for backward compatibility

	* tests/: more test code, including backward compatibility test

	* caldav/lib/namespace.py: fixing issue

	* caldav/objects.py (Calendar): compatibility hack for zimbra -
	gotcha!  Use Calendar display name in the Calendar URL instead of
	Calendar ID.

	* caldav/objects.py: internal change - _create method now returns
	nothing, but sets self.url and self.id instead.

	* caldav/objects.py (DAVObject): convenience fix - made client a
	conditional parameter to __init__.  Defaults to parent.client if
	parent is given.

	* caldav/objects.py (Calendar): convenience fix - made methods
	Calendar.event_by_uid and Calendar.event_by_url.  Calendar.event
	is an alias to Calendar.event_by_uid for backwards compatibility.
	Those methods also loads the object from the remote server (hmmm
	... does that make sense, it's inconsistent with the
	CalendarSet.calendar method)

	* caldav/objects.py (Event): a potential compatibility fix - when
	creating an event, some servers seems to want the uid to match the
	URL (zimbra will yield 302 on the PUT request).  However, I wasn't
	able to GET the event from zimbra, neither before nor after this
	fix :-(

	* caldav/elements/cdav.py: compatibility fix - collation
	"i; octet" (with whitespace) not recognized by baikal.  "i;octet"
	(without whitespace) is OK.

	* caldav/objects.py (Calendar): Convenience fix: method add_event
	for making it easier to add events.  Better error handling; if
	calendar creation succeeds but setting calendar name fails, delete
	the calendar before raising the exception.

	* caldav/objects.py (Event): Bugfix for zimbra - 302 is now an
	acceptable return code when creating a new event.

	* caldav/davclient.py (DAVClient.request, DAVResponse): Full HTTP
	communication is now available in debug logs

	* caldav/davclient.py (DAVClient.__init__): Username and password
	can now (optionally) be given as separate parameters instead of as
	a part of the configuration URL

	* caldav/objects.py: By now it's sufficient to pass the base URL
	while initializing the DAVClient object.  The library will find
	the principal URL and home calendar set URL through GETPROP

	* caldav/objects.py (Calendar): workaround for problem that
	calendar name didn't get set on some (all?) caldav servers.

	* caldav/objects.py (Principal, CalendarSet): created a method
	calendar() to make it easier to generate a calendar object
	(without server-side communication), and make_calendar for
	creating a new calendar at the server side.

	* tests/test_caldav.py: all broken tests have been disabled.
	Temporary made smaller tests to demonstrate what is actually
	working on all caldav servers I've tested against (Zimbra,
	DAViCal, Baikal and SoGo).

	* caldav/objects.py (DAVObject): (internal change) set __str__ and
	__repr__ to make debugging easier

	* caldav/objects.py: (internal change) Since the principal path and the calendar
	home set path are different on most CALDav server implementations,
	a new class CalendarSet has been made.

	* caldav/lib/url.py: (internal change) Complete rewrite and
	API-change. internally all URLs are now handled as objects

	* caldav/objects.py (Principal): (internal change) made it
	possible to set principal.calendar_home_set (hardly useful except
	for from the unit testing code).

	* All files: misc minor changes to reflect all the changes above.
Updated net/py-caldav to 0.2.1
Updated to latest release, 3.0.14. From ChangeLog:

- **MongoDB**: Now endures a connection failover (Issue #123).
- **MongoDB**: Fixed ``KeyError`` when a replica set member is removed.
    Also fixes celery#971 and celery/#898.
- **MongoDB**: Fixed MongoDB broadcast cursor re-initialization bug.
- **Async**: Fixed bug in lax semaphore implementation where in
  some usage patterns the limit was not honored correctly.
- **Redis**: Fixed problem with fanout when using Python 3 (Issue #324).
- **Redis**: Fixed ``AttributeError`` from attempting to close a non-existing
  connection (Issue #320).
- Redis: Fixed serious race condition that could lead to data loss.

    The delivery tags were accidentally set to be an incremental number
    local to the channel, but the delivery tags need to be globally
    unique so that a message can not overwrite an older message
    in the backup store.

    This change is not backwards incompatible and you are encouraged
    to update all your system using a previous version as soon as possible.

- Now depends on :mod:`amqp` 1.4.4.
- Pidbox: Now makes sure message encoding errors are handled by default,
  so that a custom error handler does not need to be specified.
- Redis: The fanout exchange can now use AMQP patterns to route and filter
  messages.
    This change is backwards incompatible and must be enabled with
    the ``fanout_patterns`` transport option::

        >>> conn = kombu.Connection('redis://', transport_options={
        ...     'fanout_patterns': True,
        ... })

    When enabled the exchange will work like an amqp topic exchange
    if the binding key is a pattern.

    This is planned to be default behavior in the future.

- Redis: Fixed ``cycle`` no such attribute error.
Updated net/py-kombu to 3.0.14
Updated to latest release, 3.1.1.2. New file in PLIST:

${PYSITELIB}/flask_bootstrap/static/jquery.min.map
Updated www/py-flask-bootstrap to 3.1.1.2
Updated to latest release, 4.2.0. Shared library name change. From NEWS:

Implemented a new function to read the ZID file if the ZID file backend
is SQlite3. This is not a security problem because the ZRTP cache was
always public and readable, refer to RFC6189.

SQL statement returns all ZID records, sorted by date, newest on top. The
function can then step thru the DB cursor and read the records.

The version also include sevral fixes, usually compiler warnings, some
small problems reported by 'cppcheck' analyser.

Because we have a new set of functions the API changed, thus it's necessary
to recompile applications that use the new library version.
Updated net/libzrtpcpp to 4.2.0
Update devel/p5-CPAN-Meta-YAML to 0.012.

Changes from previous:
----------------------
0.012     2014-02-24 13:07:18-05:00 America/New_York

  - Generated from ETHER/YAML-Tiny-1.61.tar.gz

0.011     2014-02-13 20:30:30-05:00 America/New_York

  - Generated from ETHER/YAML-Tiny-1.60.tar.gz

0.010     2013-09-23 13:11:20 America/New_York

  - Generated from ETHER/YAML-Tiny-1.55.tar.gz

  - Fix broken test when copying from YAML-Tiny

  - updated Makefile.PL logic to support PERL_NO_HIGHLANDER

0.009     2013-09-23 10:16:19 America/New_York

  - Generated from ETHER/YAML-Tiny-1.55.tar.gz

  - Makefile.PL will use UNINST=1 on old perls that might have
    an old version incorrectly installed into the core library path
Updated devel/p5-CPAN-Meta-YAML to 0.012.
Fixes undefined variable references.
Bumping BUILDLINK_ABI_DEPENDS.libzrtpcpp.