With Kopano apps installed (Core, Webapp, Webmeetings, Z-Push), the distupgrade UCS 4.1 to 4.2 deinstalls most of Kopano server packages.
/var/log/univention/updater.log starts deciding to uninstall this way:
Investigating (0) kopano-utils [ amd64 ] < 8.1.2.1-11.1 -> 8.2.1.530-2.3 > ( mail )
Broken kopano-utils:amd64 Hängt ab von on kopano-client [ amd64 ] < 8.1.2.1-11.1 -> 8.3.1~35-6.1 > ( mail ) (= 8.2.1.530-2.3)
Considering kopano-client:amd64 44 as a solution to kopano-utils:amd64 4
Removing kopano-utils:amd64 rather than change kopano-client:amd64
what literally means: kopano-client is avaliable in version 8.3.x, but kopano-utils only up to 8.2.x
Digging where the packages came from:
apt-cache policy kopano-client
kopano-client:
Installed: 8.3.1~35-6.1
Candidate: 8.3.1~35-6.1
Version table:
*** 8.3.1~35-6.1 0
500 http://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ z-push-kopano_20170630110344/amd64/ Packages
apt-cache policy kopano-utils
kopano-utils:
Installed: (none)
Candidate: 8.2.1.530-2.3
Version table:
8.2.1.530-2.3 0
500 http://appcenter.software-univention.de/univention-repository/4.2/maintained/component/ kopano-core_20170425130134/amd64/ Packages
8.1.2.1-11.1 0
500 http://appcenter.software-univention.de/univention-repository/4.1/maintained/component/ kopano-core_20170425130134/amd64/ Packages
Browsing manually in the repository, I see there’s a component kopano-core_20170530164016 but the log reveals that this component was not accessed at all (only the 20170425… one).
Could it be that this component didn’t get activated?