Am 10.01.22 um 20:18 schrieb Dirk Müller:
On Montag, 10. Januar 2022 13:18:35 CET Ben Greiner wrote:
See my initial post about an explanation why you see "deleted" entries in your projects. (I include :backports:fixups into the definition of "your"). TL;DR: An overeager user managed to get his wish granted that stuff got deleted. The restoration afterwards did not fix your now broken projects.
The :fixups is needed in devel:languages:python:backports to get it back to building, not in "my" project.
As mentioned by Axel, someone even added :fixups to the path in d:l:p now. I am not sure if that is a good idea for any of the use cases discussed in this thread.
I have over 1000 unresolvables and over 200 failures now.
Also, as discussed in the thread, you probably want paths to the :Update repos either in your projects or in d:l:p:backports directly.
that causes rpmlint-backports to be included which wipes the binaries, not a good idea.
so I'm going over things and revert it into a working state. so the plan was to delete SLE_15_SP3 repository and then to add 15.3, and instead 15.3 got deleted?
I think there was no real "plan", just some misguided user requests which were acted upon. When I called out the actors on it I only got childish reactions and harassment but no sign of thinking along.
- 15.3 got deleted - openSUSE_Leap_15.3 got created - 15.3 got recreated - openSUSE_Leap_15.3 got deleted - SLE_15_SP3 got deleted
Not necessarily in that order. In the end its irrelevant. All we want is a sane state.
Thanks for fixing it up! It's always good to have someone look over it who actually uses the stuff.
BTW, SLE_15_SP2 in d:l:p is still using :backports. Whichever route you want to go, please at least make it consistent or provide a good reason why it should be different.