Univention Bugzilla – Bug 42808
univention-system-setup-boot still installed after installation
Last modified: 2017-01-17 15:09:12 CET
Happend in technical training on 8 machines and possibly on a customer system: http://forum.univention.de/viewtopic.php?f=56&t=6180 All machines in technical training have been installed via ISO on a USB stick. The debian installer and the webbased system setup part have been successfully gone through. But: network was not available during system setup part AND automatic update in the end of installation has been deselected. The systems seemed to be fine after installation and rebootet fine to commandline. Later on, the network connectivity was restored and univention-upgrade has been performed on command line. After reboot, univention system setup was shown ==> UCRV system/setup/boot/start was "true" I was able to reproduce this problem on a system installed without network access (ethernet interface was present, but no switch attached). I would bet that the script univention-system-setup/usr/lib/univention-system-setup/cleanup-post.d/90_remove_univention_system_setup_boot is the culprit. The following aptitude command seems to have failed or performed only half-way: aptitude -q -y markauto univention-system-setup-boot- \ univention-management-console-web-server \ univention-management-console-module-setup </dev/null When reproducing the problem, aptitude showed the status "id" (installed, marked for deletion) right before calling univention-upgrade → univention-system-setup-boot is still installed. # dpkg --get-selections univention-system-setup-boot univention-system-setup-boot install #
Why is aptitude used? As far as I can see we have no dependency on it. Anyway, univention-remove is the tool we should use.
(In reply to Stefan Gohmann from comment #1) > Why is aptitude used? As far as I can see we have no dependency on it. AFAIS, this was introduced as part of Bug 36873 [r56190].
The issue is that we cannot remove a package if our sources.list file is not correctly written. Even univention-remove would not work in that case. We ship /etc/apt/apt.conf.d/99updatecheck.conf, which aborts APT and DPKG operations if there is a "An error occurred during the repository check." line in /etc/apt/sources.list.d/15_ucs-online-version.list Manually calling 'dpkg -r univention-system-setup-boot' worked in my first test
This was introduced by UCS 4.1 errata 277, bug 42450, r72760
(In reply to Erik Damrose from comment #4) > This was introduced by UCS 4.1 errata 277, bug 42450, r72760 Ah, yes that makes sense.
r73980 Use apt-mark and dpkg instead of aptitude to configure correct package status in 90_remove_univention_system_setup_boot r74022 changelog univention-system-setup 9.0.5-3.996.201611011750
OK: r73980 OK: r74022 OK: univention-system-setup 9.0.5-3.997.201611031621 OK: installer OK: appliance mode IGNORED: univention-welcome-screen failed to install because of an error in /etc/apt/sources.list in one test
UCS 4.1-4 has been released: https://docs.software-univention.de/release-notes-4.1-4-en.html https://docs.software-univention.de/release-notes-4.1-4-de.html If this error occurs again, please use "Clone This Bug".