Odhiambo Washington wrote:
- SQLAlchemy - At the stage where one runs 'mailman info', I encountered the first error: : sqlalchemy.exc.NoSuchModuleError: Can't load plugin: sqlalchemy.dialects:postgres
This is solved by a change in mailman.cfg so that the URI starts with postgresql:// instead of postgres://. SQLAlchemy used to accept both but has removed support for the postgres name. <https://github.com/sqlalchemy/sqlalchemy/issues/6083#issuecomment-801478013>
This is covered here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.h... "BREAKING CHANGE: When using PostgreSQL database with Mailman, starting with Mailman Core 3.3.7 (due to bump in SQLAlchemy 1.4+), the urls in [database] section will require postgresql as the scheme."
- Django==4.x At the point of running the post-update processes, particularly the "migrate" bit, I got the following error: : ImportError: cannot import name 'url' from 'django.conf.urls' (/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/urls/__init__.py)
This was recently covered here: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/N...
When I came to upgrade my actual installation I migrated to the Mailman-Web package so this file is now maintained by the Mailman developers.
- The last issue that I encountered is one I kind of solved, but completely don't understand the consequences of the solution I applied: /opt/mailman/mm/bin/django-admin migrate
System check identified some issues:
I got these as well. I have safely ignored these but didn't suppress the warnings like you have done. My Googling and continued usage since upgrading to Django 4.x indicates these are safe to ignore but need to be dealt with by the developers at some point.
Thanks. Andrew.