[Pkg-mailman-hackers] Bug#1037358: mailman3-web: Upgrade from Debian 11 to Debian 12 broke mailman/mailman3-web

[Pierre-Elliott Bécue]

Martin Krolikowski <martin.krolikowski at gmail.com> wrote on 23/06/2023 at 10:40:12+0200:

> Hi,
> after the upgrade I ran into the same problem:
> # django.db.utils.OperationalError: no such column:
> hyperkitty_mailinglist.archive_rendering_mode
>
> I solved it by following the post upgrade steps described here:
> https://docs.mailman3.org/en/latest/upgrade-guide.html
> # mailman-web migrate
> solved the hyperkitty error above.
>
> Regards

mailman-web is a proxy binary that calls
/usr/share/mailman3-web/manage.py which is also proxy-called by a
properly configured django-admin command.

In all cases, migrate does the DB migration, and it is supposed to be
done in the postinst in case of an upgrade.

If you needed to do it by hand, it means that the migrate called in
postinst failed, I'd be glad if you could find me the errors you got.

Cheers!
-- 
PEB
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 853 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-mailman-hackers/attachments/20230623/7758d873/attachment.sig>