On 3/8/22 11:40, Mark Sapiro wrote:
On 3/8/22 10:10, Lars Schimmer wrote:
Hi!
Today I tried a mailman3 upgrade of the debian packages and I got this error:
django.db.migrations.exceptions.NodeNotFoundError: Migration hyperkitty.0007_allauth_20160808_1604 dependencies reference nonexistent parent node ('socialaccount', '0003_extra_data_default_dict')
Anyone has a idea howto fix those?
This is a reference to a migration in django-allauth. is django-allauth installed. If so, what version?
What does the database query
SELECT app, name FROM django_migrations WHERE app = 'socialaccount';show. It should be
app | name ---------------+------------------------------ socialaccount | 0001_initial socialaccount | 0002_token_max_lengths socialaccount | 0003_extra_data_default_dict (3 rows)
Possibly one way to fix this is to run
django-abmin migrate socialaccount
where django-admin is the name of your django management command.
Then running django-abmin migrate should succeed. The issue appears to
be due to the face that django-admin migrate runs 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.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan