11 Jan
2022
11 Jan
'22
8:39 p.m.
I agree that this is a Debian packaging issue and I agree with Mark that the underlying issue is the "sed:" error message. I have only had one reply to my Debian bug report. That reply told me what I had to do make apt-get usable again (since it was stuck on the mailman3 error) but that post did not address the "sed:" bug itself and nobody else has responded to the bug report. So, it looks like I am on my own as far as my Debian mailman3 installation is concerned.
So, here is what I plan to do:
- apt-get remove mailman3 mailman3-web mailman3-full. This should not remove any configuration data or database files but I will run "apt-get --dry-run remove" first just to make sure.
- Install mailman3 using the venv and web instructions as suggested in this thread. I plan to use mysql (mariadb) since my database was originally implemented with mysql.
- I will poach as much of the configuration data as I can find from my original Debian mailman3 installation.
Thanks to everyone for your support and replys!
Gordon