Univention Bugzilla – Bug 55593
univention-upgrade updateto dont get an hint or message
Last modified: 2023-01-25 08:39:22 CET
If you are using an UCS 5.0-1 or UCS 5.0-2 and use this command in a shell: "univention-upgrade --updateto=4.4-9" the system dont show any message like "your system is higher then your argument you chose" or "The installed system version is higher then you want to install" and the system will be updated/upgraded.
on a UCS 5.0-1 we get this message "Checking for release updates:5.0-2 is available but updater has been instructed to stop at version 4.4-999" but on a UCS 5.0-2 we don't, which is somehow understandable since there is no newer version available except errata updates.
`univention-upgrade` combines several old tools into one command: - `univention-update` was used to do release upgrade; this is what you limit with `--updateto` - `univention-actualise` was used to install security — now errata — updates only. The low-level commands are still available below `/usr/share/univention-updater/` and do get called from there. As such WONT-FIX or WORKS-FOR-ME (as intended).
At least it seems to become a documentation bug as '<CTRL> f' -> 'univention-update <ENTER>' do not show one hint that these commands are changed and the UCS5 docs still say: "5.3.3 Updating individual systems via the command line The following steps must be performed with root user rights. An individual UCS system can be updated using the univention-upgrade command in the command line..." It is, from point of view, extremely dangerous that the major release value is not considered by that command option. If that has changed it must be documented.
(In reply to Dirk Schnick from comment #3) > At least it seems to become a documentation bug as '<CTRL> f' -> > 'univention-update <ENTER>' do not show one hint that these commands are > changed and the UCS5 docs still say: `univention-upgrade` was introduced with UCS 3.0-0 by Bug #23453 in 2011 and the behavior is unchanged since then. The old scripts were first moved to `/usr/share/univention-udpater/` and replaced by a wrapper printing a warning for years until they were also finally removed in 2018 for UCS-4.3 by Bug #36719 > It is, from point of view, extremely dangerous that the major release value > is not considered by that command option. Because you're not doing a *release* update, but only installing *errata* with are for your *current* release only. The "real" bug is often this: if you forget to specify that `--updateto 4.4-9` *once* in an non-interactive update with `--ignoressh --ignoreterm --noninteractive </dev/null` your system will update to the latest version and then will be past that boundary forever. There is no way to roll that back other then restoring your system from a backup. In Bug #37869 I proposed to add a UCRV for this to make this option "sticky" and to get it applied every time until you overwrite it on CLI again. > If that has changed it must be documented. Nothing changed.