This request is superseded by
request 1152941
(Show diff)
Overview
Request 1150178 superseded
- Build for Python 3.12
- Bump django-requests-debug-toolbar
- Created by crameleon
- In state superseded
- Supersedes 1150055
- Superseded by 1152941
Loading...
author
I also tried bumping the dependency %{python_module django-requests-debug-toolbar >= 0.0.6} however my build for django-requests-debug-toolbar does not provide python311-*, making python_module not resolve. Unsure if that's specific to my branch or an issue with the python-django-requests-debug-toolbar package, but I left the bump out here.
Login required, please
login
in order to comment
I noticed the new django-requests-debug-toolbar version did not resolve in my project, because it did not build for 3.12 unless I remove
%{?sle15_python_module_pythons}from it: https://build.opensuse.org/package/rdiff/openSUSE:infrastructure:mailman3/python-django-requests-debug-toolbar?linkrev=base&rev=2. With that, Postorius builds fine against it: https://build.opensuse.org/package/show/openSUSE:infrastructure:mailman3/python-postorius. I guess it will magically work in devel:languages:python:mailman?on Factory yes, but it should be kept in sync also with the mailman version login (line 50 in https://build.opensuse.org/package/view_file/devel:languages:python:mailman/python-mailman/python-mailman.spec?expand=1)
but thank you for the fix :)
Sorry, could you elaborate on the mailman version login ? :-) Line 50 there seems to just reference Tumbleweed.
%if 0%{?suse_version} >= 1600 # Newest python supported by mailman is Python 3.12, but we have just Python 3.11 in SLE # See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/docs/NEWS.rst %define pythons python312 %define mypython python312 %define mypython_sitelib %{python312_sitelib} %else %if 0%{?suse_version} >= 1550 || 0%{?sle_version} >= 150500 %define pythons python311 %define mypython python311 %define mypython_sitelib %{python311_sitelib} %else %{?!python_module:%define python_module() python3-%{**}} %define pythons python3 %define mypython python3 %define mypython_sitelib %{python3_sitelib} %endif %endifIn words, we use python312 on Tumbleweed, python311 on newer SLE-based systems and python3 on old systems.
the old systems probably don't matter, but there is python311 stack (not python312, since it didn't exist at the time of designing) in the new SLE
I understand, so I should keep python311 if not Tumbleweed?
Yes, there are people (like me) who use this in production on SLE15 or Leap 15.5. You're breaking those installations.
Here is a repo building for 15.5: https://build.opensuse.org/project/show/home:gladiac:mailman
And I just noticed that someone broke Hyperkitty.
Now you know my frustration when someone breaks the Mailman stack for Tumbleweed in Factory. ;-) I superseded the requests to only switch to python312 in the Tumbleweed clause. Please check.