[Pkg-mailman-hackers] Bug#1148663: mailman3-web: Mailman3 not working following distribution upgrade from Debian 12 to 13
Alain Williams
addw at phcomp.co.uk
Mon Sep 21 19:08:34 BST 2026
Package: mailman3-web
Version: 0+20240312-1+deb13u1
Severity: grave
Justification: renders package unusable
mailman3 works after I patched /usr/lib/python3/dist-packages/robot_detection.py
It had escape sequences in strings that python did not like: \- \s \/ \. \; \/ \\
The bug that I am reporting is that the web interface does not work. When I go to
the web page it just says 'server error' 'An error occurred while processing your request.'
I see in: /var/log/mailman3/web/mailman-web.log
django.db.utils.OperationalError: (1054, "Unknown column 'socialaccount_socialapp.provider_id' in 'SELECT'")
So: were some new database table columns needed to be created when the
upgrade happened ?
-- System Information:
Debian Release: 13.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.107+deb13-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages mailman3-web depends on:
ii dbconfig-mysql 2.0.25
ii dbconfig-sqlite3 2.0.25
ii debconf [debconf-2.0] 1.5.91
ii init-system-helpers 1.69~deb13u1
ii python3 3.13.5-1
ii python3-django-hyperkitty 1.3.12-3
ii python3-django-postorius 1.3.13-1+deb13u1
ii python3-mysqldb 1.4.6-2+b5
ii python3-psycopg2 2.9.10-1+b1
ii python3-whoosh 2.7.4+git6-g9134ad92-10
ii ucf 3.0052
ii uwsgi-core 2.0.28-9
ii uwsgi-plugin-python3 2.0.28+8+0.0.2+b1
Versions of packages mailman3-web recommends:
pn libapache2-mod-proxy-uwsgi | nginx <none>
Versions of packages mailman3-web suggests:
ii mariadb-server [virtual-mysql-server] 1:11.8.6-0+deb13u1
-- debconf information:
mailman3-web/superuser-name: admin
mailman3-web/install-error: abort
mailman3-web/db/dbname: mailman3web
mailman3-web/db/basepath: /var/lib/mailman3/web
mailman3-web/pgsql/authmethod-admin: ident
mailman3-web/nginx-choice:
mailman3-web/purge: false
mailman3-web/dbconfig-upgrade: true
mailman3-web/passwords-do-not-match:
mailman3-web/pgsql/admin-user: postgres
mailman3-web/dbconfig-reinstall: false
mailman3-web/missing-db-package-error: abort
mailman3-web/upgrade-error: abort
mailman3-web/remote/host: localhost
mailman3-web/pgsql/authmethod-user: password
* mailman3-web/dbconfig-install: true
* mailman3-web/database-type: mysql
mailman3-web/mysql/authplugin: default
* mailman3-web/mysql/admin-user: root
mailman3-web/dbconfig-remove: true
mailman3-web/pgsql/method: TCP/IP
mailman3-web/internal/skip-preseed: false
mailman3-web/remote/port:
mailman3-web/db/app-user: mailman3web at localhost
mailman3-web/remote/newhost:
mailman3-web/pgsql/no-empty-passwords:
mailman3-web/pgsql/manualconf:
mailman3-web/pgsql/changeconf: false
mailman3-web/superuser-mail: root at localhost
mailman3-web/internal/reconfiguring: false
mailman3-web/mysql/method: Unix socket
mailman3-web/restart-webserver: true
mailman3-web/emailname: bf2024.phcomp.co.uk
mailman3-web/remove-error: abort
mailman3-web/configure-webserver: none
mailman3-web/upgrade-backup: true
More information about the Pkg-mailman-hackers
mailing list