Dne 30. 03. 20 v 12:19 Steffen Winterfeldt napsal(a):
What's missing is that the self update repo says which product it is intended for.
Exactly. The problem is that repositories themselves do not contain any additional metadata describing them, the metadata can only describe the included packages. Otherwise the solution would be easy...
I think the self update should contain the information. We could require some hint in the repository meta data or a special package (like these xxx-release packages or simply a package named/providing selfupdate-for-foo-bar) that contains the info.
Using some *-release package for this purpose sounds like a good idea as well. We could compare the product ID in the /etc/os-release file in the inst-sys with the file from *-release package in the repository, they should be the same. If not we could easily display the user-friendly product data: PRETTY_NAME="SUSE Linux Enterprise 15 SP2" Unfortunately for the SLES installer it's a bit more complicated because the inst-sys contains the /etc/os-release file from the "unified-installer-release" package with the ID above. But that package is not released and the released "sles-release" package contains a different ID ("SLE" vs. "SLES"). So the question is whether the maintenance team could actually release a completely "new" package as a self-update... Alternatively the self-update repo could contain the published "sles-release" package and we would compare only the "VERSION_ID" value in the os-release file, the check would be less strict. This value is the same for all SLE products ("15.2") and is the same also in the "unified-installer-release" package -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org