Univention Bugzilla – Bug 44894
univention-upgrade causes umc to be autoremoved on base-systems
Last modified: 2017-08-30 16:29:43 CEST
When updating a 4.2-Base-System, apt flags umc-packages to be autoremoved. Since univention-upgrade forces autoremove, these packages and config-files are removed, leaving a system wit broken services, like apache2. This bug is replroducable on UCS-4.2 Base-Systems.
If I remember correctly, UMC is not installed by default, right? I think it is a problem in our UMC package because it should be possible to remove it.
univention-web (1.0.42-38): r82424 | Bug #44894: allow UMC to be removed on a basesystem univention-apache.yaml: r82425 | YAML Bug #44894 univention-apache (9.0.5-12): r82424 | Bug #44894: allow UMC to be removed on a basesystem r82423 | Bug #44894: allow UMC to be removed on a basesystem univention-management-console (9.0.80-64): r82424 | Bug #44894: allow UMC to be removed on a basesystem r82422 | Bug #44894: allow UMC to be removed on a basesystem univention-web.yaml: r82425 | YAML Bug #44894 univention-management-console.yaml: r82425 | YAML Bug #44894
Removing univention-management-console flags some packages to be autoremoved on which some customers might depend on: docker.io php5 runit (for custom init scripts) sudo pam/heimdal packages <- I don't think these are important on an unjoined system. Some python libs like python-dateutil <- This might break some customer scripts but at least it should not delete any configs. Adding univention-apache, univention-sudo and univention-docker to univention-basesystem might be a solution. But univention-apache depends on univention-directory-listener which I think should not be on a basesystem?
(In reply to Jürn Brodersen from comment #3) I split this into Bug #44894. This fixes the package state. Apache and such can be started again after the upgrade. The other packages can be installed manually if needed.
(In reply to Florian Best from comment #4) > (In reply to Jürn Brodersen from comment #3) > I split this into Bug #44894. This fixes the package state. Apache and such > can be started again after the upgrade. The other packages can be installed > manually if needed. Ok What I tested: Upgraded a base system from ucs 4.2-0 to ucs 4.2-1 -> Apache still works -> OK YAML -> OK
<http://errata.software-univention.de/ucs/4.2/155.html> <http://errata.software-univention.de/ucs/4.2/156.html> <http://errata.software-univention.de/ucs/4.2/157.html>