Bug 38009 - Package lists allow to remove essential packages
Package lists allow to remove essential packages
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Package management
UCS 4.0
Other Linux
: P5 normal (vote)
: UCS 4.x
Assigned To: UMC maintainers
:
Depends on: 36711
Blocks: 36508
  Show dependency treegraph
 
Reported: 2015-03-11 13:44 CET by Florian Best
Modified: 2019-01-03 07:18 CET (History)
4 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2015-03-11 13:44:51 CET
Should also be solved on a deepter level (package management should prevent such uninstallations).

+++ This bug was initially created as a clone of Bug #36711 +++

The package list contains "Tools: file". If that is added to the list of packages to be removed, this also force-removes cacklib, python-cracklib, python-univention,  univention-config, and so on. After that the system is unuable.

The package list removal mechanism should not be allowed to remove essential UCS packages.
Comment 1 Alexander Kläser univentionstaff 2015-03-24 09:18:57 CET
We could use dpkg's hook system, cf.:

http://unix.stackexchange.com/questions/76294/hook-a-script-to-apt-get
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:18:34 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.