Franklin Weng writes:
I had a blog article describing how I did it.
Thank you for mentioning this.
As far as I know, Debian packages use the system Python and the system Django. Is that correct?
I have had trouble myself with [language.en] charset: ascii myself when importing Mailman 2 lists into Mailman 3. This was an *ancient* instance (Mailman 2 installed in 2009, 21.1.15). Save yourself pain and set it to utf-8. I need to make sure before I make such a change in a public release though.
As far as I know [language.master] charset isn't relevant anymore as all out message catalogs are UTF-8 now.
I need to think about the 'django_mailman3.lib.auth.fedora' issue. I'm not sure why that should be enabled out of the box in Mailman's distribution. HyperKitty was originally a Red Hat/Fedora contribution, I guess that's why it's there and nobody has removed it. But I need to make sure before I make such a change in a public release here, too.
The utf8mb4 problem is Somebody Else's problem. We don't know what the implications of setting utf8mb4 are, that's for the MySQL folks or the Debian packager. (The fact that MySQL-family databases can't handle 4-byte UTF-8 out of the box in 2023 doesn't make me feel warm and fuzzy about MySQL, though.) Postgresql and sqlite do not have this problem.
In our current releases, the "mailman" command and the "mailman-web" command are separate. mailman-web/manage.py and django-admin are basically aliases for mailman-web. I think "mailman-web", not "mailman" is what you mean in your last note. Note that "manage.py" doesn't know anything about functions of the "mailman" command, since it is derived from Django. So you might want to check that and correct it.
Steve