Hi, Martin Krolikowski <martin.krolikow...@gmail.com> wrote on 25/06/2023 at 13:18:28+0200:
> Hi,
> the only log messages that could possibly be related to this issue are
> in /var/log/apt/term.log:
> Setting up python3-mailman-hyperkitty (1.2.1-1) ...
> /usr/lib/python3/dist-packages/requests/__init__.py:87:
> RequestsDependencyWarning: urllib3 (1.26.12) or chardet (5.1.0)
> doesn't match a supported version!
> warnings.warn("urllib3 ({}) or chardet ({}) doesn't match a supported "
>
> Regards
> Martin
>
> Am Fr., 23. Juni 2023 um 15:17 Uhr schrieb Pierre-Elliott Bécue
> <p...@debian.org>:
>>
>>
>> Martin Krolikowski <martin.krolikow...@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
So this is actually quite stupid.
While some errors required to be fixed in settings etc, I had plenty
troubles understanding why some django updates were not done, and also
why things worked properly in my case.
It seeps to be because they're done as part of the mailman3-web upgrade,
which did not occur because I did not release any new version of
mailman3-web in bookworm. Why it worked in my case is because it
actually seems I did a "reconfigure" of mailman3-web after fixing the
config file.
So actually, I think I can now fix this issue...
--
PEB
signature.asc
Description: PGP signature
