Hello, Unfortunately, many builds for SLE and Leap in devel projects are currently broken. This is a result from some back and forth changes of enabled repositories in devel:languages:python:backports, which needs to be corrected in a consistent way.* Some history: devel:languages:python:backports had several repositories for the SLE/Leap 15 family enabled: - SLE_15 - SLE_15_SP1 - SLE_15_SP2 - SLE_15_SP3 - openSUSE_Leap_15.2 - openSUSE_Leap_15.3 - (openSUSE_Leap_15.4, not sure if this ever existed) - 15.3 - 15.4 Because of the unification between SLE and Leap from 15.3 onwards, some of these are identical duplicates but create the duplicate workload for the obs servers (all of Factory in this case!). So some time ago, there was a survey and poll how newly enabled projects should name their single SLE15SP3/Leap_15.3 repositories, and the decision was "15.3". I can't find the reference right now. Unfortunately there is no guideline or wiki page about it, only some mailinglist post. There was also a discussion on the packaging ML earlier last month, without a clear guideline. As a consequence, the web interface only lets you create one "15.3" repository, no matter on which distribution checkmark of the SLE/Leap family you click:   <repository name="15.3">     <path project="openSUSE:Leap:15.3" repository="standard"/>     <arch>x86_64</arch>   </repository> Now, devel:languages:python, some of the subprojects there and possible other devel projects outside of this namespace had devel:languages:python:backports in their path like this:   <repository name="15.3">     <path project="devel:languages:python:backports" repository="TARGETREPO"/>     <path project="openSUSE:Leap:15.3" repository="standard"/>     <arch>x86_64</arch>   </repository> Unfortunately, among projects, TARGETREPO was not used consistently as "15.3" but used a variant of the duplicates above. Enter some user** who wanted to get "his" project fixed. His request: "Please delete the duplicates, please use openSUSE_Leap_15.3 as the proper name." His request was granted by the project maintainer. Unfortunately, this broke all the devel projects which used one of the deleted repositories 15.3, including devel:languages:python. The meta configuration now read:   <repository name="15.3">     <path project="deleted" repository="deleted" />     <path project="openSUSE:Leap:15.3" repository="standard"/>     <arch>x86_64</arch>   </repository> Now, just re-adding 15.3 does not fix the "deleted" entries. You have to fix it manually. So my request to fix the path entries and use the repo names found by consensus was understood as to revert the previous users' request and recreate the "15.3" and "15.4" repositories in d:l:p:backports. On the other hand, openSUSE_Leap_15.3 and similar have been removed again (as they would indeed be duplicates). Now of course those projects having had those repositories in their path also have the "deleted" entries, while those from the previous deleted still have it too. In order to fix things and get consistent, I propose that all maintainers of devel projects making use of devel:languages:python:backports, devel:languages:python and any transitive projects check their repository configuration and adjust accordingly. In my eyes, the correct entries would be for all of them:   <repository name="15.3">     <path project="devel:languages:python:backports" repository="15.3"/>     <path project="openSUSE:Leap:15.3" repository="standard"/>     <arch>x86_64</arch>   </repository>   <repository name="15.4">     <path project="devel:languages:python:backports" repository="15.4"/>     <path project="openSUSE:Leap:15.4" repository="standard"/>     <arch>x86_64</arch>   </repository> - Ben [1] https://lists.opensuse.org/archives/list/packaging@lists.opensuse.org/thread... * Although the value of d:l:p:backports is vanishing fast anyway. Most packages in Factory have already dropped or will drop soon support for Python 3.6. ** name intentionally omitted, this is not a blame post but a request to get the technical situation corrected.