Univention Bugzilla – Bug 52833
univention-updater: univention-list-installed-unmaintained-packages does not consider maintained packages from other sources
Last modified: 2023-06-19 14:56:46 CEST
To determine whether unmaintained packages are installed on a system, the tool "univention-list-unmaintained-installed-packages" currently only uses univention-maintained-packages.txt that can be found in the univention-errata-level module and checks that against all installed packages. It does not consider some special cases where maintained packages from other sources that are not on that list are falsly treated as if they were unmaintained.
Would it be possible to consider only packages that have an installation candidate on one of our repository server? ==> exclude packages from appcenter.software-univention.de from the check
(In reply to Sönke Schwardt-Krummrich from comment #2) > Would it be possible to consider only packages that have an installation > candidate on one of our repository server? > ==> exclude packages from appcenter.software-univention.de from the check yes, another idea would be to check the package was installed from a "maintained" repository, e.g. apt-cache policy univention-node-exporter univention-node-exporter: Installiert: 0.0.0-13 Installationskandidat: 0.0.0-13 Versionstabelle: *** 0.0.0-13 500 500 https://appcenter.software-univention.de/univention-repository/4.4/maintained/component prometheus-node-exporter_20181119120420/all/ Packages 500 https://appcenter.software-univention.de/univention-repository/4.3/maintained/component prometheus-node-exporter_20181119120420/all/ Packages 100 /var/lib/dpkg/status This package is from a maintained component and the script could check this to determine the maintained/unmaintained status
e9867b1c40a1214834c89d4d910cd8d31972953a - univention-updater treat packages from */maintained/component* as maintained
The script produces predictable results, even if they are not completely consistent with my initial expectations towards it. During my investigation I have gone through parts of the development history of the script, which I believe are necessary to know about, when doing further development on it and this will be required, because there are some decisions still pending in regards to the implementation of our app center. This however is off-topic here and I have created another ticket to deal with it. I tried to summarize the state as good as possible in Bug #53241.
UCS 5.0 has been released: https://docs.software-univention.de/release-notes-5.0-0-en.html https://docs.software-univention.de/release-notes-5.0-0-de.html If this error occurs again, please use "Clone This Bug".