Dear Users,
trying to update mailman3 to lastest version, we fail during
mailman-web migrate with:
Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: Applying account.0006_emailaddress_lower...Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", line 89, in _execute return self.cursor.execute(sql, params) File "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", line 328, in execute return super().execute(query, params) sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email
We found a workaround to fake the migration with
migrate --fake Operations to perform:
Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount
Running migrations:
Applying account.0006_emailaddress_lower... FAKED
Applying account.0007_emailaddress_idx_email... FAKED
Applying account.0008_emailaddress_unique_primary_email_fixup... FAKED
Applying account.0009_emailaddress_unique_primary_email... FAKED
Applying django_q.0015_alter_schedule_schedule_type... FAKED
Applying django_q.0016_schedule_intended_date_kwarg... FAKED
Applying django_q.0017_task_cluster_alter... FAKED
Applying django_q.0018_task_success_index... FAKED
Applying postorius.0019_alter_emailtemplate_data... FAKED
And mailman 3 is still processing mails. I'm unsure if i should recover from snapshot or keep it going?
Could this be some duplicate users with same mail-address?
I have at least spotted one user and delete him.
thank you.
Stefan