Univention Bugzilla – Bug 42485
Deleting "obsolete app files" may actually delete important app file
Last modified: 2016-09-28 14:05:54 CEST
Holds for etherpad: The Non-Docker version ships a join script /usr/lib/univention-install/50etherpad-lite.inst _in its package_. After a univention-app update this file is delete, because the installed app does not ship it as an "external" join script. The script does not exist in /var/cache/.../etherpad.inst -> The App Center thinks the file shall not exist anywhere -> The file is deleted from /usr/lib/... For join scripts already executed, this may be an issue barely noticable. But for scripts not yet executed or for schema files (!), this is a big issue - and not really to fix automatically, once the file has been deleted (apt-get install etherpad --reinstall ?). We should remove this code completely. Or we should only iterate over Docker Apps. Currently, Non-Docker Apps may not ship external join scripts. And even if they can some day, this check is still dangerous.
Only removing files from Docker Apps. I still think that the overall idea of removing obsolete files is correct. It is just wrong for Non-Docker Apps. univention-appcenter 5.0.22-18.224.201609260147
OK - univention-appcenter _update_local_files removes files only for docker apps OK - yaml OK - merged to 4.2-0
<https://errata.software-univention.de/ucs/4.1/279.html>