Am Donnerstag, 8. Juni 2023, 10:08:20 CEST schrieb Daniel Garcia:
In addition, only 311 Python is built with Suse projectconfig. This means that no upgrade from 15.4 to 15.5 would work.
What do I have to enter in my projectconfig so that 15.4 is built and that 3.6 and 3.11 are built for 15.5?
Can anyone help me?
The only change is the new macro to build for modern python. The idea is to try to make it easier to build packages from tumbleweed in 15.4 and newer, but that will be with python3.11.
To build for python3.6, you can override the macro in your custom project or modify the .spec file to remove the macro call.
What we're doing in SLES15-SP4 is to "rename" python 3.6 packages from python-foo to python3-foo, and those packages doesn't have the %sle15_python_module_pythons, so the new packages are similar to what we've in the openSUSE:Factory project.
Hello, first of all thank you for the quick answer. What you describe, customize ProjectConfig or psec, I have now already done for 15.4. But I had to do that after the new macro %sle15_python_module_pythons() was introduced. But what you describe does not work for packages I need for 15.4 and 15.5. Hence my question. What do I have to do to build the same Python package in the following way: For Leap 15.4 only as python3, so with python3.6. For Leap 15.5 as python3 and as pyton311 package. Because only then I can upgrade from Leap 15.4 to 15.5. Or is there any other way I can do this? Have now adjusted my ProjectConfig like this: %if "%_repository" == "15.3" || "%_repository" == "15.4" || "%_repository" == "openSUSE_Leap_15.3" macros: %sle15_python_module_pythons() %global pythons python3 macros %endif so without 15.5. But it doesn't work 100%. Because in 15.5 python311 is built, but not python3. But I need both versions for a clean upgrade. Maybe someone here has a tip? I can't be alone with this problem? I have about 100s of python packages. And I never had such an upgrade problem until now. And I have been doing my update for about decades in the following or similar way: sudo zypper --releasever=15.5 dup -d sudo zypper --releasever=15.5 dup I have never had a problem with this. And certainly not such a serious one. Does anyone else have this problem? And maybe has a solution? Greetings Eric