On 01.09.2021 17:43, Manfred Schwarb wrote: ...
On the level of build.opensuse.org, there are no such complications, packages are merged to one access point. As it should be.
Actually no, it is not what happens. On build.opensuse.org level binary packages built as part of another project are imported into openSUSE:Leap:15.3. But nothing in metadata of these packages identifies them as belonging to Leap 15.3. Thinking more about it, single binary may be imported into any number of unrelated projects, so this is probably correct.
So OBS search for binary packages (which is what s.o.o search is using) has no way to identify binary package as belonging to or even being related to Leap 15.3.
Hmm. That is the issue, it seems: #> rpm -q --qf "%{DISTRIBUTION}\n" glibc SUSE Linux Enterprise 15
# rpm -q --qf "%{DISTRIBUTION}\n" SuSEfirewall2 SUSE Linux Enterprise 15 SP3
And how exactly can you associate them with openSUSE Leap 15.3 based on this information? Not every SLE package is part of openSUSE to my best knowledge.
I think the former is wrong, this should be have a "SP3" in it, I guess.
How is it relevant to search on s.o.o or opi? Neither queries binary package directly.
All packages will surely be compiled anew for every service pack?
Not that I am aware of.