On 12/18/23 6:24 AM, Helio Loureiro wrote:
Hi,
Indeed it was the configuration. It was placed into /etc/mailman3/mailman-web.py. After a I changed to /etc/mailman3/settings.py a few things advanced a little bit more.
I had to figure out how to fix mysqlclient installation since there isn't a mention about it and the simple "pip install mysqclient" was breaking with pkg-config issues. But it did work at the end.
Now I can see further messages on mailman3-web than before.
(venv) mailman@new-server ~ (v3.3.9)> mailman-web migrate System check identified some issues:
WARNINGS: account.EmailAddress: (models.W036) MariaDB does not support unique constraints with conditions. HINT: A constraint won't be created. Silence this warning if you don't care about it. account.EmailAddress: (models.W043) MariaDB does not support indexes on expressions. HINT: An index won't be created. Silence this warning if you don't care about it. Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0004_alter_emailaddress_drop_unique_email...Traceback (most recent call last):
I'm not sure why there would be an issue with this migration, but there is a possible compatibility issue depending on how you installed things.
django-mailman3<=1.3.11 is not compatible with django-allauth>=0.58.
In your venv, try
pip install django-allauth\<0.58
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan