Performing an upgrade e.g. from UCS 4.2 to 4.3 (when Kopano updates have been previously installed from the Kopano repository) cannot be done in an automated way, since it requires the availability of all Kopano packages for the new UCS version at the time of the upgrade. With the below steps a successful upgrade from e.g. UCS 4.2 to 4.3 can be performed.
0. Install the latest available Kopano release from the repositories
You should start this process with the latest versions.
1. Disable the Kopano repositories
This needs to be done so that the upgrade is no longer blocked by the pre-upgrade checks of Univention. The repositories can either be deactivated from the "APP SETTINGS" from each app, through the UCS browser or by executing the following snippet when logged in via ssh:
2. Manually add the repository for the UCS version you are upgrading to
As explained above it is required that we have a package source that matches the new UCS version during the upgrade. For this it is the easiest to just add this to the /etc/apt/sources.list file.
The following command will automatically get your configured username and password and adds the repo to the bottom of the file:
3. Perform the UCS upgrade as described by Univention
It was reported that before doing the actual upgrade UCS may want to upgrade some Kopano packages already before kicking off the dist upgrade. This should be denied.
4. Remove the entry from "Step 2" from your sources.list file.
5. Install any available app updates
Only the apps contain the actual integration bits between Kopano and UCS. In the case of the UCS 4.3 upgrade the integration takes care of using the proper PHP version for WebApp for example.
Since the versions of e.g. kopano-webapp that you have previously installed from the official Kopano repositories are higher than the version provided by the app, only the integration parts will be updated and the WebApp remains at the previous version.
6. Reenable the Kopano repositories
To benefit from the updates that are published by Kopano you should now reenable the package repositories, either through the "APP SETTINGS", UCR or from the commandline.