Hi Odhiambo, thank you for responding.
Let me first say that I am familiar with Python virtualenv, and while it may be the recommended **generic** installation procedure, there is no denying that Linux distros will offer software using their own packaging mechanisms. It would seem that moving this conversation over to the Debian community would be the best move to take then, if I continue to have issues and their packaging is to .
It turns out that I left the "-l" in the hyperkitty_import command. So I re-ran it with the "-l" included. I got the same warnings about primary keys but on first glance it appears to have successfully imported the entire set of archives. Something interesting to note: if I examine the mailman-web script, it attempts to run that same python script as the user www-data. This is just as I was doing (lucky guess!), but using su instead of sudo.
It seems like I've managed to complete the full process of migrating my list documented on that webpage (apart from rmlist'ing the old list).
FWIW, Here's the output:
$ sudo -H -u www-data /usr/share/mailman3-web/manage.py hyperkitty_import -l mylist@mysite.com /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox ... warnings ... Importing from mbox file /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox to mylist@mysite.com Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list mylist@mysite.com'.
And here's the result of rebuilding the index.
$ sudo -H -u www-data /usr/share/mailman3-web/manage.py update_index_one_list mylist@mysite.com ... very similar warnings ... Indexing 1497 emails