Using:

Roundcube 1.2.0 on shared server (Bluehost running php5.6.17) with the following Kolab plugins:

• kolab/libcalendaring 3.2.9.2
• kolab/calendar 3.2.9.1

What happened:

After adding "kolab/libcalendaring": "~3.2.9" to composer.json requires (all changes made via ssh and vim on Bodhi Linx 3.2.1):

$ php composer.phar install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file

• Installing kolab/libcalendaring (3.2.9.2) Cloning 3.2.9.2

Do you want to activate the plugin libcalendaring? [N|y] y

Then,

After requiring "kolab/calendar": "~3.2.9":

$ php composer.phar update
Loading composer repositories with package information
Initializing PEAR repository https://pear.php.net
Updating dependencies (including require-dev)

**Deprecation Notice: The Composer\Package\LinkConstraint\VersionConstraint class is deprecated, use Composer\Semver\Constraint\Constraint instead. in phar:///ROUNDCUBEDIRECTORY/composer.phar/src/Composer/Package/LinkConstraint/VersionConstraint.php:17
Deprecation Notice: The Composer\Package\LinkConstraint\LinkConstraintInterface interface is deprecated, use Composer\Semver\Constraint\ConstraintInterface instead. in phar:///ROUNDCUBEDIRECTORY/composer.phar/src/Composer/Package/LinkConstraint/LinkConstraintInterface.php:17**

Installing kolab/calendar (3.2.9.1)
Cloning 3.2.9.1

Do you want to activate the plugin calendar? [N|y] y
Updated local config at /ROUNDCUBEDIRECTORY/config/config.inc.php
Status: 500 Internal Server Error
Content-type: text/html

Resulting client side error message:

When attempting to save calendar data: "Failed to save changes."

Expected

Normal install.

• != Expected Deprecation Notice
• != Expected 500 Internal Server Error

Functionality update:

I was able to get the calendar working by manually creating the tables according to the SQL initialization files.

However, that is more of a workaround/self-support issue than a fix to the bug (if there is one). Likewise, this improvement does not seem to do anything about the deprecation error, except that it is not appearing when I last updated composer.phar.