On 1/31/24 08:02, Hans Mayer via Mailman-users wrote:
Dear All,
recently I did a system os upgrade debian 11.8 -> 12.4 / bullseye -> bookworm
This did also upgrade Mailman3 version 3.3.3 -> 3.3.8 as a used the packages which came with Debian OS.
Initially after the upgrade I had some troubles with the MM3 services to start, but I fixed this.
Now almost everything is running. Only the Archives are not working.
Issues with the Debian poackage should be reported to Debian. See <https://wiki.list.org/x/12812344>.
The browser shows a server error, when I look at the mailman-web.log I see
ERROR 2024-01-31 15:14:14,403 2699563 django.request Internal Server Error: /mailman3/hyperkitty/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3/dist-packages/django/db/backends/sqlite3/base.py", line 423, in execute return Database.Cursor.execute(self, query, params)
sqlite3.OperationalError: no such column: hyperkitty_mailinglist.archive_rendering_mode
You need to run the Django admin (however that's spelled in the debian
mailmanweb package) migrate command (and probably others, e.g.,
collectstatic, compress, compilemessages).
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan