On 7/12/22 6:12 AM, skooperit@gmail.com wrote:
Hi all,
I have a few contradictory questions.
1. How to upgrade the 3.x version?
2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1?
3. If so, what would be the best way to do that?
My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages:
django-mailman3 1.3.5 mailman 3.3.2 mailman-hyperkitty 1.1.0 mailman-web 0.0.3 mailmanclient 3.3.2 postorius 1.3.3
We have ~200 lists with more than a decade of history.
So you have installed Mailman 3, apparently following https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a caveat. Current released versions of HyperKitty (I don't see your version above) don't work with mistune >= 2.0.0. This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet released. If your installed mistune is not 2.0.0rc1, you can work around this with this patch ``` --- a/hyperkitty/lib/renderer.py +++ b/hyperkitty/lib/renderer.py @@ -4,7 +4,7 @@ from django.conf import settings import mistune from mistune.plugins.extra import plugin_url -from mistune.scanner import escape_html, escape_url +from mistune.util import escape_html, escape_url class MyRenderer(mistune.HTMLRenderer): ``` Or you can downgrade mistune with ``` pip install mistune==2.0.0rc1 ``` in your virtualenv. To answer your questions, to migrate your lists, you use `mailman import21` and to migrate archives, `mailman-web hyperkitty_import`. Give these commands with the `--help` option for more info. Downgrading lists from Mailman 3 to Mailman 2.1 is not currently possible. There is no inverse to `mailman import21`. You can export a HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan