Am Montag, 8. Mai 2023, 15:17:22 CEST schrieb Georg Pfuetzenreuter:
On 5/8/23 15:07, Eric Schirra wrote:
Am Montag, 8. Mai 2023, 11:47:07 CEST schrieb Dirk Mueller:
Eric Schirra wrote:
The second is that there are no python311 packages under Leap. So the whole thing cannot work at all.
They're in progress of being added to Leap, however that comes via maintenance and will take time.
And all packages in Leap are called python- and not python3-.
And that's okay. you can keep it that way *unless* you want to update to 3.11. The rename to python3 is only needed if you have two different source versions (one for 3.6 and one for 3.11). if you can build for both or only build for python3 no work is needed.
then build for 3.6.
I would like to keep it that way.
But exactly that this no longer works, I try to show here.
That's because for a few days no longer works. Since a few days the new macro has been inserted in the non-public part, which is not visible for me via the GUI. And this although it was said, exactly this would not happen.
Thus, the packages in my HomeRepo, just built with python311. As far as it would go. "Normal" python 3.6 packages are no longer built at all.
Since I can not change the "non-public part", I do not know how to describe it, I helped myself with a crutch.
I now add in my part of the ProjectConfig that I can change the following:
macros: %sle15_python_module_pythons() %global pythons python3
:macros
Because only then the packages which have the above macro in their specfile will be built at all. And they will be built suitable for Leap 15.4.
Also I tried to show that a pure: <path project="openSUSE:Leap:15.4" repository="standard"/>
in the meta data can't be the solution either. Once because there are important innovations in the updates and secondly because I can not really check whether the packages fit together via huapt.
So I have to have the following in my meta forcibly: <path project="openSUSE:Leap:15.4:Update" repository="standard"/>
I hope I could clarify my problem/concern now. And I hope there is now a solution for it. I can't imagine that I'm the only one with this problem.
You are not. Devel packages for Leap 15.4 are not building since a while now, requiring me to branch them and redefine %pythons myself to get the 3.6 version to build again. I'm all for the new Python stack but I wonder if there's a better way to build it than having the working 3.6 packages break during the process.
That is exactly what I mean and what I am pointing out. That the packages in devel:languages:python can no longer be built is clear to me. But I could always take the last version compatible with python 3.6 if it was already too old in Leap itself. And exactly that is no longer possible. Unless I add my crutch to the ProjectConfig. And that just since a few days, since just the new macros became active everywhere. :-( Regards Eric