Univention Bugzilla – Bug 54233
Remove "unmaintained" from manual
Last modified: 2021-12-10 16:04:47 CET
The UCS 5.0 manual still says: "For additional repositories the installation of unmaintained packages is not possible by default. To enable installation, the Univention Configuration Registry variable repository/online/component/.*/unmaintained must be set to yes." => https://docs.software-univention.de/manual-5.0.html#software::configrepo This should be removed. +++ This bug was initially created as a clone of Bug #51588 +++ For UCS-5 we want to switch to the pool/ structure similar to Debian. repo-ng needs to support that.
This is wrong: *components* still use the UCS-4 layout with separation between [un]maintained.
(In reply to Philipp Hahn from comment #2) > This is wrong: *components* still use the UCS-4 layout with separation > between [un]maintained. The manual still says in the same chapter: The Univention repository contains all packages provided by Univention and Debian. A distinction is made between maintained and unmaintained packages. All packages in the standard package scope are in maintained status. Security updates are provided in a timely manner only for maintained packages. The list of maintained packages can be viewed on a UCS system in univention-errata-level/maintained-packages.txt. unmaintained packages are not covered by security updates or other maintenance. To check if unmaintained packages are installed, the command univention-list-installed-unmaintained-packages can be executed.
(In reply to Michael Grandjean from comment #3) > (In reply to Philipp Hahn from comment #2) > > This is wrong: *components* still use the UCS-4 layout with separation > > between [un]maintained. > > The manual still says in the same chapter: and this is *still* correct: > The Univention repository contains all packages provided by Univention and > Debian. A distinction is made between maintained and unmaintained packages. Yes, we still distinguish between [un]maintained, but we no longer enforce the separation via repositories: All packages are available from *one* repository "ucs500" since 5.0-0. The check for [un]maintained is now done with `univention-list-installed-unmaintained-packages`, which is based on "/usr/share/univention-errata-level/maintained-packages.txt" which is shipped with each "univention-errata-lebel" package. The tool list all packages as "unmaintained" which are installed but not part of that file. > All packages in the standard package scope are in maintained status. Still true; note the work "state", which is correct as we no longer use "repositories". > Security updates are provided in a timely manner only for maintained > packages. Still true: we still provide weekly updates for maintained packages while Debian has many more security updates, which we only import for the next UCS release as we currently do for UCS 5.0-1. > The list of maintained packages can be viewed on a UCS system in > univention-errata-level/maintained-packages.txt. > unmaintained packages are not covered by security updates or other > maintenance. To check if unmaintained packages are installed, the command > univention-list-installed-unmaintained-packages can be executed. see above. BUG -> INVALID