Am 08.03.2022 um 21:08 schrieb Mark Sapiro:
Possibly one way to fix this is to run
django-abmin migrate socialaccountwhere django-admin is the name of your django management command.
Then running
django-abmin migrateshould succeed. The issue appears to be due to the face thatdjango-admin migrateruns the migrations in alphabetical order by app. This is fine if migrations were run during the period after socialaccount.0003_extra_data_default_dict was created and before hyperkitty.0007_allauth_20160808_1604 was created, but it's an issue in an installation that wants to migrate hyperkitty.0007_allauth_20160808_1604 without having previously migrated socialaccount.0003_extra_data_default_dict.
Thx for your always competent answers. In this case I just needed to uncomment the not needed socialaccount lines in mailman3.cfg. As we do not use them.
And now I hope for a debian package upgradem or I need to replace them with virtuelenv install as soon as I need to upgrade.
MfG, Lars Schimmer
TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer@cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723