Page tree
Skip to end of metadata
Go to start of metadata

This feature is for most of the apps only available for customers with a valid Kopano subscription. The exception to this is the z-push app, since this does not require a subscription to access the package repository.

Once the repositories are enabled these will be used to update the components of Kopano itself (e.g. core, webapp, webmeetings). When there has been an update for the app integration, this will be provided by an app update shown in the Univention App Center. These app updates can be installed without a problem and will not downgrade the packages installed through the repositories.

Warning: this procedure will block the update from Univention 4.1.x to 4.2.x as well as from 4.2.x to 4.3.x, since the package dependencies for Kopano cannot be cleanly resolved during the upgrade. This has been resolved for the 4.2.x upgrade with the 8.4.5.0 app update. See Upgrading from UCS 4.1 to 4.2 with repositories for additional required steps.

The problem still exists for the 4.3.x update. Univention has announced that they want to introduce an App Center feature that would allow us to publish more Kopano updated directly to the App Center.

 

Starting with version 1.2 of Kopano4UCS (which is part of the app version 8.1.1.10-8.1-2) it is now easily possible to update Kopano directly through the repositories provided by Kopano.

 

For this feature you have to manually once enable the desired repository (at the moment of writing only available for kopano-core). You will need to use the Kopano license serial as password for access to the repositories, and can use the following snippet to quickly enable the repository for Kopano Core from the command line:

univention-config-registry set \
        kopano/repo/kopano-core='true' \
        kopano/repo/username='serial' \
        kopano/repo/password='YOUR-KOPANO-SERIAL'


Updating Kopano WebApp

Starting with version 1.3 of Kopano4UCS (included in the Kopano WebApp  app 3.2.0.335-19.1-2) its also possible to update Kopano WebApp and the individual WebApp plugins through the official Kopano repositories. For WebApp it is also possible make use of the pre-final and master repositories.

univention-config-registry set \
        kopano/repo/kopano-webapp='true' \
        kopano/repo/kopano-webapp-releasetype='final' \
        kopano/repo/kopano-files='true' \
        kopano/repo/kopano-files-releasetype='final' \
        kopano/repo/kopano-mdm='true' \
        kopano/repo/kopano-mdm-releasetype='final' \
        kopano/repo/kopano-smime='true' \
        kopano/repo/kopano-smime-releasetype='final' \
        kopano/repo/username='serial' \
        kopano/repo/password='YOUR-KOPANO-SERIAL'

If kopano-*-releasetype is not set, it will default back to only install updates from the final repository.

Updating Kopano WebMeetings

Starting with version 2.0.5 of Meetings4UCS (included in the Kopano WebMeetings app 3.0.0.92) its also possible to update Kopano WebMeetings through the official Kopano repositories. Just like with WebApp you can choose different release stages. 

univention-config-registry set \
        kopano/repo/kopano-webmeetings='true' \
        kopano/repo/kopano-webmeetings-releasetype='final' \
        kopano/repo/username='serial' \
        kopano/repo/password='YOUR-KOPANO-SERIAL'

If kopano-*-releasetype is not set, it will default back to only install updates from the final repository.

Updating Z-Push

Starting with version 1.3.5 of Kopano4UCS (included in the Z-Push 2.3.7 app) its also possible to update Z-Push through the official repositories. Just like with WebApp you can choose different release stages. But unlike the other repositories no username/password is required.

univention-config-registry set \
        kopano/repo/z-push-kopano='true' \
        kopano/repo/z-push-kopano-releasetype='final'

If z-push-kopano-releasetype is not set, it will default back to only install updates from the final repository.

Upgrading from UCS 4.1 to 4.2 with repositories

Starting with version 1.3.10 of Kopano4UCS (included in the Kopano Core app 8.4.5.0) repository usage for UCS 4.1 is disabled. To perform the upgrade from 4.1 to 4.2 the update repositories have still to be deactived, though. The following script can be used for this:

if [ $(ucr get version/version) == "4.1" ]; then
        univention-config-registry set \
        kopano/repo/kopano-core='false' \
        kopano/repo/kopano-webapp='false' \
        kopano/repo/kopano-files='false' \
        kopano/repo/kopano-mdm='false' \
        kopano/repo/kopano-smime='false' \
        kopano/repo/kopano-webmeetings='false' \
        kopano/repo/z-push-kopano='false'
fi

Once the upgrade to 4.2 is completed the update repositrories can be enabled again to receive the latest updates.

Workaround updating from UCS 4.2 to 4.3 with repositories

The below procedure currently leads to problems with php7-mapi not cleanly installing if Kopano 8.6.2 was already installed prior to the upgrade. We advise to wait for a newer Kopano Groupware Core update before attempting the update.


  1. disable repositories in the UCR (see above for a snippet how to do this)
  2. add Kopano repository for Univention 4.3 (or where that is not available use the one for Debian 9) directly to /etc/apt/sources.list
    1. e.g. "deb https://serial:Z123@download.kopano.io/supported/core:/final/Univention_4.3/ /"
  3. start the dist upgrade to 4.3
    1. there have been reports about UCS trying to upgrade packages before the upgrade. this should be denied and the packages only be upgraded during the 4.3 upgrade
  4. remove the manually configured repositories from the sources.list
  5. install any available app updates
  6. reenable the repositories in the UCR
  • No labels