Update to 0.9.9.3. Nothing much changed between .2 and .3, update is
straightforward.
While here, make MESSAGE more helpful in case of package upgrade.
Changelog:
0.9.9.2 => 0.9.9.3
Functionality Enhancements
* Bindings available to a principal are now listed in the Admin UI.
* Attempt to login using supplied basic authentication credentials, if all else fails.
Bug Fixes
* WebDAV Sync is now supported for Addressbook collections.
* VCARD resources will no longer report a blank ETag in an XML responses.
* The ETag property will be properly quoted when appearing an XML response.
Other Changes
* 412 error responses to PUT for addressbook resources now include useful information.
* A new temporary configuration option is added to allow use of the old sync-response tag in WebDAV sync for compatibility with the Inverse CardDAV plugin for Lightning.
* Basic recognition of VLIST resources.
Changelog:
0.9.9.1 => 0.9.9.2
Functionality Enhancements
* Tickets and Bindings related to a collection or principal are now listed in the Admin UI.
Bug Fixes
* The CardDAV 'addressbook-query' report is enabled.
* A bug is fixed in the database libraries which caused some valid hexadecimal strings to be treated as numbers.
* The PAM auth method now parses the username field better (Jim Hague).
* An ETag will now be sent in response to a PUT for non-Calendar resources as well as for calendaring ones.
* Collection / Principal maintenance screens will no longer cause query errors during the create action.
0.9.9 => 0.9.9.1
Functionality Enhancements
* Initial support for vCard Extensions to WebDAV (CardDAV) - Draft
* WebDAV Sync RFC (draft) support is updated to draft version -03
* Support for /.well-known/caldav and /.well-known/carddav URLs (per RFC5785: Defining Well-Known URIs)
Bug Fixes
* Free/busy handling has been completely rewritten.
* LDAP group handling should be better
* UTF8 calendars should now be more reliably imported.
* There should be no need to override the DAV header.
* Many others.
Other Changes
* Some updated translations
* Clients which set the Content-Type incorrectly on PUT should be accommodated with a warning logged.
* Errors in the DAViCal configuration file should not generate output to the screen. This has been a common problem causing breakage in the DAV functionality. Errors will still be logged to the PHP error log (usually the Apache error log).
DAViCal is a server for calendar sharing. It is an implementation of the
CalDAV protocol which is designed for storing calendaring resources (in
iCalendar format) on a remote shared server.
DAViCal supports basic delegation of read/write access among calendar users,
multiple users (or clients) reading and writing the same calendar entries over
time, and scheduling of meetings with free/busy time displayed.
An increasing number of calendar clients support the maintenance of shared
remote calendars through CalDAV, including Evolution, Mulberry, Chandler,
Mozilla Calendar (Sunbird/Lightning), and various other closed-source
products such as Apple's iCal and iPhone.
