Upgrading from Kolab 3.4 to Kolab 16

The purpose of this guide is, to describe the procedure of upgrading a Kolab Goupware installation from a default installed Kolab 3.4 (last “community version”) to Kolab 16. The guide is not taking into consideration any customized configuration. neither is it considering installations of Kolab 3.4 on CentOS 6, which is not supported for Kolab 16.

Upgrading Kolab

Install the Kolab Groupware repository configuration:

# cd /etc/yum.repos.d/
# wget http://obs.kolabsys.com/repositories/Kolab:/16/CentOS_7/Kolab:16.repo

Remove the existing Kolab 3.4 repositories:

# rm Kolab\:3.4.repo
# rm Kolab\:3.4\:Updates.repo

Make sure that the packages from the Kolab repositories have a higher priority than e.g. the EPEL packages:

# for f in /etc/yum.repos.d/Kolab*.repo; do echo "priority = 60" >> $f; done

Replace php-mysql with php-mysqlnd:

# yum shell
> remove php-mysql
> install php-mysqlnd
> run
(Confirm as requested)
> exit

Update all:

# yum -y update

Note

During the cleanup, you might see the message:

/var/tmp/rpm-tmp.TUmak9: line 1: fg: no job control
Cleanup : cyrus-imapd-2.5-108.3.el7.kolab_3.4.x86_64 347/404
/var/tmp/rpm-tmp.K51Mal: line 2: fg: no job control
warning: %postun(cyrus-imapd-2.5-108.3.el7.kolab_3.4.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package cyrus-imapd-2.5-108.3.el7.kolab_3.4.x86_64

This is a warning, and the Cyrus-imapd package will be updated. This can be checked after the update with the command:

# rpm -qv cyrus-imapd

Drop the policy_result table from MySQL.

Updating the Configuration

After upgrading the packages to Kolab 16 repository, the configuration needs to be updated.

Configure the new module “Guam”:

# setup-kolab guam

Warning

If the Kolab 3.4 installation was a standard installation with no changes to the defaults, then the following 2 commands can be run at no risk (The correct password for the current roundcube database user is still needed for verification).

However, if changes were made to the defaults, the original configuration should be copied off for later compare with the newly written configuration.

Update the roundcube configuration:

As setup-kolab is unable to write to the already existing mysql database, an error message will show:

ERROR 1007 (HY000) at line 1: Can’t create database ’roundcube’; database exists
ERROR 1050 (42S01) at line 8: Table ‘session’ already exists

The new and updated config file will however be written and the appropriate services be restarted.

The correct password for the current roundcube database user is still needed for verification.

# setup-kolab roundcube

Update the imap configuration:

# setup-kolab imap

Update: Kolab responsive skin

We’re pleased to announce an update for the Kolab Enterprise skin.

This update is a release of the new kolab Enterprise Responsive skin (known under the working title: Elastic). The release is available for for Kolab 16, on Red Hat Enterprise Linux 7, CentOS 7, Debian 8, Debian 9, Ubuntu 16.04 and Ubuntu 18.04,

The kolab-webclient meta package now provides (and requires) the new responsive kolab skin.

 

The skin can be selected from 'Settings -> Preferences -> User interface'. It is possible for an administrator to limit the list of skins available to end users (See below).

 

 

 

As the name indicates, the skin is responsive. It responds to the amount of screen space available on the host, and is hence equally useful on a large desktop monitor:

..and a mobile device:

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

As mentioned, an administrator can configure the skins available to end users by adding the following to the config file /etc/roundcubemail/config.inc.php:

$config['skins_allowed'] = array('kolab');

..and remove the ‘skin’ item from the ‘dont_override’ setting in the same file:

$config['dont_override'] = array();

If desired, change the default skin for those users who has no preference configured (in the same file):

$config['skin'] = 'kolab';

This last configuration eliminates the need for the ‘dont_override’ setting.

Update: pykolab 0.7.33

We’re pleased to announce an update for the pykolab packages, version 0.7.33.

This update is a bugfix release for Kolab Enterprise 14, available for Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, CentOS 6, CentOS 7, Debian 7 and Debian 8.

The following issues are fixed;

  • T123747: An exception where making probelms when handling iTip CANCEL for a resource event. This has been fixed
  • Clean up of the use of duplicate names for functions and in-function scope variables when both are used in the same scope
  • T29104: Support unicode characters in event location field
  • Various other smaller inconveniences

Update: php-net-ldap3 1.0.7

We’re pleased to announce an update for the php-net-ldap3 packages, version 1.0.7.

This update is a bugfix and update release for Kolab Enterprise 14, available for Red Hat Enterprise Linux 6, CentOS 6, Red Hat Enterprise Linux 7, CentOS 7, Debian 7 and Debian 8.

The following issues are fixed and changed:

  • ‘find_domain()’ gave a wrong result when domain wasn’t found. This is fixed
  • Recursive deletion of domains failed. This is now fixed
  • LDAP_OPT_DEBUG_LEVEL option couldn’t be disabled. This is now fixed
  • ldapsearch commands was failing when configured host contained protocol schema prefix. This is now fixed

Update: roundcubemail-plugins-kolab 3.2.22

We’re pleased to announce an update for the roundcubemail-plugins-kolab packages, version 3.2.22.

This update is a bugfix and update release for Kolab Enterprise 14, available for Red Hat Enterprise Linux 6, CentOS 6, Red Hat Enterprise Linux 7, CentOS 7, Debian 7 and Debian 8.

The following issues are fixed and changed:

  • T141857: iTip was detecting date/time change wrongly in some situations. This has been fixed
  • T27883: Allow an event updates on iTip request without SEQUENCE bump
  • T149558: ‘^’ characters were not allowed in parameters in the iCal parser. This has been fixed
  • Fix recurrence text when there are exceptions defined
  • Make iTip links optional and disabled by default
  • T103344: Fix missing first occurrence of an event when moved to another day
  • T101742: Fix resizing all-day events