On 9/30/23 15:23, Wikinaut wrote:
After having changed and re-changed "only" the line in /etc/mailman3/mailman-web.py (which looks to be only a "blinder" and the real problem could be a different one)
POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/'
This should not include the mailman3/ path. If http://localhost/mailman3/ gets to Postorius, it should just be 'http://localhost/'.
the web access via Postorius is not working any more and throws "Error 500"
My logfile /var/log/mailman3/web/mailman-web.log shows now
...> from django.utils.encoding import force_bytes, force_str, force_text
ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py)
I already run pip install -U postorius to update that (looks okay to me):
Requirement already satisfied: postorius in /usr/local/lib/python3.9/dist-packages (1.3.8) ... Requirement already satisfied: django<4.2,>=3.2 in /usr/local/lib/python3.9/dist-packages (from postorius) (4.1.9) ... dpkg -l | grep django ii python3-django 2:2.2.28-1~deb11u2 all High-level Python web development framework
Something is confused here. Your Django version from dpkg is 2.2.28, bit
from your above pip install, it is 4.1.9. I'm not sure haw the Debian
package installs, but probably in a venv.
ii python3-django-q 1.2.1-1 all Django multiprocessing distributed task queue (Python 3 version)
I don't know what the django-q version in the venv is, but Django >=4.0 requires django-q >=1.3.0
If The Debian backage includes Django>=4.0 and django-q<1.3.0, it's a Debian packaging issue.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan