[Pkg-mailman-hackers] Bug#1041496: RE: mailman3-web: Upgrade from Debian 11 to 12 dpkg can't configure mailman3-full and -web

[Takatsugu Nokubi]

I don't know why your mailman3-web was broken, anyway I can fix the problem
with the following steps:

* add config to /etc/mailman3/mailman-web.py

```
DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'
Q_CLUSTER = {
    'timeout': 300,
    'retry': 600,
    'save_limit': 100,
    'orm': 'default',
    'poll': 5,
}
```

* make django migration

```
sudo -u www-data /usr/share/mailman3-web/manage.py makemigrations
sudo -u www-data /usr/share/mailman3-web/manage.py migrate
```

to enable DEFAULT_AUTO_FIELD config

* restart service

```
sudo service mailman3 restart
sudo service mailman3-web restart
```

to enable Q_CLUSTER  config


On Mon, 07 Aug 2023 11:30:23 +0200 "Richard Rosner" <
rrosner at fsmuw.rwth-aachen.de> wrote:
>
> It would be very much appreciated if a solution could be found, or at
least help provided to figure out the problem. Right now, both
mailman3-full and mailman3-web can't be configured, so every time apt runs,
it also tries to fix them. While mailman3 itself is working, mailman3-web
is completely dead.
>
> PS: I also tried
adding DEFAULT_AUTO_FIELD='django.db.models.AutoField' to the settings.py,
but I don't see any changes. Output is this (for dpkg --configure -a):
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/attachments/20230813/e3c0f4ec/attachment.htm>