Please also consider documents of following release updates and
3rd party components.
Do you want to continue [Y/n]? Y
WARNING: Cyrus-2.2 is no longer supported by UCS-4 and must be migrated to a
newer version of Cyrus-IMAPd. See sdb.univention.de/1213 for
more details.
Error: Please check “/var/log/univention/updater.log” for details.
ERROR: update failed. Please check /var/log/univention/updater.log[/size]
did you check /var/log/univention/updater.log for additional details?
[bug]36372[/bug] has some informations about the check, you might want to have a look at comment #3.
updater.log has the exact information that the systems drops on console while doing the upgrade. Any more ideas? . I also tried univention-install --reinstall cyrus-common-2.4
Please also consider documents of following release updates and
3rd party components.
Do you want to continue [Y/n]?
Custom preupdate script /var/lib/local-preup.sh not found
WARNING: Cyrus-2.2 is no longer supported by UCS-4 and must be migrated to a
newer version of Cyrus-IMAPd. See sdb.univention.de/1213 for
more details.
Error: Update aborted by pre-update script of release 4.0-0
exitcode of univention-updater: 1
ERROR: update failed. Please check /var/log/univention/updater.log
check_for_cyrus22 () {
case "$(dpkg-query -W -f '${Status}' cyrus-common-2.2 2>/dev/null)" in
install*) ;;
*) return 0 ;;
esac
echo "WARNING: Cyrus-2.2 is no longer supported by UCS-4 and must be migrated to a"
echo " newer version of Cyrus-IMAPd. See http://sdb.univention.de/1213 for"
echo " more details."
if is_ucr_true update40/ignore_cyrus22; then
echo "WARNING: update40/ignore_cyrus22 is set to true. Skipped as requested."
else
exit 1
fi
}
at first a note regarding the preup.sh: this script is directly fetched from the configured repository. In most cases updates.software-univention.de/4 … l/preup.sh is used. This is the file where I searched for the function yesterday.
From your dpkg-query line I can not see any hints too, but the script is using the “-f” switch to determine the status.
example from a 4.0 installation, enhanced for easier reading:
root@m:~# dpkg-query -W -f '${Status}' cyrus-common-2.2; echo
unknown ok not-installed
root@m:~# dpkg-query -W -f '${Status}' cyrus-common-2.4; echo
install ok installed
There might be some environmental influence which leads the script to assume that the cyrus-common-2.2 is installed.
In case you are sure that this is not the case (and no other inconsistencies in the package-status are appearing) you could set the mentioned UCRV “update40/ignore_cyrus22” to “true” and skip this check.
Hi Dirk,
Didn’t saw your post. To circumvent and resolve the problem I did
1) univention-remove cyrus-common
That removed cyrus-common-2.4 and all the packages related to it. The system then automtically reinstalled cyrus-common-2.2.
2) I followed the procedure described on See [sdb.univention.de/1213](http://sdb.univention.de/1213)
3) Did an upgrade then to cyrus-common-2.4 and univention-upgrade the passthrough. SOLVED.
Upgrade process is went all good through 4.0 and it is stalled on 4.01 on an error I will post in another thread.