On 1/9/22 09:53, Matěj Cepl wrote:
Dne 08. 01. 22 v 13:03 Ben Greiner napsal(a): The crucial part is the
<path project="devel:languages:python:backports" repository="15.3"/>
which is still missing in devel:languages:python.
Why should we put backports into regular devel project? I thought that point of 15.3 repository in d:l:p is to show what is buildable on the regular real Leap 15.3.
The real main purpose was Leap users used to add d:l:p to there systems which would cause them to break in strange ways because it would always pull in packages that wouldn't work on there system.
So Leap builds were disabled in d:l:p and backports was created just to have modules built against the actual python in leap so users could get the newer versions of the modules that would work with the distro python which generally breaks less things.
In neither the use case you or I described is there a need for d:l:p to include d:l:p:backports so I also don't understand the use case, so what exactly is broken and how does this change fix it. On the other hand not having the Update target in 15.3 can cause issues. I'd use the following for example.
<repository name="openSUSE_Backports_SLE-15-SP3"> <path project="openSUSE:Backports:SLE-15-SP3:Update" repository="standard"/> <path project="openSUSE:Backports:SLE-15-SP3" repository="standard"/> <arch>x86_64</arch> </repository>