Am Dienstag, 25. April 2023, 09:20:33 CEST schrieb Daniel Garcia:
On mar, 2023-04-25 at 08:32 +0200, Eric Schirra wrote:
I see more and more %{?sle15_python_module_pythons} and %{sle15modernpython} in packages changes.
But i can't find any documentation about it. Not in wiki and not in python-rpm-macro.
So what's the deal with "%{?sle15_python_module_pythons}" ? And what's the deal with "%{sle15modernpython}" ?
This is related to SLE, we are trying to make the changes in factory to do not have different sources for the modern python packages provided there.
Hello Daniel, you wrote:
This macro won't do anything in Tumbleweed or other versions where it's not defined and in SLE it's just to set the "pythons" macro to a different value, so the multibuild can produce python3.11 packages there.
and Robert wrote: "The definition will come from the project config, not from the python-rpm-macros package. " I have not defined %{?sle15_python_module_pythons} anywhere in the project_configs. But since a few days every package which has %{?sle15_python_module_pythons} in its spec can't be built anymore. It always comes with Leap 15.4 similar "unresolvable: nothing provides python311-setuptools". Packages without %{?sle15_python_module_pythons} are built. It is also reproducible. If I remove %{?sle15_python_module_pythons} from the packages, they are built again. My questions now: What changed after your announcement? Why does it suddenly want to build 3.11 package although not defined anywhere? Why is %{?sle15_python_module_pythons} observed now? Where is the problem or error? Can someone help me? Regards Eric