On 9/26/22 09:14, tflatley@gmail.com wrote:
hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate
Probably not. First of all, mailman-web migrate will only affect the
mailmanweb database, not the mailman database, migrations for which are
run implicitly when Mailman core is started.
Also, migrations will only affect tables for which there are migrations, not all tables.
this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file
python3 manage.py migrate
Yes.
Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.
The above message saying you need to make migrations because of changes to models indicates that your Debian/Ubuntu package is broken as the packager should have created all necessary migrations.
i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db?
I am confused as to why you are trying to run an out of date and possibly broken Debian/Ubuntu package when it appears you have successfully installed the latest PyPI packages in a venv.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan