On 03/30/2017 02:27 PM, David Krantz wrote:
I tried to upgrade today. The result is a broken install which fails when trying to upgrade the database.
$> ./bin/mailman-post-update [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", line 94, in __exit__ six.reraise(dj_exc_type, dj_exc_value, traceback) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", line 236, in _commit return self.connection.commit() django.db.utils.IntegrityError: update or delete on table "auth_user" violates foreign key constraint "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on table "social_auth_usersocialauth" DETAIL: Key (id)=(3) is still referenced from table "social_auth_usersocialauth".
This is <https://gitlab.com/mailman/hyperkitty/issues/106>.
I have tried to drop and recreate the databases but I get the above result anyway.
I'm not sure what you mean by drop and recreate the databases. You
should just drop the social_auth* tables, or if there's nothing in the
database you want, just starting with an empty database should work.
The description in https://wiki.list.org/DOC/Mailman%203%20installation%20experience is very hazy. The process of symlinking in libraries is fiddly to say the least. I get mailman to start but not any web interface. I have not tested mailman so if it works rather than just start I do not know.
Sorry about that. The symlinking was due to my starting with bundler and then "undoing that" without trying to find everywhere the old paths might be referenced.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan