Description Max Pohle 2021-05-10 17:13:47 CEST

The new script `univention-list-installed-unmaintained-packages` in its current state does not completely do what its name suggests as it also lists some maintained packages for various reasons.


# Reason 1

It seems as if a decision about how the applications are to be handled was postponed at some point in time, which causes some inconsistency in the transition time of transition: https://taiga.knut.univention.de/project/oschwieg-ucs-5/us/5430

To overcome this the script currently searches the "install candidates", having similar output to `apt policy <package>` and then filters out packages containing `/maintained/component/` in the url path.

While this currently works, it contradicts the reasons for having started with the topic, because the unification was began to eliminate some unnecessary incompatibilities between UCS and the Debian project and eliminate unnecessary complexity by doing so. This exception keeps some of the complexity we wanted to get rid of and we should take care, that this conversion from knowledge to code does not drive further decisions.


# Reason 2

The file `/usr/share/univention-errata-level/maintained-packages.txt`, which is created by repo-ng and deployed using the `univention-errata-level` packet is currently not up to date - I was told. I am however not able to verify this information, because I am missing a single-source-of-truth (except for the file itself). However I see no reason for not having maintained applications in the list as well. This solution has been suggested multiple times by different people and would simplify the code of the `univention-list-installed-unmaintained-packages` script.