Univention Bugzilla – Bug 42603
Find next release update immediately after release update
Last modified: 2016-10-20 12:40:52 CEST
If upgrading the container appbox:4.1-0 to 4.1-1, the update stops. 4.1-2 is found after one hour of waiting. The scripts should make sure that 4.1-2, 4.1-3, 4.2-0 is found in one "univention-app upgrade". See Bug#41840 - we tried to fix it in univention-updater. Due to side effects, we should fix it in univention-docker-container-mode
Fixed in univention-docker-container-mode 1.0.13-2.61.201610080210 Doing /usr/share/univention-updater/univention-updater-check after release_update and app_update. This should find packages right after the App installation and 4.1-5 right after the upgrade from 4.1-3 to 4.1-4. If 4.2-0 is available but held back because of missing repositories, the script should stop. One univention-app upgrade is enough to update. Can be tested by manually installing this version into a 4.1-0 appbox image (e.g., tecart).
OK - update the docker container from 4.1-0 to 4.1-3 with on univention-upgrade call on the host -> univention-app shell dudle ucr get version/patchlevel 0 -> univention-upgrade ... -> univention-app shell dudle ucr get version/patchlevel 3 OK - YAML OK - merged to 4.2-0
<http://errata.software-univention.de/ucs/4.1/301.html>