Hello.
This is a follow-on to my earlier post about hyperkitty_import Unicode Errors. I am progressing through a migration from Mailman 3.2.1 to Mailman 3.3.3 based on Debian packages. Since I have 3.2.1 instances running in production, I've created new databases for the 3.3.3 instances. I copied the Mailman3 DB to the new database and allowed the install process to upgrade the DB Schema. For the Mailman3-Web DB, due to the codepage issues, I did not initially copy the content. My thought was that I would try to re-import my v2.1 archives into a new database that has the correct Unicode settings.
However, this places me at square one with respect to users, permissions, etc.
What I would really like to do is to drop all of the previous archives and start fresh. Looking at the table list for the database, It would appear that all of the archive content is stored in the tables with names that start with 'hyperkitty_' I'm wondering if I could just wipe the content of these tables, or exclude them from a backup, and then start fresh.
Alternatively, if I restore the exiting archives to the new database with the correct unicode settings, could I re-run the hyperkitty-import tool and get it to pick up all of the messages it skipped due to the unicode problem?
Please advise.
Thanks.
-Dave
-- Dave Hall Binghamton University kdhall@binghamton.edu
On Sat, May 6, 2023 at 2:27 PM Dave Hall <kdhall@binghamton.edu> wrote:
Hello.
When running hyperkitty_import to import Mailman 2.1 archives, I frequently get errors like
django.db.utils.OperationalError: (1366, "Incorrect string value: '\\xE1\\x90\\xA7\\x0A\\x0AO...' for column
mailman3web.hyperkitty_email.contentat row 1")Is there a known cause for this? Is it fixed in some release more recent than 0+20180916?
Thanks.
-Dave
-- Dave Hall Binghamton University kdhall@binghamton.edu