
On Sat, Jun 12, 2021 at 05:14:28PM +0300, Andrei Borzenkov wrote:
Since SLE 11 (or may be even SLE 10) each service pack needs just two repositories - Pool and Updates (there were some deviations and of course this should be adjusted for each module but in general this holds true).
I thought may be I forgot something so I installed SLES 15 SP2 (with subscription) yesterday and sure thing - the only repositories are those for SP2, there is no SP1 or SP0 anywhere. I do not have beta subscription for SLE 15 SP3 so cannot test but I would be surprised if it had been different.
Why Leap 15.3 now suddenly has all previous service packs in its sle update repository? This is what seems to cause all those problems with patches for wrong SP.
SLES 15 SP3 is built out of layered "codestream". We do not rebuild all packages for all service packs, on new service packs only the changed packages are in the "service pack level" codestream, others are taken from lower ones. e.g. "vim" is only built in the SLES 15 GA codestream and used in GA, SP1, SP2 and SP3. So for the sle/ tree vim updates will appear in sle-sp0/ only. This various from package to package. Some are also in all service packs, like the kernel is in every codestream level. This works as we guarantee compatibility from lower service packs to higher ones. This is different to how Leap was done before, there we rebuilt everything on the same codestream level. The problems in update stack are unrelated to that, there are 2 core problems: - the build of the sle repo assumed that all service packs have same or higher released package version-releases (so linear increasing only). We had some cases where this was not the case (same version, lower releasenr) and these showed up as errors. (gzip, numactl, build, webkit2gtk3, libreoffice, tomcat, google-poppins-fonts, etc.) - We so far strictly assumed that Backports and SLE packages do not overlap. Still we have several cases where this happens (libmodulemd, librepo, gnu-hpc-compilers, obs-service-tar_scm, eclipse) where it was violated and now leads to problems. I am resolving those as I find them / they get reported. Ciao, Marcus