Univention Bugzilla – Bug 54308
Possibly mixed package versions from "ucs" and "errata" repositories pre join
Last modified: 2022-01-07 09:04:39 CET
Possibly mixed package versions from "ucs" and "errata" repositories pre join Our policy is not to upgrade a system until it has been joined. The idea being that the joining system will be in a predictable state (all packages are from the "ucs" repository). If we or a customer tries to install software before the system has been joined and followed our policy of not upgrading (for example the ucs@school installation on replica servers), they might run into dependency problems (bug 54180) and the system will have some packages upgraded but not necessarily all. I think we should improve this situation, I see three options: 1) Disable all package installations until joined This would break ucs@school and is imho not a good customer experience. 2) Upgrade the system pre join Our "do not upgrade" pre join policy seems to have been working in the past, so I'm reluctant to change it. 3) Do not enable the errata repository before the system has been joined This is my preferred solution. Installing software is still possible without completely destroying the predictable state of the joining system
We have always supported installing updates BEFORE joining by not doing the JOIN during system-setup but explicitly afterwards by manually running `univention-join`: you can disable JOIN but do updates after installation from USS. So this is supported by UCS. Also remember that the next patch level release will be based on the previous release + all released errata: So that mix of packages will must always be a valid candidate for the next release! Thus I would close this bug as WONTFIX or even INVALID.