On Wednesday 2021-09-01 15:58, Andrei Borzenkov wrote:
This means *building* binary packages inside of openSUSE:Leap:15.3 which entirely defeats the new workflow of importing existing binary packages built inside of SLE (Backport).
I tried to open issue for OBS search, but response was "not a bug":
"But all of this is not an OBS code issue. Either report it for software.o.o or to the leap 15.3 release managers."
Personally I still think this *is* OBS issue - it lacks API necessary to search for imported binary packages.
Hold the thought. OBS has a few commands to ask for that. The SLE15 packages are not imported/aggregated, but _inherited_, and furthermore, only inherited _for building_. Leap15.3 has the same relationship to SLE15 like devel:languages:python to openSUSE:Factory. You would never find coreutils under python. Now then, OBS can be queried for build-time package inheritance: osc buildinfo openSUSE:Leap:15.3/pandoc standard x86_64 This contains coreutils, and the location it is sourced from. search.opensuse.org could make use of this. Secondly, one could make Leap use aggregation instead. Though using more disk space, then at least, ("list binary packages available via this project") osc ls -b openSUSE:Leap:15.3 would show coreutils, which search.opensuse.org could capitalize on as well (but I think it does not currently process binaries at all, just obs-level source packages). Still not helpful for the end-user, but at least I hope I could provide a hypothesis on why people think it's not an OBS "problem". search.opensuse.org really needs to special-case openSUSE:Leap:* ... unfortunately - but in the same way as Leap:* needs special-casing in zypper.