Am 10.01.22 um 12:58 schrieb Dirk Müller:
On Montag, 10. Januar 2022 11:19:48 CET Simon Lees wrote:
In the past we have shipped similar updates to rpm-macros into the Update repo and not released them to customers then with the updates repo enabled they can still be used for builds. That is probably the best solution to this problem or we update the wiki to indicate these features don't exist in 15.3.
untili recently we used to have devel:languages:python:backports:fixups to address python 3.6 issues in devel:languages:python:backports.
I've been maintaining that for at least a year, if not two years, and kept things building in devel:languages:python:backports for 15.3.
coming back from a two day vacation, I notice that all my projects have been deleted links, all the CI jobs have been red, and the project configuration has been completely changed, and now hundreds to thousands of build failures.
Is there any chance that I can get back a working setup please? what issue has been tried to be solved with the changes and how can I get a state that works?
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.
You think can fix them by adjusting your meta configuration to
<repository name="15.3"> <path project="devel:languages:python:backports" repository="15.3"/> <arch>x86_64</arch> </repository> <repository name="15.4"> <path project="devel:languages:python:backports" repository="15.4"/> <arch>x86_64</arch> </repository>
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.